dresch26
asked on
Windows 2003 x32 AD to Windows 2003 R2 x64 AD
Hi
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?
Thanks,
Aaron
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?
Thanks,
Aaron
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
http://support.microsoft.com/?kbid=216498
How to remove data in Active Directory after an unsuccessful domain controller demotion
http://support.microsoft.com/?kbid=216498
ASKER
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.
Thanks,
Aaron
Thanks,
Aaron
Don't do anything destructive.
Call MS PSS and ask for private Hotfix - 919151.
See this for more detal.
http://www.msblog.org/2006/05/09/trying-to-upgrade-the-schema-using-r2-64bit-cd-on-an-existing-32bit-windows-server-2003-sp1/
Call MS PSS and ask for private Hotfix - 919151.
See this for more detal.
http://www.msblog.org/2006/05/09/trying-to-upgrade-the-schema-using-r2-64bit-cd-on-an-existing-32bit-windows-server-2003-sp1/
ASKER
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!
Aaron
Aaron
ASKER
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-5b
an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name (25f5a121-6b55-4184-821c-5
couldn't be resolved, the server name (PRIMARYDC.DOMAIN.COM) resolved to the IP address
(192.168.9.21) 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