Migration steps: SBS 2011 Standard to Win 2012 Standard with Essentials Experience

Hello,

I’m looking for clarification on a couple steps in migration of a SBS 2011 Standard server to a new server running Win 2012 Standard with Essentials Experience enabled. I’ve reviewed the migration steps in the Microsoft TechNet article below-

https://technet.microsoft.com/en-us/library/dn408633.aspx

This client is no longer using the SBS Exchange Server; they are on Office 365. I’ve disabled all user mailboxes on SBS Exchange, and they are not using public folders. They do not use folder redirection, and the SBS server is not sharing printers. The SBS server will be wiped after migration.

The TechNet article mentions that Exchange on the SBS server will have to be removed if Office 365 integration with Essentials Experience will be used, however I don’t see it listed as a step. I want to make sure I have the main sequence right-

1. Promote Win 2012 server as an additional AD server in the existing SBS domain (done, and sysvol/netlogon shares on Win 2012 server verified)
2.      Add Windows Server Essentials Experience role to Win 2012 Standard server
3.      Transfer FSMO roles to Win 2012 server
4.      Join computers to the new Windows Server 2012 R2 Essentials server
5.      Move settings and data to Win 2012
6.      Uninstall Exchange Server 2010 from SBS server
7.      Remove AD Certificate Services from SBS server
8.      Demote SBS server
9.      Remove the SBS server from the network
10.      Perform post-migration tasks on Win 2012 server: DNS entries, shared folders
11.      Configure Office 365 integration component in Win 2012 Essentials

Is this sequence correct?

What about removing SBS 2011 from Programs and Features on the source server? Is that necessary only if the source server will be re-purposed with the existing Win 2008 R2 installation?

Thanks!
apmartinAsked:
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.

Larry Struckmeyer MVPCommented:
SBS cannot be used as a non-sbs server so your last question does not apply.  I would follow the migration documents and or your outline, but I would not skip any part that is applicable to your situation.  Realize that no document can cover every possible scenario, so you should modify the steps to meet your requirements.
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
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 2012

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.