Exchange CAL’s also come in two flavours, Standard and Enterprise (For most people standard is fine, enterprise lets you use archiving and unified messaging.
![transition exchange server 2010 to 2016 transition exchange server 2010 to 2016](https://c7solutions.com/wp-content/uploads/2019/06/image-4.png)
You will need to buy the Exchange 2010 Base product ( Server Licenses come in two flavours, Enterprise or Standard) and you will need a CAL for each client that will access Exchange. Unless you have Microsoft “Software Assurance” you cannot simply upgrade to 2010 for free. Exchange 2003 to 2010 Licensing Requirements
#Transition exchange server 2010 to 2016 install
Post install the NEW server will hold client access, mailbox, and hub transport roles. I’m putting in Exchange 2010 onto a new server running Server 2008 R2. In this example I’ve got a n existing Exchange 2003 environment running on Windows 2003. This means you prepare your existing Windows domain and Exchange Organisation, to let Exchange 2010 exist, then you build an Exchange 2010 server, migrate your data into it, and finally remove your original Exchange 2003 server. In fact there is no direct upgrade, you need to perform what Microsoft calls a “Transition” to Exchange 2010. Unfortunately you can’t just “Pop in the DVD” and let it upgrade.
![transition exchange server 2010 to 2016 transition exchange server 2010 to 2016](http://4.bp.blogspot.com/-vTuGQPJ1zWg/TwQnhQ_bGAI/AAAAAAAACLI/e--JRAk-RVg/s1600/9.png)
There are a lot of people who held out on the upgrade to Exchange 2007, and those people will now be looking to jump straight to Exchange 2010. Be under no illusions the terminology used in the title and the tags on this page, are to catch the web searches of those who have an Exchange 2003 Server and want to move all their Exchange, to Exchange 2010 server. Before we start, I’m aware “Migration”, “Swing Migration”, and “Transition” have three very different meanings, depending on which KB, blog or piece of Microsoft documentation you are reading.