Slow Logoff Times - Remote Desktop 2008R2
Hey,
I've been troubleshooting this issue for a couple days now and haven't been able to get to the bottom of what is going on.
A client of mine has reported that their users have been having really slow log off times for quite a while now (we could be talking years).
- When a user logs off, it hangs at 'Please wait for the User Profile Service...'
- They have a Windows Domain with 3 2008 R2 Remote Desktop Servers setup with load balancing (all VM's).
- They have roaming profiles configured (via AD not GPO) and the average profile is around 300MB.
- The write speeds between the servers is around 50-60MB/sec, so really shouldn't take long to write the profiles back.
- IPv6 is enabled on all servers (except 1 of the 2 DC's).
- DNS has been checked over, all appears correct.
- DCDIAG has been run on both DC's and passes successfully.
- I've tested removing the roaming profile path in AD and it logs off straight away.
Event Viewer has the following warnings:
6005/Winlogon
The winlogon notification subscriber <Profiles> is taking long time to handle the notification event (Logoff).
6006/Winlogon
The winlogon notification subscriber <Profiles> took 103 second(s) to handle the notification event (Logoff).
There is another error across all 3 servers that I don't think is relevant to the issue, but here it is incase someone knows something I don't:
3100/Search
The winlogon notification subscriber <Profiles> took 103 second(s) to handle the notification event (Logoff).
I've thrown a days worth of investigating/googling into this so far and haven't made any progress; any help and advice would be greatly appreciated!
I've been troubleshooting this issue for a couple days now and haven't been able to get to the bottom of what is going on.
A client of mine has reported that their users have been having really slow log off times for quite a while now (we could be talking years).
- When a user logs off, it hangs at 'Please wait for the User Profile Service...'
- They have a Windows Domain with 3 2008 R2 Remote Desktop Servers setup with load balancing (all VM's).
- They have roaming profiles configured (via AD not GPO) and the average profile is around 300MB.
- The write speeds between the servers is around 50-60MB/sec, so really shouldn't take long to write the profiles back.
- IPv6 is enabled on all servers (except 1 of the 2 DC's).
- DNS has been checked over, all appears correct.
- DCDIAG has been run on both DC's and passes successfully.
- I've tested removing the roaming profile path in AD and it logs off straight away.
Event Viewer has the following warnings:
6005/Winlogon
The winlogon notification subscriber <Profiles> is taking long time to handle the notification event (Logoff).
6006/Winlogon
The winlogon notification subscriber <Profiles> took 103 second(s) to handle the notification event (Logoff).
There is another error across all 3 servers that I don't think is relevant to the issue, but here it is incase someone knows something I don't:
3100/Search
The winlogon notification subscriber <Profiles> took 103 second(s) to handle the notification event (Logoff).
I've thrown a days worth of investigating/googling into this so far and haven't made any progress; any help and advice would be greatly appreciated!
Last Comment
ASKER
Yeah, I've read through that one and double checked; all the servers (2 DC's + 3 TS') only have 1 NIC.
ASKER
Hmm, I'll give it a go. I haven't used this tool before...
either have I
ASKER
Any other ideas? I didn't even get to using this tool, it requires a 6GB download.
ASKER
I just tried using Group Policy to configure roaming profiles instead of AD settings and found the exact same delay (2mins 9secs for a blank profile).
No luck there unfortunately.
No luck there unfortunately.
Do you have verbose GP logging enabled?
This will write to the application log under Group Policy. This might uncover something else.
This will write to the application log under Group Policy. This might uncover something else.
Just found this hotfix that is meant to address the issue you are experiencing
https://support.microsoft.com/en-us/kb/981830
https://support.microsoft.com/en-us/kb/981830
ASKER
We tried the hotfix, but received the error: "This update is not applicable for your computer"
As a test, set the roaming profile path based on IP address instead of server name. Also, what is the response time to the roaming profile repository from the Remote Desktop server?
Is there QoS in place or any other network configuration that could be causing packet loss?
Install Network Monitor and try running a network trace.
Is there QoS in place or any other network configuration that could be causing packet loss?
Install Network Monitor and try running a network trace.
ASKER
Thanks for the reply.
We've tested using an IP instead and it didn't make any difference. We also don't have any QoS set up either.
I'm not familiar with Network Monitor - I did install and run it, but am not sure how to decipher the information from it.
We've tested using an IP instead and it didn't make any difference. We also don't have any QoS set up either.
I'm not familiar with Network Monitor - I did install and run it, but am not sure how to decipher the information from it.
you could use procmon from sysinternals
howto: http://www.howtogeek.com/school/sysinternals-pro/lesson5/all/
Download and iinstructions
or even better use the windows performance toolkit and run it on one machine (you need to get the appropriate tool for the client O/S
howto: http://www.howtogeek.com/school/sysinternals-pro/lesson5/all/
Download and iinstructions
or even better use the windows performance toolkit and run it on one machine (you need to get the appropriate tool for the client O/S
Is this happening to all users? can you create a new user, let's say test1 w/o roaming profile and have it logon and and off and see what it does. Then give it a roaming profile and notice the differences if any--keep in the mind the first time will be quite long as it copies the roaming profile to the server. also check the DNS setting on the users logging on; their local DNS settings.
What Anti-Virus app is installed on the server. I've seen packet inspection services slow all processes down. This could be your problem. You might want to try disabling the AV. If that helps, reactivate it and look into disabling packet inspection or another function of the AV app that is causing the problem.
Based on what you've written, I suspect a network issue.
First try some basic pings from the RDS to the profile repository. Try 1500-byte pings. And a tracert. Then try them from the profile server back to RDS.
In Network Monitor, you would be looking for retransmissions that would be indicative of a network-related issue.
Lastly, double check the network config on the RDS servers and profile server. I once nearly went nuts trying to figure out a similar issue, and it ended up that the issue was an incorrect default gateway config. That's just something you always *assume* is set up correctly.
First try some basic pings from the RDS to the profile repository. Try 1500-byte pings. And a tracert. Then try them from the profile server back to RDS.
In Network Monitor, you would be looking for retransmissions that would be indicative of a network-related issue.
Lastly, double check the network config on the RDS servers and profile server. I once nearly went nuts trying to figure out a similar issue, and it ended up that the issue was an incorrect default gateway config. That's just something you always *assume* is set up correctly.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
This was quite a unique issue and only by using a monitoring tool was I able to see what may've been causing this.
I am opposed to not give me any points since I recommended that you use Windows Performance Toolkit
yo_bee very indirectly you mentioned WPT only by following a link (you provided) reading and then following a link from it. I also mentioned WPT but by name and a download link
So you should object to this closure as well since you gave some direction.
Windows Server 2008
Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.
86K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
https://social.technet.microsoft.com/Forums/windowsserver/en-US/361b5901-1098-4379-b1a0-6227b447afce/please-wait-for-the-user-profile-service-message-when-logging-on-to-ts-2008?forum=winserverTS.
Seems that you have done a pretty thorough job investigating this.