Tagged: 

Viewing 2 reply threads
  • Author
    Posts
    • #19207
      Michael Pietroforte
      Keymaster
      Member Points: 35,424
      Author of the year 2018
      Rank: 4

      When I run psexec  on a Windows Server 2012 R2 machine to remotely update Group Policy on a Windows 7 and a Windows 8.1 client , the Group Policy settings don’t change on the clients. The event log indicates that a manual Group Policy update has been running. This is the output of psexec and gpupdate on the server.

      psexec \\win7 gpupdate /force
      
      PsExec v1.98 - Execute processes remotely
      Copyright (C) 2001-2010 Mark Russinovich
      Sysinternals - www.sysinternals.com
      Updating Policy...
      
      User Policy update has completed successfully.
      Computer Policy update has completed successfully.
      
      gpupdate exited on win7 with error code 0.

      If I run gpupdate locally on the clients, Group Policy updates correctly. I can also remotely update Group Policy with PowerShell and GPMC.

    • #19337
      Michael Pietroforte
      Keymaster
      Member Points: 35,424
      Author of the year 2018
      Rank: 4

      It turned out that the PsExec parameter -i is required to update user policies. Without the parameter only computer polices are refreshed. Only if the user on the source and the target computer are the same will user policies be updated without the parameter.

      This is the correct syntax:

      psexec \\ComputerName –i gpupdate
    • #19338
      Michael Pietroforte
      Keymaster
      Member Points: 35,424
      Author of the year 2018
      Rank: 4

      Also check out my new guide of how to use PsExec with gpupdate.

Viewing 2 reply threads
  • You must be logged in to reply to this topic.
© 4sysops 2006 - 2022

CONTACT US

Please ask IT administration questions in the forums. Any other messages are welcome.

Sending

Log in with your credentials

or    

Forgot your details?

Create Account