This will run a GPUpdate /force on all computer objects in the OU selected and any child OUs and will refresh both the computer and user policies. This method, requires Server 2012, or Windows 8 with the remote server administration tools.The following command will retrieve the computer objects from the Servers OU and run the Invoke-GPUpdate against them.When you do, all you get is: The processing of Group Policy failed. This could be caused by one of more of the following:a) Name Resolution failure on the current domain controller.b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). To diagnose the failure, review the event log or invoke to access information about Group Policy results. To fix both issues - add the following Key to your registry:[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\RPC]"Server2003Negotiate Disable"=dword:00000001Or save that in a text file and give it a extenstion, then double click it. The Local Group Policy Editor (gpedit.msc) is a Microsoft Management Console (MMC) snap-in that provides a single user interface through which all the the Computer Configuration and User Configuration settings of Local Group Policy objects can be managed.There are times when you need to remotely refresh the group policy on a group of computers, bypassing the 90 minute ( 30 minute offset) default interval.Let’s look at 3 ways to achieve that, two of the methods require Server 2012 or Windows 8 with the remote administration tools to initiate the refresh, and the 3rd method can be initiated from Windows 7 or Server 2008 R2. Server 2012 introduced the functionality to remotely refresh Group Policy settings for all computers in an OU from the Group Policy Management Console (GPMC).
This option has no effect if there are no extensions called that require a logoff.
Some group policy client-side extensions are only processed at startup (e.g.