I'm running into problems preparing the schema in my AD. We currently have Exchange 2010 SP3 installed onsite with our Office365 tenant space. We have been upgraded to V15 in Office365. I followed the instructions and connected via powershell to our tenant space and generated the MyTenantOrganizationConfig.XML file. Running the exhange setup with /TenantOrganizationConfig switch comes back with not supported with /PrepareSchema. Runing setup with just the /TenantOrganizationConfig doesn't work either. Both URL links below don't work, the first one just takes you to a general Exchange page. Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup Copying Files... File copy complete. Setup will now collect additional information needed for installation. 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 | E xport-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. For more information, see: http://go.microsoft.com/fwlink/?LinkId=262888 For more information, visit: http://technet.microsoft.com/library(EXCHG.150 )/ms.exch.setupreadiness.DidTenantSettingCreatedAnException.aspx The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Hi Golemb I believe you said you have Exchange 2013 CU1 On-Premises now but you want to go Hybrid O365. May I ask why you want to go Hybrid?? I always remind myself "Keep it Simple", so situations like this does not happen in the Production. If you can keep it Simple and just do Exchange 2013 On-Premises. Fred Chamanara | Advanced Agile Technology LLC | Hire us | please mark "Propose As Answer" if helpful.

Exchange Hybrid Deployment http://technet.microsoft.com/en-us/library/hh852414.aspx The bulk of my users will be in Office365 (18,000+) What Office365 offers in mailbox storage space I can't even being to offer locally. Due to business requirements I have to have about 400 mailboxes locally. Exchange 2010 SP3 is already installed working, I just need to upgrade to 2013 move mailboxes over so the look and feel is the same for onsite and in Office365.

Golemb This link will help you for your move from Exchange 2010 On-Premises to Exchange 2013 On-Premises. Planning Exchange 2013Fred Chamanara | Advanced Agile Technology LLC | Hire us | please mark "Propose As Answer" if helpful.

Hi I have the same problem. Running the command "setup /prepareSchema /TenantOrganizationConfig:c:\MyTenantOrganizationConfig.XML /IAcceptExchangeServerLicenseTerms" results in: Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup The parameter 'tenantorganizationconfig' is not valid for current operation 'PrepareSchema'. Setup checks failed: Invalid command line arguments. Couldn't find any Information about that issue. Regards Peter

PeterN22 - good that I'm not that only one that has bumpped into this problem. This morning I contacted Office365 Exchange support. The tech I was working with was going to ask around if anyone has seen this problem. But they feel that it might not be an Office365 support issue due to issue with premise Active Directory / Exchange 2013 install. I have opened a support case with my MS gold support partner, when I get a resolution I will port an update.

Hi golemb That would be great. Peter

PeterN22 This is the information I got back from Microsoft. From the Exchange 2013CU1 media run setup with /PrepareAD switch instead of /PrepareSchema Use the following syntax: Setup /PrepareAD /IAcceptExchangeServerLicenseTerms /TenantOrganizationConfig:C:\Temp\TenantOrganizationConfig.XML Adjust the path to the TenantOrganizationConfig file as need for your environment. After running this successfully on my DC I verified the schema version is now 15254. http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx

Hi golemb Thanks, that worked for me as well. Unfortunately now I have another problem, my Office 365 tenant still doesn't meet the needed AdminDisplayVersion 15.0.620.28. It seems that I still have 14.16.175.8 :( Regards Peter