Yes, this is expected because Fast Logon Optimization is
enabled, which essentially says don't wait for the network before presenting the
logon screen. This screws with certain policy. Try enabling the following policy
on those XP machines:
Computer Configuration\Administrative
Templates\System\Logon\Always wait for the network at computer startup and
logon
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brenda Casey
Sent: Tuesday, May 10, 2005 6:57 PM
To: [email protected]
Subject: RE: [ActiveDir] Computer Configuration GP applying to W2K but not WinXP
The computer configuration policy will apply after
several reboots and a gpupdate /force (but not just a gpupdate). I didn't
think that it should take several reboots to apply this policy. Thanks for
your help.
Thanks,
Brenda
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Mar-Elia
Sent: Tuesday, May 10, 2005 10:25 AM
To: [email protected]
Subject: RE: [ActiveDir] Computer Configuration GP applying to W2K but not WinXP
Brenda-
Is Fast Logon Optimization enabled (on by
default) on the XP machines? Does the situation change after the 2nd or 3rd
reboot (i.e. the computer policy is finally delivered on XP)?
From: [EMAIL PROTECTED] on behalf of Brenda Casey
Sent: Tue 5/10/2005 9:14 AM
To: [email protected]
Subject: [ActiveDir] Computer Configuration GP applying to W2K but not WinXP
I have applied a startup script (to change a local admin
password) to the computer configuration in a GP. I have also
configured several user configuration items in this policy.
This policy applies successfully to all W2K workstations, but only the User
Configurations are applied on a WinXP workstation. Any thoughts on what I
am missing? Any and all help is appreciated!
Thanks,
Brenda
