• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 331
  • Last Modified:

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
0
rdefino
Asked:
rdefino
  • 4
  • 3
1 Solution
 
AmitIT ArchitectCommented:
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.
0
 
rdefinoAuthor Commented:
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?
0
 
AmitIT ArchitectCommented:
RU10 is minimum required, so let it complete and then do it. There is no other work around.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
rdefinoAuthor Commented:
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.
0
 
AmitIT ArchitectCommented:
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.
0
 
rdefinoAuthor Commented:
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?
0
 
AmitIT ArchitectCommented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now