Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Michael Pietrzak

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 52
Reply with quote  #1 
Well, I have battled my university for about five years now on the attempts to migrate my department to Gmail (or Google apps, whatever).

I have learned yesterday that I can keep my Exchange server but the higher ups want me to migrate off Exchange 2003\Server 2003.

From what I've read, the only option I have is to perform a migration to Exchange 2010 (Then to something after that if need-be).

Small victory I guess but in the same meeting that I learned I can keep my Exchange, I learned that campus will be moving to hosted Exchange.

Our university is moving to a unified AD structure so MS is giving students free Office 365 and staff will move to Exchange.

The move to a unified AD is fine with me. Departments will have their own OU's.

Anyways, any advice\comments about the move from Exchange 2003 to 2010. Hardware has been allocated.

Regards,
Michael
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 832
Reply with quote  #2 
User the Exchange Server Deployment Assistant
https://technet.microsoft.com/en-us/office/dn756393.aspx

Ask questions.
Read the document, read the called out links, read it again and if you have some resources, build a test lab for 2003, 2010 and I assume 2016.

Be careful you don't potentially end up hosting the hybrid configuration, as this may may you point for any issues on the bigger migration.

Hardest thing I've seen in the migration is getting certificate authentication for locked down devices configured.
All the rest is grand and well documented.
 


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

New to the forum? Read this
0
dennis-360ict

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 58
Reply with quote  #3 
I should read similar threads like this;
http://newforum.minasi.com/post/migrating-from-exchange-2007-to-exchange-2016-7998866

Code:

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 exchange 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.


In your case it would require a move to 2010 and then 2016 if you want to do a rolling upgrade. If you can use the .pst option, i think that would give you the option to have a nice clean environment. there are also some (paid) tools that can (crossforest) migrate the mailboxes if you want.

Or just hire a company who has exchange experience and let them make a migration plan so you can follow that. Come to think of it, thats what we do.. ;-) But i think you want a company thats nearer to you, as we're in the netherlands.

__________________
-----
Home is where is sleep
0
Wes

Senior Member
Registered:
Posts: 208
Reply with quote  #4 
Why not go to the hosting with the rest of the uni?  I'm assuming you have a good reason but I'm curious what it could be.
0
Michael Pietrzak

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 52
Reply with quote  #5 
Oh no, we full intend to migrate users to campus hosted Exchange. This move off Exchange 2003\Server 2003 is a interim move.

Campus security wants end-of-life OSes to be migrated off if possible.
0
Wes

Senior Member
Registered:
Posts: 208
Reply with quote  #6 
Ah gotcha.  Honestly it seems like a lot of hassle to go through - what is the intended timeframe for the hosting move?  You might find it easier (depending on how many mailboxes you're dealing with) to move to your own office 365 tenant for the interim...
0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 219
Reply with quote  #7 
True enough Wes.   I stopped Using Exchange in 2008.  I've been in the cloud ever since.  But there are valid uses for on premise exchange servers. 
I can't thing of them right now though!!!!

__________________
Curt Spanburgh
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 832
Reply with quote  #8 
Quote:
Originally Posted by cspanburgh
True enough Wes.   I stopped Using Exchange in 2008.  I've been in the cloud ever since.  But there are valid uses for on premise exchange servers. 
I can't thing of them right now though!!!!


A financial business that generates a lot of email, both internal and external is one.

Some of the gov agencies don't want mail between sites  to travel over any other network than theirs is a second use case I've seen.


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

New to the forum? Read this
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.