![autodiscover not working outlook 2016 autodiscover not working outlook 2016](https://www.mcbsys.com/wp-content/uploads/2019/02/O365-Autodiscovery-1_thumb.png)
- #Autodiscover not working outlook 2016 install
- #Autodiscover not working outlook 2016 password
- #Autodiscover not working outlook 2016 windows
(Once again, we also tested this behaviour with realistic external TLD and 2LD domains.) In other words, using an email domain of naksec.test, we were unable to get Outlook to try autodiscover.test, even after had failed. The good news is that we were unable to provoke Outlook to visit any domains that would have been outside our own network. (We also tried with realistic external TLD and 2LD domains, e.g.fr and. The bad news is that, even after setting the excludehttpsautodiscoverdomain option, we nevertheless observed Outlook 2016 trying to locate in our experiments.
![autodiscover not working outlook 2016 autodiscover not working outlook 2016](http://woshub.com/wp-content/uploads/2018/04/outlook-autodiscover-xml-example.jpg)
…we have to say that this wasn’t how things worked out in our own (necessarily brief) tests. What we observedĪs simple as the Group Policy workaround might sound, and as much as Microsoft’s own help file for Office group policy settings seems to reassure you that the setting we’ve listed will suppress the use of “autodiscover” domain names…
![autodiscover not working outlook 2016 autodiscover not working outlook 2016](https://s36505.pcdn.co/wp-content/uploads/2015/10/exchange-2016-outlook-certificate-warning.png)
Registry entry that supposedly prevents “autodiscover” domain names being used. Registry Key: HKCU\software\policies\microsoft\office\\outlook\autodiscoverĬreate Value: excludehttpsautodiscoverdomain If you don’t have the template files installed, or don’t want to use GPEDIT or Group Policy for this process, you can turn on the setting in the registry yourself:
#Autodiscover not working outlook 2016 install
Note that you will need to install Microsoft’s Administrative Template files for Microsoft 365 and Office, or else the Microsoft Outlook Group Policy items described above will not appear. According to Microsoft, this means that “Outlook not use the following URL: Group Policy setting for regulating Autodiscover Group Policy setting that supposedly prevents “autodiscover” domain names being used. Click on Disable Autodiscover, choose and turn on Exclude the query for the AutoDiscover domain.
#Autodiscover not working outlook 2016 windows
The data returned by that SRV record is, like the previous two items, under the control of the owner of the naksec.test domain, given that the DNS name is a subdomain of naksec.test.)Īccording to Guardicore, however, in their tests – perhaps conducted with an older version of Windows and Outlook, but we’re not sure – there was an extra step in the process, namely that if both of these sites failed…Ī Administrative Templates > Microsoft Outlook 2016 > Account Settings > Exchange. (The last request above was a DNS lookup known as an SRV record, a common way of looking up server names for specific services, including autodiscover, in Microsoft domains. Indeed, when we tried setting up Outlook 2016 on a network with no autodiscover files or servers present, and where we therefore expected Outlook to go through its entire repertoire of possible autodiscover file locations, we observed it looking for the following sequence of network names within our own domain:
![autodiscover not working outlook 2016 autodiscover not working outlook 2016](https://i0.wp.com/www.vspbreda.nl/nl/wp-content/uploads/2015/12/122115_1100_SolvedOffic3.png)
Microsoft’s autodiscover process can include numerous different steps, as explained in its own Autodiscover documentation, and different apps may use slightly different variants on the Microsoft’s central theme.įor email accounts, Autodiscover typically involves creating a short list of URLs where configuration file data can be expected, and then trying to access those URLs and fetch the setup data that’s stored there, until one of them succeeds (or all of them fail).įor an email address such as as shown above, the documentation suggests that you’d look for the following configuration files: If you’ve ever gone through the process, you’ve probably seen the two simple setup screens above, where you put in your email address, tell it you’re looking for an Exchange server, and Outlook goes out and autodiscovers the configuration details for you.
#Autodiscover not working outlook 2016 password
The problem, according to the researchers, is down to a Microsoft feature known as Autodiscover, which is used by various parts of Windows, notably Outlook, to simplify the setup of new accounts.įor example, if I want to hook up Outlook on my laptop to “the Exchange server” that’s run by IT, I don’t need to know and type in a whole pile of technical specifications correctly before I get as far as setting up a password and sending my first email. …in which they claim to have collected hundreds of thousands of Exchange and Windows passwords that were inadvertently uploaded to their servers by unsuspecting Outlook users from a wide range of company networks. Researchers at a cybersecurity startup called Guardicore just published a report about an experiment they conducted over the past four months… Thanks to James Cope and Rajeev Kapur of Sophos IT for their help with this article.