hasindependent.blogg.se - Activesync mail server for outlook 2016

#Activesync mail server for outlook 2016 full#
#Activesync mail server for outlook 2016 password#

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.

#Activesync mail server for outlook 2016 full#

I can't fix it until Microsoft publishes documentation or someone reverse engineers the full protocol.Our goal with this article is to articulate the various client connectivity scenarios you may encounter in your Exchange 2016 designs. If you change the protocol to something else, the error message will contain a list of all supported protocols.įor now, the executive summary is: autodiscover is broken in Outlook 2016 with anything but Office 365 (even Microsoft Exchange Server appears to have trouble in many setups - I tried two and only one worked). The best thing I currently have is 's reply to autodiscovery requests, e.g. Unfortunately though, Outlook fails to properly deal with the configuration it receives. The autodiscover.php script handles that correctly and sends ActiveSync configuration if that hasn't been disabled. If I manually create an Exchange account with the new wizard, I get the request to autodiscover.xml as in older Outlook versions, with a user agent of Microsoft Office/16.0 (Windows NT 10.0 MAPI Pro). Unfortunately though, I'm not actually able to get Outlook to properly configure the account quite yet. I've implemented the JSON protocol and will post a PR soon. The new wizard leads to a single request to with user agent OutlookMobileCloudService-Autodetect/1.0.0 - and that request is sent by some Microsoft IP address, not the Outlook client itself. I am simply unable to get to the old wizard.

Even worse, when I click the "New" button, it gives me the new wizard.

#Activesync mail server for outlook 2016 password#

The OLCFG.EXE trick suggested above doesn't work for me as it always asks for my admin password and then launches as Administrator, not the user I'm running Outlook as. I haven't had any success with Outlook 2016's autoconfiguration.