SBS 2008 to Server 2012 R2 Standard

Hi all,

I'm preparing to do a migration of SBS 2008 (DNS, DHCP, Exchange, AD, Fileserver and a few apps that I know the ins and outs of) to Server 2012 R2.  I've got the 2012 R2 host set up and updated, and currently am installing 4 VM's to manage the roles that I need.  My current outline looks like this:

Client-DC:  AD, DNS, DHCP
Client-FS: fileserver, minor apps
Client-EX:  Exchange server (and related)
Client-APP:  bigger apps, SQL

I've looked around at other people's migration questions and blogs, and have determined the following procedure (criticism and links to other useful / disaster preventative notes would be appreciated!):

1)      Install AD Services & DNS.
a.      Forest prep the SBS 2008 to new schema
b.      Join existing domain and promote to DC, no role migration at this point. (happy to commit and just roll this over at this point, ideas       welcome).
c.      Install and Configure DNS, DHCP etc.
d.  Migrate exchange 2007 to Exchange 2013 via instruction set here:
2)      Install print services, configure & deploy via GPO. Remove old print services form SBS
3)      Use RoboCopy to replicate user files between SBS and 2012, switch users to use this as the filestore.
4)      Uninstall Exchange from SBS (if not done already)
5)      Move AD roles (must complete within 21 days).

Let me know what you think, and if you have any useful in depth details for me to review before I get started any further - post 'em!  I love to read before I start.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Scott CSenior EngineerCommented:
I think you have just about everything covered.  I recently did an Server 2003 to Server 2012 R2 migration and pretty much followed the steps you listed above with the exception of Exchange...the client wasn't using Exchange.

Once you have DHCP set up on the new server you can run the following command to make sure you are getting addresses from the new server.

ipconfig /all | find /i "DHCP server"

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
browningitSysadminAuthor Commented:
Even with the best of plans, I've still encountered issues.  I'm going to close this and open a new question about specific events.
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
Windows Server 2008

From novice to tech pro — start learning today.