I had two DCs in 1 domain.
DC1 = Win2000 SP4 [FMSO roles / GC]
DC2 = Win2003
DC1 used to be standalone DC, but about 4 months ago brought DC2 online (using ADMT) as a companion DC. Never gave it GC functions, just DNS, DCHP, and AD functions along with DC1 Decided we wanted to remove DC1 and convert to Novell file server. Changed DC2 to be Global Catalog and have all FSMO roles. Tried to gracefully demote DC1, but it wouldn't budge. So I did DCPROMO /FORCEREMOVAL and then the metadata cleanup.
...now I get "domain does not exist" issues and my sysvol is completely empty(!). AD info is still available from DC2, but I have to get it by doing "connect to domain controller" in AD Users & Computers, then manually entering in DC2. Logging now reveals that DC2 is being prevented from becoming full DC because of SYSVOL issue.
...now my delimma: DC1 has been totally blown away as it related to active directory (i.e., no sysvol to recover with). It hasn't even rejoined the domain because, obviously, the domain quit working once DC1 got demoted. DC2 appears to have the AD info, but Sysvol is in "struggle mode." DC2 has all appropriate FSMO roles, GC roles, and DNS/DHCP roles given and verified, so that probably isn't it. How do I make DC2 produce a SYSVOL?
...in the meantime, we've been scrounging up our tape buckups for system state info. Might not have recent DC1 System State because of recent tape issue. Any idea on how to make this happen possibly w/o system state info? SS info would be idea because DC1 is still active. Restoring SS would be a good start, but might not be possible.
...i realize there are quite a few precautions that weren't taken like always having more than 1 DC at any given time, checking File Replication event logs more closely, not just assuming I had been making system state backups, etc etc. ...I know. But those comments won't help me fix the problem, so trust me I'm very cognizant of these things.
Thanks and looking forward to EE's famously helpful answers.