Your organization may require all communication with Exchange web services to use TLS 1.2.  If you are getting an Exchange error "An existing connection was forcibly closed by the remote host" you may need to make registry modifications in order for Quicklaunch to use TLS 1.2.  

Follow these instructions:



Add the following registry entry on the failing PC, reboot it, and test.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\.NETFramework\\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

Here is the Microsoft source article: https://docs.microsoft.com/en-us/officeonlineserver/enable-tls-1-1-and-tls-1-2-support-in-office-online-server#enable-strong-cryptography-in-net-framework-45-or-higher