/build/static/layout/Breadcrumb_cap_w.png

Gpupdate from batch file giving me grief!

Morning chaps,

Want to pick your brains on “gpupdate /force” if you have a free moment.

On the our unattended XP SP2 build, there is a (batch) scripted OU move followed by a gpupdate /force.

This seems to have been fine for a while, but is now returning a confirmation prompt:

“Certain computer policies have are enabled that can only run during startup”
“OK to reboot?. <Y/N>”

I’m assuming that there are certain policies that cause this to crop up – eg startup scripts or suchlike.

MS tout gpupdate as a scripting tool, but the potential for the above prompt to crop up is clearly a problem in a script. I can’t find any MS docs on criteria for the prompt appearing, or a built-in way of suppressing it. Feeding “N” from a response file is also not working for me.

Any ideas?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: mcoleman210 17 years ago
Yellow Belt
0
I just ran across this today myself. "gpupdate /force /No" seems to work.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ