bobohost
asked on
Can't Adpret Windows 2000 DC For Windows 2008 Server
When i ran /forestprep i got the follwing error
"Adprep was unable to extend the schema.
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not updated.
[User Action]
The schema conflict must be resolved before running adprep. Resolve the schema conflict, allow the change to replicate between all replication partners, and then run Adprep. For information on resolving the conflict, see Microsoft Knowledge
Base article Q325379."
They don't have Exchange running as they host email outside with another company. Not sure if they ever had it but checked both DC's and didn't see it. I'm trying to add a new windows 2008 server as a domain controller but can't adprep the current domain. I tried going through various articles but I'm not an expert and don't be seem to be getting anywhere.
I ran DCDIAG and everything reports fine. Not sure if they had an exchange server installed at one time and got rid of it but now they are using a hosted solution. I don't see it installed on any of the Domain Controllers.
"Adprep was unable to extend the schema.
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not updated.
[User Action]
The schema conflict must be resolved before running adprep. Resolve the schema conflict, allow the change to replicate between all replication partners, and then run Adprep. For information on resolving the conflict, see Microsoft Knowledge
Base article Q325379."
They don't have Exchange running as they host email outside with another company. Not sure if they ever had it but checked both DC's and didn't see it. I'm trying to add a new windows 2008 server as a domain controller but can't adprep the current domain. I tried going through various articles but I'm not an expert and don't be seem to be getting anywhere.
I ran DCDIAG and everything reports fine. Not sure if they had an exchange server installed at one time and got rid of it but now they are using a hosted solution. I don't see it installed on any of the Domain Controllers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jason Watkins
It sounds like the schema was prepped for Exchange 2000 at some point. Perhaps prepping the schema for Exchange 2003, might get you around the errors?