Solved

Outlook 2016 on an Exchange Server 2016

Posted on 2016-11-09
5
47 Views
Last Modified: 2016-11-20
I have a 2012 R2 server with Exchange 2016 installed.
I have multiple users with Outlook 2013 (Office 2013) connected to it without issue

When I try to add a user with Outlook 2016 (Office 365 2016) it won't find the server.

According to Microsoft, Outlook 2016 doesn't use the Autodiscover service any longer.

That said, how do I get my Outlook 2016 client's connected to my inhouse Exchange 2016 server?
0
Comment
Question by:Docomon
  • 3
5 Comments
 
LVL 16

Assisted Solution

by:Ivan
Ivan earned 250 total points
ID: 41881294
Hi,

I think you got it wrong. Outlook 2016 is using autodiscover, and that is the only way to connect Outlook 2016 to exchange.

When you try to setup account, after entering email address and password, what happends?
Have you tried to verify that everything is ok, via https://testconnectivity.microsoft.com/

Regards,
Ivan.
0
 
LVL 14

Assisted Solution

by:Edwin Hoffer
Edwin Hoffer earned 250 total points
ID: 41881852
Dear User
Yes, as suggested by our expert Outlook 2016 supports autodiscover. The manual way to connect the autodiscover is removed after Outlook 2013. To enable autodiscover you have to enable Auto discover from the exchange server. You can refer the informative article if the Exchange Account Setup is missing in Outlook. Esle clicking on the link will show you the methods to configure Autodiscover In Exchange Server 2016. Hope this will work.

Thanks & Regards
Edwin Hoffer
0
 

Author Comment

by:Docomon
ID: 41888309
I ran the Microsoft test and Autodiscover failed.  We do have a trusted certificate from Godaddy.

Here is the error from Microsoft Test:


      Attempting the Autodiscover and Exchange ActiveSync test (if requested).
       Testing of Autodiscover for Exchange ActiveSync failed.
       
      Additional Details
       
Elapsed Time: 1622 ms.
       
      Test Steps
       
      Attempting each method of contacting the Autodiscover service.
       The Autodiscover service couldn't be contacted successfully by any method.
       
      Additional Details
       
Elapsed Time: 1622 ms.
       
      Test Steps
       
      Attempting to test potential Autodiscover URL https://turnermedicalinc.com:443/Autodiscover/Autodiscover.xml
       Testing of this potential Autodiscover URL failed.
       
      Additional Details
       
Elapsed Time: 1098 ms.
       
      Test Steps
       
      Attempting to resolve the host name turnermedicalinc.com in DNS.
       The host name resolved successfully.
       
      Additional Details
       
IP addresses returned: 206.166.251.243
Elapsed Time: 462 ms.
      Testing TCP port 443 on host turnermedicalinc.com to ensure it's listening and open.
       The port was opened successfully.
       
      Additional Details
       
Elapsed Time: 253 ms.
      Testing the SSL certificate to make sure it's valid.
       The SSL certificate failed one or more certificate validation checks.
       
      Additional Details
       
Elapsed Time: 382 ms.
       
      Test Steps
       
      The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server turnermedicalinc.com on port 443.
       The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
       
      Additional Details
       
Remote Certificate Subject: CN=moth3.hiwaay.net, Issuer: CN=RapidSSL SHA256 CA, O=GeoTrust Inc., C=US.
Elapsed Time: 350 ms.
      Validating the certificate name.
       Certificate name validation failed.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
Host name turnermedicalinc.com doesn't match any name found on the server certificate CN=moth3.hiwaay.net.
Elapsed Time: 0 ms.
      Attempting to test potential Autodiscover URL https://autodiscover.turnermedicalinc.com:443/Autodiscover/Autodiscover.xml
       Testing of this potential Autodiscover URL failed.
       
      Additional Details
       
Elapsed Time: 131 ms.
       
      Test Steps
       
      Attempting to resolve the host name autodiscover.turnermedicalinc.com in DNS.
       The host name couldn't be resolved.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
Host autodiscover.turnermedicalinc.com couldn't be resolved in DNS InfoDomainNonexistent.
Elapsed Time: 131 ms.
      Attempting to contact the Autodiscover service using the HTTP redirect method.
       The attempt to contact Autodiscover using the HTTP Redirect method failed.
       
      Additional Details
       
Elapsed Time: 5 ms.
       
      Test Steps
       
      Attempting to resolve the host name autodiscover.turnermedicalinc.com in DNS.
       The host name couldn't be resolved.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
Host autodiscover.turnermedicalinc.com couldn't be resolved in DNS InfoDomainNonexistent.
Elapsed Time: 5 ms.
      Attempting to contact the Autodiscover service using the DNS SRV redirect method.
       The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
       
      Additional Details
       
Elapsed Time: 172 ms.
       
      Test Steps
       
      Attempting to locate SRV record _autodiscover._tcp.turnermedicalinc.com in DNS.
       The Autodiscover SRV record wasn't found in DNS.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
Elapsed Time: 172 ms.
      Checking if there is an autodiscover CNAME record in DNS for your domain 'turnermedicalinc.com' for Office 365.
       Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
There is no Autodiscover CNAME record for your domain 'turnermedicalinc.com'.
Elapsed Time: 214 ms.
0
 

Accepted Solution

by:
Docomon earned 0 total points
ID: 41888880
I broke down and called Microsoft for $499 and they fixed it in about 20 minutes. Had to create a new DNS zone for autodiscover and changed the certificate binding in IIS.

Thanks for everyone's help!
0
 

Author Closing Comment

by:Docomon
ID: 41894666
Had to call Microsoft to get it fixed.
0

Featured Post

Networking for the Cloud Era

Join Microsoft and Riverbed for a discussion and demonstration of enhancements to SteelConnect:
-One-click orchestration and cloud connectivity in Azure environments
-Tight integration of SD-WAN and WAN optimization capabilities
-Scalability and resiliency equal to a data center

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question