You can specify a delay in from 0 minutes to a maximum of 44640 minutes (31 days). -RandomDelayInMinutes: this option pecifies the delay, in minutes, that Task Scheduler waits, with a random factor added to lower the network load, before running a scheduled Group Policy refresh.-Force: this forces the command to run without asking for user confirmation.In the following examples we are going to use the options below: To avoid putting a load on the network, the refresh times will be offset by a random delay. The refresh can be scheduled to immediately start a refresh of policy settings or wait for a specified period of time, up to a maximum of 31 days.
You can combine this cmdlet in a scripted fashion to schedule the Gpupdate command on a group of computers. The Invoke-GPUpdate cmdlet refreshes Group Policy settings, including security settings that are set on remote computers by scheduling the running of the Gpupdate command on a remote computer. What we are going to use is the powerful Invoke-GPUpdate cmdlet, already available on Windows Server 2012, 2012 R2 and Windows Server 2016 systems.
In this brief article we will see how to force gpupdate command on all client computer of an organizational unit by running a PowerShell command from a remote computer.
Client computers update Group Policies every 90 minutes by default, in a functional and working domain.