migration sbs2003 to 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-1992655%22%20slang%3D%22en-US%22%3Emigration%20sbs2003%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1992655%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20have%20some%20project%20to%20do%3C%2FP%3E%3CP%3Eon%20my%20customer%20site%20we%20have%20%3A%3C%2FP%3E%3CP%3E1.%20sbs%202003%20with%20just%20this%20roles%20-%20dc%2Bdhcp%2Bdns%2Blot%20of%20shared%20folders%20(fileserver)%20(without%20exchange%20move%20365)%3C%2FP%3E%3CP%3E2.%20another%20server%202012%20r2%20for%20second%20DC%26nbsp%3B%3C%2FP%3E%3CP%3E3%20i%20create%20new%202%202019%20servers%26nbsp%3B%3C%2FP%3E%3CP%3Ewhat%20is%20the%20best%20way%20to%20migrate%20without%20lost%20all%20map%20users%20drive%20and%20demote%20sbs%202003%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1992655%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1993514%22%20slang%3D%22en-US%22%3ERe%3A%20migration%20sbs2003%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1993514%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20two%20prerequisites%20to%20introducing%20the%20first%202019%20domain%20controller%20are%20that%20domain%20functional%20level%20needs%20to%20be%202008%20or%20higher%20and%20older%20sysvol%20FRS%20replication%20needs%20to%20have%20been%20migrated%20to%20DFSR%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FStorage-at-Microsoft%2FStreamlined-Migration-of-FRS-to-DFSR-SYSVOL%2Fba-p%2F425405%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FStorage-at-Microsoft%2FStreamlined-Migration-of-FRS-to-DFSR-SYSVOL%2Fba-p%2F425405%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'd%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20verify%20health%20%3CSTRONG%3Ecorrecting%20all%20errors%20found%3C%2FSTRONG%3E%20before%20starting%20%3CSTRONG%3Eany%3C%2FSTRONG%3E%20operations.%20Then%20stand%20up%20the%20new%202019%2C%20patch%20it%20fully%2C%20license%20it%2C%20join%20existing%20domain%2C%20add%20active%20directory%20domain%20services%2C%20promote%20it%20also%20making%20it%20a%20GC%20(recommended)%2C%20transfer%20FSMO%20roles%20over%20(optional)%2C%20transfer%20pdc%20emulator%20role%20(optional)%2C%20use%20dcdiag%20%2F%20repadmin%20tools%20to%20again%20verify%20health%2C%20when%20all%20is%20good%20you%20can%20decommission%20%2F%20demote%20old%20one.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello everyone 

i have some project to do

on my customer site we have :

1. sbs 2003 with just this roles - dc+dhcp+dns+lot of shared folders (fileserver) (without exchange move 365)

2. another server 2012 r2 for second DC 

3 i create new 2 2019 servers 

what is the best way to migrate without lost all map users drive and demote sbs 2003 

thanks

1 Reply

The two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYS...

 

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, 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 again verify health, when all is good you can decommission / demote old one.