server 2008 r2 | group policy

I have an environment that consists of two sites.

When i run a group policy modelling wizards on a domain controller on each site, i get different results.

We are having issues with a GPO not applying in one of the sites

If i use the GPMC and attach to the domain controller in the site, the required gpo is there?
Who is Participating?
MaheshConnect With a Mentor ArchitectCommented:
Have you checked DFSR propagation test from dfs management snap in on DCs
U need to install DFS management tools from server manager under features for that

If above is not successful, you can do DFSR non-authoritative restore as per article in my earlier comment
Jian An LimSolutions ArchitectCommented:
do you have a site level GPO?
You probably have a problem with replication between your domain controllers. Use repadmin to check the replication health status of your domain controllers. I think repadmin gets installed with the RSAT AD tools. It should also be on the domain controllers. It is a command line utility.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

navigate to \\DC\sysvol\polices path on both DCs and see if both DCs are showing same number of GPO folders

If there is variation, check file replication services event log for event ID 13568, it might be journal  wrap issues

you could run non-authoritative restore of sysvol on DC where GPO count is not appropriate OR DC where you find 13568 event OR on ADC so that it rebuild sysvol from PDC server
Follow below article
Rodney BarnhardtServer AdministratorCommented:
I would look for the following errors in the event viewer:  Journal wrap, JRNL_WRAP_ERROR, 13508, 13568

If they exist on one DC, but not the other, do the following on the DC with the errors:
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.

The reg key entry will change itself back once the rebuild is complete.

If the error is on both servers, then you will need to do a restore. The problem will be locating and ensuring you have a backup prior to the problem.
Have you run dcdiag /v /e > c:\dcdiag.txt to chech the health of AD?

repadmin /showrepl >c:\readmin.txt to check replicaton..

Also check the GPT amd GPC version numbers... The follow link has more details on this for you.
cmatchettAuthor Commented:
in my dcdiag, i am getting

The processing of Group Policy failed. Windows attempted to read the file \\path\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. 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).

c) The Distributed File System (DFS) client has been disabled.

Question, i have tried to link a new gpo and it also isn't applying.

When i do rsop query on the local computer, it shows the gpos that i want to apply in the list.

Is it because of the above?
MaheshConnect With a Mentor ArchitectCommented:
Try Authoritative FRS restore as stated in earlier comment:

1 stop file replication service on all DCs
2 On PDC server, Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
In the right pane, double click BurFlags.
In the Edit DWORD Value dialog box, type D4 and then click OK.
3 Start file replication service
4 Ensure that event id 13516 is populated in file replication service event logs
5 open command prompt and enter Net Share, It should show sysvol and netlogon  shares

6 Then logon to other DCs one by one and modify the same registry above with value of D2
7 start the file replication service
8 Check for event id 13516 in file replication service event
9 open command prompt and enter Net Share, It should show sysvol and netlogon shares

Now check if you are able to create new GPO and it get replicated to other DC as well.
cmatchettAuthor Commented:
we are using windows 2008 r2 so the FRS doesn't come into play?
MaheshConnect With a Mentor ArchitectCommented:
So you mean to say that you are running on DFSR Sysvol?

Is File replication Services (NTFRS) is disabled on all your domain controllers?
If not still you are running on FRS Sysvol
Its not mandatory that when you have 2008 R2 DCs, you are on DFSR Sysvol, it depends upon how your domain constructed
If you are upgrading AD from 2003 to 2008 R2 \ 2012, then Sysvol will run through FRS only
If you are creating new 2008 R2 domain with 2003 as domain   functional level, still your sysvol remains on FRS
If you created domain on 2008 R2 with 2008 as domain functional level, then your sysvol will remain on DFSR
U can migrate FRS sysvol to DFSR after you have raised domain functional level to 2008

Check which scenario is applicable in your case

If you have DFSR Sysvol, follow below article to have DFSR Sysvol authoritative restore
cmatchettAuthor Commented:
This domain was created with the domain functional level of 2008 r2

I have checked the sysvol on all of the domain controllers, the GPO exists on all domain controllers.  The versions are all the same.

I have also checked the permissions on the sysvol share.
MaheshConnect With a Mentor ArchitectCommented:
Check if you have any orphaned GPOs, if found remove them
Use below PowerShell script
cmatchettAuthor Commented:
would orphaned GPOs stop other GPOs from applying?
MaheshConnect With a Mentor ArchitectCommented:
sometimes you might face issues due to orphaned GPOs
cmatchettAuthor Commented:
sorry for only coming back to this now...

restarting the domain controller fixed my modelling issue.

A group policy with loopback processing enabled was always causing issues
All Courses

From novice to tech pro — start learning today.