Logon script starting asynchronously, but GPO set to synchronous...

[JHongTurney]

Here's the problem I'm having:

In the GPO (linked, enforced), under both Computer and User config
(just to be sure) I've got the "Run Logon Scripts Synchronously"
setting set to Enabled. I'd like our logon script to finish before
launching explorer, but when anyone logs in the shell is coming up as
soon as (or sometimes even before, on the newer, faster PC's) the logon
script appears...

Any idea how to change this? I've added the reg keys I found in
postings related to Win2000 here (RunLogonScriptSync) to my test box
under HKCU and HKLM, but nothing has had the effect I'm hoping for.

Is there something different with WinXP? The server is Win2003.

Thanks!
Jason Hong-Turney

 

[Guest]

Do you have the same problem if the user logs off the network and then logs
back in?(Not from a fresh startup or reboot) I've seen the same kind of
problem with users and it causes them not to get their drive mappings b/c of
the script not running properly. But I've found that this is usually the
case when the user starts up from a shutdown or does a reboot. If they log
off the network and then log back on, the script runs fine. I'm pretty sure
it has to do with the fact that the NIC driver is one of the last things
started by WinXP, and thus Explorer and other services are already starting
up before the script has a chance to run.

 

[JHongTurney]

Logging off doesn't seem to solve the issue, unfortunately. The reg
keys I added are only, as I mentioned before, to HKCU and HKLM, but
I've had luck before adding things to the HKEY_USERS\.DEFAULT branch,
so I'll try that and post back.

Jason

 

[JHongTurney]

Logging off doesn't seem to solve the issue, unfortunately. The reg
keys I added are only, as I mentioned before, to HKCU and HKLM, but
I've had luck before adding things to the HKEY_USERS\.DEFAULT branch,
so I'll try that and post back.

Jason

No luck

 

[Guest]

I take it you tried this one

Root Key: HKEY_CURRENT_USER
Key: Software\Microsoft\Windows\CurrentVersion\Policies\System
Entry: RunStartupScriptSync
Data Type: REG_DWORD
Data : 1


If so not 100% sure what's up, but try this
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/mngwinxp.mspx
article, apparently some changes can take upto 3 logins to take effect.

Ashleigh