"RDS is currently busy" and I can not log in to the server

0

1

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

mcnsvr

Posted 2018-04-18T07:43:43.350

Reputation: 5

Are you able to connect to this RDP Server using your account from other machine when you can't connect from yours desktop? – mariaczi – 2018-04-18T07:59:13.453

@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 – 2018-04-18T11:10:18.587

Answers

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

Patrick R.

Posted 2018-04-18T07:43:43.350

Reputation: 1 221

"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 – 2018-04-20T08:10:47.583

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. – 2018-04-20T08:38:40.160

No I mean there must be an another way to fix this issue. The problem continues since the beginning of 2018. – mcnsvr – 2018-04-20T08:54:27.203

What else can you say me about fixing this error? – mcnsvr – 2018-04-20T08:55:39.200

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. – 2018-04-20T09:29:02.243

So my best option to do not see this log on issue anymore is adding new user ?? (but you're getting a reference from technet, so you not sure ?) – mcnsvr – 2018-04-20T10:11:57.603

Dude I need a permanent solution – mcnsvr – 2018-04-20T10:12:23.997

Dude, i've already given you the answer in the very first post. I've updated it for more clarity, I don't think I can explain it any better. – Patrick R. – 2018-04-20T10:29:09.773

Ok I will check and maybe do it. Thanks for your best support on this! AND I will let you know the situation in this time. – mcnsvr – 2018-04-20T12:06:49.000

Alright, good luck to you. – Patrick R. – 2018-04-20T13:36:25.730

How did it turn out? If you haven't found a way around this, you might mark it as answered. – Patrick R. – 2018-05-16T10:40:14.697

Asked: 2018-04-18T07:43:43.350

Viewed: 3 586 times

Active: 2018-04-20T10:28:20.650