Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

The previous article introduced setting up attribute filtering, and this one starts deploying Exchange Hybrid.
After the on-premises Exchange is mixed with Exchange Online, users will have a consistent experience whether they are in the cloud or on-premises, so it is still very good.
Let's start mixing next.
First, log in to the ECP of the local Exchange, click "Hybrid", and check "My office 365 organization is hosted by 21Vianet".
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
Next, it is recommended to log in to Microsoft's official website to download the Exchange Hybrid Wizard " http://aka.ms/HCWCN ", because If we click to enable it directly, sometimes the international version of the hybrid wizard tool will be downloaded.
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
Then click the Install Hybrid Wizard tool to select
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
Office 365 China, the next step
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
is to enter the local Exchange credentials and the office 365 administrator credentials are
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
connected successfully . Mail flow to select our "Client Access Server", the next step is to select our "Mailbox Server", the next step is to select the public network certificate of the local Exchange, the next step is to enter the organization's FQDN, and the next step is to update the configuration process. Our local and cloud Exchange mail flow and user email addresses have been added and created, and the update is complete, but it prompts me that "MRS proxy settings" is not configured. Next, we need to configure MRS to log in to the local Exchange ECP, server-virtual directory, and find EWS , check "Enable MRS Proxy Endpoint" check "Basic Authentication", save
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
Next, we log in to the Exchange Management Center of Office 365, open "Mail Flow" - "Connector" - "Outbound to afd60657", edit
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
and add our domain name to it, the next step
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
is because my local Exchange is going out through the mail gateway \Receive mail, so here I add the public IP of the mail gateway to the receiver, the next step is to
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
check that it is correct, and the next step is to enter an email address to verify
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)
whether the connector can work normally . , The Exchange hybrid deployment is OK for mail flow troubleshooting . Next, we migrate the local mailbox to O365, log in to the local Exchange ECP, find the local mailbox to be migrated, click "Go to Exchange Online" and enter the mailbox administrator account, the next step Enter the FQDN of the mailbox, that is, the FQDN of the MRS. Next, enter the name of the new migration batch and the limit of error items. Next, select a mailbox to receive the migration report . The data is being synchronized, and the time varies according to the network bandwidth. Data synchronization is completed. After that, click "Complete this migration batch" and wait for a while. The migration has been completed. We can see that the user has changed the type of Office 365 mailbox. At this point, the entire mixing and migration process has been completed. In the next article, we will start deploying ADFS.
Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)


Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Exchange 2013CU17 and Office 365 Hybrid Deployment - Exchange Hybrid (4)

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325323804&siteId=291194637