![]() ![]() ![]() On the next screen enter the details exactly as shown here, then click OK: Check the last check box and then click on the 'Exchange Proxy Settings' button: Then, under the Security tab change the 'Logon network security' to 'Anonymous' : On the next screen click on the 'More Settings' button: Then select 'Microsoft Exchange or compatible service' and then Next: To do this: On the Outlook configure screen check off the 'Manually configure server settings or additional server types' option, then Next: ![]() Enter the name, email address and password of the user and Outlook is able to work out all the other settings.īut, when those AutoDiscover records are not working - either they have not been set up with or they are not functioning correctly, and either way the first thing you should try is to get those working - you need to configure Outlook manually to connect to the Office 365 server. This forces Outlook to bypass the initial root domain queries and get the autoodiscover settings with minimal delay.įor domain-joined Windows clients, you may use the Office 2013 Administrative Templates or Office 2016 Administrative Templates to apply this workaround on multiple computers.ĭownload and extract the files, and then copy the content of the ADMX folder to the PoliciesDefinitions folder in the SYSVOL domain share.When using Office 365, and if the AutoDiscover DNS records are setup correctly and working, configuring Outlook is easy. To workaround this issue, until a more permanent solution can be applied, you may use the following Registry settings to force Outlook to bypass the root domain discovery and redirect to the autodiscover CNAME or A record to resolve the address for autodiscover settings. ![]() Most organizations use a autodiscover CNAME or A record to resolve the autodiscover address, which is also the recommended solution for both on on-premise Exchange deployment and when all mailboxes are placed in Exchange Online. The situation is furthermore complicated when the option to manually enter the Exchange server settings is removed in Outlook 2016.Ĭommon for these cases is that the internal autodiscover CNAME record is added in a split-DNS zone and resolves to – straight out of the Office 365 domain registration wizard.ĭigging deeper, the Test E-mail AutoConfiguration reveals that the autodiscover process is delayed by a series of (16) queries and the subsequent timeout for autodiscover settings from the root domain, like. As the use of Office 2016 has started to gain momentum, a number of organizations have experienced cases where Outlook 2016 take extraordinary long time to setup a new profile with a hosted Exchange 2010/2013 solution, like Exchange Online. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |