Link to home
Start Free TrialLog in
Avatar of Michael Retter
Michael RetterFlag for United States of America

asked on

GPO errors in Windows 2003 Domain

I have a network with 3 Windows 2003 DC's I am working on. All of the computers and servers constantly get application errors 1030 and 1058 in the event logs. When I look in the Sysvol folders on the DC's only one of them has the Policies folder. All of the DC's have the scripts folder, which update whenever a change is made from any of the DC's. I need to decommision the only DC that has the Policies folder. It is on the original version of Windows 2003 server and it doesn' t even have room to load a a service pack. Looks like this problem has been around for years. Can I just copy the Policies folder from that old DC to one of the other DC's and let it replicate to the remaining DC? I also can't run the Domain Controller Security Policy or the Domain Security Policy from any DC. I get an error "Group Policy Error" Failed to open the Group Policy Object. Details say "you may not have appropriate rights"
The network seems to work fine with the exception of these GPO errors.
ASKER CERTIFIED SOLUTION
Avatar of ArneLovius
ArneLovius
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Michael Retter

ASKER

I fixed the problem by stopping the FRS service on all of the Domain controllers except the one that actually had a policies folder in ths SYSVOL. I then edited the registry on each of the other DC's and set the BurFlag to D2 as described in Microsoft KB290762. I then started the FRS service on the other DC's one at at time and the SYSVOL folder on each of the DC's than populated with the policies folder. I can now run the Domain Controller Security Policy and the Domain Security Policy from any DC
I've requested that this question be closed as follows:

Accepted answer: 0 points for MikeRett's comment #a38848697

for the following reason:

It fixed my problem
Exactly as I described, a journal wrap error...
As the OP has posted that he resolved the problem with the fix for a journal wrap error, I would suggest 2) with points awarded to my post #a38848879