0

After 2 users have connected (except myself) to the server with RemoteDesktopServices, then I can not log in until the server restarts.

error

It gives the error shown on the screenshot.

Everyone in the office can log in except me. But when the server is restarted, I can log in too.

What I already tried:

  • Task Manager: disconnect other users as admin from another account.

  • sfc /scannow on cmd as admin

  • "HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client " " Name: RDGClientTransport " -> I didn't find anything as that name

Improve this question
2
  • Are you able to connect to this RDP Server using your account from other machine when you can't connect from yours desktop?
    – mariaczi
    Commented Apr 18, 2018 at 7:59
  • @mariaczi I think I did not test what you said that now. I may have applied it on other machines at the office as far as I can remember.
    – mcnsvr
    Commented Apr 18, 2018 at 11:10

1 Answer 1

Reset to default
0

Cause

At least since Server 2008, there is a maximum of two concurrent RDP sessions allowed. If you've got the system virtualized, you can have three sessions at once: two via RDP, one via direct console login. Normally, if the other users log out completely, the slot should become available again.

This means that while you can have dozens of people who can be authorized to RDP on the machine, only two can do so at the very same time.

If you need more people on the machine on the same time, you've got what Microsoft now calls a Remote Session Host, formerly known as a terminalserver.

Solution

As soon as you need more than two people at the same time, you've got what Microsoft considers a Session Host (formerly Terminalserver), so to be able to have more concurrent users, you will need to install the session host role service on the machine.

You will also need to buy additional RDS User Cals to be properly licensed afterwards.

Reference: Technet

Improve this answer
11
  • "Normally, if the other users log out completely, the slot should become available again." -> YES but I can't you know. I need another opportunity to fix this without adding host role
    – mcnsvr
    Commented Apr 20, 2018 at 8:10
  • What exactly are you saying? You need more than two users at the same time without upgrading to session host? That's simply not possible.
    – Patrick R.
    Commented Apr 20, 2018 at 8:38
  • No I mean there must be an another way to fix this issue. The problem continues since the beginning of 2018.
    – mcnsvr
    Commented Apr 20, 2018 at 8:54
  • What else can you say me about fixing this error?
    – mcnsvr
    Commented Apr 20, 2018 at 8:55
  • What is the error for you? The message on the screenshot? That is intentional behaviour. If you need more users, then what you've got is a terminal server from microsofts point of view.
    – Patrick R.
    Commented Apr 20, 2018 at 9:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .