For our environment, we should select the default Office 365 Worldwide. When you click on the Office 365 Exchange Online dropdown box you’ll see an overview of all available Office 365 environments. Since Inframan has only one Exchange server it will automatically select this server. The wizard will look in Active Directory for installed Exchange servers, and it will try to detect the optimal Exchange server to configure. When the HCW wizard appears click Next to start the wizard. This will start the Hybrid Configuration Wizard that will configure the Hybrid configuration, or long term coexistence configuration between Exchange 2010 and Office 365.
#EXCHANGE 2010 TO OFFICE 365 INSTALL#
This will automatically download the new HCW from Office 365, click Install to start the new HCW. To start the new Hybrid Configuration Wizard logon to the Exchange 2010 server and go to to download and start the new HCW. In February 2016 Microsoft released a new Office 365 Hybrid Configuration Wizard (HCW) for Exchange 2010, replacing the old HCW that was initiated from the Exchange Management Console. īasically, we will create the following configuration (again, there is no Exchange 2016 server installed in the existing organization):įigure 14. But that might be an interesting topic for a future blog post. Better is to create an Exchange 2010 hybrid environment, and when the mailboxes (or most the mailboxes) are moved to Office 365 upgrade your existing Exchange 2010 environment to Exchange 2016. Despite what other people tell you, there’s no need to add a newer version, and Exchange 2010 Hybrid is fully supported by Microsoft.
Therefore, I typically recommend using only one version, so if you’re running Exchange 2010 on-premises, there’s no need to add an Exchange 2013 or Exchange 2016 server to your configuration, just as a ‘hybrid server’. However, when using multiple versions of Exchange in a Hybrid configuration there’s always add complexity, and when configured incorrectly you can get unexpected results. Hybrid configurations can consist of Exchange 2010, Exchange 2013 or Exchange 2016 or a combination of versions, so it is possible to have an Exchange 2010 and Exchange 2013 coexistence scenario on-premises, and connect this to Exchange Online. Now that Directory Synchronization is in place using Azure AD Connect we can focus on connecting the on-premises Exchange environment to Exchange Online, this a called an Exchange Hybrid Configuration.
#EXCHANGE 2010 TO OFFICE 365 HOW TO#
In this blogpost I’ll discuss how to create an Exchange 2010 hybrid environment. In my previous blogpost, I’ve discussed the prerequisites for moving from Exchange 2010 to Office 365 when using Directory Synchronization (using Azure AD Connect).
0 kommentar(er)
