?
Solved

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

Posted on 2015-01-12
9
Medium Priority
?
3,012 Views
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.
Tao
0
Comment
Question by:mindit1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
9 Comments
 
LVL 24

Expert Comment

by:VB ITS
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
0
 
LVL 25

Expert Comment

by:Coralon
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..

Coralon
0
 

Author Comment

by:mindit1
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.
Tao
0
Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

 

Author Comment

by:mindit1
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?
Cheers,
Tao
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40548425
Did you restart the server after you changed the registry key?
0
 

Author Comment

by:mindit1
ID: 40549375
Sure I did.
0
 

Accepted Solution

by:
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.
Tao
0
 
LVL 24

Expert Comment

by:VB ITS
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.
0
 

Author Closing Comment

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

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

OfficeMate Freezes on login or does not load after login credentials are input.
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
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…
Suggested Courses

771 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