Author Topic: Outlook 2016 Autodiscover  (Read 8664 times)

JohnnyS

  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Outlook 2016 Autodiscover
« on: December 08, 2015, 01:11:22 pm »
Hello everyone,

I have a problem using Outlook 2016 using the Exchange account setup (non Activesync). Outlook 2013 seems to be able to Autodiscover for Exchange email, but when I tried Outlook 2016, it doesn't find the Autodiscover correctly and now there is no method to manually set up this type of account in Outlook 2016 (Microsoft took it away in 2016). When I use the Exchange Analyzer online it also say my Autodiscover is not working. Is my Apache config pointed at the wrong place? I'm am using the latest Zentyal 4.2. I have ActiveSync installed and working on iPhone and Outlook 2016 can find Exchange Activesync Autodiscover settings (although with large email accounts it tends to fail, but that's a post for another thread) if that info helps. Thanks so much!

trysomething

  • Zen Warrior
  • ***
  • Posts: 119
  • Karma: +5/-0
  • Founder of The Tiki Lab
    • View Profile
    • The Tiki Lab | Bridging the gap between technology and vision impairment!
Re: Outlook 2016 Autodiscover
« Reply #1 on: December 09, 2015, 08:04:56 pm »
The quick, easy fix for this works like:
1.  If you're not using a trusted 3rd party ssl certificate download (from Zentyal Webmin Mail>Openchange>Download Cert) and install it as a "Trusted Root CA", DO NOT AUTOMATICALLY INSTALL IT B/C THAT DOESN"T WORK, pick the TRUSTED ROOT CONTAINER!!!!!
2.  Wherever your external DNS is being handled it's likely they didn't create a DNS record for it so create a subdomain "Autodiscover.yourdomain.com" - please pay close attention to "Autodiscover" and not "autodiscover" because if it's not cap it don't work.
3.  Point that subdomain "Autodiscover.yourdomain.com" at "https://yourdomain.com:443/autodiscover/autodiscover.xml"
NO, that's not a typo, it's the file "autodiscover.xml" inside the directory "autodiscover" and yes, they are both lower case, the caps part only counts in the sub domain.

Once everything is all propagated through the DNS you should have a properly working and fully functional autodiscover.
You may need to tweak things, like obviously changing "yourdomain.com" to whatever the actual domain is.  In addition I have some instances where Zentyal is solely an email server and the web server resides on a completely different IP/Subnet/etc. in which case the HTTP redirect for the subdomain points back to the FQDN "https://hostname.yourdomain.com:443/autodiscover/autodiscover.xml" since the actual domain name points to a completely different server.
If you're not using trusted 3rd party SSL certificates and you have not installed the root certificate from Zentyal Mail>Openchange as a trusted root certificate then you will NEVER, ever, never be able to connect vial autodiscover in Outlook.  It doesn't matter what you do, or how you tweak something unless you're inside the LAN you will not be able to connect.
To the dumb a** that's going to try and be smart popping off with VPN, why on God's Green Earth would you even consider having that much overhead for people to be able to send/receive email when they can just install the cert?  No, VPN is not the solution to that problem and no, VPN is not a very good idea for so many other reasons.
Anyways this should get you of the ground and working with 2016 and for the record it's still there it's just hidden better for the manual config side of things.  They're just trying to scare everyone into going Exchange since they killed SBS hundreds and maybe thousands have migrated to Zentyal, ClearOS and Netserver as alternatives.  Basically MS knocked themselves out of cornering the market LoL.
You will have to excuse my posts not having actual links in them.  I'm blind and can never find that insert hyperlink button LoL.  If you, or someone you know has vision problems check out The Tiki Lab.

klinutzu

  • Zen Monk
  • **
  • Posts: 77
  • Karma: +0/-2
    • View Profile
Re: Outlook 2016 Autodiscover
« Reply #2 on: December 19, 2015, 08:32:03 am »
hello and sorry for my noob questions: where is autodiscover.xml? tried to find it, but no luck... and another one: how to do

Point that subdomain "Autodiscover.yourdomain.com" at "https://yourdomain.com:443/autodiscover/autodiscover.xml"

sorry again for my dumb questions. regards, calin

Number12

  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: Outlook 2016 Autodiscover
« Reply #3 on: December 23, 2015, 08:13:08 am »
I have been playing with the autodiscover on and off all day today but cannot get outlook to respond to it. Viewing the page in the browser gives me the correct "error 600" to indicate that the request had no payload but running the configuration test built in to outlook results in no configuration being found and an "error 500" but with no other useful information.

I have also followed the instructions here (and below) to manually setup the server but am having difficulties with the LegacyDN and ServerDN settings. This results in the account being created successfully but outlook failing to load and populate the .ost file. I presume this is from incorrect authentication but haven't got much further with it since. Keen to know if other people have better results.

Quote
Connecting to Exchange using local AutoDiscover

You can create an AutoDiscover XML file to connect to your Exchange account when AutoDiscover is not available.

There are three steps:
  • Create an AutoDiscover XML file.
  • Save the AutoDiscover XML file somewhere on your computer, such as your Documents folder.
  • Associate the AutoDiscover XML file with your mailbox.

1. Create an AutoDiscover XML file

1.1 Connect WITHOUT Outlook Anywhere (RPC/HTTP)
If you are NOT using OutlookAnywhere to connect, the AutoDiscover XML file should look like the following, where highlighted attributes are customized for your connection environment:
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
        <User>
            <AutoDiscoverSMTPAddress>xxSMTP_ADDRESSxx</AutoDiscoverSMTPAddress>
            <LegacyDN>xxUSER_LEGACYDNxx</LegacyDN>
        </User>
        <Account>
            <AccountType>email</AccountType>
            <Action>settings</Action>
            <Protocol>
                <Type>EXCH</Type>
                <Server>xxSERVER_NAMExx</Server>
                <ServerDN>xxSERVER_DNxx</ServerDN>
                 <AuthPackage>xxRPC_AUTH_PACKAGExx</AuthPackage>
            </Protocol>
        </Account>
    </Response>
</Autodiscover>

1.2 Connect with Outlook Anywhere (RPC/HTTP)
If you are using OutlookAnywhere to connect, the AutoDiscover XML file should look like the following, where highlighted attributes are customized for your connection environment:
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
        <User>
            <AutoDiscoverSMTPAddress>xxSMTP_ADDRESSxx</AutoDiscoverSMTPAddress>
            <LegacyDN>xxUSER_LEGACYDNxx</LegacyDN>
        </User>
        <Account>
            <AccountType>email</AccountType>
            <Action>settings</Action>
            <Protocol>
                <Type>EXCH</Type>
                <Server>xxSERVER_NAMExx</Server>
                <ServerDN>xxSERVER_DNxx</ServerDN>
                <AuthPackage>xxRPC_AUTH_PACKAGExx</AuthPackage>
            </Protocol>
            <Protocol>
                <Type>EXPR</Type>
                <Server>xxOUTLOOK_ANYWHERE_SERVERxx</Server>
                <SSL>On</SSL>
                <AuthPackage>xxHTTP_AUTH_PACKAGExx</AuthPackage>
                <ServerExclusiveConnect>on</ServerExclusiveConnect>
                <CertPrincipalName>xxCERTIFICATE_PRINCIPAL_NAMExx</CertPrincipalName>
                <ServerExclusiveConnect>off</ServerExclusiveConnect>
            </Protocol>
        </Account>
    </Response>
</Autodiscover>

1.3 The USER_LEGACYDN value
You must obtain the value for xxUSER_LEGACYDNxx from your Exchange administrator.

1.4 Values under the EXCH protocol
The value xxSERVER_NAMExx is what you would have put in the “Server” field in the Outlook 2013 manual configuration dialog:

The value xxSERVER_DNxx must be obtained by your Exchange administrator.
The value of xxRPC_AUTH_PACKAGExx is what you would have chosen in the “Logon network security” field for Outlook 2013 Manual Configuration, and is most likely “Negotiate”:

Other acceptable Auth values are listed here: https://msdn.microsoft.com/en-us/library/ee178834(v=EXCHG.80).aspx

1.5 Values under the EXPR protocol
The values xxOUTLOOK_ANYWHERE_SERVERxx, xxCERTIFICATE_PRINCIPAL_NAMExx, and xxHTTP_AUTH_PACKAGE should be set to what you used to put in the “Microsoft Exchange Proxy Settings” dialog box.

The Auth Package is likely “Basic”. Other acceptable Auth values are listed here: https://msdn.microsoft.com/en-us/library/ee178834(v=EXCHG.80).aspx
If you don’t have a Certificate Principal Name, you should use the value “none” in the AutoDiscover XML file.
The <ServerExclusiveConnect> value tells Outlook to always try HTTP first. If you don’t want to always try HTTP first then set the value inside <ServerExclusiveConnect> to “off”.

2. Save the AutoDiscover XML
With the AutoDiscover XML file created, it needs to be saved on your computer. A convenient place is your Documents folder. In the next step you will need the full path to the file. You can get this by holding SHIFT, right-clicking the file name, and choosing the “Copy as path” option:

3. Associate the XML file with your Mailbox
To allow Outlook to use the XML file for your mailbox settings, do the following:
Open up the registry editor (Start | regedit).
Navigate to the path HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
Create a new String Value, named with your SMTP address e.g. *** Email address is removed for privacy ***
In the Data type (or paste) the path to the AutoDiscover XML file you created. If you Pasted the result of the “Copy as path” command that was previously described, make sure there are no quotes (“) around the name of the file.

fcscholz

  • Zen Apprentice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Outlook 2016 Autodiscover
« Reply #4 on: February 09, 2016, 09:03:12 am »
Hi,

I have also followed the instructions here (and below) to manually setup the server but am having difficulties with the LegacyDN and ServerDN settings. This results in the account being created successfully but outlook failing to load and populate the .ost file. I presume this is from incorrect authentication but haven't got much further with it since. Keen to know if other people have better results.


Same Problems here! Is there a "step-by-step"-Instruction to setup the correct audosicover.xml for Zentyal and Outlook 2016?
I would be glad!

Regards
Florian
« Last Edit: February 09, 2016, 12:44:33 pm by fcscholz »