pramod1
asked on
ACTIVE DIRECTORY
I tried copying sysvol from c drive(which was less in space) to d drive on same windows server 2003
I followed below article
https://support.microsoft.com/en-us/kb/842162
I tried dcdiag /test:netlogons and getting error 1203
how should I check sysvol health also I don't see any file replicated in sysvol blank folder in D drive
I followed below article
https://support.microsoft.com/en-us/kb/842162
I tried dcdiag /test:netlogons and getting error 1203
how should I check sysvol health also I don't see any file replicated in sysvol blank folder in D drive
ASKER
I cannot demote and promote I had to do manually.
please help me here, how should I rectify this failure and steps to check sysvol health.
please help me here, how should I rectify this failure and steps to check sysvol health.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
forget it mr. tortur
I am asking I cannot do because of policy reasons and you are harping on same
thanks for help
I am asking I cannot do because of policy reasons and you are harping on same
thanks for help
Not sure to understand you completly.
I am harping? well, maybe, as I am a musician ;-)
Nevermind, do as you want and most of all as you can.
Good luck.
I am harping? well, maybe, as I am a musician ;-)
Nevermind, do as you want and most of all as you can.
Good luck.
Did you have any issues in following that MS KB article or every step went fine ?
I suppose you did the second choice of the MS KB, "Modify the registry and manually move the SYSVOL tree to a new drive."
Do you have another DC ? If yes you could try the first KB choice, demote and promote again specifying sysvol path, which seems more clean to me and will have a very good chance to succeed.
Also I never had to relocate sysvol, maybe other expert will have a more accurate advice on it.
Other comment :
Well if you don't have another DC, you should think about adding one for redundancy.
Win 2003 is oooooold and now unsupported, so very vulnerable if we speak about network security.