Link to home
Start Free TrialLog in
Avatar of SINC_dmack

asked on

Should I upgrade Exchange '10 to '13 or go straight to '16?

We have several small Exchange '10 servers (under 100 mailboxes) and are thinking about upgrading to a newer version of Exchange.  '16 has been out for a few weeks and presumably some of you have gone from '10 to '16, so is it safe to make that jump, or should we go to '13 and wait a few months before going to '16?  I've seen people say Exchange '16 is basically Exchange '13 SP2, which makes it seem like it should be less-scary to go up two Exchange versions.

(There are several old threads about this, but the most recent one I could find is from July.)
Avatar of Kamal Khaleefa
Kamal Khaleefa
Flag of Kuwait image

there is still issues with exchange 2013
if your environment is not heavy duty go 2016 other wise stay on exchange 2013 with latest cu  10
i wont support going to newer version than 2013 for exchange or SQL
Avatar of SINC_dmack


Could you elaborate on the issues that you've found that make you think it's unwise to upgrade to Exchange '16 at this time?  Thanks!
with 2013
roles disappear
Health mailbox corruption
Replication corruption
slowness with cas server "queries"
Public folder corruption
Compatability  with mobiles and client "older client  outlook version"
Discovery mailbox corruption

Not all of these solved till now in cu10
Thats y i don't recommend going to 2016
my environment 4 cas 4 mbx 2 dr
Avatar of Amit
Flag of India image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Exchange 2016 has no "wow" features to speak of. Straightforward, Exchange 2016 is a clear shift to Microsoft's touted "cloud first" strategy.
One of the wow feature is, you save money for extra license. Also, note cloud is the future. All big companies are heavily investing on cloud solution. As far as, i know Exchange 2016 is the best edition after 2003.
I'm reviewing the Exchange Server Deployment Assistant to evaluate moving from Exchange '10 to '16 directly and will keep this thread updated.  Thanks everyone for your input thus far!
I did migrate from '10 directly to '16.  There were no undue hiccups, and the '16 deployment has been running fine for a couple of months.
I used the Exchange deployment guide and moved from Exchange '10 straight to '16, per Amit's recommendation.