Home > IT Answers > Windows Server > Group policy startup scripts
TJMann
0 pts.
 Group policy startup scripts
Active Directory, Microsoft Windows
When I add, change or delete a startup script location in Group Policy, it takes a day or more before my client machines pickup the changes. I have made other changes in the policies which seem to replicate rather quickly. I have forced replication in A/D sites and services and ran gpupdate /force /boot on the client machines. When I run the Group Policy Results Wizard on client machine, other changes appear to have taken, but the startup script modification I have made has not been set/changed yet. Any help is greatly appreciated! Thank you, TJ

Software/Hardware used:
ASKED: January 10, 2005  3:21 PM
UPDATED: May 29, 2008  10:45 AM
RELATED QUESTIONS
Answer Wiki:
Correct me if I'm wrong but the startup script should take effect when the client starts up, eg. when they reboot their system. That might explain why they pickup the changes the day after. <a href="http://itknowledgeexchange.techtarget.com/profile/Alessandro.panzetta">Alessandro Panzetta</a> You may also perform a <b>GPUPDATE /FORCE</b> command that will force the GPOs to be updated.
Last Wiki Answer Submitted:  May 29, 2008  10:44 am  by  0ct0pus   0 pts.
All Answer Wiki Contributors:  0ct0pus   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

I have rebooted the machines and refreshed the policy with the same results. It’s so strange that all other changes will take, except the startup script changes. Thanks for the help! TJ

TJMann
 0 pts.