The differences between Exchange 2016 and Exchange 2013

exchange logoIt’s been a while since Exchange 2016 was published and some of you probably are long after the first impressions and experiences in working with the newest release. Those of you, who haven’t had this pleasure yet, need to know that moving to Exchange 2016 doesn’t have this offbeat taste and Exchange 2013 users should feel like at home.

The technology used in Exchange 2016 descends straight from the previous on-premise version and Microsoft’s experience with cloud based solutions like Office 365. That’s why the newest Exchange is labeled as “forged in the cloud”, it combines multi-role server with a strong focus on enhanced hybrid solutions.

Some of the most important technological changes and innovations in Exchange 2016 include redesigned architecture (no CAS role), new OWA client, new transport protocol, improved document collaboration, eDiscovery and DLP upgrades, better performance, and more.

Infographics Exchange 2013 vs 2016

A part of CodeTwo products supports Exchange 2016, check out:

Tools for Exchange Server

2 thoughts on “The differences between Exchange 2016 and Exchange 2013

  1. I’m noticing since we upgraded to Exchange 2016 in April 2017, that my users who previously had permissions to manage email distributions list with the ability to modify the list, no longer have permissions. What’s changed and how do we fix this? Thank you!

    • Hi Marcia,
      Permissions concerning distribution groups (or public folders) are not migrated automatically, so I am afraid you will have to assign them from scratch. The permissions required to manage distribution groups are Organization Management and Recipient Management.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.