Have you ever run the Hybrid Deployment Check and received any of the following errors?
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 parameter ‘TenantOrganizationConfig’ is not valid for current operation ‘PrepareSchema’. Setup checks failed: Invalid command line arguments.
Could not load type ‘Microsoft.Exchange.Data.SubscribedPlanDetails’ from assembly ‘Microsoft.Exchange.Data, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
I’ve hit this issue a few times, let’s review the two solutions that have led to success for me.
Run the following in an administrative command prompt:
Setup.exe /PrepareAD /TenantOrganizationConfig MyTenantOrganizationConfig.xml /IAcceptExchangeServerLicenseTerms
Note In this scenario, schema extension is performed implicitly by running the /PrepareAD switch. Therefore, to complete these steps, you must have Schema Admin rights to perform the schema changes in addition to the rights that are necessary to perform the /PrepareAD steps.
If you’re running Exchange RTM upgrade to the lastest CU from the following link.
Looking for other Exchange Hybrid Deployment Check Fails and Fixes? Read about getting past a “username or password is invalid” error on our blog!
Brandon Stuart, PEI