Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm trying to replace an old Windows 2000 domain controller with a new Windows 2008 Server. I have the Active Directory Domain Services role installed on the new server and joined it to the domain. The next step is to promote the new server to be a domain controller in the existing domain. After that is done I can the take old server offline.

I've already run the adprep tool with /forestprep and /domainprep. When I run dcpromo it looks like it replicates everything, creates the users, groups, and computer objects, but then I get this error:

The operation failed because:

Active Directory Domain Services is missing critical information after installation and cannot continue. If this is a replica Active Directory Domain Controller, rejoin this server to the domain.

"Directory object not found."

I have tried re-joining the computer to the domain and there's nothing helpful in the event logs. I'm at a loss for how to get past this. Any help appreciated.


My own searches found this MS Knowledge Base article:
http://support.microsoft.com/kb/248079

But it's not really helpful. As far as I can tell, all four items it's looking for are present, re-creating the domain isn't a good option, and the 2000sp1 slipstreaming advice doesn't apply to my windows 2008 box.


Checking into each of the objects from the KB article, I noticed the SID for my the Administrator account is: S-1-5-21-2025429265-492894223-1708537768-1124. Note that is does not end with "500", and therefore is somehow likely wrong. The built-in Administrator account is nowhere to be found. This is the account referenced by the 2nd bullet point item under the "Causes" heading in the linked knowledge base article. Any ideas how to fix this? I'm going to make this specific part a separate question as well, but I'll be sure to keep both up to date.


Update on what might have happened. It won't help solve the problem, but in case anyone's curious I found some old notes that help explain the problem. Apparently, once upon a time this server ran an FTP service that has since been replaced with better alternatives. At the time the service was running, the then-administrator noticed that script kiddies where trying to brute-force the administrator password via that service. Now it seems that in windows 2000 you can't disable FTP access for the Administrator account short of shutting down the service. He tried re-naming the account, but they somehow followed the rename. And so after "a nasty hack" he instead "removed" the account. I think I may have to re-create the domain somehow :(

share|improve this question
    
What is the event log telling you? I have a feeling there will be some helpful info in there. –  MDMarra Aug 22 '09 at 22:32
    
I know this is kind of obvious, but have you rejoined the server like it's asking? –  MDMarra Aug 23 '09 at 0:44
    
Yes, I have. –  Joel Coel Aug 23 '09 at 1:05
    
+1, interesting question –  Oskar Duveborn Aug 23 '09 at 15:00
    
Does everything test ok with dcdiag and netdiag ? –  JJ01 Aug 24 '09 at 4:28

4 Answers 4

You need to update the AD schema to the 2008 format. Between each version of AD (2000, 2003, 2003R2 and 2008) there have been schema changes. There's a tool called adprep on the 2008 DVD. I think first you will run adprep /domainprep and then adprep /forestprep. There is potentially a third one that's new to 2008. running adprep /? should help you.

share|improve this answer
    
You run /forestprep first. Here is the technet article detailing its use: technet.microsoft.com/en-us/library/cc731728%28WS.10%29.aspx –  MDMarra Aug 22 '09 at 23:13
    
I've already done that. –  Joel Coel Aug 23 '09 at 0:20
    
Just to be completely certain, it's been run on the/an old 2000 DC right? And was the domain upgraded from NT4 at some time or installed as 2000? –  Oskar Duveborn Aug 23 '09 at 15:03
    
Yes, I ran it on the old DC. The old DC has always been Windows 2000, never NT. –  Joel Coel Aug 24 '09 at 19:11

This is going to sound crazy but only because I did this to myself once. Check and be sure there are no firewalls or network issues. I had one network once where I accidently had the windows firewall turned on, on one of the DC's (there were 4), so because this DC wasn't replicating properly I couldn't do any AD upgrades. Though the rest of the network was working fine so there were no symptions until I tried to update the schema in my case.

Simple test, make sure each DC can ping every other DC and that all DNS is resolving properly. Also ensure the AD is in the highest that Windows 2000 can go, I'm not sure how backwards compatiable 2008 is as a DC.

share|improve this answer
    
+1 for the firewall comment. I assumed 2008 would configure its own firewall for AD, but it didn't. I couldn't do ANYTHING with the AD until I disabled the Windows Firewall alltogether. –  Mark Henderson Aug 23 '09 at 6:02
    
That was about 4 hours for me to figure out, checking all the other AD stuff thinking something was all messed up in my AD. –  SpaceManSpiff Aug 23 '09 at 6:23
    
+1 for Firewall –  dmoisan Aug 23 '09 at 20:44
    
I did check this, but it wasn't the firewall. –  Joel Coel Aug 25 '09 at 15:41

Your account's SID is NOT wrong. The only account which ends in that 500 is the built-in Administrator account which is created when the domain is built. Likewise that applies to the built-in administrator account in the local SAM of a workstation/server/* NT box.

As for your dcpromo problem, post the dcpromo.log from %SystemRoot%\Debug.

Thanks, Brian Desmond Active Directory MVP

share|improve this answer
    
Sorry, I didn't mean my administrator account: I meant the Administrator account- the built in account that is created when the domain is built. It's just not there. –  Joel Coel Aug 23 '09 at 12:43

Make sure that the domain is upgraded from mixed mode. The initial 2000 install (like the others) has a limited functionality version. You can bounce it up to full 2000 only domain. Once that is done, try the upgrade again.

If you get no joy with that, get a copy of 2003 ( your 2008 licence also downgrading ) and do the upgrade to a 2003 domain. Once again, upgrade the domain functionality level afterwards. Then try step up to the 2008 domain.

Also, leave some time after each step if/when it completes so things can replicate in the background.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.