GPO replication times...

[SammyBar]

Hi all,

For how long a group policy set at the domain server takes long to become
active on a WinXP PC? Suppouse the case the XP is not reset until the end of
the working day. Should I wait for the XP PC to be reset for the
actualization to occur? Or it can be actualized even without reset?
Can I force the XP to actualize the recently created GPO object immediately?
The GPO object is assigned to a group of computers instead to an
Organizational Unit.

Thanks in advance
Sammy

 

[Jeff Rapp]

Hi Sammy,

There is a refresh period for GP computer settings. Off the top of my head I
want to say it is 20 minutes. Keep in mind that if the setting can only be
applied during a reboot (an example would be a software installation
package) then you will not see it on the remote pc until after the reboot.

You can force a GP update on a PC by typing gpupdate at a command prompt. To
see the different options for gpupdate type gpupdate /? at the command
prompt.

Hope this helps,

Jeff

 

[Guest]

The default refresh period is 90min + 30min (randomise offset) for
workstations and member servers. DC will be 5min with no offset.

To modify the above settings:
Computer Configuration\Administrative Templates\System\Group Policy\
Group Policy Refresh Interval for Computers
Group Policy Refresh Interval for Domain Controllers

Can also use GPUPDATE /FORCE on the workstation to perform a manual refresh
without rebooting.

HTH.

 

[Paul Williams [MVP]]

Bear in mind though, that not all policy is applied during background
processing. That some policy is only reapplied if the GPO has changed (GPO
version has incremented). And that XP uses a feature called fast-boot
optimisation, which might result in a second reboot being needed before all
applicable changed policies are applied.

 

[Guest]

Yeah, this is true.

User that execute the gpupdate might be force to reboot or logoff.