gpupdate /force prompts for a reboot

I'm running the command "gpupdate /force" on my login script. I get this error:

Refreshing Policy...

User Policy Refresh has completed.
Computer Policy Refresh has completed.

Certain Computer policies are enabled that can only run during startup.

OK to Reboot?. (Y/N)

I've tried hitting "yes" but I keep getting the same error.  It appears to be a rights issue because I logged in as me with network administrator rights and I did not get the error.  I did narrow it down to something in the Default Domain Policy. If I run the gpudate without the /force option it finishes and closes, but I'm not sure what the repercussions are of taking off that switch. Ideas?
StevenscsAsked:
Who is Participating?
 
uescompCommented:
if your running gpupdate /force on the server you probably will get an error message due to the features on the server that would like a reason for the restart etc, on all servers they wont let you shut down/restart until you hit restart/shutdown (select it) a second time and lets you put in notes on why you are doing so.

Otherwise there is not much of a difference, using force just basically is a backup with the restart because rebooting the pc will update the policy.
0
 
Todd GerbertIT ConsultantCommented:
That's expected behavior when using the /force switch.
You shouldn't need to run gpupdate in your login script, group policies are already being processed at computer startup and user login.
0
 
InderjeetjaggiCommented:
Users dont have rights on local computer which might be causing this issue.
Check if below article helps you

http://www.security-forums.com/viewtopic.php?t=58482

http://www.pcreview.co.uk/forums/thread-1533511.php
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

 
DonNetwork AdministratorCommented:
Go over...
 
 
 Changing the Group Policy Refresh Interval
http://technet.microsoft.com/en-us/library/cc757597(WS.10).aspx 
0
 
Todd GerbertIT ConsultantCommented:
Just to clarify...if you run "gpupdate" the group policy processing client attempts to perform optimizations and only processes what it believes has changed, the "/force" switch causes it to always re-process all policies whether they've changed or not.  Depending on what your policies are will determine if a reboot is needed, and the "/boot" switch - which is what I believe usecomp is referring to - will cause an automatic restart if gpupdate deems it necessary.
0
 
Todd GerbertIT ConsultantCommented:
In addition to background updates, computer Group Policy is always updated when the system starts.
In addition to background updates, Group Policy for users is always updated when users log on.
http://technet.microsoft.com/en-us/library/cc757597(WS.10).aspx
0
 
DonNetwork AdministratorCommented:
Didnt I just post that link?
0
 
Todd GerbertIT ConsultantCommented:
Didn't realize it was the same document...just reinforcing that gpupdate is redundant in a login script.
0
 
StevenscsAuthor Commented:
Thank a lot, you guys are great!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.