Need Help Fixing Sysvol Replication
We are currently run 2 domain controllers, both 2008 R2 in our environment. Call them DC1 and DC2. Both servers are on the same lan as each other with no firewall in between.
DC1 is the pdc holding all fsmo roles. DNS currently runs on this server too.
DC2 is a domain controller and not a gc server.
AD replication works just fine. We are using DFS-R for sysvol replication. This seems to be completely broken with both servers. In troubleshooting this I seem to be getting no where fast. I found that there are a handful (maybe more) of objects missing when using adsi edit tool. Until I started looking at this recently, we did not have any system state backups scheduled. Therefore, I cannot just roll back to a previous state and initiate restores to fix this.
I would like to demote the pdc and re-promote it to fix this issue so that all objects and attributes are created properly again. My thinking is that I backup the sysvol folder on DC1, demote the server, re-promote it, restore the sysvol folder, then initiate an authoritative restore for DC1, and a non-authoritative restore for DC2. It seems the last IT guy severely broke some things while trying to do another task.
Can someone advise on this? Would the steps I mentioned be ok to perform? What all would I need to do to fix this issue? Your help is much appreciated.
DC1 is the pdc holding all fsmo roles. DNS currently runs on this server too.
DC2 is a domain controller and not a gc server.
AD replication works just fine. We are using DFS-R for sysvol replication. This seems to be completely broken with both servers. In troubleshooting this I seem to be getting no where fast. I found that there are a handful (maybe more) of objects missing when using adsi edit tool. Until I started looking at this recently, we did not have any system state backups scheduled. Therefore, I cannot just roll back to a previous state and initiate restores to fix this.
I would like to demote the pdc and re-promote it to fix this issue so that all objects and attributes are created properly again. My thinking is that I backup the sysvol folder on DC1, demote the server, re-promote it, restore the sysvol folder, then initiate an authoritative restore for DC1, and a non-authoritative restore for DC2. It seems the last IT guy severely broke some things while trying to do another task.
Can someone advise on this? Would the steps I mentioned be ok to perform? What all would I need to do to fix this issue? Your help is much appreciated.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER