SBS2003 to 2012r2 migration


I am migrating a SBS2003 server with Exchange to a 2012r2 server without exchange. We abandoned the Exchange years ago. What roles do I have to enable on the new server prior to promoting it? If I recall my last migration correctly I was able to perform the promotion to DC during the work day with no user problems. That was going from a 2000 to a 2008r2. My plan is to promote the new server to DC then transfer all the files overnight and finally demote the old server to a member server before finally removing it entirely. Does this sound like the right path? Is there anything I should consider prior to starting? Thanks in advance for any help.

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.

NinjaStyle82Systems AdministratorCommented:
You should be all set, you just install ADDS role and after it's installed you will see a notification in server manager to promote. Should be OK to promote during the day. After you demote the old server raise the forest and domain functional level and verify event logs etc. I have seen a few people with FRS errors in the event log after adding a 2012 R2 DC if you haven't migrated to DFSR.
NinjaStyle82Systems AdministratorCommented:
Also, don't forget to update any drive mappings to the new server name!
Scott CSenior EngineerCommented:
Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 network

 Migrating Windows Server 2003 FSMO Roles To Windows Server 2012 R2

 Migrating DHCP From Windows Server 2003 to 2012 R2

You will need to make sure the domain and forest level are both at 2003 before you can promote the 2012 server to a DC.

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
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Keystone49Author Commented:
Great! Thanks for the info. My domain and forest level are both 2000. Ok to just raise the level to 2003?
Scott CSenior EngineerCommented:
Yes.  I did this for one of my customers last week.  I informed them what I was doing but they didn't notice a thing.
Lee W, MVPTechnology and Business Process AdvisorCommented:
Your existing server is an SBS server.  You DO NOT want to transfer the FSMO roles until you are finished with everything else and BEFORE you demote it.  Otherwise, you start a clock that in 3 weeks will shut down the SBS Server.

SBS has NO PROBLEM with other servers or DCs so long as they are NOT SBS-class systems (including Essentials class systems).  So setup the new server as a DC, migrate your files, printers, apps, etc. and when you are ready to demote, run DCDIAG /C /E /V and correct any unexplained errors and THEN Transfer the FSMO roles and DEMOTE the existing SBS server.
Lee W, MVPTechnology and Business Process AdvisorCommented:
Don't forget to remove SBS Group Policies that will no longer apply (I would suggest you consult SBS 2003 migration to 2008/2011 documentation from Microsoft and simply skip the non-applicable parts.
Keystone49Author Commented:
Well it was going great but now I'm having DHCP problems. Went through the migration and my server is showing a bad IP ( for the dhcp and my clients can't connect to the new server now. Should be Any help cause I'm pulling my hair out. Thanks.
Scott CSenior EngineerCommented:
If you go back to your original DHCP server does it work?  If so, just set the new one up the same, turn off the old DHCP server then start up the new one.
Keystone49Author Commented:
Well I was starting to have problems with the old one. So I recreated it on the new server created the scope and when I went to renew on a client I get message unable to contact dhcp server. Weird thing is when I was setting up server options and I would type in the name of the server it would resolve to the 169. Address. I typed in the ip manually but I'm guessing that is part of my problem.
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.