Exchange 2016 outlook 2007

I’m looking to upgrade our Exchange 2010 to Exchange 2016 but half of our users are still on Office 2007. Microsoft doesn’t “support” Outlook 2007 with Exchange 2016 but I’m wondering if it would still work.

Has anyone tried it?

I’m really not looking to purchase all new office licenses as 2007 still works great. Maybe Exchange 2016 isn’t worth the effort?

Nope - you’ll need to update Outlook as ‘it doesn’t work’ really means ‘it doesnt work!’!
The Activesync component doesnt support the older protocols 2007 talks, just like Office365 doesnt

I’m not sure but you might be able to IMAP or POP3 it but you are losing everything that is good about Exchange. You could have them use the OWA. It is really good in 2016.

Your clients should have been upgraded first.

To go with what Rod said. Exchange 2010 is supported till 2020, Outlook 2007 will die off next year when updates end. Office needs upgraded before Exchange. While you are at it, just move to 365 and get your Exchange and Office licenses. Remove onsite Exchange from your plate

IF you don’t have the funds to upgrade the clients you should have held back on exchange too, from here you have 3 options as I see it.

1. Stop don’t migrate any more people and upgrade the client

.2 Have them migrated but put them on OWA access until you can upgrade the clients

1. Just stop, Outlook 2007 isn’t supported, outlook 2010 is only supported with a specific KB installed,.

Your going to make this worse for yourself if you don’t apply one of the 3 above.

While moving to O365 is also something to consider it has the same requirements as Ex2016 for outlook

Thanks for the opinions so far but…has anyone tried it?

It isn’t going to work.

Outlook 2007 does not support MAPI over HTTP

Ok. I’m trying it.
I installed Exchange 2016 into my environment. I have left the Outlook 2007 people on the old Exchange 2010 and they seem to be working fine. I have moved a test user to the Exchange 2016 and he can OWA using the new server fine.

I’m going to make sure everything is stable and then try getting a Outlook 2007 to talk with the Exchange 2016.

Yes I have tired it and Outlook 2007 (run all updates to be safe) DOES work in on Exchange 2016. We had to cheat a little to ensure the GAL would work as we did host files for autodsicover and the server name to be safe. Once done the GAL populated. We also run our Exchange 2016 server in a multi-tenant environment. See this aritcle as well to see about the connection. Redirect Notice… .

There has been some posts about Outlook 2007 having some search issues. But most of the people who use O2007 just send and receive email. Thats all they care about but most of our users are on O2013 or higher.

See this blog too: ITPro Today: IT News, How-Tos, Trends, Case Studies, Career Tips, More

Thanks for Nicholas for posting. I’m having success with a mixed environment but haven’t tried moving the O2007 mailboxes yet.

see the following:

Outlook 2007 and Exchange 2013/2016 - Keeps Prompting for Logon Credentials -...

After migrating to Exchange 2013 and/or 2016, and still having a couple of Microsoft Outlook 2007 installations left, the following issue started popping up: as soon as users launch their Outlook 2007 (while already being migrated to Exchange...

Est. reading time: 9 minutes

Over the weekend I finished installing Exchange 2016 to coexist with Exchange 2010 as an upgrade project. Actually, I finished the installation on Friday; I migrated all the mailboxes over the weekend. No errors or real problems aside from a few huge mailboxes. I have a handful of Office 2007 users, and I knew going into this that they were going to be my pain points.

Guess what? No pain points! Supported, schmorted. Granted, the Exchange 2010 server is still running, and the instructions I was following advised to change the authentication method for external clients on the new server to NTLM from Negotiate. Also, I’ve only tested internal Office 2007 clients, so I don’t know how external clients will behave. Nonetheless, they work.

This just gives me time to upgrade those users and obtain Office 365 licenses for them.