mindit1
asked on
It take long time to establish a remote desktop session to Windows 2012 R2 RD Session Host
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.
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:
I've exhausted all efforts, Please shed some light on this. Thanks.
Tao
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.
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:
I've exhausted all efforts, Please shed some light on this. Thanks.
Tao
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
Coralon
ASKER
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
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
ASKER
Thanks VBITS for your suggestion.
I have changed the DelayedDesktopSwitchTimeou t 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
I have changed the DelayedDesktopSwitchTimeou
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
Did you restart the server after you changed the registry key?
ASKER
Sure I did.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
Either way, glad to see you got the issue sorted.
ASKER
After fixing the virtual network issue, found the remote desktop connection problem is fixed. So I posted the solution.
Is the delay always 30 seconds? If so, you can try editing the following registry key:
Double click on the DelayedDesktopSwitchTimeou
In the Value data box, type 5