SBS 2003 to 2012 R2 Standard Server Migration

I am getting ready to migrate an SBS 2003 environment to a Server 2012 Standard (not Essentials).  Note that this site is NOT using Exchange 2003 or SharePoint on the SBS 2003 server currently although they are installed - so removing these servers is a consideration.  I have a task list below, if those of you that may have more experience with this may have suggestions.  

Basically I see doing the steps in this order HOWEVER one consideration is installing File and Printer share roles on the new 2012 server BEFORE doing the DCPromo on the 2012 server.  I don't see an issue with that, but most of the forums I find seem to hint at moving data and printers in that 21 days time limit after adding the 2012 AD controller.

Also, does the 21 days  on SBS start after adding the 2012 DC or after moving the FSMO roles?  I've read different reports.

Thanks.


-      Get latest updates on Destination 2012 server

-      Run DCDIAG and REPLMON(?) on SOURCE SBS 2003 SERVER to identify AD issues

-      Run Server 2003 Best Practice Analyzer on SOURCE SBS 2003 SERVER to check for errors.

-      Get notes on Shares and Printers from Source 2003 server

-      Raise the Domain Functional Level to 2003, Raise Forest Level to 2003

-      Remove Exchange and Sharepoint. Sharepoint is in the Add/Remove Programs, need to find out if Exchange can be removed easily.  Exchange not being used nor is SharePoint in the old or new environments.

-      Run AD Role install on  2012 Server.  ADPrep runs during the install of the AD DC role from what I’m reading. Run dcdiag and repadmin after

-      Install File and Print services on Destination 2012 Server

-      Create printer shares for printers

-      Create file shares verify permissions on new share folders, migrate data  to Destination 2012 Server

-      Move FSMO roles to Destination 2012 Server

-      On Source SBS 2003 Server run dcpromo to remove from domain
DarthywAsked:
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.

it_saigeDeveloperCommented:
Looks good, I would also look at migrating DHCP to the 2012 server - Step-By-Step: Migration of DHCP from Windows Server 2003 to Windows Server 2012.

As for your question, *after* you move the FSMO roles.  You can run an SBS (or Essentials) server side-by-side with multiple DC's of any supported OS, for any length of time, so long as the SBS server retains the FSMO roles.

-saige-
0
DarthywAuthor Commented:
Thanks IT_Saige!

I'm familiar with DHCP, so no problem there.  Currently they use Untangle to do DHCP, which is what my boss is more familiar with, but I will present it to him.  We have Windows handling DHCP at a couple sites.

Have you ever uninstalled Exchange from SBS 2003?  In my reading I will use the original install CD, disc 2, which they believe they have.  I just read some various success and failure stories about removing it.  Obviously we have backups of the server if something hoses, but I'm curious if removing Exchange could be as potentially difficult as my research indicates or it that's the exception.  They don't use Exchange and likely wouldn't on a server down the road, so worse to worse I can leave it and AD will carry over the Exchange objects, but if it's not usually a big hassle I'd like to try to remove it and Sharepoint (Which I can do via Add/Remove Programs)
0
it_saigeDeveloperCommented:
If I recall correctly, the only *real* sore spot with removing Exchange from SBS 2003 had to deal with an administrative mailbox.  It was almost like a catch*22, you needed the mailbox to remove the collaborative roles, but needed to remove the mailbox to remove exchange.

Go ahead and start the uninstall process for Exchange and just report any errors you get.  There are plenty of Experts here that have dealt with this in the past.

-saige-
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
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

DarthywAuthor Commented:
Thanks.  OK.  I plan to try it tonight or tomorrow morning.
0
DarthywAuthor Commented:
Oh, do I really need to deal with removing SharePoint from the SBS 2003 server.  I must have found one article that sorta mentioned it when researching, but I'm not finding much or any suggesting removing SharePoint, just Exchange if it is unused on SBS2003.
0
DarthywAuthor Commented:
Overall, good success with the migration from SBS 2003 (no longer using Exchange) to 2012 Standard.  I put my basic steps below in case someone else needs it.  Thanks for the assist it_saige!

1. Made sure 2003 SBS server had SP2, ran Best Practice Analyzer to check for any major issues (found a couple minor warnings, nothing to deal with.)  Ran DCDiag on SBS 2003 server, and no errors.

2.  Since users weren't using Exchange on SBS2003 on the old server went into ADUC, right-clicked user accounts and selected Exchange Tasks, then delete mailboxes to end all mailbox connections.  Opened Exchange System Manager and  ran a mailbox cleanup to make sure no mailboxes had connections.

3. Installed Active Directory Services on the new 2012 Standard server.  Then promoted it to domain controller, global catalog w/ DNS.  Ran DCDiag and Repadmin to check for errors.  Note that there were initially some errors when checking after it was all complete, but a couple hours later tests were good.  Ran BPA on the 2012 server for AD.  Note that there was no Forestprep or Domainprep as those occur automatically on promo of a 2012 server.  Be sure to use an admin account in the Enterprise Admins and Schema Admins group.

4. Installed print and file services on the 2012 server.  DHCP migrated as well.   Migrated the printers and user shares.  We adjusted the logon scripts on the 2003 SBS server to point to the shares on the new 2012 server, then removed the shares on the 2003 server.

5.  After a day or so making sure the users were good, I uninstalled Exchange 2003 by going to Add/Remove Progs, and selecting SBS Server in the list.   Choose Change/Remove.  Chose Remove next to Exchange when prompted.  Rebooted.  Gave replication a chance.

6. Moved FSMO roles to 2012 server.  Then I shut down the 2003 server long enough to test logons, password changes, etc.  Be sure the DHCP services are pointing users to the new server for DNS or you'll have slow logons.

7.  Then DCPromoed the 2003 server, - after booting it up again, DCDiag and Repadmin to check for issues.  shutdown the old server.  Tested the new.  

Those are the key steps above.  Note that I didn't really run into any complications, thankfully.  All told though it was hours and hours of work.  Not something to cutover in a really short time if you want to be careful.
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
SBS

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.