My SYSVOL is empty!!!!

[Roeee]

All,

We have (or had) two DC's in our domain, unfortuantely one DC completely died leaving the other in a semi-operational state. After much coersion we managed to get the remaining DC into a working state.

However, I have noticed that the SYSVOL folder is completely empty...not good. This came to my attention because the GPO's I have arent working.

I am going to try and restore (we only have a copy of the SYSVOL from the DC that died), however this is where you come in! WHat is the best course of action? My plan would be to perform the following.

+ Copy the sysvol from another server to a folder on faulty server
+ Rename empty sysvol and import the other sysvol back in from the restore of the server that died.

Failing that...
+ receate the Default Domain policy and Default Domain Controller Policy.

Obviously I realise there is a little more to it than that, however I would like to know if this plan will work and / or would you recommend any other steps beforehand?

Am I likely to experience any problems with an empty SYSVOL or when attempting to recreate / rebuild.

Any advice, hints, tips will be greatly appreciated.


Thanks,
Mike

 

[markdmac]

Roeee, sound like you had some big problems with AD replication on top of the other server problems.

Honestly there is no way to know if this server or the other was the cause of the trouble. I think I would suggest a complete rebuild of the doamin to ensure you have it all working properly. It would b e alot more work, but could save you a lot of time in the future.

I hope you find this post helpful.

Regards,

Mark

 

[Roeee]

Markdmac, thanks for the response.

It isnt as bad as it possibly could be, we are going to rebuild the broken DC and populate by re-replicating the AD data. Have you any idea what effect the empty sysvol may have and how to recover?

Thanks again.

 

[markdmac]

Sorry the effects are unknown to me.

I hope you find this post helpful.

Regards,

Mark