It take long time to establish a remote desktop session to Windows 2012 R2 RD Session Host

Posted on 2015-01-12
Last Modified: 2015-01-27
The problem:
It takes long time to establish a remote desktop session to Windows 2012 R2 RD Session Host Server. When connecting, it delays on blue login splash screen, saying "Welcome" , for around 30 sec before loading user profile. Once connected, it performs as normal.
RD stuck on "Welcome" login screen for 30 sec
It is a single server RD Session Host Server deployment on Windows Server 2012 R2.
The services deployed are:
- RD Connection Broker
- RD Session Host
- RD Gateway
- RD Licensing (activated, RD licenses added)
- RD Web Access
Here is the deployment overview:
RD Deployment Overview
I've exhausted all efforts, Please shed some light on this. Thanks.
Question by:mindit1
  • 5
  • 3
LVL 24

Expert Comment

ID: 40546350
Is there anything in the logs that would indicate an issue? Remember that not all issues get logged as Informational or Error events so check all the logs around the time you log into the RDS host.

Is the delay always 30 seconds? If so, you can try editing the following registry key:

Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Double click on the DelayedDesktopSwitchTimeout entry
In the Value data box, type 5
LVL 25

Expert Comment

ID: 40546579
Are you using roaming profiles?  In general using Roaming Profiles will cost around 15-20 seconds load time.  So, it doesn't take much to turn that into 30 seconds.  There is a lot that can be done to optimize and minimize that time.  Without roaming profiles, then your load time should be more like 5-10 seconds..


Author Comment

ID: 40548388
Thanks Coralon,
We are not using roaming profile.  it just stuck at "Welcome" for 30 sec before starting "Applying user settings..." Loading profile doesn't take long time after passed "Welcome" stage.
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.


Author Comment

ID: 40548394
Thanks VBITS for your suggestion.
I have changed the DelayedDesktopSwitchTimeout registry key to value 5 (was 0) with no avail.
Checked Windows event log, no error log before and after RDP login session.
One related log (level information) during the connection is: Winlogon ID 7002 - User Logoff Notification for Customer Experience Improvement Program.
What else would make the RDP connection delay on "Welcome" for 30 sec?
LVL 24

Expert Comment

ID: 40548425
Did you restart the server after you changed the registry key?

Author Comment

ID: 40549375
Sure I did.

Accepted Solution

mindit1 earned 0 total points
ID: 40554758
Thanks all for your advise. The issue has been resolved. It was due to network problem between Terminal Server VM and Domain Controller VM (Hyper-V). After disabled VMQ feature on the Hyper-V host network card, the delay is no longer present.
LVL 24

Expert Comment

ID: 40554760
Ah yes, good old VMQ at it's best. Might have been worth noting that this RDS machine was a Hyper-V Virtual Machine in your original question. We can only give you answers based on the information you give us so please ensure you provide us with the full picture if you decide to post another question on EE.

Either way, glad to see you got the issue sorted.

Author Closing Comment

ID: 40572367
After fixing the virtual network issue, found the remote desktop connection problem is fixed. So I posted the solution.

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let’s list some of the technologies that enable smooth teleworking. 
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question