Functional versions of Office-Outlook?
Problem reported by Mark Thornton - Today at 10:44 AM
Submitted
I'm being asked to upgrade from Office 2016 and it's associated Outlook to something more current because, well that's what they want...

Office 2019, 2021, 2024? Do the registry hacks still apply? Which are still relevant? Do later versions know to look at the 16.0 registry key for these settings, or do we need to place them in the current version registry settings?

I am also confused seeing some recent posts suggesting "PreferLocalXML" should be set to 1 and referencing a local xml file, but I can't find an example of what the local xml file should contain to make it useful.

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover]
"PreferLocalXML"=dword:00000000
"ExcludeLastKnownGoodURL"=dword:00000001
"ExcludeExplicitO365Endpoint"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeScpLookup"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\RedirectServers]
"autodiscover-s.outlook.com"=hex(0):
"autodiscover.hotmail.com"=hex(0):
"autodiscover.smartermonitor.com"=hex(0):
"autodiscover-s.partner.outlook.cn"=hex(0):
"autodiscover-s.outlook.de"=hex(0):
"autodiscover-s.office365.us"=hex(0):
We run the 2021 LTSC version for our clients. 2024 has issues with firewall rules triggering because of unusual fast and many connections at once. And it keeps going banging on the server all the time.
J. LaDow Replied
We have several 2021 Pro Plus installs that use (Classic) Outlook - connecting via IMAP/SMTP with autodiscover works without intervention if your autodiscover is setup right.  

It took a while to get our autodiscover setup just right with DNS and so forth, but once done - we didn't need to make registry changes for our clients to connect.

We don't use MAPI/Exchange though -- and no (New) Outlook installs.
MailEnable survivor / convert --

Reply to Thread

Enter the verification text