Unable to expand 2013 exchange schema

Posted on 2013-06-27
Last Modified: 2013-07-24
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?
Question by:rdefino
  • 4
  • 3
LVL 42

Expert Comment

ID: 39282494
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.

Author Comment

ID: 39282518
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?
LVL 42

Expert Comment

ID: 39282521
RU10 is minimum required, so let it complete and then do it. There is no other work around.
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.


Author Comment

ID: 39282524
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.
LVL 42

Expert Comment

ID: 39282537
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.

Author Comment

ID: 39282552
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?
LVL 42

Accepted Solution

Amit earned 500 total points
ID: 39282566
Schema information is stored under DC not under Exchange server. If you have restored DC from Prod that could be one more reason for this issue. You should upgrade all server in your production domain to SP3 RU10 then use DC or xml file.

Or, you just install new dc in test lab, and then extend the schema.

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
This script can help you clean up your user profile database by comparing profiles to Active Directory users in a particular OU, and removing the profiles that don't match.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now