Disable Autodiscover Certificate Error Outlook 2007
Contents |
360 games PC games outlook autodiscover certificate error exchange 2007 Windows games Windows phone games Entertainment All Entertainment
Disable Autodiscover Outlook 2007 Registry
Movies & TV Music Business & Education Business Students & educators
Autodiscover Certificate Error Outlook 2010
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Outlook 2010 Autodiscover Certificate Error Exchange 2003
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All autodiscover certificate error exchange 2010 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(7) October 2015 (5) September 2015 (2) August 2015 (11) July 2015 (19) June 2015 (6) May 2015 (5) April 2015 (1) March 2015 (4) February 2015 (7) January 2015 (7) December 2014 (1) November 2014 (1) autodiscover certificate error exchange 2013 October 2014 (1) September 2014 (7) August 2014 (4) July 2014 (3) June 2014 (5) outlook 2013 certificate error May 2014 (3) April 2014 (6) March 2014 (7) February 2014 (8) January 2014 (9) December 2013 (2) November 2013 (6) October 2013 outlook 2013 certificate warning disable (12) September 2013 (3) August 2013 (10) July 2013 (3) June 2013 (7) May 2013 (5) April 2013 (8) March 2013 (6) February 2013 (1) January 2013 (8) December 2012 (7) November 2012 (10) October 2012 (21) September https://support.microsoft.com/en-us/kb/940726 2012 (19) August 2012 (9) July 2012 (22) June 2012 (16) May 2012 (7) April 2012 (12) March 2012 (11) February 2012 (5) January 2012 (6) December 2011 (3) November 2011 (2) October 2011 (4) September 2011 (2) August 2011 (14) July 2011 (2) June 2011 (2) May 2011 (1) April 2011 (1) March 2011 (2) February 2011 (1) January 2011 (4) December 2010 (1) October 2010 (3) September 2010 (2) August 2010 (1) March 2010 http://kwsupport.com/2014/03/outlook-2010-displays-autodiscover-security-certificate-alert-window-at-startup/ (2) January 2010 (2) December 2009 (1) October 2009 (3) August 2009 (1) April 2009 (1) March 2009 (1) January 2009 (1) December 2008 (1) November 2008 (1) Search This Site How to reach us Web: Contact usEmail: kw@kwsupport.com Outlook 2010 displays Autodiscover Security Certificate Alert window at startup By KW Mar 06 2014 I had a customer with an SBS 2008 server who called this past week to say that they were getting the following popup alert when starting up Outlook 2010: The name on the security certificate is invalid or does not match the name of the site I ran the Microsoft Remote Connectivity Analyzer to test Autodiscover for this customer. And sure enough, it was failing the test to validate the server name. Certificate name validation failed. Host name xxx.com doesn’t match any name found on the server certificate. The first article I reviewed was KB 940726. Although the title of this KB article indicates that it was written for Outlook 2007 and Exchange 2007, it is also applicable to Outlook 2010 and Exchange 2010. It covers how to change the internal URL for the Autodiscover service stored inside Exchange via Exchange PowerShell commands. However, in my case, the PowerShell command get-ClientAccessServer | fl was showing that the AutoDiscoverServiceInternalUri field was showing the correct URL. In talking with other MVPs, it appears that
in someenvironments Posted by Andrew S Higginbotham 16 Background: I originally discovered this issue back in early Feb & let a couple people on the Exchange Product Team know https://exchangemaster.wordpress.com/2013/05/07/new-behavior-in-outlook-2013-causing-certificate-errors-in-some-environments/ about it via the TAP but it seems to be affecting more customers than initially thought so I thought I’d share. In Outlook 2007 through Outlook 2010 all domain-joined Outlook clients would initially query Active Directory for AutoDiscover information & ultimately find a Service Connection Point (SCP) value that would point them to their nearest Client Access Server's AutoDiscover virtual certificate error directory. If that failed then they would revert to using DNS like any non-domain-joined Outlook client. The order of this non-domain-joined lookup is as follows: https://company.com/autodiscover/autodiscover.xml https://autodiscover.company.com/autodiscover/autodiscover.xml Local XML File http://company.com/autodiscover/autodiscover.xml (looking for a redirect website) SCP AutoDiscover Record Why it ever looked to https://company.com/autodiscover/autodiscover.xml I’ll never really know because honestly I’ve never come across a customer who had it autodiscover certificate error deployed that way; most have https://autodiscover.company.com/autodiscover/autodiscover.xml but I imagine when Exchange 2007 was first being developed they weren’t exactly sure how customers would be implementing AutoDiscover. Issue: The above methods have served us well since Exchange 2007 timeframe but for some reason the Outlook team decided to try & implement some giddyup into Outlook & try to speed up the process. They decided to have domain-joined Outlook 2013 clients query both the SCP values in AD as well as the DNS records at the same time. If an SCP record was found it would still be used but in the event it failed then it would already have the DNS response ready to go. Great idea, however there’s one problem in the implementation. If Outlook 2013 encounters any kind of Certificate error while doing the simultaneous DNS query then you will receive a pop-up in Outlook about the cert. I actually stumbled upon this while in the middle of the scenario below: That’s right, I actually get a certificate pop-up for my lab’s domain name (ash15.com) & n