I have 1 XP SP2 Client that our Computer Policies do not apply to at reboot.
The user, after powering on his machine, must log on, do a GPUPDATE, log off
and then back on, in order for policy to apply. XP SP2 firewall is turned
off and policies are applying to all other machines. Any ideas?
Is the "Always wait for the network at computer startup and logon" in
CompConf\Adm Temp\System\Logon activated and applied to the computer's
OU? It forces the computer to wait for the network to be fully
initialized before letting the user log in.
cheers,
Florian
--
Nachwuschsadmin aus dem Süddeutschen/Germany.
eMail: Vorname [bei] frickelsoft [Punkt] net.
blog: http://www.frickelsoft.net/blog.
.
replication and policy problem /forward by Hover Xue [MSFT] ...Hover Xue told me to public this here! ... I have done gpupdate /force dont helpt... Have you run "gpupdate /force" to refresh ... Verify that the password policy has ... (microsoft.public.win2000.active_directory)
replication and policy problem /forward by Hover Xue [MSFT] ...Hover Xue told me to public this here! ... I have done gpupdate /force dont helpt... Have you run "gpupdate /force" to refresh ... Verify that the password policy has ... (microsoft.public.win2000.active_directory)
Restricted Group Policy not working in timely manner ... We have defined "Domain Admins" as a restricted group in the Default ...Domain Policy GPO.... A normal GPUPDATE will not do ...GPO Refresh Frequency has not been modified from default settings. ... (microsoft.public.windows.group_policy)
Re: Disable group policy on a server ... instead of you can use gpupdate or gpupdate /force in the run line. ... Sometimes a reboot is required depending on the setting the policy has changed so after gpupdate the command window displays to reboot. ... If the policy setting comes form the default domain policy or another ... (microsoft.public.windows.server.active_directory)
Re: Disable group policy on a server ... instead of you can use gpupdate or gpupdate /force in the run line. ... Sometimes a reboot is required depending on the setting the policy has changed so after gpupdate the command window displays to reboot. ... If the policy setting comes form the default domain policy or another ... (microsoft.public.windows.server.active_directory)
