Here is the answer I got from a contact at Microsoft.
We've had a wireless update rollup package available for some time. This will solve many authentication delays that are the result of some startup dependencies.
http://support.microsoft.c
There's also a separate fix available which you should try that solves a couple other issues we've seen with PEAP-MSCHAPv2.
http://support.microsoft.c
The second fix is what it needed. The computer account would not log on to the domain. Without the computer account authenticating to the network, it cannot go out and query AD for the log on scripts and GP. The patch allows the machine to authenticate faster, as well as the user. Now all my scripts run, all GP is up to date.
Thanks
Main Topics
Browse All Topics





by: pambooPosted on 2004-07-04 at 05:36:42ID: 11467649
when wxactly do you want to run the Logon Script?
1. System is connected to the network
2. User tries logging in