Re: Group Policy refresh question
- From: "Brandon Baker" <brandonb@xxxxxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 10:08:50 -0500
Rebooting does do the same thing. Some policies don't require a reboot and
that is mainly what gpupdate/force is for.
"BillTheCurious" <BillTheCurious@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10D239E1-9EFF-4890-92E8-78A8C6AE664B@xxxxxxxxxxxxxxxx
> This question concerns a WinServer 2003 environment, but I didn't see a
> discussion group for Win2k3 Active Directory :-( This question is about
> the
> mechanics of Group Policy refresh.
>
> I understand Group Policy refreshes at a preset interval. I'm also pretty
> sure Group Policy will refresh when you reboot a computer.
>
> Last night I made adjustments to Group Policy. I then ran gpupdate /force
> on the workstation to apply those changes immediately. After running it,
> the
> gpupdate process required me to reboot the computer.
>
> So here's my question. Why not just reboot a computer if gpupdate is
> going
> to require you to reboot anyway??? Why bother with gpupdate /force?
>
> I see all the MS docs about the refresh interval - but that concerns PCs
> that are running and won't be rebooted. They'll get the update at the
> interval.
> If I don't want to wait, MS suggests using gpupdate, but they don't
> suggest
> rebooting as a method to immediately apply the new policy. Won't it do
> the
> same thing?
>
> Thanks in advance for your help.
.
- References:
- Group Policy refresh question
- From: BillTheCurious
- Group Policy refresh question
- Prev by Date: Re: Strong Password Group Policy not working
- Next by Date: main DC
- Previous by thread: Re: Group Policy refresh question
- Next by thread: Constant User Lockout
- Index(es):
Relevant Pages
|
