Solved

Exchange 2013 Upgrade to 2016

Posted on 2016-08-03
6
70 Views
Last Modified: 2016-08-11
Hey guys thanks in advance for your responses.

I just built a new production AD Environment and deployed Exchange 2013.  Everything was going great until i was asked to deploy Exchange 2016 instead.  I have no user accounts or mailboxes yet and i was wondering, can i just uninstall Exchange 2013 and install 2016 instead? assuming of course i follow all the prerequisites. I only have the one server now, but planning on deploying multiple MBX + DAGs.

Any thoughts are appreciated!

Thank you!
0
Comment
Question by:martinezjrj
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 16

Accepted Solution

by:
Todd Nelson earned 500 total points
ID: 41741580
Thoughts...

1) Is your AD forest functional level set to Windows Server 2008 or newer?  If not, then you won't be able to install Exchange 2016 in your forest until that change is made.

2) I suppose since this is a "new production AD environment" there are no other Exchange servers in the forest other than the Exchange 2013 server you installed?  If not, then what other Exchange versions are installed?  If Exchange 2007, you will need to migrate to Exchange 2013 and decommission 2007 prior to installing 2016.

3) Supposing your forest meets the requirements for Exchange 2016 and no versions of Exchange older than 2013 are present, you can simply remove/uninstall Exchange 2013 and then install Exchange 2016 in your environment. Alternately, if you have made any configuration settings in Exchange 2013 and want to retain them, it might be best to install Exchange 2016 then remove Exchange 2013. Either way should be fine.
 
4) Do not install .NET Framework 4.6.1 on any server that will host Exchange.  .NET Framework 4.6.1 is only supported with Exchange 2013 CU13 and Exchange 2016 CU2 after those specific versions have been installed.

Hope this helps.
1
 
LVL 19

Expert Comment

by:R--R
ID: 41741897
Since you build new AD and installed Exchange 2013, i assume there are no other Exchange version exist at site.

I suggest install Exchange 2016 and then remove Exchange 2013 after that.

you can follow the link below written by PAUL CUNNINGHAM

http://exchangeserverpro.com/installing-exchange-server-2016-into-an-existing-organization/
0
 

Author Comment

by:martinezjrj
ID: 41743078
Thanks for the responses!

  • Domain and Forest functional level is 2012 R2
  • I only have 2 servers. 1 DC and 1 Exchange 2013
  • There are no other Exchange Servers in the domain

Are there any ramifications of simply uninstalling 2013?  For example, with the Schema changes that may affect the 2016 installation.

Cheers!
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 16

Expert Comment

by:Todd Nelson
ID: 41743107
Are there any ramifications of simply uninstalling 2013?

No.
0
 

Author Comment

by:martinezjrj
ID: 41743110
Thanks Todd!

Cheers!!
0
 

Author Closing Comment

by:martinezjrj
ID: 41752666
I thought i had already closed this, but i guess not. I'll try again.

Thanks Todd i appreciate your time and input!  Also a big thanks to everyone else's input.

Cheers!
0

Featured Post

Raise the IQ of Your IT Alerts

From IT major incidents to manufacturing line slowdowns, every business process generates insights that need to reach the people required to take action. You need a platform that integrates with your business tools to create fully enabled DevOps toolchains.

You need xMatters.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question