The task you are trying to do can’t be completed because remote desktop services is currently busy
Remote desktop services is really handy specially in COVID situation. It can give you liberty to complete your tasks remotely on any windows operating system. By Default windows server operating system allows two concurrent remote desktop connections to any server. If a third user like to connect the RDP services one must be disconnected or sign off. If there is no group policy applied for disconnected or time out user sessions, they will remain connected but the state will be disconnected. Those disconnected sessions can create problems like “The task you are trying to do can’t be completed because remote desktop services is currently busy”. it can happen if a user is disconnected successfully but his session is still in the middle, in this case the RDP services will give this error for that particular user.
1. This issue occurs because of a deadlock situation that occurs between the Csrss.exe process and some applications (for example, Microsoft Excel or Microsoft Visio). https://support.microsoft.com/en-sg/help/2661332/you-cannot-reestablish-a-remote-desktop-services-session-to-a-windows-server-2008-r2-based-server
2. This problem occurs because of a synchronization issue in the user profile service (profsvc) between the work thread and the main service routine. When the user profile service stops, the service might still be busy trying to clean up the profiles. https://support.microsoft.com/en-us/help/3014783/-remote-desktop-services-is-currently-busy-or-the-group-policy-client-failed-logon-error-when-you-log-on-to-an-application-in-windows-server-2008-r2?sd=rss&spid=14134
There are multiple workarounds to temporarily fix this issue without restarting the machine. These deadlocks will end with server restart but sometimes its not possible to readily restart the server in case of production environment.
Go to windows services
Find service named “Remote Desktop Services”
Restart the service
Note: it will disconnect all the RDP sessions connected at that time. The service restart process will take around 2 minutes. Retry to connect to RDP with the problematic user.
It worked for me and surely it will work for everyone.
Please feel free to leave a comment.