I've entered the same credentials for the user's email that worked for an external Autodiscover test but onsite the test fails. Support says that propagation may take up to one day. I tried adding the mailbox to my own Outlook, to test it on another machine, but that didn’t work either. But that made no difference, even after a reboot. Request-id: 8a174911-96e4-490e-bcc3-43735ed6e310 REG ADD HKCUSoftwareMicrosoftOffice16.0OutlookAutoDiscover /v ExcludeSrvRecord /t REGDWORD /d 00000001 ipconfig /flushdns. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN). Note that in the reg-file the backslashes ( ) in the file-path are doubled but will show up as single backslashes within the Registry Editor. It contains an autodiscover.reg file that you can open in Notepad so that you can edit the Value Name and the Value. This is usually the result of an incorrect username or password. Tip To do this, you can also use the download from Step 2. The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL for user (mailto: address].Īn HTTP 401 Unauthorized response was received from the remote Unknown server. I've run the Remote Connectivity Analyzer and gotten fails during the Autodiscover POST request with the following error: Autodiscover is working fine offsite but it's not working onsite. Recently migrated from Office 365 to an onsite Exchange 2016 server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |