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).
Secondly, is the GPO you created an actual option in Group Policy Management Console (GPMC)?
When you select an OU to remotely refresh the Group Policy settings on all the computers in that OU, the following operations happen: This document describes a method to force a remote Group Policy refresh to all computers in an OU and all OUs that are contained within the selected OU by using the GPMC.
An equivalent Windows Power Shell method is also presented for each procedure.
Or you can use the Invoke-GPUpdate Windows Power Shell cmdlet to refresh Group Policy for a set of computers, including computers that are not within the OU structure—for example, if the computers are located in the default computers container.
The remote Group Policy refresh updates all Group Policy settings, including security settings that are set on a group of remote computers, by using the functionality that is added to the context menu for an OU in the Group Policy Management Console (GPMC).
I ask this because your Gpresult also says that your domain type is of Windows 2000 which probably does not have that option (I am assuming this because Win 2000 pre-dates Powershell), Activate the GPO setting "Always wait for the network at computer startup and logon" (in Computer Configuration\Policies\Administrative Templates\System\Logon).