And, from personal experience in our And, to that – not one user has complained that it takes too long
to boot up, either. Wouldn’t have mattered if they had, anyway.
J -rtk From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Mar-Elia 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 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 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 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 |
- RE: [ActiveDir] Computer Configuration GP applying to W2K ... Rick Kingslan
- RE: [ActiveDir] Computer Configuration GP applying to... Crawford, Scott