GPO not applied

Hello All,

Previously I had a problem with my GPOs created on one DC and for some reason it was missing in the other DC. Upon checking and troubleshooting it, I eventually was able to resolve by performing the DFSR authoritative restore. The problem I am facing now is that the password policy GPO linked to Domain would not apply at all. I used the GPCresult /r and of course the GPO in question was not listed as applied. I also applied the GPCupdate.exe but still the GPO in question is not applied. Any ideas or suggestions on how I should proceed on trying to resolve this issue?? Any help or recommendation is greatly appreciated. I am new to GPO concept so you would have to spell it out a little bit for me to understand. Thanks!

Who is Participating?
Dan McFaddenConnect With a Mentor Systems EngineerCommented:
Have you verified that replication is fully functional?  As a start, I would run the following:

1. dcdiag /e /v
2. repadmin /replsummary

Are there errors?

Also, if you know what the file name of the GPO is, does it exist on all DCs?  Are the contents of the following location, the same on all DCs?:  C:\Windows\SYSVOL\sysvol\\Policies

Here's a decent link on troubleshooting GPO:

lotusmail1Author Commented:
Thanks for your advise. It helped a lot.

Rodney BarnhardtConnect With a Mentor Server AdministratorCommented:
If you are still having a problem, I would check the FRS logs on each DC to see if you are experiencing any event ID's 13508 or 13568. These indicate JRNL_WRAP_Errors. I had a problem with GPO's randomly not processing correctly a few weeks ago. If you do, here is how to correct it.

Perform the following on one domain controller at a time. Start with the DC that has the JRNL_WRAP_ERROR in the event viewer.
Stop the FRS service
Click on Start, Run, and type REGEDIT
Go to the following location:
"System|CurrentControlSet|Services\NtFrs\Parameters\Backup/Restore\Process at Startup"
Double click on the value name "BurFlags"
Change the value to "d2"
Restart the FRS service
The SYSVOL should be recreated and the data will gradually repopulate. Refresh the event viewer until event ID 13516 appears indicting the rebuild is complete.

Once completed, the system will reset the registry key back. However, as stated above, you have to ensure there are no other replication problems prior to doing this.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.