What’s odd to me is that this experience is inconsistent with other mailboxes that were previously moved to Exchange 2016 and Outlook is connecting without issue.Įssentially what happens after an existing mailbox has been moved to Exchange 2016 and the Outlook client is restarted, the autoconfiguration process fails during the “Log on to server” task.Īs a result, Outlook is never able to attach to the mailbox on Exchange 2016 or update the existing profile. One of the latest issues I’ve experienced has been with an Outlook client (2010 or newer) not connecting to a mailbox that has been moved to (or even newly created in) Exchange 2016. We followed this for guidance: įortunately, in our case Windows and Exchange were already well patched so we only needed to add these registry keys and DWORD items on the server and reboot it.Lately, it seems as if I run across some new issue or anomaly on a weekly basis after implementing Exchange 2016 for one customer or another. It’s quite frustrating but it does wonders for building a personal knowledge base. This is great solution because only the server needed to be touched and we did not have to touch the workstations. This works because Windows 11 supports TLS 1.2 by default at this time and Windows 2008 R2 can be made to support TLS 1.2. That is all of the workstations connected to the same subnet as the server never had a problem after the Windows 11 upgrade, but all of the workstations outside of that subnet failed with proxy (Error Code 80000000). In our case, this happened when the Windows 10 workstations were upgraded to Windows 11 and is only noticed on workstations connected outside of the subnet the server is connected to.
Therefore, Outlook can't communicate with Exchange. Our failed configuration was: Outlook 2013 running on Windows 11 not connecting to Exchange 2010 running on Windows 2008 R2 via proxy.Ĭause of failure: Windows 11 disables TLS 1.0 and TLS 1.1 by default and Exchange 2010 running on Windows 2008 R2 uses TLS 1.0.
0 kommentar(er)
