Remotely running GPUpdate

Whenever troubleshooting Group Policy on a client computer, the first step is almost always connect to the computer and do a GPUpdate. Support personnel want to try this first because there are many cases where missing or incorrect GPO settings are simply the result of a timing issue, and manually issuing a GPUpdate command will resolve the situation.

This scenario means that you as the support person have to find a way to remotely connect to that user's workstation, simply for the purpose of typing this command. You could try to talk the user through it over the phone, but we all know how easy it is to spell out commands (not easy), let alone explain to the user how to get the command prompt open in the first place.

Starting with Windows 7 clients, there is a way to remotely invoke a GPUpdate command. Nice! All that is needed to do this is a PowerShell window open on your own computer.

Well, the receiving client computer also needs to allow your remote command through its firewall on the inbound. The same ports are required here as when GPMC reaches into a computer for Group Policy Results data. TCP ports 135 and 445 will need to be allowed between your computer and the endpoint computer.

As an example, I am currently logged into my LAPTOP1 workstation. A user is having trouble on LAPTOP2, and I want to try a GPUpdate as a first troubleshooting step. Without ever talking to the user or connecting to their computer, I simply open up my local PowerShell prompt and issue the following command:

Invoke-GPUpdate -Computer LAPTOP2

That's it! A command has been issued over the network to LAPTOP2, asking it to perform a background Group Policy refresh. Now I can ask the user to test again, and see if that corrected the problem.

Table of Contents for Remotely running GPUpdate

Create new playlist

Sign In

Sign Up

Table of Contents for
Remotely running GPUpdate