followkerop.blogg.se - Check connecting outlook 2016 to exchange 2013

#Check connecting outlook 2016 to exchange 2013 Offline

CAS2010 in Site1 will proxy the request to CAS2010 in Site3. CAS2010 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox is located within Site3, which does not contain any OWA ExternalURLs.

Blue User will connect to as his namespace endpoint.

CAS2010 in Site1 will authenticate the user, do a service discovery, determine that the mailbox is located within the local AD site and retrieve the necessary data from the Exchange 2010 Mailbox server.

Red User will connect to as his namespace endpoint.

Outlook Web Appįor more information, see the article Upgrading Outlook Web App to Exchange 2010.

#Check connecting outlook 2016 to exchange 2013 Offline

Note: In addition to the mail and directory connections, Outlook Anywhere clients also utilize Exchange Web Services and an Offline Address Book, url’s for which are provided via the Autodiscover response. CAS2010 in Site2 will de-encapsulate the RPC data embedded within the HTTP packet and since the target mailbox database is located within the local site, will retrieve the necessary data from the local Exchange 2010 Mailbox server. Orange User will connect to as his RPC proxy endpoint.CAS2010 in Site1 will de-encapsulate the RPC data embedded within the HTTP packet, determine that the mailbox server hosting the mailbox is located in another AD site (in this case Site3) and proxy the Outlook RPC data to the target Exchange 2010 Client Access server. Blue User will connect to as his RPC proxy endpoint.

CAS2010 in Site1 will de-encapsulate the RPC data embedded within the HTTP packet and since the target mailbox database is located within the local site, will retrieve the necessary data from the local Exchange 2010 Mailbox server. Red User will connect to as his RPC proxy endpoint.Keep in mind the importance of configuring the RPC Client Access array endpoint correctly, as documented in Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations. Internal Outlook Connectivityįor internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will connect to the Exchange 2010 RPC Client Access array endpoint (assuming one exists). If split-brain DNS is not configured, then set AutoDiscoverServiceInternalUri to a value that resolves to the load balanced VIP for the 2010 Client Access servers in your environment.įor more information on how Autodiscover requests are performed, see the whitepaper, Understanding the Exchange 2010 Autodiscover Service. Note: The recommended practice is to configure the 2010 Client Access server’s AutoDiscoverServiceInternalUri value (which is the property value you use to set the SCP record) to point to, assuming split-brain DNS is in place. Outlook clients and ActiveSync clients (on initial configuration) will submit Autodiscover requests to the CAS2010 infrastructure and retrieve configuration settings based on their mailbox’s location. The Autodiscover namespace,, as well as, the internal SCP records resolve to the CAS2010 infrastructure located in Site1. To understand the client connectivity before we instantiate Exchange 2016 into the environment, let’s look at how each protocol works for each of the three users. Similarly, the term, Non-Internet Facing AD Site, simply means any Active Directory site containing Exchange servers whose virtual directories do not have ExternalURL property populated.

Note: The term, Internet Facing AD Site, simply means any Active Directory site containing Exchange servers whose virtual directories have the ExternalURL property populated. This site contains Exchange 2010 infrastructure.

Non-Internet Facing AD Site (Site3) - This is an AD site that does not have exposure to the Internet.

The primary namespace is and resolves to the CAS2010 infrastructure located within this AD site.

Regional Internet Facing AD Site (Site2) - This is an AD site that has exposure to the Internet.

There are two namespaces associated with this location – and resolve to the CAS2010 infrastructure.

Internet Facing AD Site (Site1) - This is the main AD site in the environment and has exposure to the Internet.

Existing EnvironmentĪs you can see from the above diagram, this environment contains three Active Directory sites: To that end, this article will begin with a walk through of a deployment that consists of Exchange 2010 in a multi-site architecture and show how the connectivity changes with the introduction of Exchange 2016. Our goal with this article is to articulate the various client connectivity scenarios you may encounter in your Exchange 2016 designs.