[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 656
  • Last Modified:

Windows 2008 DC can't process the Default Domain Policy

I have two domain controllers, one is running Windows 2003 (dc1) and the other is Windows 2008 R2 (dc2).  Before we attached dc2 to the domain we ran adprep on dc1.  Now for some reason dc2 is not able to process the Default Domain Policy.  The folder containing this group policy is empty.

How can I get DC2 to process the default domain policy?
0
GreyHippo
Asked:
GreyHippo
  • 2
1 Solution
 
AmitIT ArchitectCommented:
Can you post dcdiag result with /q
0
 
GreyHippoAuthor Commented:
:\Users\administrator.domain>dcdiag /q
         Warning: DC2 is not advertising as a time server.
         ......................... DC2 failed test Advertising
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:

         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:

         ......................... DC2 failed test NCSecDesc
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:11:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:16:02
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:21:03
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:26:03
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:31:04
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:36:05
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:41:05
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:46:06
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:51:06
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   13:56:07
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   14:01:07
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/20/2012   14:06:08
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\local.domain.com\sysvol\local.domain.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Poli
cy settings may not be applied until this event is resolved. This issue may be t
ransient and could be caused by one or more of the following:
         ......................... DC2 failed test SystemLog
0
 
AmitIT ArchitectCommented:
It looks sysvol is not replicated properly. Check if PDC is reachable. If so, do the nonauthoritative restore and test again, steps are below

http://support.microsoft.com/kb/290762

Above steps should fix the issue. Else last option is to remove the dc from 2008 and promote it again.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
When you did the adprep did you do both Forestprep and Domainprep /gpprep?

The commands should have been run on the FSMO holder (Forestprep = Schema Master DomainPrep /gpprep = Infrastructure Master.

What I would recommend is demoting the DC2 (2008r2) (do any cleanup if necessary) rerun the commands on DC1 again and promote the DC again.

If it is not replicating correctly make sure that Sites and Services are setup correctly. I would not restore the policy as this issue was probably from a misconfigured setting/service while promoting the DC.

Hope this helps!
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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