startup script on winxp

[BoomStick]

Hey all,

I am running a startup script via GPO on my workstations. On my win2k
clients, the login screen does not come up until the startup script is done
executing. The XP machines will give the user a login screen before it's
finished. This is problematic with what I am doing in the startup script.

Has anyone seen this and possible have a fix.

According to the GPMC I am running, the "run logon scripts synchronously" is
enabled. I'm not sure if that effects the startup script however.

Thanks,

Jared

 

[Jerold Schulman]

On Mon, 15 Mar 2004 10:01:00 -0700, "BoomStick" <jared_luker-remove

Hey all,

I am running a startup script via GPO on my workstations. On my win2k
clients, the login screen does not come up until the startup script is done
executing. The XP machines will give the user a login screen before it's
finished. This is problematic with what I am doing in the startup script.

Has anyone seen this and possible have a fix.

According to the GPMC I am running, the "run logon scripts synchronously" is
enabled. I'm not sure if that effects the startup script however.

Thanks,

Jared

See tip 4133 in the 'Tips & Tricks' at http://www.jsiinc.com

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

 

[BoomStick]

Hmm... this seems a little bit odd, but I do not have "Always wait for the
network at comptuer startup and logon," as an option in Computer
Configuration -> Administrative Templates -> System -> Logon

I only have the following:

Run logon scripts synchronously
runstartup scritps asynchronously
run startup scripts visible
run shutdown scripts visible
maximum wait time for group policy object
delete cached copies of roaming profiles
do not detect slow network connections
slow network connection timeout for user porfiles
wait for remote user profile
prompt user when slow link is detected
timeout for dialog boxes
log users off when roaming profile fails
maximum retries to unload and update user profile
add the administrators secuirty group to roaming user profiles
do not check for user ownership of romaing profile folders
only allow local user profiles

Sorry for any typos... I typed that out pretty fast...

Any suggestions?

Jared

 

[Torgeir Bakken (MVP)]

Hmm... this seems a little bit odd, but I do not have "Always wait for the
network at comptuer startup and logon," as an option in Computer
Configuration -> Administrative Templates -> System -> Logon

Hi

If I run gpedit.msc on a Windows XP computer, I find that setting.

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?scid=kb;EN-US;305293

Scripts May Not Run Before Windows Explorer Starts Even Though
the "Run Logon Scripts Synchronously" Setting is Enabled
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304970

By registry edit; Set the value SyncForegroundPolicy to 1 (REG_DWORD) in
this key:

HKEY_LOCAL_MACHINE\Software
\Policies\Microsoft\Windows NT
\CurrentVersion\Winlogon\


With a VBScript:

Set oShell = CreateObject("WScript.Shell")
sRegValue = "HKLM\Software\Policies\Microsoft\Windows NT\" _
& "CurrentVersion\Winlogon\SyncForegroundPolicy"

oShell.RegWrite sRegValue, 1, "REG_DWORD"

MsgBox "Please reboot the computer"





--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide:
http://www.microsoft.com/technet/community/scriptcenter/default.mspx

 

[BoomStick]

Torgeir:

That reg hack did the trick... I'll just push that out via startup script so
that it behaves like it's supposed to from that point on out.

Thanks a ton for you help!

Jared

 

[Derek Melber [MVP]]

You might want to verify that you have the correct ADM templates installed
on your DCs and client computers that you are using for updating GPOs. This
setting for Waiting for the network should be there, especially if you are
trying to support XP Pro clients. The 2k ADM templates won't have all of the
correct settings, but the ADM templates from either XP or 2k3 server will.

 

[Derek Melber [MVP]]

This is the correct Registry hack for the GPO that controls whether or not
the client computer waits for the network. If you have more than one XP
client, you will want to fix your GPOs first, then set this there,
otherwise, you will have to run this on every client computer.