Current Position:Home > autodiscover to https failed 0x800c820d

autodiscover to https failed 0x800c820d

  • Free/Busy not working after mailbox migration to Exchange 2013 Updated:10-11

    I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013 It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated.  If we remove the Outlook profile and recreate it, all is

  • Autodiscover fails in Ex2010/Ex2013 co-existence Updated:11-30

    Dear readers, Currently we are in the preparation phase of the migration from Exchange 2010 to Exchange 2013. I have followed the Exchange Deployment Assistant, but unfortunately it does not work as expected. I think i might have created an autodisco

  • Exchange AutoDiscover not working correctly in 2010/2013 environment Updated:10-11

    Here's my setup: Mixed environment transitioning: Exchange 2010 running on Server 2008 in a VM Exchange 2013 running on Server 2012 in a VM I have split dns so that points to my 2013 server internally and my 2010 server extern

  • Wrong Autodiscover Server returned in XML Updated:11-30

    We are trying to migrate to new Exchange 2013 CAS servers, however the autodiscover xml information they handing out still has the old server name in it X-CalculatedBETarget: old server X-DiagInfo: old server X-BEServer: old server Persistent-Auth: o

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007 Updated:10-11

    <style type="text/css">P { margin-bottom: 0.21cm; }</style> Hello, recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients. But the problem is they can't connect from his O

  • What is required to Exchange integration work - (Can't connect to Exchange Web Server)? Updated:11-30

    Hi guys, We have just 'beaten' our Lync installation until it decided to work with mobility, however the clients (IOS) complain that it "Can't connect to Exchange Web Server". Entirely possible its our own fault! My question is: What exactly do

  • Autodiscovery from external Exchange 2007 SP1 Updated:11-30

    Dear all, We have 1 Exchange 2007 and 1 CAS server running and a Terminal Server. All Outlook 2007 clients are connecting using HTTPS/RPC internally and external. Now our problem is that when we try to configure an outlook client 2007 from the outsid

  • SharePoint SiteMialbox failed with 503 error (AutoDiscover.svc web service call failed) Updated:10-11

    SharePoint SiteMialbox failed with 503 error (AutoDiscover.svc web service call failed) I followed Technet articles to configure SiteMailBoxes in our environment & exchange sever. When we created Sitemailbox in a SiteCollection &when we try to ope

  • AutoDiscover failing to locate ActiveSync ExternalURL Updated:11-30

    I am experiencing an issue where ActiveSync w/ AutoDiscover fails to recognize or read the ExternalURL's that I have configured. When I run a test using ExRCA or attempt to configure an EAS device using Autodiscover I get the event log shown below. H

  • Exchange 2007 2010 coexist autodiscover fails Updated:11-30

    We are migrating from 2007 to 2010. Autodiscover is not working on the 2010 CAS servers (4 of them). SMTP=[email protected] Attempting URL found through SCP Autodiscover to https://autodis

  • Testing of Autodiscover for Exchange ActiveSync failed. Updated:11-30

    Hello Friends, Attempting the Autodiscover and Exchange ActiveSync test (if requested). Testing of Autodiscover for Exchange ActiveSync failed.  Additional Details Elapsed Time: 2573 ms. Test Steps Attempting each method of contacting the Autodiscove

  • Test-OutlookConnectivity cmdlets fail with 401 unauthorized on Autodiscover Updated:11-30

    I've done quite a lot of searching on this.  The defacto answer is disable loopback processing.  That does not solve the issue.  All virtual directory permissions have been checked and are the recommended MSFT settings.  All NTFS permissions have bee

  • Autodiscover Failing Updated:11-30

    Hi I have an exchange server 2013 SP1 installed consisting of 2 CAS and 2 mailbox servers, I am facing some issues with my autodiscover service. When I assign a SSL certificate using SHA1 hashing algortihm everything works fine when i changed to a ce

  • Autodiscover fails after mailbox move Updated:11-30

    Hello, Environment: existing exchange 2010 org, with new Exchange 2013 introduced. Clients are Outlook 2013. Clients can connect to all mailbox on the 2010 Server, also can connect to new mailboxes on the 2013 Server. But if I move an existing mailbo

  • Testing Autodiscover failed Updated:11-30

    We are running Exchange 2007 on Windows 2008 and planning to move to Office 365. However, we can't do it because Exchange 2007 Autodiscover issue. When we test it from, we receive Testing Autodiscover failed wth these

  • Bindings in IIS on Exchange 2010 causing Test-outlookwebservices to fail on Autodiscover Updated:11-30

    Exchange 2010 is coexisting with Sharepoint 2013 Foundation. Exchange 2010 have 2 internal IP's (1 for Exchange and 1 for Sharepoint). Under IIS we had set up binding on port 443 to 1st IP, and second IP was used to bind it to 80 port for SharePoint.

  • Autodiscover failing on testexchangeconnectivity Updated:11-30

    Hey guy's. I'm trying to migrate a small business server running exchange 2010 sp 3 to office 365 using a cut-over migration. Everything seems to be successful until now, but when i try doing the migration endpoint, we couldn't discover the migration

  • The attempt to contact Autodiscover using the HTTP Redirect method failed. Exchange 2007 to Office 365 Cutover Mirgation Updated:11-30

    I am getting the following error message shown below. Wondering if i could get some help on how to resolve this issue.My understanding is that the only way to resolve this issue is to install an Exchange 2010 or 2013 server in your on-premises organi

  • Autodiscover fails on mobile phones Updated:11-30

    I have a new Exchange 2013 server and connectivity works fine from all clients. The only exception is the autodiscover on smart phones.  iPhones and Android phones are all I have tried.  Setting the connection up manually works fine. Used the testcon

  • OneDrive OneDrive for business - URL autodiscover failing Updated:10-11

    Using Office 2013 SP1 with the latest updates I'm struggling with the autoprovisioning of the OneDrive URL. When a user starts OneDrive for business the OneDrive application should automatically enter URL for the users OneDrive location, e.g. https:/