I tried copying sysvol from  c drive(which was less in space) to d drive on same  windows server 2003

I followed below article

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
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mr TorturSystem EngineerCommented:

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.
pramod1Author Commented:
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.
Mr TorturSystem EngineerCommented:
Ok but why ?
Demote and promote would be a clear choice, if not you are going to troubleshoot and won't know how much time you will need to spend, with less success warranty.
If you don't have another DC you could create and promote a new temporary one, even with a VM, everything could be so easy now.

1. You create a new DC2 and give it fsmo roles
2. You give enough time for both DC to communicate and replicate AD/DNS/GPO, etc..
3. You demote the existing DC1
4. you promote again DC1 as a DC specifying sysvol folder path
5. you take back the fsmo roles on DC1 and demote the temporary DC2. Done.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pramod1Author Commented:
forget it mr. tortur

I am asking I cannot do because of policy reasons and you are harping on same

thanks for help
Mr TorturSystem EngineerCommented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.