Rebuilding Default Domain Policy.

  • Thread starter Thread starter George Sullivan
  • Start date Start date
G

George Sullivan

Our Domain Security Policy has become corrupt. How can I
make both my DC's think I have a blank policy and can
rebuild this blank one from scratch. I am getting the
following error when trying to start the Domain Security
Policy GUI: Failed To Open The Group Policy Object.
You may not have the appropriate rights.
Details:
The specified domain either does not exist or could
not be contacted.

Thanks to all.
 
George, I doubt your policy is corrupt. Here's why - Gpedit is trying to
reach
\\yourdomain.com\sysvol\yourdomain.com\policies\{31b....}\Machine\Microsoft\
WindowsNT\Secedit\gpttmpl.inf and cannot resolve yourdomain.com


Try troubleshooting this path one step at a time from the run line.
Remember to use your domain name and not your machine name.

Chances are
1. You do not have a DC registering the Same as Parent Folder record in DNS
2. SYSVOL is not shared on the DC

Let us know how that goes

--Shawn

This posting is provided "AS IS" with no warranties and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

domain security policy 6
Can't open domain security policy in AD when primary domain controller is turned off 7
GPO Error on Default Domain Policy 5
Security Policy Is not opening. 9
Object Access Audit Policy for a Domain 4
Default Domain Policy 5
Local Security Policy on a DC 6
Domain Controller Security Policy vs. Domain Security Policy? 1

Back
Top