RDP shows black screen for first 10-15 seconds
Hello,
We have a RDS 2012 server that shows a black screen for the first 10-15 seconds(with white cursor), then continues on with "waiting on local session management" and the others texts, then logs in fine.
When logging off, also nothing happens for about 10-15 seconds, then it logs off. Same for reboot/shutdown.
Any ideas what could be the issue?
Tried with disabling all policies, creating a local user and new ad user but the issue remains. Its from all thin clients, laptops and rdp from other server.
Thanks in advance.
Patrick
We have a RDS 2012 server that shows a black screen for the first 10-15 seconds(with white cursor), then continues on with "waiting on local session management" and the others texts, then logs in fine.
When logging off, also nothing happens for about 10-15 seconds, then it logs off. Same for reboot/shutdown.
Any ideas what could be the issue?
Tried with disabling all policies, creating a local user and new ad user but the issue remains. Its from all thin clients, laptops and rdp from other server.
Thanks in advance.
Patrick
A black screen with terminal servers is unfortunately a common problem.
Can you maybe tell which hotfix rollup update you have installed.
Could you check if you see any messages in the System eventlog with a description like:
A timeout (30000 milliseconds) was reached while waiting for a transaction response...
You might also have a look at this hotfix:
https://support.microsoft.com/en-us/help/3047296/rdp-session-becomes-unresponsive-when-you-connect-to-a-windows-server
Can you maybe tell which hotfix rollup update you have installed.
Could you check if you see any messages in the System eventlog with a description like:
A timeout (30000 milliseconds) was reached while waiting for a transaction response...
You might also have a look at this hotfix:
https://support.microsoft.com/en-us/help/3047296/rdp-session-becomes-unresponsive-when-you-connect-to-a-windows-server
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Are there any network resources (mapped drives) that are set up on the machine that may not be connecting properly, have incorrect credentials, or are not always available?
If you've checked this then try enabling boot logging.
Start>Run>msconfig>boot>cl
Reboot
Then check the C:\windows\ntbtlog.txt log for any inconsistencies, drivers that can't load, etc.