Adding a Server 2019 as secondary DC to an exisitng 2012 R2 domain

Question

Hello, I am looking for guidance in adding a new Server 2019 as a secondary DC to an existing 2012 R2 domain. Does anyone have a steps by step procedure?
Thank you

Answer 1

Please run;

Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt

then put unzipped text files up on OneDrive and share a link.

Answer 2

Hi,
The minimum requirement to add a Windows Server 2019 Domain Controller is a Windows Server 2008 functional level. The domain also has to use DFS-R as the engine to replicate SYSVOL.
To raise the forest functional level
Open Active Directory Domains and Trusts. To open Active Directory Domains and Trusts, click Start , click Administrative Tools , and then click Active Directory Domains and Trusts .
In the console tree, right-click Active Directory Domains and Trusts , and then click Raise Forest Functional Level .
In Select an available forest functional level , select the value and then click Raise .

If you want to check if the DFSR is used for for the Sysvol replication , the following command can be used:
Command：
dfsrmig.exe /getglobalstate
If the Result: 3 (ELIMINATED) the DFSR is used for the replication.
If not, FRS should be migrated to DFSR:
https://learn.microsoft.com/en-us/windows-server/storage/dfs-replication/migrate-sysvol-to-dfsr

Then before add the new dc , we should also make sure everything is working well, following command for your reference :
Dcdiag /v >c:\dcdiag1.log
Repadmin /showrepl >C:\repl.txt
Repadmin /showreps * 

Last ,the new DC can be added , following for your reference:
https://www.petenetlive.com/KB/Article/0001262(third-party link)
This response contains a third-party link. We provide this link for easy reference. Microsoft cannot guarantee the validity of any information and content in this link.

Best Regards,

Answer 3

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-SYSVOL/ba-p/425405

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.

--please don't forget to Accept as answer if the reply is helpful--

Answer 4

Hello, thanks for everyone's response. I ran dfsrmig.exe /getglobalstate and shows
Current DFSR global state: 'Eliminated'
Succeeded.

Dcdiag /v >c:\dcdiag1.log - This log indicates passed for each stage
Repadmin /showrepl >C:\repl.txt - No errors shown
Repadmin /showreps * - Results with this error....... LDAP error 81 (Server Down) Win32 Err 58.

What does this error represent? Current DC is Server 2012 R2
Thank you

Answer 5

Sounds good, also check that domain functional level is 2008 or higher.

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.

--please don't forget to Accept as answer if the reply is helpful--