What Command Would You Use To Display Running Services On A Windows Os

Sometimes users cannot connect to RDS farm servers running Windows Server using the built-in RDP client (mstsc.exe) with the following error:

The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Delight endeavour again in a few minutes. Other users should still be able to log on.

RDS error The task you are trying to do can't be completed because Remote Desktop Services is currently busy

In this example, the RDS host admin tin can see a lot of stuck user sessions with the name(4) instead of usernames and Disconnected status in the Users tab of Task Director.

RDS - disconnected sessions with (4) instead of username

The problem occurs in all Windows Server versions: 2008 R2, 2012 R2, 2016 and 2019.

The error may appear on a number of reasons:

An error in the operation of the Remote Desktop Services;
A bug in the csrss.exe process;
An issue with a user profile or profsvc service;
Lack of RAM or disk space on the RDSH server;
Incorrect Group Policy settings.

Unfortunately, there is no official Microsoft solution able to solve the problem completely. All you tin exercise is to become rid of symptoms.

Almost always troubleshooting implies reset of a trouble user session or RDS server restart, but in some cases the trouble persists. Let's study the solutions starting with the easiest one.

Check RDS Server Resources

Make sure that you lot have plenty server resources since the trouble may occur due to the lack of RAM or disk space. Check the RAM load and how much free space is left on the disk with the operation arrangement installed (in that location must be at least 1GB). Likewise, view the event log to see if there are any disquisitional errors related to RDS.

If everything is OK, move on to the side by side stride.

Reset Stuck Customer Remote Desktop Session on RDS

First of all, try to detect and reset a session of the user who cannot logon to the RDS server with the error "Remote Desktop Service is currently busy". Notice a user in the Users tab of the Task Director and click Log off in the context menu. In most cases it is plenty to solve a problem, but sometimes you tin can notice multiple hung sessions with the name (4) instead of a username in the Task Manager. As a rule, there will be 4 processes in a hung RDS user session:

Client Server Runtime Process (csrss.exe)
Desktop Windows Director (dwm.exe)
Windows Logon Application (winlogon.exe)
Windows Logon User Interface

To start with, attempt to reset all hung (4) RDS sessions in the Task Manager as described to a higher place. If it doesn't help, it is better to reboot the server. Only this is often non possible, as information technology volition affect other users' sessions on RDS host. So we volition effort to solve the trouble without rebooting the host:

Run the elevated control prompt and execute the command:query session
It will prove all users and their remote sessions on the RDS host. At that place are 3 columns we need in the output: SESSIONNAME, USERNAME and ID. Find the (4) user and the corresponding ID, in this example information technology isID 2. Nosotros must to kill the csrss.exe procedure that is working in this session, simply we'll have to find it starting time;
Display the list of running process in the session ID you lot received earlier:query process /id 2
Discover the csrss.exe process (check the Epitome column) and its PID. In my instance, the PID is5140. You need to kill this process.
Check it in the Task Manager. Open up the Task Director, get to the Details tab and detect the PID and the process from the previous step. If the PID you need corresponds to the csrss.exe procedure, kill the procedure past clicking End task in the context menu or past entering the following control in the command prompt:taskkill /F /PID 5140

Do it for each (4) user if there are some of them.

Resetting an RDS User Session

If you were not able to log off a problem user in the Task Manager, you can effort to reset an RDS user session from the control prompt:

Open the control prompt as administrator and run the command:query session
Copy the SESSIONNAME of the trouble user.
Enter:reset session <SESSIONNAME> Specify the session name you take instead of <sessionname> as shown in the screenshot beneath:

Do information technology for each problem RDS user session. Then you may try to log on and a problem should not occur once again. If you can restart your server, information technology is ameliorate to do information technology.

Check Licensing Settings on your RDS Host

Brand sure that the license server and license type (CAL Per User/ CAL Per Device) specified on your RDS host are correct.

Once I got the error 'The chore you are trying to do can't be completed because Remote Desktop Services is currently busy' when afterwards the installation of the RDSH role I forgot to specify the hostname/IP address of the server with the Remote Desktop Licensing role. In that instance, two RDP users connected as usual and the third i faced this mistake.

You can specify the address of the server with RDS licenses:

Remove the RDP Connexion Limit in GPO

You can use Group Policies to limit the number of concurrent (simultaneous) RDS connections. This policy setting is disabled by default.

Make sure if the policy is enabled and get its value using gpresult.

Run the post-obit command in the elevated command prompt:gpresult /H c:\gpresult.html
Open the gpresult.html file located in the root of disk C. It is a mutual .html file and information technology is recommended to open it in the Internet Explorer since it may be displayed incorrectly in other browsers;
Find the GPO setting named Limit number of connections under Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host\Connectionsor typeLimit number of connections to search on page

If there is no such policy settings, it is not applied and there are no restrictions on the number of concurrent connections. If the policy is enabled and the maximum number of connections is set, change the value as you lot want. You tin edit a local Grouping Policy Editor (gpedit.msc), and if the policy is set using domain GPO, edit it in gpmc.msc. After you take done it, don't forget to run the commandgpupdate /force to refresh and apply the new Group Policy settings immediately.

Out-of-the-box Solutions: What to Practice If Zip Helps

If you have enough server resource, see no errors in RDP logs, resetting the user's session didn't help for some reason, and tin can't restart the RDSH host immediately, then you should try the post-obit options: