rdefino
asked on
Unable to expand 2013 exchange schema
So I have done a bare metal restore of 2 of my DC's to put into an isolated lab to test the schema expanding.
Now I was successful on expanding the schema for MS system management center, so now I need to test expanding the schema for exchange 2013.
After working on this and generating my tenant config file from my production 2007 exchange environment. I run the command that's in the screen shot and you can see the output.
Is there anyway to expand the schema without having a connection to the exchange environment?
Capture.PNG
Now I was successful on expanding the schema for MS system management center, so now I need to test expanding the schema for exchange 2013.
After working on this and generating my tenant config file from my production 2007 exchange environment. I run the command that's in the screen shot and you can see the output.
Is there anyway to expand the schema without having a connection to the exchange environment?
Capture.PNG
You should upgrade your Exchange 2007 to SP3 RU10 that is the minimum requirement with Exchange 2013 and then again export the file and rerun the schema upgrade setup.
ASKER
we are in the middle of upgrading to RU10. Is there any way I can still create the file on an exchange server that is running RU10 and expand the schema in my lab?
RU10 is minimum required, so let it complete and then do it. There is no other work around.
ASKER
Well some server have it and some don't yet. Can I create the config file on the server with RU10?
It will be weeks before all the servers are upgraded.
It will be weeks before all the servers are upgraded.
If you want to coexist with Exchange 2013, all 2007 need to be upgraded to SP3 RU10 and Exchange 2010 to SP3 bare minimum.
As you are creating file where few servers are still not upgraded to RU10, same information that xml file contains, and during 2013 schema update, it checks the xml file and find still few servers are not at RU10 and stops.
Only option left is not to use xml file and do a normal schema upgrade, However, i don't think that will solve your purpose.
As you are creating file where few servers are still not upgraded to RU10, same information that xml file contains, and during 2013 schema update, it checks the xml file and find still few servers are not at RU10 and stops.
Only option left is not to use xml file and do a normal schema upgrade, However, i don't think that will solve your purpose.
ASKER
This schema update is being done in a lab, so there are no exchange servers, just the restored DC.
How can I do the schema update without the config file?
How can I do the schema update without the config file?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.