Dirk Kotte
asked on
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
2003 32bit?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am able to do directly from SBS 2003 (not R2) to W2016.
Thanks a lot.
Thanks a lot.
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
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
As long as you're at R2 for 2003 the migration will be fine.