6/18/2023 0 Comments Outlook 2019 and exchange 2010The value can be set to ServerExclusiveConnect or to None to clear the flags. This increases the speed at which Outlook 2010 clients will connect when clients are primarily accessing Exchange over the Internet. “The OutlookProviderFlags parameter specifies that Outlook 2010 clients should connect using RPC over HTTP (Outlook Anywhere) before trying RPC over TCP connections. The Set-OutlookProvider Cmdlet is documented at (v=exchg.141).aspxĪs stated in the above documentation, running all connections over HTTP is not recommended for Exchange 2010 unless most clients use Outlook Anywhere as their primary connection method (it is recommended for Exchange 2013 and Exchange 2016 though). This is done using the Set-OutlookProvider Cmdlet in Exchange Management Shell: Set-OutlookProvider EXPR -OutlookProviderFlags:ServerExclusiveConnect 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. 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.
0 Comments
Leave a Reply. |