steps to migrate DC from W2003 to W2016

Hi all,
i need to migrate from single old W2003 DC to new 2016 DC (new hardware too).
There are no other servers within these LAN ... only 4 Workstations.
Are there special considerations  to do these big step?

please give me some informations how to do the migration.

thanks
LVL 25
Dirk KotteSEAsked:
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.

Cliff GaliherCommented:
2003 is so dead that Microsoft has not put out any supported path for that upgrade.  I've never tried it.  I don't know anybody who has.

Technically the pieces are there.  FRS and 2003 DDL and DFLs are deprecated but still exist even in 2016.  But it is still a huge change.

1) Make a backup.
2) Make a backup
3) MAKE.  A.  BACKUP.  (this is a risky migration and was put off too long.  SO MAKE A BACKUP!)
4) Test your backup.
5) Add your 2016 server to the domain
6) Add the ADDS role.
7) Complete the wizard.
8) Demote the 2003 server.
9) remove the computer from the domain.
10) Bump the DDL and DFL up as high as you can.  Preferrably 2016
11) Migrate from FRS to DFS-R .
12) Done.
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
Lee W, MVPTechnology and Business Process AdvisorCommented:
I think I've had to do a 2003 to 2016 migration (I do a lot of migrations from different versions to different version and I think I've done this combo before... I think) and if memory serves, you cannot go directly from 2003 to 2016.  You'll need to step.  Go from 2003 to 2008 R2 or 2012 to 2016.  I did just do a 2003 to 2012 R2 with no issues.  But support is generally capped at a 10 year period and I think 2003 direct to 2016 was not supported and as such not possible.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Scott CSenior EngineerCommented:
I've done a 2003R2 to 2016 in a lab and it worked correctly.

As long as you're at R2 for 2003 the migration will be fine.
0
Shaun VermaakTechnical Specialist/DeveloperCommented:
2003 32bit?
0
Madison PerkinsConsultantCommented:
I did a sbs2003 to server 2016 and office 365 about 6 months ago.  I had not touched sbs2003 in ten years so I wanted to find a good guide.  https://www.server-essentials.com Well worth the cost of the guide.

I would recommend you p2v the old server and do the mig virtually to iron out the steps.
0
Dirk KotteSEAuthor Commented:
I am able to do directly from SBS 2003 (not R2) to W2016.
Thanks a lot.
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Just a note:
While it *MAY* work going directly from 2003 to 2016, it is NOT supported.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/active-directory-functional-levels

And my perspective is always that you should be doing things in a supported manner whenever possible.  

Even when it SEEMS to work, there could be issues that don't make themselves obvious for a time... and while none of us like calling Microsoft for help, those really tough issues, sometimes you need them and the product teams to get involved. If you do this in an unsupported way, Microsoft has a reasonable option of saying "sorry, you're on your own" which may end up with you rebuilding the domain.

Sometimes you can't escape this potential... others... and I would consider this one, it means you are required to perform extra steps.  2003 to 2012 (or 2008) and then to 2016.

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/active-directory-functional-levels
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 2016

From novice to tech pro — start learning today.