Windows 2003 x32 AD to Windows 2003 R2 x64 AD


 I am running two DC both running Windows 2003 32-bit.  We recently bought a new server to replace the main domain controller.  Of course the new server is Windows 2003 R2 x64.  I moved over the the catelog & FSMO to the backup DC.  I removed what was our primary Domain Controller from the Active Scheme & removed it physically from the network.  I put the replacement server in its place and added it to the AD as the same name as the old server with the same IP address.  My problem comes when trying to run DCPROMO on the windows 2003 R2 x64 server.  I get the following error:

"The version of the Active Directory schema of the source forest is not compatible with the version of Active Directory on this computer."

From what I've read about the issue it seems that I need to run the adprep.exe from the Windows 2003 R2 x64 CD2 on the exsisting DC(Windows 2003 32-bit).  It would appear the AD Scheme upgrades doesn't have as much to do with 32-bit vs. 64-bit, but with the fact that the new server is running Release 2.  I ran this adprep on the current domain controller (windows 2003 32-bit) and it gives me the following error:

"The image file .....ADPREP.EXE is vaild, but is for a machine type other than the current machine."

If I try to run this same adprep on the DC I'm trying to promote I get an error telling me it needs to be a DC first.  

Has anyone come across this issue before?


Who is Participating?
oBdAConnect With a Mentor Commented:
Interesting problem. Unless you have a x32 version of R2, you can try to just reinstall the new DC, but use the first disk *only*, do NOT continue the setup with the second disk. Then run dcpromo on the new DC (which should now be just a regular Server 2003 SP1). Once dcpromo has been finished successfully, run the adprep from the second DC, and finally continue the R2 setup from the second CD.
dresch26Author Commented:
Intresting point.  I will try that tomorrow morning.  I had to reinstall the OS directly out of the box as Dell made a 12GB OS partition leaving the other 50Gb for who knows what.  I ran the dcpromo after running the 2nd CD.  

 I ran dcdiag on the working Domain contoroller and it came up with only one error which I don't know is the overall issue or jsut a potential issue that hasn't shown it's face yet becasue it's the weekend. I think the host is the old DC that I removed.

   Testing server: DOMAIN\PRIMARYDC
      Starting test: Connectivity
         The host 25f5a121-6b55-4184-821c-5bdea4dddbd3._msdcs.DOMAIN.COM could not be resolved to
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name (25f5a121-6b55-4184-821c-5bdea4dddbd3._msdcs.DOMAIN.COM)
         couldn't be resolved, the server name (PRIMARYDC.DOMAIN.COM) resolved to the IP address
         ( and was pingable.  Check that the IP address is registered correctly with
         the DNS server.
         ......................... PRIMARYDC failed test Connectivity

Doing primary tests

   Testing server: DOMAIN\PRIMARYDC
      Skipping all tests, because server PRIMARYDC is
      not responding to directory service requests
Depends on what you mean with "removed" when you talk about the old machine. Did you run dcpromo on it to depromote it properly, or did you just shut it down and deleted the account? Seems like the latter to me. If you didn't run dcpromo, you need to do some cleanup before you can run dcpromo on the new machine.
How to remove data in Active Directory after an unsuccessful domain controller demotion
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

dresch26Author Commented:
I ran the dcpromo on the old machine to demote it.  At the time it was running DHCP & DNS.  It appeared to transfer the responsibilities over to the existing DC no prob.  I was looking at the previous issue.  It seems a rogue entry in the DC's DNS was causing the issue.  Our network is 192.168.9.x.  The previous person had put 198.x.x.x for DNS lookup, so when I took down the only good entry it didn't know what to do.  All in all, I feel pretty good about the state of AD.  I will be heading into work soon to reinstall the OS as suggested & try a DCPROMO before installing any bits from CD2.  That is a good link non the less, I found some very intresting information in there.

Don't do anything destructive.

Call MS PSS and ask for private Hotfix - 919151.

See this for more detal.
dresch26Author Commented:
You beat me to it!!  I will call them tomorrow to get the hotfix, One bit I read was that running an adprep from a Windows 2003 x64 (non R2) would do the trick, but that didn't work.  
Netman66Connect With a Mentor Commented:
The process would be to install R2 x64 from CD1 and BEFORE adding R2 to it you would DCPROMO it into the domain and move the Schema Master onto it.  Once that's done, adprep it with R2 version of adprep and install the R2 components.  You can then transfer the Schema role back to the original server if you want.

That hotfix is simply the 32bit version of adprep for R2.
dresch26Author Commented:
okay... thats it.  I've put the restored the old domain controller and removed this one for right now.  I will try that out tomorrow & POST the results.  Thank you very much for your input!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.