Rebuild Sysvol

[FN-GM]

Has anyone here ever had to do this? I will be following this - How to rebuild the SYSVOL tree and its content in a domain

 

Does anyone who has done it before have any tips please?

 

Thanks

[srochford]

I have done it but not for some time (and I seem to remember it was just part of a disaster recover planning exercise rather than because it was needed!)

 

What's gone wrong? Is it one server that's gone out of sync or do you think that there's bits of stuff wrong on multiple DCs?

 

If it's just one server then it's probably quicker, cleaner and "nicer" to dcpromo down the faulty server, wait a bit (say 30 minutes) and then dcpromo it back up. That way you rebuild sysvol on that server and don't touch any other DC

[DMcCoy]

Has anyone here ever had to do this? I will be following this - How to rebuild the SYSVOL tree and its content in a domain

 

Does anyone who has done it before have any tips please?

 

Thanks

 

I think you really need to carefully work out what is and isn't working on every one of your DCs because something is broken and it's probably going to break again until you find the underlying cause.

 

List the DCs, if they have DNS/AD/sysvol working. Is DNS also being replicated through AD successfully?

 

It sounds as if you don't have any servers with a full set of services running at the moment which will make getting sysvol running difficult.

 

Does sites and services show the replications between servers correctly?

[FN-GM]

All DC's are suffering with something or other. One DC has had a USN roll back for some unknown reason. This happened when i demoted an old DC. Now the the server that is playing up with USN i need to demote it to fix it. The only problem is the one that is playing up is the only one that has Netlogon becuase apart of the problem with USN is it wont replicate.

[DMcCoy]

All DC's are suffering with something or other. One DC has had a USN roll back for some unknown reason. This happened when i demoted an old DC. Now the the server that is playing up with USN i need to demote it to fix it. The only problem is the one that is playing up is the only one that has Netlogon becuase apart of the problem with USN is it wont replicate.

 

A roll back is pretty serious, you haven't demoted and re-promoted a server have you? How many DCs? Any of them VMs? All time synchronised to a non VM machine?

 

How to detect and recover from a USN rollback in Windows Server 2003 lists some options for 2003 when a USN rollback occurs, there may be a 2008 version too, it's going to be quite serious stuff however you fix it. Any idea how long it's been broken and if there is a backup with a working system state?

[FN-GM]

Hi

 

 

They are all VM's i have not done snap shots or anything. There is another thread about it. The only way to sort the problem would be to demote the server that is having trouble and that is the only one with sysvol.

 

DNS and AD are fine just sysvol. The domain controller suffering from the roll back needs to be eliminated really, the other DC doesn't show the USN problem in event log

 

The other thread is here - http://www.edugeek.net/forums/windows-server-2000-2003/29209-replication-problems.html

 

Thanks

Edited January 22, 2009 by FN-GM

[FN-GM]

Just thought i would give you an update, after the rebuild everything is up and running just fine now

 

Thanks for all the input

 

Z