migrating from sbs 2008 to exchange 2010 2008 r2

Posted on 2014-02-19
Last Modified: 2014-03-05
We need to migrate from an SBS2008 box to 2008 r2 box running exchange 2010. We also plan on completely getting rid of the sbs box. I feel that I have two options for this. Either I could just build a 2008 r2 server running exchange 2010 and move all mailboxes to it. Then, create a new domain controller and transfer all FSMO roles from the sbs box to the new DC. Then gracefully decommission the sbs box.

The other option is to do an sbs Migration where I create a "tempdc" - take that tempdc offsite, seize all of the FSMO roles - manually remove the old SBS box, and then create my new 2008 r2/exchange 2010 server. Then Forklift the exchange database from the sbs box to my tempdc, clean it up and start moving mailboxes from the tempdc to the final dc. This option pretty much allows me to eliminate Sbs very quickly.

Based on these two options, I think I'd rather go with option one because the most important thing with this client is downtime and a forklift would probably add a good 4 hours  considering I'm dealing with a 200gb database.

Any thoughts on the best option?
Question by:StarfishTech
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
LVL 16

Accepted Solution

gurutc earned 167 total points
ID: 39870263

I like option 1 because it's the most 'little steps' instead of fewer 'big steps' where things could go more wrong.

- gurutc
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 167 total points
ID: 39871154
Why are you even considering this:

"The other option is to do an sbs Migration where I create a "tempdc" - take that tempdc offsite, seize all of the FSMO roles - manually remove the old SBS box, and then create my new 2008 r2/exchange 2010 server"

Huge downtime, huge risk, for no reason at all.

You can do a graceful migration of Exchange from SBS, there are no limits there. The only time you come in to limits is when you are getting ready to remove the SBS server and have to move the FSMO roles.

I don't think I would even consider anything else.


Author Comment

ID: 39871216
Thank you Simon. My concern is this - we have a lot of mailboxes and a lot of users that access Outlook Anywhere and use mobile devices. Are concern is, when we move a mailbox to the new server, is outlook smart enough to redirect to the new server? Also, I take it when a mailbox is moved, OWA/mobile devices will be broken until we repoint OWA traffic in our firewall to the new server?
Revamp Your Training Process

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action.

LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39873023
As long as the ld and the new server is alive, then Outlook will redirect automatically.
ActiveSync and Outlook Anywhere will proxy to the old version of Exchange. OWA will want to redirect - you will need to have two unique host names, SSL certificates and IP addresses for coexistence. This is covered in the client access migration information on TechNet.

LVL 74

Assisted Solution

by:Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy earned 166 total points
ID: 39889797
Be aware, that if you migrate to single server which is running both as your DC and hosting Exchange you are creating an unsupported scenario.  SBS is the only supported scenario which can be both a DC and host Exchange.

Since Server 2008 R2 license allows for 4 instances to be installed, I'd suggest that you deploy TWO virtual machines, one as your DC and the other with Exchange.  The DC doesn't require much in the way of resources (it should do fine with 512MB of RAM if it's only acting as the DC) which allows you to allocate the majority of resources to your Exchange Server.

LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39890118
"migrate to single server which is running both as your DC and hosting Exchange you are creating an unsupported scenario"

That isn't correct. Microsoft support Exchange on a domain controller, but it isn't recommended and they strongly discourage it.

Windows 2008 R2 ENTERPRISE allows four VMs per box, standard is 1:! where the host must only be doing HyperV hosting. Windows 2012 would be a better choice as that does allow two VMs per physical box on standard edition, allowing the DC and Exchange function to be split out.

LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 39890168
True enough.  What I was thinking regarding licensing though is Server 2012 downgraded to 2008R2, which is only 2 VM's, not the four I mentioned -- but still sufficient for this to work.

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Incremental backup to a shared folder 3 51
exchange, owa 4 43
SyncBackPro or easeUS Todo Backup 16 57
DNS logs 1 19
This article explains how to install and use the NTBackup utility that comes with Windows Server.
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This video discusses moving either the default database or any database to a new volume.

738 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