During a migration for a customer from an Exchange 2007 environment, to Office 365, I ran into some issues that I’d like to share, as I could not find any material on this subject elsewhere.
Our plan was easy, update the Exchange 2007 servers to the latest Servicepack and CU to allow coexistence with an Exchange 2013 server as detailed on technet. I’d then build up the Hybrid relationship on the 2013 machine, move the mailboxes and phase out the 2007 machines. The 2013 machine would remain for on-premises Lync connectivity, which needs a CAS to talk to.
Once the Exchange 2013 server was installed, I prepared the machine for Hybrid connectivity, added the relevant domains to Office 365 and started the Hybrid setup wizard from the Exchange 2013 ECP.
I received the following error:
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory
An IIS directory entry couldn't be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (EXCH2007-1\EWS (Default Web Site):ADObjectId) [Get-WebServicesVirtualDirect
ory], IISGeneralCOMException
+ FullyQualifiedErrorId : [Server=EXCH2013,RequestId=f962a8dd-2d39-4b36-85c3-a16a15fc3252,TimeStamp=9-6-201
5 07:50:59] [FailureCategory=Cmdlet-IISGeneralCOMException] 18EA544C,Microsoft.Exchange.Management.SystemConfigura
tionTasks.GetWebServicesVirtualDirectory
+ PSComputerName : exch2013.fqdn
An IIS directory entry couldn't be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (EXCH2007-2\EWS (Default Web Site):ADObjectId) [Get-WebServicesVirtualDirect
ory], IISGeneralCOMException
+ FullyQualifiedErrorId : [Server=EXCH2013,RequestId=f962a8dd-2d39-4b36-85c3-a16a15fc3252,TimeStamp=9-6-201
5 07:50:59] [FailureCategory=Cmdlet-IISGeneralCOMException] 18EA544C,Microsoft.Exchange.Management.SystemConfigura
tionTasks.GetWebServicesVirtualDirectory
+ PSComputerName : exch2013.fqdn
The hybrid wizard aborted, and could not continue.
The Get-WebServicesVirtualDirectory command checks all Exchange servers in the topology, but apparently it was unable to access the EWS instances on the two Exchange 2007 servers.
Adding the Exchange 2013 server’s computer account to both the Exchange 2007 server’s local administrator group resolved this error, and allowed the Hybrid Configuration wizard to successfully complete.
– So we need a wildcard or if SAN certificate is used it needs to contain FQDN legacy.contoso.com , correct ?
– Also not clear in the blog article. If we install an Exchange 2013 ‘hybrid’ server in Exchange 2007 environment we first need to move mailbox to Exchange 2013 server and then we can move it to Office 365 ?
– If a mailbox is still on 2007 and another user is in O365 does Free Busy work between a 2007 and O365 mailbox ?