Your network contains an Active Directory domain named contoso.com. All domain controllers run Windows
Server 2012 R2.
An organizational unit (OU) named OU1 contains 200 client computers that run Windows 8 Enterprise. A Group
Policy object (GPO) named GPO1 is linked to OU1.
You make a change to GPO1.
You need to force all of the computers in OU1 to refresh their Group Policy settings immediately. The solution
must minimize administrative effort.
Which tool should you use?

A.
The Secedit command

B.
The Invoke-GpUpdate cmdlet

C.
Group Policy Object Editor

D.
Server Manager

E.
The Set-AdComputer cmdlet.

Explanation:
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. You can
combine this cmdlet in a scripted fashion to schedule the Gpupdate command on a group of computers.
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. To avoid putting a load on the network, the refresh times will be offset by a
random delay.
Note:
In the previous versions of Windows, this was accomplished by having the user run GPUpdate.exe on their
computer.
Starting with Windows Server 2012 and Windows 8, you can now remotely refresh Group Policy settings for all
computers in an OU from one central location through the Group Policy Management Console (GPMC). Or you
can use the Invoke-GPUpdate cmdlet to refresh Group Policy for a set of computers, not limited to the OU
structure.

http://technet.microsoft.com/en-us//library/jj134201.aspx
http://blogs.technet.com/b/grouppolicy/archive/2012/11/27/group-policy-in-windows-server-2012-using-remotegpupdate.aspx