Server 2003 to 2012 R2 AD and server migration

Going over what I need to prepare for migrating from 2003 AD/DNS to 2012 R2 AD/DNS and was wanting any suggestions, do's/don't's but after this is done I have existing LUN that contains all the data the current 2003 server is sharing.

What happens to the disk provisioned to the 2003 server currently?
Does the migration take care of this too?
Do/can I attach the VMDK files to the 2012 server and move on?
LVL 1
HaroldNetwork EngineerAsked:
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.

Scott CSenior EngineerCommented:
Here is my 2003 to 2012 checklist

Migrating 2003 to 2012
Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 network
http://blogs.technet.com/b/canitpro/archive/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-2003-network.aspx

 Migrating Windows Server 2003 FSMO Roles To Windows Server 2012 R2
http://blogs.technet.com/b/canitpro/archive/2015/02/11/step-by-step-migrating-windows-server-2003-fsmo-roles-to-windows-server-2012-r2.aspx

 Migrating DHCP From Windows Server 2003 to 2012 R2
http://blogs.technet.com/b/canitpro/archive/2014/11/26/step-by-step-migrating-dhcp-from-windows-server-2003-to-2012-r2.aspx


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.

If 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.

I'll let someone with more experience with the disk provisioning issues answer.
1

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
Ganesamoorthy STech LeadCommented:
0
HaroldNetwork EngineerAuthor Commented:
@ScottCha: I'm guessing this is a none production migration? Will all the machines have to be reconnected to the new AD server?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

HaroldNetwork EngineerAuthor Commented:
Can someone tell me, can I do this during production?
Does the server come down at all?
Will mapped shared storage come over with AD migration?

Thanks
0
Scott CSenior EngineerCommented:
This is done during production.  I did the above during business hours and nobody was affected.   The only thing that was done after hours was a share/file copy of the accounting software data.

The old server doesn't need to come down at all until it is ready to be demoted as a DC.

Sorry didn't answer this earlier, missed it in all of the emails I get.
0
HaroldNetwork EngineerAuthor Commented:
So my question here "Will mapped shared storage come over with AD migration?" Is I have to move the storage?

I was hoping I could attach the VMDK files to the VM, no?
0
Scott CSenior EngineerCommented:
Yes, you should be able to attach the VMDK to the new server and continue, however, this is something that I would do after-hours so as to not interrupt production.  Or if something doesn't go as planned, you have time to fix or back out.

In my case there was no external storage so it had to be copied.
0
HaroldNetwork EngineerAuthor Commented:
Gotcha, thanks much!!
0
HaroldNetwork EngineerAuthor Commented:
Thanks again for your help!!
0
Scott CSenior EngineerCommented:
Sure thing.  Message me if I miss another post.
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
Windows Server 2003

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.