As you can see, here is a Windows 7 PC after gpupdate: This means it is being applied.

Well, it was the exact same way when I made the GPO and it did not do those two until a few days passed... My domain controller is a Windows Server 2012 R2 and the clients being tested are Windows 7 SP1 Configuracion De Equipo implies it is a computer policy (please correct my if I'm misinterpreting this).

This command supersedes the now obsolete /refreshpolicy option for the secedit command.

So what’s the difference between GPUpdate and GPUpdate /force? In fact, running GPUPdate /force on a large number of computers can be damaging to your career.

This is because these machines will hit a domain controller and reevaluate every GPO applicable to them.

Sometimes I could run GPUpdate, other times I had to run /force.

As it turned out, Group Policy was always working – I just didn’t understand it. If you just edited a GPO and want to see results immediately, running gpupdate will do the trick.

gpresult /r on the client does show that it recieves it and it is being applied but it does not do it: This is for network shares, scripts, automatic software installation, etc.

I also shutdown and restart the PC but still nothing.

This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller.

b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).