How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.
Exchange 2007 on SBS 2008 Transition to Exchange 2013 on server 2012
Hey guys,
We are moving from SBS 2008 to server 2012. We have set up 3 server 2012 boxes, DC, exchange 2013, and sharepoint 2012. We want to transition completely off of exchange 2007 in one shot, and as we only have around 30 mailboxes, i think it is possible, time wise. I havent really seen anything definitive on the exchange 2007 to 2013 move, so any help would be appreciated.
I have already updated 2007 to sp3 ru8, and have also install 2013 on the new 2012 box.
thanks guys.
We are moving from SBS 2008 to server 2012. We have set up 3 server 2012 boxes, DC, exchange 2013, and sharepoint 2012. We want to transition completely off of exchange 2007 in one shot, and as we only have around 30 mailboxes, i think it is possible, time wise. I havent really seen anything definitive on the exchange 2007 to 2013 move, so any help would be appreciated.
I have already updated 2007 to sp3 ru8, and have also install 2013 on the new 2012 box.
thanks guys.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Best in normal circumstance would be to do a PST move over
You can give a try to move with data or without and check .... dont think there is any doc for migration as of yet
- Rancy
"Merry Christmas and Happy New Year"
You can give a try to move with data or without and check .... dont think there is any doc for migration as of yet
- Rancy
"Merry Christmas and Happy New Year"
You cannot move to Exchange 2013 without PST unless you wait for the next SP for Exchange 2007 which will allow coexistance and enable Server 2012.
Once done, you should be allowed to move the mailboxes.
Once done, you should be allowed to move the mailboxes.
Are you doing a migration or building a new domain?
If you're building a new domain, then you can export the mailboxes (and good luck by the way - I've built a domain from scratch for a network for 15 users instead of doing a migration and that took a week to fully clean up. And they weren't complex, but the profile issues alone sucked up a great deal of time. Moral - DO A MIGRATION! Even if that means you have to start over.)
But, if you are doing a migration, you should know that you can't. Not yet. Exchange 2013 is not yet compatible with 2007 or 2010. Patches aren't expected until the first half of next year (some suggest Q1, but I'd guess if Q1, you're looking at late March). So you might just have to wait.
And it is not best in my opinion to export to PST - Migrate the mailboxes if the exchange servers are on the same domain - once they can be on the same domain.
If you're building a new domain, then you can export the mailboxes (and good luck by the way - I've built a domain from scratch for a network for 15 users instead of doing a migration and that took a week to fully clean up. And they weren't complex, but the profile issues alone sucked up a great deal of time. Moral - DO A MIGRATION! Even if that means you have to start over.)
But, if you are doing a migration, you should know that you can't. Not yet. Exchange 2013 is not yet compatible with 2007 or 2010. Patches aren't expected until the first half of next year (some suggest Q1, but I'd guess if Q1, you're looking at late March). So you might just have to wait.
And it is not best in my opinion to export to PST - Migrate the mailboxes if the exchange servers are on the same domain - once they can be on the same domain.
We are staying with the current domain. I have been able to move 2 test user mailboxes to the exchange 2013 box successfully from the 2007 box. I'm looking for a set-by-step to complete the move to the 2013 CAS, and make sure mail is flowing.
There is no step by step as i said earlier good that you are able to move test with other functionalities and check all is working
- Rancy
- Rancy
Glad they seem to be ok, but bottom line, what you're doing is NOT advisable because the updates to allow both exchange servers to work properly together are not currently available. What your doing, but doing this BEFORE they are available is putting your network at risk of failure.
As for a step by step guide - I seriously doubt you'll find one because currently, there is no supported way of doing it.
Why don't you question us on any issues as you go along and we can assist.
PS: are your connectors working fine?
PS: are your connectors working fine?
Thanks for the advise guys.
Leew, I'm going to take your advise and STOP this process before we endanger our network. I have moved the mailboxes back to the 2007 box, and will wait for RU9.
Do you suggest we wait for 2013 SP1, or should SP3 ru9 on 2007 be good enough?
Leew, I'm going to take your advise and STOP this process before we endanger our network. I have moved the mailboxes back to the 2007 box, and will wait for RU9.
Do you suggest we wait for 2013 SP1, or should SP3 ru9 on 2007 be good enough?
The key is you want to do things that are tested and supported whenever possible. I have had to do unwise things because of changes by others, but if you don't HAVE to move to Exchange 2013, then don't do it UNTIL the move can be supported by Microsoft.
Bottom line - if you want to move to 2013 when the update for 2007 is out, do it. At least then you'll get help if there's a problem. That said, I would really hope you are leveraging virtualization to build test networks to do this in a test environment before actually doing it in a production environment so that you can better understand the issues you might face in your actual network.
Bottom line - if you want to move to 2013 when the update for 2007 is out, do it. At least then you'll get help if there's a problem. That said, I would really hope you are leveraging virtualization to build test networks to do this in a test environment before actually doing it in a production environment so that you can better understand the issues you might face in your actual network.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial