I find this rather strange. I've scoured the web looking for posts or people who are facing the above issue and there doesn't seem to be many. My organization have been plagued with this issue for months and despite a hotfix being issued by Microsoft, I still see the problem re-occurring now and then. The Story: I have a login script in my org that basically checks for the user group memberships and displays the status in an IE banner. I know for a fact that it hangs when when the script is attempting to enumerate the group memberships during debugging. Using procmon, I was also able to see lots and lots of FILE LOCK CONFLICT when wscript.exe is attempting to write the local AD schema to %userprofile%\\AppData\Local\Microsoft\Windows\SchCache\<forest_name>.sch Findings: I contacted Microsoft and they've acknowledged that this is a bug in Vista. So the boxing feature which is suppose to help has instead become a bug and is causing logon delays as long as 20 minutes. I was also told that this feature have been turned off by default in Windows 7 but will not be done for Vista. What the fix does is merely adding a check during an ADSI call to check if the local AD schema already exist and is the latest. If yes, it will continue loading the logon script. Otherwise, the delay will happen again. That means, this issue will: 1. Need to occur at least once when a user logs on for the first time. 2. Occur again if there is a change in the AD schema and the latest schema is downloaded again. Well, so far so good and my users are prepared to encounter this at least once or when a change in the AD schema occur but I have personally seen the "hang" occur during continuous logon even with the hotfix present. Anyone out there have the same issue? I would love to hear your thoughts on this. You can read about the issue here. The suppose hotfix can be found here.

Some updates: Apparently, this issue is not only affecting Vista but Windows 7 as well. Microsoft has acknowledge the issue and has produced a hotfix for this. The link can be found here In addition to that, a registry tweak is required for the Vista fix where else the Windows 7's tweak is already incorporated into the hotfix. Strange but this is what I was told. So in essence, remember to create the required key for the Vista hotfix. The key is as follow (choose to implement either one): HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System Value type: DWORD Value name: RunLogonScriptsNormally Value: 1 Hope this helps anyone out there who has the same issue that's been plaguing us for so long