|
Posted by Laura E. Hunter [MVP] on June 6, 2006, 7:34 am
Please log in for more thread options
What you're seeing at work is actually the Group Policy Refresh cycle:
changes you make to GP don't take effect immediately since settings are
cached on the machine for a certain length of time: 90 minutes by default
for member servers and workstations, 2 minutes by default for domain
controllers. You can force Group Policy to refresh by rebooting the
computer or simply typing 'gpupdate /force' from the command prompt.
See the following KB for more details:
http://www.vet.upenn.edu/newsandevents/news/Barbaro.htm
HTH
--
Laura E. Hunter
Microsoft MVP: Windows Server - Networking
Responses provided as-is; no warranties expressed or implied
> Is it a bug, or as designed that when I change the policy:
>
> Default Domain Controllers/Computer/Windows Settings/Security
> Settings/Local
> Policy/Allow Log On Locally
>
> to add a group of users, that this doesn't take effect until I reboot the
> server. If I just log off and log on as a user in the group I added I
> still
> can't get access. Once rebooted I can login as this user.
>
> The environment has just one 2003 R2 SP1 server acting as domain
> controller,
> Active Directory, DNS, WINS etc.
>
> rgds
>
> -Rob
> robatwork at mail dot com
| 
XML Sitemap