Exchange move from 2011SBS

We are trying to move Exchange 2010 to from the SBS 2011 server to a newly installed Exchange 2010 on a 2008 r2 server.  The 2008 r2 server has Exchange 2010 sp3 installed on the same domain and is not going to be a Domain controller.
How do we move the database and mailbox without eliminating the 2011 SBS domain controller without conflicts for now.  Eventually we will eliminate the 2011 SBS but need to insure Exchange is migrated to the new machine and is working correctly before decommissioning the SBS 2011.  We have internal conflicts on how this should be done
D GCEOAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hello,  I don't generally respond to questions, but hey let's try something new, while I came on to actually post a question and saw yours...

First are some assumptions accurate, e.g.  Your new 08 server is a member server in a new/separate domain 2008 or 2016 Domain?  Your users are logging into what domain now and you plan them to be logged into what domain in the future post the migration of exchange to the new server?

There are several migration plans and options and routes, while taking into consideration the env and goals makes a difference in what route you plan to go in my opinion.
D GCEOAuthor Commented:
The new 2008 r2 server has been added to the current domain (SBS 2011). We have installed Exchange 2010 sp3 on the new 2008 r2 server and have it configured.  We have moved over the Public mailbox and want to move over the live mailbox and then decommission Exchange on the SBS server once Exchange  is up and functioning properly on the 2008 server.  We are hoping to do this prior to moving to the new 2012 r2 Domain and completely eliminating the SBS 2011.
Once we have the Exchange 2010 working on the 2008 standalone server, we will upgrade to Exchange 2013 and add the server to the new domain.  We are hoping to do this without shutting the company down as it will have a severe impact on production.
It's a pretty big project. I've gotta say that seeking guidance on such a significant and risky process on a forum may not be the best option.
Seek professional help from a company with experience of both SBS & Exchange. if you get this wrong you could lose everything.

Also, the phrase "We have internal conflicts on how this should be done" worries me.
Please tell us more on that one, and also provide us with more background on your setup so we can provide better advice.

In general, if you are trying to move away from SBS 2011 you need the following:

A new Domain controller
A new Exchange server
A lot of licensing costs (you'll need new CALs for both AD & Exchange)
A good backup solution.

Assuming these are all viable, why are you migrating to such old versions of Server & Exchange? they are 8+ years old at this point :-)
5 Ways Acronis Skyrockets Your Data Protection

Risks to data security are risks to business continuity. Businesses need to know what these risks look like – and where they can turn for help.
Check our newest E-Book and learn how you can differentiate your data protection business with advanced cloud solutions Acronis delivers

D GCEOAuthor Commented:
My coworker says SBS 2011 won't allow Exchange to move but I am hoping there is a way.  We will stay on the old Domain until we know Exchange is stable on the 2008 member server
D GCEOAuthor Commented:
We have a new Domain controller as well as a new Exchange 2013 server.  I am working with a co-worker who has experience in Exchange and built the current network.  He is not familiar however with migrating from SBS 2011 to a new member server.  He thinks SBS 2011 will not release the mailbox and/or database to a different server but is hoping there is a way to do it.  I personally am new to Exchange so I am tasked to assist with a project where I am not in my comfort zone.
D GCEOAuthor Commented:
By the way, we have the new Domain ready with the exception of getting their old mail into the new Exchange.  In our research, we apparently are better off to get everything working correctly on the old system prior to moving to the new Domain/Exchange system
I had some of the same questions as the poster "Steve", in particular why 08 and why on SBS, why not going hosted etc... even if hybrid, but chose not to ask them... Admittedly SBS  is very limiting in things it may sometimes allow and it restricts, but I honestly have very little experience with SBS, but rather more familiar and comfortable Server and Enterprise infrastructures management and exchange versions.  How many mailboxes are you talking about? How many database and how big?  Again, a
'Steve' commented this can go awry very easily and migrations often time take a lout of planing and forethought. Admittedly, you can piece together a plan using online resources, but you have to be sure to cover and research every possible caveat.   When I'm not driving I'll take a look more at info you provide and see what high level outline can possibly provide to get you started.  Getting a consultant to advise may be worth the money though.
Michael B. SmithManaging ConsultantCommented:
You literally just need to move the mailboxes and copy the configuration from the old server to the new server (there is quite a bit of configuration). At some point your firewall/router will need to be updated to point to the new server.

If you aren't familiar with Exchange, and downtime isn't an option, you should consider buying Jeff Middleton's SwingIt, or retaining a consultant.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
D GCEOAuthor Commented:
We are both familiar with SBS and have worked with it for 20+ years which is why we are leary of how this might "blow up".  Since we cannot create a Trust with SBS we were hoping to find a way to move the database without having to export the existing mailboxes to .PST and importing them into the new user mailboxes which could take a very long time.
The other more complicated way that could work is to make the 2008 server a DC on the SBS network and setup the 2008 exchange server with all the roles then use the built in mail box migration to transfer complete mailbox and settings.  However, this is risky and transferring all FSMO roles is a real pain.  Once it is done and we try to rename the new domain controller we could be down should anything go wrong.
Hoping for a utility or easier way if possible without shutting down the company
D GCEOAuthor Commented:
I looked at Jeff Middleton's SwingIT but it appears at first glance that it is related to going from 2003 to 2011.  Is there another link I should check out?
Michael B. SmithManaging ConsultantCommented:
I suppose I misunderstood. You are standing up an entirely new AD forest?

You CANNOT move an Exchange server from one AD forest to another. It will not work. At all.
D GCEOAuthor Commented:
Yes, however prior to going to the new AD Forest, we want to eliminate the current Exchange on SBS 2011and move it to a 2008 r2 server.  Once this is done, we will upgrade the Exchange 2010 to Exchange 2013.  When this is completed and stable we will consider the new Domain.  We just want to kill SBS 2011 which is why we added a 2008 server and installed Exchange 2010 hoping the new server could be the Exchange server on the existing Domain/Forest.
D GCEOAuthor Commented:
Bottom line, what is the best way to decommission the SBS 2011 on the current Domain/Forest while keeping the Exchange from being eliminated as well
D GCEOAuthor Commented:
I meant decommission the Exchange 2010 on the SBS 2011 server and transfer to Exchange 2010 on 2008 server.  Are we just stuck with exporting .PST files?
Michael B. SmithManaging ConsultantCommented:
If you are going to create a new forest, then you either use third-party tools or do a PST migration.

Most SBS-to-non-SBS migrations go like this:

  1. Buy a new server and install Hyper-V with Windows Server Standard
  2. Install a new DC on one VM - joined to the SBS domain
  3. Install Exchange on the other VM - joined to the SBS domain
  4. Migrate Exchange to the new VM
  5. Decommission Exchange on the old SBS
  6. Move FSMO to the new DC
  7. Decommission the old SBS

But this only works if you keep the same domain.
D GCEOAuthor Commented:
Michael, is any of this making sense to you?  Hopefully my explanation is understandable.  We are actually going on the new Forest/Domain next week.  Please feel to call if it is easier to speak directly.  If so, I will give you my phone number
Michael B. SmithManaging ConsultantCommented:
I'm also in the eastern time zone. I can give you a call about 1pm. Send me your number via a private message.
D GCEOAuthor Commented:
They do not want to keep the same domain.  The company changed their name and want the new domain to reflect the new company name.  In addition, they have change the emails to the new domain name so I have to put the old mailbox and the new one on the new Exchange. :-(
Hello,  Seems expert 'Michael'... got to it before I did and I pretty much agree for a glaring :) wrong:

Most SBS-to-non-SBS migrations go like this:

    Buy a new server and install Hyper-V with Windows Server Standard - NOPE
Buy a small SAN, provision storage(think it out) for VMs, install VMWARE with Windows Server Standard or DC depending on size of infastructure and licensing considerations of what to be deployed moving forward in your VM env...  :)  Sorry not a Hyper-V gal at all; totally reliable VMW all the way.

    Install a new DC on one VM - joined to the SBS domain
    Install Exchange on the other VM - joined to the SBS domain
    Migrate Exchange to the new VM
    Decommission Exchange on the old SBS
    Move FSMO to the new DC
    Decommission the old SBS

If two separate/new Domain create your DC and join new exchange to that DC.
use a migration script, similar to moving boxes from on premise to off premise exchange, and migrate boxes and calendars etc that way.
You're going to have to migrate the profiles for the users, relys on DNS, can use ProfWiz, etc.

Again, 'Mike' seems to have you.. I just couldn't helping contradicting that Hype-V ...:)  Best of luck. Thank you.
D GCEOAuthor Commented:
Funny.  We actually have VMware on the new system. :-)
Michael B. SmithManaging ConsultantCommented:
VMware / Hyper-V / it doesn't matter. Both are enterprise-class virtualization platforms.  If you want to argue "which is better" - I won't take part in that discussion.
To confirm my understanding, you're planning on using a new domain? That makes this a completely different proposition, which is both good and bad :-)

Firstly, this makes some of the migration much easier as you can effectively ignore the SBS system completely. Just get the data out and import back into the new Exchange system. Powershell includes exchange commands for this on SBS2011 but it can be a bit of a pain to set up. Simpler to pay for a 3rd party tool like Ontrack Powercontrols as it means no messing with the SBS server.

Secondly, and more worryingly, you've noted you and your colleagues have a lot of SBS experience. Full-fledged Server/Exchange/domains are quite different to SBS. Managing a non-SBS environment can be a steep learning curve, let alone creating one.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.