Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2010 on Prem to Exchange 2013 Hybrid with O365

$
0
0
I am a new Office 365 customer.  I currently have an On Premise Exchange 2010 SP3 server and a hybrid environment configured to use DirSync to sync everything from my local AD to O365.  I only have a couple mailboxes left to migrate up and I read that I could obtain a hybrid key for and install an On Premise Exchange 2013 server for no charge.  My plan was to get the 2013 server up and running and then retire the 2010 server once the last of the mailboxes have been migrated up to O365.  I have downloaded Exchange 2013 and obtained my hybrid key.  I went to a fresh new server to run the Exchange server setup and it failed with the following error:

[12/31/2014 15:05:25.0447] [0] Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information.
[12/31/2014 15:05:25.0447] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
[12/31/2014 15:05:25.0447] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
[12/31/2014 15:05:25.0556] [0] Session=Tenant Total Cmdlet Time=2.0783754s
[12/31/2014 15:05:25.0556] [0] Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetectionException: Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information. ---> System.TypeLoadException: Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.
   at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
   at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
   at System.UnitySerializationHolder.GetRealObject(StreamingContext context)
   at System.Runtime.Serialization.ObjectManager.ResolveObjectReference(ObjectHolder holder)
   at System.Runtime.Serialization.ObjectManager.DoFixups()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, IMethodCallMessage methodCallMessage)
   at Microsoft.Exchange.Data.SerializationTypeConverter.<>c__DisplayClass3.<DeserializeObject>b__0()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   at Microsoft.Exchange.Data.SerializationTypeConverter.DeserializeObject(Object sourceValue, Type destinationType)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.Deserialize(PSObject psObject)
   at Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.RemotePowershellSession.RunOneCommand[T](String command, Dictionary`2 parameters, Boolean ignoreNotFoundErrors)
   at Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.TenantHybridDetectionCmdlet.GetOrganizationConfig()
   at Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetection.RunTenantHybridTest(PSCredential psCredential, String organizationConfigHash)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetection.RunTenantHybridTest(PSCredential psCredential, String organizationConfigHash)
   at Microsoft.Exchange.Setup.GUI.HybridConfigurationStatusPage.StartHybridTest()
[12/31/2014 15:05:25.0572] [0] Finished loading screen HybridConfigurationStatusPage.
[12/31/2014 15:07:28.0914] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[12/31/2014 15:07:28.0914] [0] End of Setup


After a little searching, I found an article that said that I should run this command instead:  Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

When I ran that, I got this:  

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 MyTenantOrganizationC
onfig.XML".  Once the XML file has been generated, run setup with the TenantOrganizationConfig switch as follows "/Tenan
tOrganizationConfig 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.

When I ran this:  Get-OrganizationConfig | Export-Clixml -Path MyTenantOrganizationConfig.XML

I got this:

Get-OrganizationConfig : The term 'Get-OrganizationConfig' is not recognized as the name of a cmdlet, function, script, file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I'm not too sure where to go from here.  I'm running all of this from one of my DCs  Any assistance would be greatly appreciated.
Thanks.
-Chris

Viewing all articles
Browse latest Browse all 7129

Trending Articles