Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

GPO

Status
Not open for further replies.

GrimR

IS-IT--Management
Jun 17, 2007
1,149
ZA
I have a machine that points to
\\domain.com\SysVol\domain.com\Policies
in there it list about 30 folders the usual {3E635 ETC}

Now in eventvwr it shows the userenv errors relating to one folder that is missing. So I checked it on my machine and funny enough the folder is there and there are only about 10 GPO folders.

Anyone know what is happening here.
How is it possible that the same unc path displays two different set's of folders.

Has me stumped
 
Rebooted the other AD server and it seems to have sorted it out
 
Sounds like replication was behind.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers
 
Update. [Next time I'll read more carefully]

I saw that the two server's still had the incorrect GPO's. So on the incorrect server [BDC] I had the following error:

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

To fix it I tried changing the burflags to D2 on the [BDC]corrupt server as in this article [but I did not set the D4 on the [PDC]dum@ss

Then I saw that the sysvol had disappeared but had not updated from the [PDC] so I tried running enabling Enable Journal Wrap Automatic Restore dword to 1 on the PDC, and guess what it's sysvol disappeared.

So now AD was kind of useless with no netlogon's or sysvols.

So had to go through this whole article to restore my sysvol.

Then had to recreate the Domain GPO's and add exchange back
in the GPO, and delete all previous GPO's.

And guess what due to the journal wrap error's I saw that the system state had not backed up for a while, not sure yet if this is related as it could be seems as the sysvol is part of system state.

What a headache, but all is replicating again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top