This policy setting is disabled by default. We can use Group Policies to limit the number of concurrent (simultaneous) RDS connections. In GPO: Use the specified Remote Desktop license servers (Computer Configuration -> Policies -> Admin Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing).In the RDS collection settings: Tasks -> Edit Deployment Properties -> RD Licensing -> Specify a license server. ![]() ![]() We can specify the address of the server with RDS licenses: The error ‘The task we are trying to do can’t be completed because Remote Desktop Services is currently busy’ can occur when we forget to specify the hostname/IP address of the server with the Remote Desktop Licensing role. Make sure that the license server and license type (CAL Per User/ CAL Per Device) specified on the RDS host are correct. Then we may try to log on and a problem should not occur again. Specify the session name we have instead of. If we were not able to log off a problem user in the Task Manager, we can try to reset an RDS user session from the command prompt:įirst, open the command prompt as administrator and run the command: query sessionĬopy the SESSIONNAME of the problem user. If the PID we need corresponds to the csrss.exe process, kill the process by clicking End task in the context menu or by entering the following command in the command prompt: taskkill /F /PID 5140ĭo it for each (4) user if there are some of them. Now, open the Task Manager, go to the Details tab and find the PID and the process from the previous step. Now, display the list of the running process in the session ID we received earlier: C:\>query process /id 2įind the csrss.exe process (check the IMAGE column) and its PID. We must kill the csrss.exe process that is working in this session. There are 3 columns we need in the output: SESSIONNAME, USERNAME and ID.įind the (4) user and the corresponding ID, in this example, it is ID 2. It will show all users and their remote sessions on the RDS host. SESSIONNAME USERNAME ID STATE TYPE DEVICE So let us try to solve the problem without rebooting the host.įirst, run the elevated command prompt and execute the command: C:\>query session If it does not help, it is better to reboot the server.īut this is often not possible, as it will affect other users’ sessions on the RDS host. To start with, try to reset all hung (4) RDS sessions in the Task Manager.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |