Q: How can I enforce the application of machine Group Policy Object (GPO) settings on a Windows client? Are there any differences here between Windows 2000 and Windows Server 2008?

A: On a computer running Windows 7, Windows Server 2008 (and R2), Windows Vista, Windows Server 2003, or Windows XP, you can enforce the application of machine GPO settings by typing the following command (make sure that you're doing this in the security context of an administrator account and that you replace <computer_name> with the correct machine name):

gpupdate /target:<computer_name> /force

On a computer running Windows 2000, you must use the following secedit command to achieve the same thing:

secedit /refreshpolicy machine_policy

Discuss this Article 2

gpoguy
on Feb 23, 2011
The syntax above for gpupdate is incorrect. It implies you can use it to refresh a remote system, but you cannot. The /target parameter takes either "computer" or "user" to tell the command that you want to update that "side" of GPO on the local machine.
gpoguy
on Feb 23, 2011
The syntax above for gpupdate is incorrect. It implies you can use it to refresh a remote system, but you cannot. The /target parameter takes either "computer" or "user" to tell the command that you want to update that "side" of GPO on the local machine.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.