Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
MindSushi

Still Checking the Forum Out
Registered:
Posts: 8
Reply with quote  #1 
We're making the jump from 2007 to 2016 which apparently is not a user friendly process.  The quickest solution that I've run across so far is to upgrade to 2013 first and then up to 2016.  Everything that I've read so far assumes that I am upgrading to a new server with the 2013 and then decommissioning the 2007 box.  In my case, I have the existing box and the 2016 box, I'd rather not go through setting up a third box to make this happen.  Does anyone have enough knowledge/experience to know if I can just upgrade from 2007 to 2013 on the same server?  I'll also accept alternate solutions as well. [smile]

Thanks,


**Update
I had another thought.  What if I installed a HyperV instance on the second box?  Could I easily upgrade from a virtual 2013 Exchange environment to a Physical environment running 2016 and then decommission the VM?
0
Infradeploy

Avatar / Picture

Senior Member
Registered:
Posts: 165
Reply with quote  #2 
Sorry, you can't update directly. And exchange is not something you want to mess with to get unsupported scenarios.
If toy are a small shop vm's are probably the way to go.

__________________
Have SpaceSuit, Will Travel

0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 740
Reply with quote  #3 
As Ton says, don't get into unsupported states with Exchange.
Also, do not have a host acting as a host and an exchange server, you'll have licensing issues as well as backup issues.
Either a host with a 2013 + 2016 guest or get another box as the host for the 2013 VM.


__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
jsclmedave

Administrator
Registered:
Posts: 413
Reply with quote  #4 
Quote:
Originally Posted by wobble_wobble
As Ton says, don't get into unsupported states with Exchange.
Also, do not have a host acting as a host and an exchange server, you'll have licensing issues as well as backup issues.
Either a host with a 2013 + 2016 guest or get another box as the host for the 2013 VM.


What they said!!

A mussed up Exchange environment is not a rabbit hole you ever want to venture into... 

__________________
Tim Bolton @jsclmedave
Email: [string](0..20|%{[char][int](32+('527377347976847978324785847679797514357977').substring(($_*2),2))}) -replace ' '  

New to the forum? Please Read this
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 740
Reply with quote  #5 
Quote:
Originally Posted by jsclmedave

What they said!!

A mussed up Exchange environment is not a rabbit hole you ever want to venture into... 


It keeps me employed and paid [cool]

__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
anthonymaw

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 12
Reply with quote  #6 
You did not mention the size of your Exchange user base.  But off the top if it was me I would just do the supported migration to Exchange 2013.  It's a pretty decent version of Exchange, even if you install it as a 120 day free trial at first then you can think about migrating to Exchange 2016 if you really enjoy the stress and the headache.  Note that if Exchange 2016 detects any Exchange 2007 around it will fail to install.  The only problem might be licensing getting the license key to install Exchange 2013.  Your users will not see much difference between 2013 and 2016 they just want their emails to be happy.
__________________
Anthony Maw, B.Sc., MCSE, Vancouver, Canada, Earth, Solar System, Milky Way Galaxy.....
Tel/SMS: +1 604-318-9994
http://www.anthonymaw.com
0
dennis-360ict

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 43
Reply with quote  #7 
Well.. there is one way.. In Exchange 5.5 days, a migration would consist of migrating by .pst files. Basicly you would make a backup per mailbox and move that over.

There is one major drawback though, it will break any relations between any mailboxes. So of you have an resource mailbox that granted everyone rights to reserve a room or laptop by example, you will have to set those rights. It depends on your implementation if it is worth to recreate those. But you will also loose any relations between calander meetings. So if you and i are planning a meeting next week in our Outlook calander, we migrate by pst and i change this meeting, you won't get an update. I'm no exchange expert, but i think this has to do with the uniqueID your mailbox has and if you move by pst, you essentially recreate the mailbox and just move data to that new mailbox.

It depends if it is worth to recreate the exchnage environment if you want to do this.

Come to think of it, if you want to do this in the same domain, you have to deinstall Exchange 2007 and reinstall Exchange 2016 in that domain.. hmm.. that does not sound very good come to think of it..

So.. i think i would recommend installing going to Exchange 2013 first. But going from Exchange 2013 to Exchange 2016 is _very_ easy, your users probably won't even notice. We were setting up a Exchange 2013 while 2016 came out and decided to go to 2016 and it was _very_ easy. So probably you will feel the most pain going from 2007 to 2013, not to 2016.

__________________
-----
Home is where is sleep
0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #8 
In any case, an in-place upgrade is not possible.

One alternative option (I simply glanced through the preceding posts, so it may have been briefly mentioned already) is the use of a 3rd party product to go from 2007 to 2016. Binary Tree, BitTitan, Lepide and Quest (maybe rebranded under a Dell name) are vendors that come to mind.

You would have to weigh advantages and disadvantages with regard to cost - versus going through the intermediate migration step (2007 -> 2010 -> 2016).

Some examples:

https://www.binarytree.com/products/e2e-complete/

http://www.lepide.com/exchangemigrator/

0
MindSushi

Still Checking the Forum Out
Registered:
Posts: 8
Reply with quote  #9 
Thank you everyone, I appreciate the feedback.  I did find a 3rd box that we're prepping to load 2013 on.  I also want to look into the 3rd party examples mentioned to see if the cost is worth the hassle.  I'll try to report back with our final course of action.
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 740
Reply with quote  #10 
Dustin,

While some of the third party tools are great and ease the workload, there is still a learning curve from earlier version of Exchange and the migration process does (albeit sometimes painfully) offer some insight into these changes and the processes in managing them.

We use Skykick for some O365 migrations and other Quest (Dell) tools where there are time limitations/ speed is necessary, but mostly we use the MS migration paths.


__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
MindSushi

Still Checking the Forum Out
Registered:
Posts: 8
Reply with quote  #11 
Hi All,
I know it's been a little while but I wanted to offer some followup on how our progress.  We ended up going down the long road of upgrading to Exchange 2013 and then to Exchange 2016.  We've successfully upgraded to 2013 and our 2007 server is now offline.  The link that I used very heavily during this first transition was Migrate from Exchange 2007 to Exchange 2013.  This is a very extensive 17 part tutorial that is very detailed and was extremely helpful.  We are now preparing to go through the second upgrade to version 2016.

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation: