While looking at other things in Windows 7 I noticed that the Winlogon Notification timeout has been increased from 2 minutes to 10 minutes.
This made me think about an earlier post I had on the subject of Winlogon Notifiers timing out after a 2 minute delay.
But hang on....Winlogon Notification Packages have been removed in Vista+ haven't they?
As it turns out they haven't been removed entirely, you still have Winlogon Notification subscribers registering for Winlogon Notifications under the Winlogon\Notifiers key (the GPClient and TermSrv components do this for example)....but the integration with Network Providers that existed in XP/2003 has been removed.
For example: if Group Policy processing is taking a long time you may see the following:
The winlogon notification subscriber <GPClient> took 599 second(s) to handle the notification event (StartShell).
Winlogon Notification Packageshttp://msdn.microsoft.com/en-us/library/aa380545(VS.85).aspx
Winlogon Notification Packages Removed: Impact on Windows Vista Planning and Deploymenthttp://technet.microsoft.com/en-us/library/cc721961(WS.10).aspx
Winlogon notification packages do not work after you upgrade to Windows Vistahttp://support.microsoft.com/kb/925519
Great article, this is exactly the problem I am having, and I've long suspected it was because of the Group Policy. What isn't clear, however, is how do I FIX it? We just upgraded to SSDs here in the office - my computer gets to the logon screen in 20 seconds... then hangs for 5-10 minutes trying to connect.
Standard Group Policy trial and error elimination will apply - i.e. move your workstation to a test OU that doesn't have any GPO's applying to it and then link them one by one until you locate the one that contain the problem settings (and run gpupdate /force between each reboot to make sure the GPO's are reapplied at reboot).
Userenv/GpSvc logging should help identify further which settings in the problem policy are taking a long time.