Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
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.)
(There are several old threads about this, but the most recent one I could find is from July.)
Asked:
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
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
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
I recommend you move directly to 2016. Use deployment assistant tool.
https://technet.microsoft.com/en-us/office/dn756393.aspx
Note: 2016 fits into 2010 or 2013 seamlessly. Not like previous version where you have to cut over everything to higher version. You can introduce 2016 with 2010 and test it as per your environment. Even you can have user on 2016 and let your 2010 be at front.
https://technet.microsoft.com/en-us/office/dn756393.aspx
Note: 2016 fits into 2010 or 2013 seamlessly. Not like previous version where you have to cut over everything to higher version. You can introduce 2016 with 2010 and test it as per your environment. Even you can have user on 2016 and let your 2010 be at front.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day 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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange
From novice to tech pro — start learning today.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with premium.
Start your 7-day free trial.
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