microsot Hi All,, I want to move my live domain from server 2003 stranded with service pack-2 to server 2019 stranded so i want to help with Microsoft team and how to erase TAG for doing this activity kindly suggest. Thanks

It isn't supported to introduce 2019 domain controllers to a 2003 DFL domain. https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/active-directory-functional-levels Also FRS needs to be migrated to DFSR before adding 2019 domain controllers. https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405 So you'll need to do this two-step, first by migrating to 2012 R2 or 2016, removing the 2003 DCs in order to raise DFL to minimum or 2008 R2, then do the FRS-->DFSR migration, then bring in the first 2019 domain controller. To the domain controller migration general steps below; I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then stand up the new guest, patch it fully, license it (you can use evaluations for the interim step), join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one, move on to next one.

Dave Patrick The info on the new Storage Migration Service tool states that it can migrate from Server 2003 directly to Server 2019. Is that info incorrect? Ned made it look so simple in his Ignite presentation. (Though he was using a server far newer than 2003!) So far I'm unable to find any detailed documentation on how to do this with SMS. Any good pointers? The SMS info is here: https://docs.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview The Requirements for Source Servers lists Server 2003 and Server 2003 R2. It would be great to find a step-by-step on how to prepare the Server 2003 system to interact with the SMS tools.

Since a new topic and user I'd start a new thread to maintain forums clarity.

Judging by the title of this thread, I thought I was in the right place. :(

Actually, no its not. This thread was about domain migration. But even so each user's issues are unique and should be asked in a separate thread where the originator can control the thread. Plus by separating the threads user's searching for answers will get more meaningful results.

For upgrade server 2003 Std to 2019 | Microsoft Community Hub

12 Replies

Dave Patrick
MVP
Apr 25, 2019
It isn't supported to introduce 2019 domain controllers to a 2003 DFL domain.

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/active-directory-functional-levels

Also FRS needs to be migrated to DFSR before adding 2019 domain controllers.

https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

So you'll need to do this two-step, first by migrating to 2012 R2 or 2016, removing the 2003 DCs in order to raise DFL to minimum or 2008 R2, then do the FRS-->DFSR migration, then bring in the first 2019 domain controller.

To the domain controller migration general steps below;

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then stand up the new guest, patch it fully, license it (you can use evaluations for the interim step), join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one, move on to next one.
- mohammad96
  Copper Contributor
  Aug 07, 2021
  Thanks for sharing.
- terryamk
  Copper Contributor
  Jan 21, 2021
  Dave Patrick
  
  Hi Dave, I also face the similar scenario: migrating from 2003 to 2019. I find your another reply here:
  https://social.technet.microsoft.com/Forums/windowsserver/en-US/914aa5f5-432c-46e2-b6b2-ce1da0d07091/server-2003-to-2019-alternative-way-to-migrate-users-and-shares
  
  However, when I use dcdiag in my 2003 server, there is only 1 error:
  Starting test: frsevent
  There are warning or error events within the last 24 hours after the
  SYSVOL has been shared. Failing SYSVOL replication problems may cause
  Group Policy problems.
  ......................... (dc name) failed test frsevent
  
  Does it matter? Will it stop my from migrating?
  
  Also, if I have only 1 DC, should I still use repadmin to check the replication? Or I will only use it after I have setup 2012?
  
  Thank you very much
  - mohammad96
    Copper Contributor
    Aug 07, 2021
    As per above what about Group Policy so that are replicated or fails after migration.
- Harry_H3
  Copper Contributor
  May 25, 2019
  Dave Patrick
  The info on the new Storage Migration Service tool states that it can migrate from Server 2003 directly to Server 2019. Is that info incorrect? Ned made it look so simple in his Ignite presentation. (Though he was using a server far newer than 2003!) So far I'm unable to find any detailed documentation on how to do this with SMS. Any good pointers?
  
  The SMS info is here: https://docs.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview The Requirements for Source Servers lists Server 2003 and Server 2003 R2. It would be great to find a step-by-step on how to prepare the Server 2003 system to interact with the SMS tools.
  - Dave Patrick
    MVP
    May 25, 2019
    Since a new topic and user I'd start a new thread to maintain forums clarity.

Forum Discussion

For upgrade server 2003 Std to 2019

12 Replies

Resources