Link to home
Create AccountLog in
Avatar of msidnam
msidnamFlag for United States of America

asked on

Upgrading to Windows 2003 AD. AD Install wizard says i need to adprep, but i already have

We are trying to upgrade our Win 2000 AD to Win 2003. We tested the upgrade in a virtual environment and eveything went pretty smooth. When we tried it tonight in our live environment during the Windows 2003 AD wizard setup I got this error:

The operation failed because:

The Active Directory Installation Wizard cannot continue because the forest is not prepared for installing Windows Server 2003. Use the Adprep command-line tool to prepare both the forest and the domain. For more information about using the Adprep, see Active Directory Help.

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

When i run adprep /forestprep and /domainprep it says that it's already been done (which i did a while ago when i installed Exchange 2003). I also checked and i dont have the mangled LDAPDisplayName attributes. the only difference that i can think of between the virutal and live environment is that i did one last windows update to make sure i had all the critical updates installed. Not sure if that would have done anything. I dont see anything in the event viewer logs.
Avatar of Ruscal
Ruscal
Flag of United States of America image

Yes, the windows update could have effected it, but it most likely didn't do so.  When running adprep, did you do so as a Domain Administrator (or Enterprise Adminstrator) or as a regular user not in the admin groups but with delegated rights?  The user who runs adprep has to have the authority to modify the LDAP schema that sits behind AD.  In fact, running adprep is one of the extreemly few occasions where I allow my clients (and myself) to breakout the actual domain Administrator account and login as it.  (Truly so, the big guy is, in my oppinion, to be reserved for the biggest of occasions and modifying the AD schema counts).

Also, have all of the DCs replicated since the adprep was successfully run.  Untill the entire directory is consistent on the schema the check at upgrade will fail (even if the local copy is correct).  And lastly (and perhaps an obvious one, but it must be asked) has the server been rebooted and adprep tried again (you'd be amazed how often that works)?
Avatar of cdbeste
cdbeste

augh...
I have seen this caused by  .NET compatability...

SOLUTION
Avatar of cheeselover73
cheeselover73
Flag of Serbia image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
ASKER CERTIFIED SOLUTION
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of msidnam

ASKER

KCTS & Cheeselover73,
thank you. That's exactly what it was. I had no idea MS would put two different version of adprep on 2 different CD's, but it doesnt surprise me :)

I was using it from Disc 1. Once i did it from Disc 2 I was able to upgrade my new W2K3 Server to a DC. Thank you both VERY much.