Hello,
Thank you for posting in Q&A forum.
Regarding this issue, please refer to the official Microsoft documentation:
Best regards,
Jill Zhou
If the Answer is helpful, please click "Accept Answer" and upvote it.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
We have a Server 2019 Datacenter VM hosted on VCenter. When trying to log in using RDP or VCenter console, we encounter a "Please wait for the User Profile Service" or "Remote desktop service is currently busy" message. We don't have the RDS service installed on the server. After a reboot of the server, we can log in with the VCenter console and RDP.
Note: The server is up to date with Windows patches.
Please let us know if anyone has faced this issue and how to resolve it.
An early reply will be highly appreciated.
Hello,
Thank you for posting in Q&A forum.
Regarding this issue, please refer to the official Microsoft documentation:
Best regards,
Jill Zhou
If the Answer is helpful, please click "Accept Answer" and upvote it.
This may, or may not, help...
For the user logging on, once logged on, try deleting all files in the folder path:
%userprofile%\AppData\Local\Temp
you don't need those files [*hint, it's a 'Temp' folder]
Next, run a disk cleanup to include system files:
When that completes, the progress dialog box will just go away; there is no indication that it completed, it just does.
At this point, restart your system, and see what happens.
If you continue to have long login times, take a look at GPO's being applied.
Are there any drive mapping(s), done by the GPO, going on for the user logging on? If so, look at the GPO and see how the drive mappings are being done.
You can see your users GPO changes made by running 'gpresult /h username-gpo-yyyymmdd.html'. If the drive mappings are using FQDN (ex: \myfileserver\myfilesfolder), then see if you can get it changed to use the IP of the server instead (ex: \10.2.87.12\myfilesfolder). What this does is, it let's the GPO make the mapping without contacting a DNS server. If that solves the issue, you might want to look into the possibility that you have DNS issues.
Hope this helps someone.
Hi Charles,
Thank you for the steps. We attempted the steps you provided, but they did not resolve the issue. We have observed that we are experiencing the same problem on multiple servers. We are still working to find the right solution.
Regards
Vajram Gajengi