SOLVED

Upgrading 2012 R2 to 2019 Domain Controller / DFRS / DNS / DHCP

%3CLINGO-SUB%20id%3D%22lingo-sub-2873230%22%20slang%3D%22en-US%22%3EUpgrading%202012%20R2%20to%202019%20Domain%20Controller%20%2F%20DFRS%20%2F%20DNS%20%2F%20DHCP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2873230%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%20Looking%20for%20some%20advice%20been%20a%20while%20since%20I%20have%20had%20to%20do%20an%20upgrade%20of%20the%20domain%20controllers%20but%20I%20just%20want%20to%20get%20people%20advice%20on%20the%20plan%20I%20have%20put%20in%20place%20to%20do%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrent%20setup%20is%20as%20follows%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20width%3D%22426px%22%3E%3CTBODY%3E%3CTR%3E%3CTD%20width%3D%2281.1719px%22%3E%3CP%3EDomain%20Controller%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2282.3125px%22%3E%3CP%3EOperating%20System%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2284.0625px%22%3E%3CP%3EFunctional%20Level%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2258.4688px%22%3E%3CP%3EFRS%20%2F%20DFRS%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2278.9688px%22%3E%3CP%3EOther%20Functions%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2240.0156px%22%3E%3CP%3EROLE%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2281.1719px%22%3E%3CP%3EDC1%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2282.3125px%22%3E%3CP%3EMicrosoft%20Windows%20Server%202012%20(64-bit)%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2284.0625px%22%3E%3CP%3EWindows%20Server%202012%20R2%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2258.4688px%22%3E%3CP%3EFRS%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2278.9688px%22%3E%3CP%3EDNS%20%2F%20DHCP%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2240.0156px%22%3E%3CP%3EPDC%20%2F%20RID%20POOL%20MANAGER%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2281.1719px%22%3E%3CP%3EDC2%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2282.3125px%22%3E%3CP%3EMicrosoft%20Windows%20Server%202012%20(64-bit)%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2284.0625px%22%3E%3CP%3EWindows%20Server%202012%20R2%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2258.4688px%22%3E%3CP%3EFRS%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2278.9688px%22%3E%3CP%3EDNS%20%2F%20DHCP%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2240.0156px%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2281.1719px%22%3E%3CP%3EDC3%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2282.3125px%22%3E%3CP%3EMicrosoft%20Windows%20Server%202012%20(64-bit)%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2284.0625px%22%3E%3CP%3EWindows%20Server%202012%20R2%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2258.4688px%22%3E%3CP%3EFRS%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2278.9688px%22%3E%3CP%3EDNS%20%2F%20DHCP%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2240.0156px%22%3E%3CP%3ESCHEMA%20MASTER%20%2F%20DOMAIN%20NAMING%20MASTER%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%20width%3D%2281.1719px%22%3E%3CP%3EDC4%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2282.3125px%22%3E%3CP%3EMicrosoft%20Windows%20Server%202012%20(64-bit)%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2284.0625px%22%3E%3CP%3EWindows%20Server%202012%20R2%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2258.4688px%22%3E%3CP%3EFRS%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2278.9688px%22%3E%3CP%3EDNS%20%2F%20DHCP%3C%2FP%3E%3C%2FTD%3E%3CTD%20width%3D%2240.0156px%22%3E%3CP%3EINFRASTRUCTURE%20MASTER%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20aim%20is%20to%20upgrade%20all%20servers%20to%202019%20and%20upgrade%20their%20functional%20level%20to%202016R2%20and%20also%20if%20possible%20or%20easier%20keep%20the%20existing%20IP's%20and%20Names.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThings%20I%20need%20to%20try%20and%20avoid%20if%20possible%3A%3C%2FP%3E%3CP%3E-%20No%20downtime%20(or%20minimal)%3C%2FP%3E%3CP%3E-%20No%20impact%20on%20live%20services%20if%20possible%20i.e%20clients%20etc%3C%2FP%3E%3CP%3E-%20In%20place%20upgrading%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20In%20terms%20of%20the%20high%20level%20plan%20it%20was%20as%20follows%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Upgrade%2FMigrate%20to%20DFRS%20on%20all%20existing%20DC's%3C%2FP%3E%3CP%3E-%20Create%204%20new%20servers%20running%202019%20i.e%20DCNEW1%2C%20DCNEW2%2C%20DCNEW3%2C%20DCNEW4%20install%20Active%20directory%20and%20add%20as%20a%20DC%20Member%3C%2FP%3E%3CP%3E-%20Migrate%20the%20FSMO%20Roles%26nbsp%3B%20to%20the%20corresponding%20new%20server%20i.e%20DC1%20%26gt%3B%20DCNEW1%20DC2%20%26gt%3B%20DCNEW2%20etc%20etc%3C%2FP%3E%3CP%3E-%20Migrate%20DHCP%20%2F%20DNS%20to%20an%20other%20server%3C%2FP%3E%3CP%3E-%20Demote%20the%20old%20DC's%20from%20AD%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Rename%20%2F%20Re-IP%20the%20new%20DC's%20to%20the%20old%20DC's%20name%20and%20IP%20address.%20(I%20believe%20I%20will%20need%20to%20demote%20the%20new%20DCs%20i.e%20DCNEW1%20and%20move%20the%20FSMO%20Roles%20to%20another%20server%2C%20rename%20and%20re-ip%20the%20DC%20to%20DC1%20give%20it%20the%20same%20ip%20address%2C%20add%20it%20as%20a%20DC%20member%20and%20then%20move%20the%20FSMO%20roles%20back%20onto%20it%20and%20then%20repeat%20this%20process%20for%20each%20other%20DC)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20questions%20i%20have%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20I%20really%20need%20to%20upgrade%20to%20DFRS%201st%20%3F%3F%20or%20can%20this%20be%20avoided%3F%3C%2FP%3E%3CP%3EIn%20a%20very%20high%20level%20plan%2C%20does%20this%20sound%20about%20right%3F%20or%20am%20I%20overthinking%20or%20missing%20anything.%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20much%20slicker%20way%20to%20achieve%20my%20goal%3F%3C%2FP%3E%3CP%3EIn%20order%20to%20move%20a%20DHCP%20server%20I%20recall%20just%20exporting%20the%20DHCP%20scopes%20exporting%2Fimporting%20using%20%22%3CSTRONG%3E%3CU%3Enetsh%20dhcp%20server%20export%20C%3A%5Cdhcp.txt%20all%22%3C%2FU%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EIf%20I%20want%20to%20move%20DNS%20is%20there%20anything%20else%20i%20need%20to%20consider%20other%20than%20installing%20the%20DNS%20Role%3F%3C%2FP%3E%3CP%3EHow%20would%20anyone%20else%20approach%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHelp%20appreciated!%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2873230%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDHCP%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDNS%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpgrade%20Process%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2876076%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrading%202012%20R2%20to%202019%20Domain%20Controller%20%2F%20DFRS%20%2F%20DNS%20%2F%20DHCP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2876076%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%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%20move%20on%20to%20next%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%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi All, Looking for some advice been a while since I have had to do an upgrade of the domain controllers but I just want to get people advice on the plan I have put in place to do this:

 

Current setup is as follows:

 

Domain Controller

Operating System

Functional Level

FRS / DFRS

Other Functions

ROLE

DC1

Microsoft Windows Server 2012 (64-bit)

Windows Server 2012 R2

FRS

DNS / DHCP

PDC / RID POOL MANAGER

DC2

Microsoft Windows Server 2012 (64-bit)

Windows Server 2012 R2

FRS

DNS / DHCP

 

DC3

Microsoft Windows Server 2012 (64-bit)

Windows Server 2012 R2

FRS

DNS / DHCP

SCHEMA MASTER / DOMAIN NAMING MASTER

DC4

Microsoft Windows Server 2012 (64-bit)

Windows Server 2012 R2

FRS

DNS / DHCP

INFRASTRUCTURE MASTER

 

The aim is to upgrade all servers to 2019 and upgrade their functional level to 2016R2 and also if possible or easier keep the existing IP's and Names. 

 

Things I need to try and avoid if possible:

- No downtime (or minimal)

- No impact on live services if possible i.e clients etc

- In place upgrading 

 

So In terms of the high level plan it was as follows:

 

- Upgrade/Migrate to DFRS on all existing DC's

- Create 4 new servers running 2019 i.e DCNEW1, DCNEW2, DCNEW3, DCNEW4 install Active directory and add as a DC Member

- Migrate the FSMO Roles  to the corresponding new server i.e DC1 > DCNEW1 DC2 > DCNEW2 etc etc

- Migrate DHCP / DNS to an other server

- Demote the old DC's from AD 

- Rename / Re-IP the new DC's to the old DC's name and IP address. (I believe I will need to demote the new DCs i.e DCNEW1 and move the FSMO Roles to another server, rename and re-ip the DC to DC1 give it the same ip address, add it as a DC member and then move the FSMO roles back onto it and then repeat this process for each other DC)

 

Some questions i have:

 

Do I really need to upgrade to DFRS 1st ?? or can this be avoided?

In a very high level plan, does this sound about right? or am I overthinking or missing anything. 

Is there a much slicker way to achieve my goal?

In order to move a DHCP server I recall just exporting the DHCP scopes exporting/importing using "netsh dhcp server export C:\dhcp.txt all"

If I want to move DNS is there anything else i need to consider other than installing the DNS Role?

How would anyone else approach this?

 

Help appreciated!

Thanks

 

 

4 Replies

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 move on to next one.

 

 

 

 

 

Just checking if there's any progress or updates?

--please don't forget to upvote and mark answers if the reply is helpful--

 

Thanks @Dave Patrick

 

In terms of the steps to migrate DHCP / DNS does this look ok aswell?

 

Regards

Sam 

best response confirmed by Samuel_Caunt (New Contributor)
Solution

DNS is integrated within active directory. DHCP is a separate role. You could accept this one as best response and start a new thread about DHCP server installation / migration.