Registry not updating

23-Feb-2018 01:32

If this section does not appear, no Administrative Template Group Policy settings are applied.

If some Administrative Template Group Policy settings are applied, confirm that the specific ones of interest are applied to the client computer and user.

To account for any machine password issues since the machine is part of the domain, I have a GPO that sets the "Windows Settings Maximum machine account password age" to 365.

The idea being that every year I will rebuild these machines at least once.

Look at the listing of the Group Policy objects that are applied, and also the registry settings that these Group Policy objects contain.

Look for the following text in the output: If the Group Policy objects that you think should apply are not applied, then check the other possible causes that could lead to Group Policy objects not applying successfully.

So why would the computer configuration change work and not the user configuration in the same GPO?

Things I did to try and figure out what the issue was: I initially thought that it was a problem with the local workstation password being out of sync with the workstation password stored in AD.

Turns out the GPO only applies to IE10 and above, and we're stuck on IE9. I'm using IT_Franks' suggestion and pushing out a registry key via Group Policy.I know that when I make a policy change that affects the machine I have to unfreeze the machines and then reboot them a couple of times in order for the workstation to refresh its policies and then I freeze the machines again. What is really confusing me is that after I applied the GPO, when a user within the scope of this policy would log in to lab machine X the registry changes would be there.But when he would log in to lab machine Y the registry changes are not there.Confirm your Group Policy object configuration in Active Directory Use to check network configuration and that DNS is working and configured.Check to see that the user can successfully connect to a domain controller.

Turns out the GPO only applies to IE10 and above, and we're stuck on IE9. I'm using IT_Franks' suggestion and pushing out a registry key via Group Policy.I know that when I make a policy change that affects the machine I have to unfreeze the machines and then reboot them a couple of times in order for the workstation to refresh its policies and then I freeze the machines again. What is really confusing me is that after I applied the GPO, when a user within the scope of this policy would log in to lab machine X the registry changes would be there.But when he would log in to lab machine Y the registry changes are not there.Confirm your Group Policy object configuration in Active Directory Use to check network configuration and that DNS is working and configured.Check to see that the user can successfully connect to a domain controller.The same would go for every other user within the scope of this policy.