shopperkerop.blogg.se - Connecting outlook 2016 to exchange 2013

#CONNECTING OUTLOOK 2016 TO EXCHANGE 2013 WINDOWS#

In Exchange 2010, the way Outlook Anywhere was implemented is that you had one namespace you could configure. When you have an Exchange 2013 or later mailbox you are using Outlook Anywhere (RPC/HTTP) or MAPI/HTTP, either within the corporate network or outside of the corporate network RPC/TCP connectivity no longer exists for Exchange 2013 and later mailboxes. If split-brain DNS is not configured, then set AutoDiscoverServiceInternalUri to a value that resolves to the internal load balanced VIP for the 2013 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 2013 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 CAS2013 infrastructure and retrieve configuration settings based on their mailbox’s location. The Autodiscover namespace,, as well as, the internal SCP records resolve to the CAS2013 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 2013 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 CAS2013 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 CAS2013 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: Note: While not explicitly called out in this blog post and graphics, Exchange 2019 behavior is the same as Exchange 2016 behavior. To that end, this article will begin with a walk through of a deployment that consists of Exchange 2013 in a multi-site architecture and show how the connectivity changes with the introduction of Exchange 2016. The connection to MicrosoftĮxchange is unavailable.Our goal with this article is to articulate the various connectivity scenarios you may encounter in your Exchange 2016 designs. Problem is when add new account in Outlook 2016, it hit an error when Logging on to the mail server with error message "The action cannot be completed. Able to resolve the hostname for the AD, Exchange 2016, Win10, .Īlready added CNAME and MX for

opening the web shows a website with ErrorCode 600 and Invalid Request which is correct.

Testing is done in private network without internet connection.Ĭheck autodiscover seems to be working.

#CONNECTING OUTLOOK 2016 TO EXCHANGE 2013 WINDOWS#

Setup as follows:Įxchange Server 2016 - installed on Windows 2012 R2Īlready configured internal & external url to points to single url: I'm testing Exchange 2016 but can't get Outlook 2016 to connect to it.