If the above method can no longer be used you can use ADSIEdit to remove the SCP manually. The easiest way to change this is using Powershell to change the AutoDiscoverServiceInternalUri to NULL: Set-ClientAccessServer –Identity SERVERNAME -AutoDiscoverServiceInternalUri $null This XML file is located in the AutoDiscoverServiceInternalUriĬheck the AutoDiscoverServiceInternalUri Get-ClientAccessServer |select AutoDiscoverServiceInternalUri Solution 1 Powershell In order to connect to Exchange Online using Outlook for Windows, the device must be upgraded to a supported version of Outlook for Windows as outlined below. When this fails Outlook falls back to the next DNS based methods or uses a local XML file. Outlook on the web connects to Exchange Online and allows the user to interact with their email, contacts, calendar, groups, public folders and tasks. Outside the office, Outlook only wants to connect to 365. While in the office, Outlook has no issue connecting to Exchange. Most of the time, this doesn’t work for the internal users, because Outlook is hard-coded to query an AD Service Connection Point (SCP) to locate a server with the Autodiscover service Something occurs when the user adds Office 365 Home to their personal Microsoft Account that basically prevents newer versions of Outlook from finding the Exchange server and successfully connecting to their account. You need to change your internal and external Autodiscover DNS setting. Open the corresponding user account in Office 365 and disable mapi. Create or Set the DWORD: ExcludeExplicitO365Endpoint to Value : 1. Go to the following path: HKEYCURRENTUSER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover. When Migrating to Office 365 you need to reconfigure your Outlook profile. Implement a registry modification to disable Direct Connect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |