SBS 2003 has domain issues after hard drive issue

A tech on my team failed one drive in a mirror, and removed it from an SBS 2003 server.

Subsequently, NTFRS errors have been showing up in the logs, and many troubling AD issues have arisen.  Most troubling is that the SBS server will refuse to allow login because it cannot reach the domain, and the SYSVOL share is missing entirely.

There is another DC that replicates through a static VPN.  Is it possible to demote and re-promote an SBS server without causing problems?  

irvconAsked:
Who is Participating?
 
tgtranConnect With a Mentor Commented:
Sorry for not getting back to you - I was testing the procedures against my lab environment.  Somehow, MS changed the way Win2003 manipulates  junction points.  Xcopy works fine with junction points on Win2000.  I tried with Robocopy and xxcopy....  Anyway, here is the KB you may want to try:
http://support.microsoft.com/?kbid=315457

** Please post your result - I have not tried this KB out and like to know how it worked out for you
0
 
tgtranCommented:
Your best bet is to perform authoritative restore on SBS server if you have good reliable and recent backup.
If not, you can try to restore SYSVOL from the remote DC, using the steps in this link:
http://technet2.microsoft.com/windowsserver/en/library/21280b7f-9f14-4ff9-8c0d-ec0e555522f01033.mspx?mfr=true

You really don't want to take the demote/promote route.  SBS server holds all FSMO roles along with Exchange, any changes to this will give you grief more than you can imagine.
0
 
irvconAuthor Commented:
Thanks tgtran, -I'll follow up and check in tomorrow.  I figured that demoting an SBS server would make my life hell, thanks for the confirmation.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
irvconAuthor Commented:
So we tried rebuilding the SYSVOL using the the instructions above, and it was all going well up until i checked the copy of the SYSVOL folder from the other DC and it had lost the JUNCTION links in the copy process.  I tried copying locally on that machine using xcopy and windows copy, as well as copying over the network like it's recommended in the article and it lost the JUNCTION link every time.

I also tried to re-create the JUNCTION links once the directory structure was back on the DC that we're repairing, and it wouldn't let me delete the original link or re-create it.  I ended up bringing the server back up in serious limp mode as it's been running the last few days - defaulting to the remote DC for authentication purposes.

Any ideas as to why the JUNCTION links disappeared, or why i wasn't able to re-create them?
0
 
irvconAuthor Commented:
The last KB article posted by tgtran solved our issues with that SBS.  What i did was copy all the SYSVOL files out of the DC that was still up and running, take down the VPN between the two DCs so that they couldn't try to restore off each other, and setup the bad DC to perform an authoritative SYSVOL restore using the files i had copied from the other DC.

It took about 2-3 minutes after a reboot out of Directory Services Restore Mode, but there it was, my SYSVOL and NETLOGON shares were present in all their glory!

Thanks a million ;)
0
 
irvconAuthor Commented:
he last KB article posted by tgtran solved our issues with that SBS. What i did was copy all the SYSVOL files out of the DC that was still up and running, take down the VPN between the two DCs so that they couldn't try to restore off each other, and setup the bad DC to perform an authoritative SYSVOL restore using the files i had copied from the other DC.

It took about 2-3 minutes after a reboot out of Directory Services Restore Mode, but there it was, my SYSVOL and NETLOGON shares were present in all their glory!

Thanks a million ;)
0
All Courses

From novice to tech pro — start learning today.