![outlook 2016 avast certificate error outlook 2016 avast certificate error](https://blog.itgs-solutions.ch/wp-content/uploads/2019/04/Mozilla-Thunderbird-Options.png)
It is possible to set Exchange Server 2010 to prefer HTTP before TCP/IP (or rather RPC/HTTP before RPC/TCP) but that means that all clients will pick up that setting and all clients will connect to your CAS using HTTP, even clients on internal networks. There are no Connection settings in Outlook 2016 and that’s because Outlook doesn’t expose any ways of configuring an Exchange server connection other than Autodiscover. Now let’s look at the Outlook 2016 Connection settings. The easiest way was to go into account options and modify the connection settings by checking the On fast networks, connect using HTTP first, then connect using TCP/IP option.įast networks are all network interfaces with a link speed higher than 128Kbps which pretty much means all network interfaces unless you’re toying around with some obsolete dialup adapter. Let’s look at how this was handled in Outlook 2013. I’ve seen plenty of people complaining about it on the Technet forums and elsewhere but I haven’t seen anyone getting a solution but I’ve found a few ways to solve the problem. This was easy to change in previous versions of Outlook but not in Outlook 2016. The reason is that the Exchange 2010 Autodiscover service tells the client to try a regular RPC/TCP connection before resorting to a RPC/HTTP connection.
![outlook 2016 avast certificate error outlook 2016 avast certificate error](https://filedb.experts-exchange.com/incoming/2019/02_w07/1412384/certificates-info.jpg)
With a default Exchange 2010 Outlook Anywhere configuration it takes around 30 seconds after Outlook 2016 startup before the client manages to connects to the Exchange server.