• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 123
  • Last Modified:

Group Policy issues with WSUS policy

Environment is two server 2012 r2 servers and both are DCs.  DC1 holds FSMO.

There are about 30 GPOs in the servers and they all execute just fine.

A few days ago, I spun up a new WSUS server and it came up without a hitch.

I added the GPO to computer config, under admin templates pointing to the server.

Once applied to the domain, I get this error:

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          1/26/2015 1:38:40 PM
Event ID:      1058
Task Category: None
Level:         Error
Keywords:     
User:          domain\journtest
Computer:      BULLDOG2-04.domain.org
Description:
The processing of Group Policy failed. Windows attempted to read the file \\child.domain.org\SysVol\child.domain.org\Policies\{F4B11368-1AF5-424B-92C3-BBEA8185A13E}\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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
    <EventID>1058</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>1</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-01-26T19:38:40.559367700Z" />
    <EventRecordID>12993</EventRecordID>
    <Correlation ActivityID="{0165360B-81DF-43DA-90DA-FDC0154E969B}" />
    <Execution ProcessID="1240" ThreadID="5712" />
    <Channel>System</Channel>
    <Computer>BULLDOG2-04.child.domain.org</Computer>
    <Security UserID="S-1-5-21-3532712855-2137286508-2029475586-3010" />
  </System>
  <EventData>
    <Data Name="SupportInfo1">4</Data>
    <Data Name="SupportInfo2">816</Data>
    <Data Name="ProcessingMode">0</Data>
    <Data Name="ProcessingTimeInMilliseconds">562</Data>
    <Data Name="ErrorCode">3</Data>
    <Data Name="ErrorDescription">The system cannot find the path specified. </Data>
    <Data Name="DCName">DC2.child.domain.org</Data>
    <Data Name="GPOCNName">cn={F4B11368-1AF5-424B-92C3-BBEA8185A13E},cn=policies,cn=system,DC=sisd,DC=domain,DC=org</Data>
    <Data Name="FilePath">\\child.domain.org\SysVol\child.domain.org\Policies\{F4B11368-1AF5-424B-92C3-BBEA8185A13E}\gpt.ini</Data>
  </EventData>
</Event>

Note that DC2 is referenced.

So, I looked in the systole folder for both DCs and I do NOT see the new GPO in DC2.  So, I'm thinking the PC is authenticating against DC2 and since the policy is not there, it's not executing.

I also noted that in the policies folder on DC1, I have 37 policies.  In the policies folder on DC2, I have 74.  Clearly, something is amiss.

Replication is working.  I can create users and they replicate right away.

Testing replication with repadmin and the GUI returns 100% success, no errors.  Still, clearly there is a REASON the policies folders are disparate and a reason the GP is not showing up in DC2 policy folder.

So, thoughts on where to start and how to fix issue?

Thanks

Cliff
0
crp0499
Asked:
crp0499
  • 7
  • 4
1 Solution
 
rgormanCommented:
What does dcdiag show on DC2 and one of the properly functioning DC's?
0
 
crp0499Author Commented:
Both report 100% passed on dcdiag
0
 
crp0499Author Commented:
My most recent policy in DC2 is dated 10/7/2013!
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Donald StewartNetwork AdministratorCommented:
Sounds like you are having a journal wrap issue.

http://support.microsoft.com/kb/290762 - Try using the BurFlags registry key to reinitialize File Replication Service replica sets
0
 
crp0499Author Commented:
This is 2012 R2 and the article is for 2003 and 2000.

BUT

I considered the same thing.  Since both DCs are VMs, I considered demoting DC2 and going to just one DC and then bringing up another.
0
 
Donald StewartNetwork AdministratorCommented:
0
 
crp0499Author Commented:
ok, so I followed that to the letter and after I set DFSR back to TRUE, and run the two commands, I never see the two events in the log indicating replication and of course, my systole folders do not update.
0
 
crp0499Author Commented:
ok, finally, what I found was another event from 12/24/14 that replication had stopped and needed to use wmi to get it going again.  I cleared up those errors and then the above worked as expected.

So, I'm back to clean logs and my policy folder on DC2 is empty, waiting for the initial sync.

Is there some way to get that to happen sooner or should I just wait?
0
 
Donald StewartNetwork AdministratorCommented:
0
 
crp0499Author Commented:
finding more and more info.  now see error in log, event id 4012 telling me that my sysvol folder has been out of sync too long and now I must remove it from the DFS replication group and then add it back.

it looks like my replication hasn't been happening for a while and now I have issues.  I'm thinking demote and promote again.
0
 
crp0499Author Commented:
Authoritative was required since the data in the errant DC was older than the stale period.  

The authoritative restore fixed it all.
0
 
Donald StewartNetwork AdministratorCommented:
Glad to help
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now