none
How to run gpupdate /force on remote computer?

    Question

  • How to run gpupdate /force on remote computer?

    (Without psexec)


    Thanks Biswajit
    Friday, July 30, 2010 4:39 AM

Answers

All replies

  • Howdie!
     
    On 30.07.2010 06:39, Biswajit Biswas wrote:
    > How to run gpupdate /force on remote computer?
    >
    > (Without psexec)
     
    You log on remotely? You can't actually. GPupdate /force shouldn't be
    run remotely on a regular basis. Why would you have to? If you're
    clients need that in order to get Group Policy correctly, there's
    something wrong. If you need Group Policy to be applied more quickly,
    fiddle with the corresponding GP setting that dictates the refresh times
    on clients.
     
    Cheers,
    Florian
     

    Microsoft MVP - Group Policy (http://www.frickelsoft.net/blog)
    • Proposed as answer by Mike Kline Friday, July 30, 2010 6:16 AM
    Friday, July 30, 2010 5:36 AM
  • WinRM gives you funcitonality equivalent to WinRM.

    Alternatively, use any of the options listed at http://www.windowsecurity.com/articles/How-Force-Remote-Group-Policy-Processing.html

    hth
    Marcin

     

    Friday, July 30, 2010 11:17 AM
  • Invoke-Command -Computer -remotepC {

    gpupdate /force

    }

    This works in windows 7/vista/2008

     


    Thanks, Sitaram http://techibee.com http://sitaram-pamarthi.com
    • Proposed as answer by MattMJF99 Tuesday, September 18, 2012 6:43 PM
    Friday, July 30, 2010 11:30 AM
  • Take a look at these links..

    http://www.windowsecurity.com/articles/How-Force-Remote-Group-Policy-Processing.html

    How to refresh the Group Policy Settings on remote computers- http://support.microsoft.com/kb/556027/en-us

     


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, July 30, 2010 1:36 PM
  • There is an option in GPMC but OS is 2012

    Best regards Biswajit Biswas Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin

    Thursday, December 20, 2012 2:24 PM
  • Please give clearly-quaified answers. You did NOT say if this is "vbscript," "powershell," or what? And you never gave any idea of how to run it. Also, I think there is an additional parameter "/silent" or "/nologoff" or "/noreboot" - can't recall the exact parameter.


    tnjman

    Okay, looks like Powershell - and it there is no "dash" on the "remotePC" - it is just the string name of the remotePC; like this:

    Poweshell

    PS> Invoke-Command -ComputerName the-remote-pc-name {

    gpupdate /force

    }

    OR, you can use the "icm" (abbreviated command equivalent of "invoke-command"), like this:

    PS> icm -ComputerName the-remote-pc-name { gpupdate /force }

    All on one line, and it works perfectly. Thanks, and cheers!


    • Edited by TNJMAN Wednesday, March 27, 2013 4:36 PM
    Wednesday, March 27, 2013 4:21 PM
  • When answering questions, please don't give unqualfiied answers like "can't do this." It is easy to do, and it is done all the time.

    This is something that is done, and is needed, quite often; for security and other reasons.

    In a case where I had 4,000 remote workstations, it was not practical for me to log in to all 4,000 and do something interactively; nor was it practical to fiddle with group policy refresh settings. In that case, I successfully used "psexec" with the "gpupdate /force," without any issues.

    Often, changes may be needed for, let's say, 1,000 workstations out of 4,000; so it might not be appropriate to tweak the overeall policy; and yes, I know you can organize them into OUs, with different group policy settings - but again, 'security,' among other things, comes into play here. Often, we need to push a gpupdate very quickly, to a certain group of workstaitions (or servers) and we don't need, nor desire, to tweak our standardized group policies.


    tnjman

    Wednesday, March 27, 2013 4:28 PM
  • To remotely GPUpdate, I actually prefer to use the SPECOPs GPUpdate tools (free edition). You can select an OU or just computers and remotely run a gpupdate (or gpupdate /force).

    It actually runs a PowerShell script to remotely update but ties into Active Directory Users and Computers.

    You can read about remote gpupdate here: http://deployhappiness.com/gpupdate-or-gpupdate-force/

    A link for the tool is here: http://deployhappiness.com/resources/tool-downloads/


    If my answer helped you, check out my blog (and subscribe): DeployHappiness.com


    Wednesday, March 27, 2013 4:39 PM
  • My boss just chastised me for installing SpecOPs on one of our DC's because it installed JAVA and he says that is a security issue. I can't find any documentation on that and have used SpecOps for years at different companies. Is this a valid concern?

    I really need a Powershell solution that will make him "Happy".
    Monday, March 17, 2014 3:07 PM
  • Do you want to refresh group policy on one client machine or many?

    If just one, you could use the Powershell cmdlet proposed above:

    Invoke-Command -ComputerName the-remote-pc-name { gpupdate /force }

    WinRM is also an option for just one machine.

    I believe this assumes Windows 7 and above.

    If you have many computers, you might try to use a variable to "feed" the result of the Get-ADComputer cmdlet to the Invoke-Command cmdlet. If we wanted to refresh GP on all the computers in the "REMOND" OU, we could try something like this:

    -

    $computers = Get-ADComputer -Filter * -SearchBase "OU=REDMOND,DC=CONTOSO,DC=COM"

    Invoke-Command -ComputerName $computers { gpupdate /force }

    -

    Just an example, just a "rough draft". I'm not 100% sure that works - I cannot test it right now - but something along those lines *may* be a possible solution.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.



    Monday, March 17, 2014 4:24 PM