Exchange 2016: You know what it's like. You've just charted out how a new version of Exchange (in this case, Exchange 2016) can be rolled out into production when someone asks the "what about Outlook" question. No one likes going near user desktops and the thought of having to deploy a new version of Microsoft Office is enough to reduce a strong administrator to a quivering wreck, especially after the Office 2010 "ribbon" caused so much grief for some. But there's no getting away from the fact that Exchange 2016 will simply not play ball with Outlook 2007. Something more modern is required, like a nice new Outlook 2016 client. That'll do nicely. http://windowsitpro.com/blog/why-exchange-2016-ignores-outlook-2007 #ExchangeServer #Outlook
Part of planning a deployment of a new on-premises release of Exchange is a review of client requirements. It’s therefore reasonable that anyone who is interested in deploying Exchange 2016 might start to look at clients to make sure that users will be able to access the new server after it is deployed. It’s also true that you might be interested in new clients if you want to deploy technology that’s only available in a specific client.
Add a comment...