SBS2003 Migration: An Overview

This is 1 of several questions we need to ask about migrating from Small Business Server 2003 to a standard Domain running 1 server with Server 2012 R2. So please limit your answer to this one specific question:

We have added the new member server, moved the Enterprise accounting and antivirus. Exchange E-mail has moved to the cloud. What is the best way to go from here?  ...In stages? ...One big move?   ...A link with details would be helpful.

Briefly, we do not use some of the SBS2003 subsystems like WSUS, SharePoint, Remote Desktop Services (RRAS), and DFS/FRS. But we do have user folders, shared folder with group permissions, and synchronized document folders.
Who is Participating?
Lee W, MVPTechnology and Business Process AdvisorCommented:
In this scenario, I wouldn't bother virtualizing the SBS server - it's a waste of time - you're getting rid of it anyway.  Setup a new server running Windows Server 2012 R2 with the Hyper-V role.  Create a VM and install Windows 2012 R2.  Promote it to a DC.  DO NOT transfer the FSMO roles yet.  migrate everything else at your leisure to the new server (VM).  Once you're done and the SBS server isn't consciously being used for ANYTHING, you can transfer the FSMO roles THEN and ONLY THEN. (Once transferred, you have 3 weeks to complete the migration - then the SBS Server starts shutting down.  If you're not migrating to another SBS-class system (such as SBS 2008, SBS 2011, SBS 2011 Essentials, 2012 Essentials) then you can take your time.  It's important to understand that SBS *MUST* be the FSMO role holder.  If there are no other SBS servers on the network, then there is no conflict with which one holds the roles.

WARNING: I'm going to be blunt.  If you don't have experience doing this, if you don't know how to transfer roles and services, then you are not, in my opinion qualified to do this.  Hire a professional experienced in doing this.  Or spend 40+ hours in a lab/test environment learning it yourself.  Doing it right the first time will help ensure you have a positive overall experience... doing things wrong could cost you BIG in fixing it later
This is a typical scenario that I encounter all the time. I usually install a 2012 R2 Hyper-V host then I virtualize the existing SBS server. Next I setup the new 2012 R2 Domain Controller in the same domain and move all my FSMO roles to the new server. I try to move as much as possible in a 'big bang' approach but I still keep the SBS running for a while unitl everything has been moved and then I demote the old 2003 SBS DC and turn it off.  

As suggested, try to move e-mail to the cloud, use InTune and only use your local server for basic things like group policy and file shares etc.
David Johnson, CD, MVPOwnerCommented:
please note that folder redirection requires that the current folder be available to allow the clients to move to the new folder (you can use robocopy to speed up the process
USER8719Author Commented:
Thanks.  We have transferred roles before, just not with SBS. (Seems like the VM for DC is a waste of time).
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.

All Courses

From novice to tech pro — start learning today.