What is the best way to migrate SBS2008 to server2012 in VM?

I am replacing our SBS2008 machine with a new server.  I have the hardware on order, overkill for our small operation, but I got a great deal (dell Poweredge 720xd, dual xeon cpu/12- 2TB hard drives/ 128 GB ram).

We currently have about 65 users (which is why I need to get rid of SBS2008).

Would it be ok to configure the new server to boot into server2012, then have 2 instances of VM running (one for the DC and one for the Exchange)

This was my initial push to my cfo to spend the extra money on one good server vs 2 that we would be out of space in 3 years.

But now, I've read a lot of posts that 50% say no, 50% say it's ok.  Some say to run the DC on the boot drive and just run one VM for exchange.

Any suggestions/comments/concerns?  I've heard that migrating the data from SBS can also be a real pain, so anyone with help in that regard, I'd love to hear from you.
shawnfraziAsked:
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
DO NOT run ANYTHING on a Host server - your initial plan is the way to go.  You just don't want to join the host server to the domain (although in 2012, domain join of the host is supposed to be less problematic - originally, if you think logically, your problem was that the DC started AFTER the host server - so the host server could NEVER get certain group policies since many initiate only at boot and if the DC failed, you could have problems logging in with a domain account since the host wouldn't have a DC to authenticate against. Again, most of this is supposed to have been resolved).

As for migrating, I've not done an SBS to non-SBS 2012 migration, however, I wouldn't expect too many issues.  For migration purposes, just treat everything as if it's NOT SBS.  Migrate from one exchange version to another, from one server to another.   One note: DO NOT move the FSMO roles off the SBS server until the VERY LAST STEP.  It will start a 21 clock that when it expires, will have the SBS server shutting down every hour or two.  For a migration to a non SBS environment, there's NO REASON to migrate the FSMO roles until the last step making this a potentially painless migration.

BTW, start with a DCDIAG /C /E /V on the network before even promoting the 2012 system to be a DC.
0

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
shawnfraziAuthor Commented:
Thanks for the response, makes perfect sense.  This is going to be my first VM, always had physical servers before, so it's a learning experience.
0
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
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.