Exchange 2013 TenantOrganizationConfig Office 365 switch 1

So, you’re migrating to Exchange 2013 Hybrid and are currently using Exchange 2010 Hybrid. Then you’ll probably run against this error mentioning the TenantOrganizationConfig when running the schema prep:

setup /PrepareSchema /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for

Performing Microsoft Exchange Server Prerequisite Check

Prerequisite Analysis                                     FAILED

A hybrid deployment with Office 365 has been detected.  Please ensure that you are running setup with the /TenantOrganizationConfig switch.  To use the TenantOrganizationConfig switch you must first connect to your Exchange Online tenant via PowerShell and execute the following command: "Get-OrganizationConfig | Export-Clixml -Path MyTenantOrganizationConfig.XML".  Once the XML file has been generated, run setup with the TenantOrganizationConfig switch as follows "/TenantOrganizationConfig MyTenantOrganizationConfig.XML".

If you continue to see this this message then it indicates that either the XML file specified is corrupt, or you are attempting to upgrade your on-premises Exchange installation to a build that isn't compatible with the Exchange version of your Office 365 tenant. Your Office 365 tenant must be upgraded to a compatible version of Exchange before upgrading your on-premises Exchange installation. The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.

Exchange 2013 in hybrid mode can only be used by the new version of the Office 365 Exchange Online version (15.0.670.14 or higher). Before you can prepare the AD schema, there is a build-in check to verify your Exchange Online version. This also means that if you’re currently in Exchange 2010 Hybrid mode and still on the old Exchange Online version, you will not be able to install Exchange 2013, contact Microsoft if that is the case. To perform the check you must export your Office 365 Organization config to an XML file and use this when starting your schema prep.

Steps for TenantOrganizationConfig

  1. Connect to your Office 365 tenant using powershell and start the following command to export your Online Organization Configuration:
    Get-OrganizationConfig | Export-Clixml -Path C:MyTenantOrganizationConfig.XMLThis XML file will include all the Organization information, including the AdminDisplayVersion.
  2. Start your schema prep again, now using the TenantOrganizationConfig switch:
    setup /prepareSchema /TenantOrganizationConfig:C:MyTenantOrganizationConfig.XML /IAcceptExchangeServerLicenseTerms

    If you receive an error stating “The parameter ‘tenantorganizationconfig’ is not valid for current operation ‘PrepareSchema’.”, use the following command:

    Setup /PrepareAD /TenantOrganizationConfig:C:MyTenantOrganizationConfig.XML /IAcceptExchangeServerLicenseTerms

Hans Sleurink

Hans Sleurink works as a Consultant at Wortell in the Netherlands where he designs and deploys Unified Communications solutions. His main focus is on, but not limited to, Microsoft Teams (migrations), including Enterprise Voice, contact center solutions, AudioCodes, Direct Routing, Exchange, Office 365, Active Directory and other UC related topics.

More Posts - Website

Follow Me:

One comment on “Exchange 2013 TenantOrganizationConfig Office 365 switch

  1. Reply Chad Jun 25,2013 18:19

    This helped me out a great deal. Thank you very much.

Leave a Reply




This site uses Akismet to reduce spam. Learn how your comment data is processed.