Not sure why, looks like Outlook refers to some old data or old domain URLS or cannot obtain properly Autodiscover configuration file and it is trying different combinations to guess which link for Autodiscover is working. In our case we can see many redirections and autodiscover failures. ![]() There is no really any other way from the client perspective. You can give it a try if this won’t work as desired you can always revert the changes.Īlways make a copy of your registry before you change anything in the registry. So apart from first two steps Outlook 2016 implementation of Autodiscover () there are checking points we can configure how Outlook should obtain certain information. Then in case it cannot obtain certain data goes to another check point. Outlook as priority always prefer local XML configuration. If you have already configured XML autodiscover it should not affect the existing setting as the information are stored in this XML file locally anyway so Outlook will know how to connect. Outlook will skip checking Office365 Endpoint for Autodiscover. This setting is registry for client only. So to exclude Office365 checking point we add following key:ĮxcludeExplicitO365Endpoint and set the value to 1. Policy Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\AutoDiscover Non-Policy Key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover When they are deployed through GPO, or manual configuration of the policies key, the settings take precedence over the non-policy key. The policy values that are defined the Autodiscover Process section can be either policy-based registry values or non–policy-based values. Source: Outlook 2016 implementation of Autodiscover Solution Policy control via registry setting
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |