Exchange server 2016 global address list not updating
In addition, a hybrid deployment can serve as an intermediate step to moving completely to an Exchange Online organization.Contents Exchange hybrid deployment features Exchange hybrid deployment considerations Exchange hybrid deployment components Exchange hybrid deployment example Things to consider before configuring an Exchange hybrid deployment Key terminology Exchange hybrid deployment documentation Take a look at the following scenario.Build your server and install a supported OS (either Server 2012 Standard or Datacenter or Server 2012 R2 Standard or Datacenter). Once installed, join to your domain and install windows updates.Once you've gone through the preparation steps above, it's now time to install Exchange.Now that you're a little more familiar with what a hybrid deployment is, you need to carefully consider some important issues.
In this lab, we have a single Exchange server called litex01 in the domain which is running Exchange 2013 CU10. We’ll install an Exchange 2016 server called litex02.
However, users will authenticate with your on-premises Active Directory via AD FS as their primary method of authentication.
In the event AD FS can't connect to your on-premises Active Directory for any reason, clients will attempt to fall back and authenticate against usernames and passwords synchronized to Office 365.
The recommendation from Microsoft for Exchange 2013 was to install multi-role servers but with Exchange 2016, the CAS and MBX roles have been merged so installing multi-role servers is no longer possible.
For the first Exchange server in the organization, the user that performing the install must be a member of the Enterprise Admins and Schema Admins group in AD and a member of the local admins group on the server you are installing Exchange on.