200mgMemberAug 26, 2014 at 4:00 pm #164170
We have several 2K8R2 Terminal/RDS servers located at several different locations throughout North America. Somewhat recently, some of these servers will hang on login at various stages of adding group policies, ie “Applying Group Policy Printers” or “Applying Folder Redirection”.
The event viewer application log file shows multiple instances of:Quote:Event ID: 6005 Source: Microsoft-Windows-WinLogon
Message: The winlogon notification subscriber
is taking long time to handle the notification event (Logon)
What’s odd is, this issue affects servers randomly. Each site has at least 2 TS servers. All of them are the same hardware (Dell T410’s and T420’s) and same level of Windows updates. The TS servers are “synced up” for lack of a better phrase. This issue may affect one of the two servers at one location, none of the servers at another location, or both servers at another location.
I cannot find anything in event viewer that preceeds the Event 6005 that is causing the Event 6005 to happen. The only change I have made thus far is adding the below netsh configuration to one of the servers. I am still waiting to see the outcome of this change.Quote:netsh interface tcp set global autotuninglevel=disabled
Has anyone else run into this Event 6005 issue? Many of my google searches point to a long or invalid script or possibly a printers GPO that cause this, I think I can rule those out in this case. I’ve also read where Item level targeting in GPO’s can cause issues, and some of the GPO’s here do have alot of item-level targeting in them.
Just thought I’d ask you guys if you have ever seen anything like this before.
You must be logged in to reply to this topic.