I have a single DC domain that has been upgrade starting from NT4.0. I cannot get past the FRS message when joining a new 2019 STD server

DaveVavricka-1259 25 Reputation points
2023-03-20T21:37:51.7933333+00:00

I started with 2003 and 2012R2 DC's.

I had to force out the 2003 DC . It was demoted but there was still remnants left. Actually saw a reference to a Server 2000 DC at one point.

I have been able to upgrade the Domain and Forest to 2012R2.

Have the 2019 STD server joined to domain, BUT cannot get it promoted as a DC.

I have ran DCDiags, all successful.

Ran ADPREP /forestprep, all successful.

Ran ADPREP /domainprep /gpprep, all successful.

When I run FRSDiag tool, it is looking for the 2003 server to replicate to. It is no longer a DC. I get the message below:

Warning 13508 The File Replication Service is having trouble replicating from "Old DC 2003" to "2012R2 DC" for C:\windows\sysvol\domain

Currently I only have 1 DC, 2012R2

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,398 questions
Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,519 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 425.8K Reputation points MVP
    2023-03-20T21:41:19.72+00:00

    The two prerequisites to introducing the first 2019 or 2022 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

    Also may need to perform some cleanup to remove remnants of any that no longer exist.

    Clean up Active Directory Domain Controller server metadata

    Step-By-Step: Manually Removing A Domain Controller Server

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


3 additional answers

Sort by: Most helpful
  1. Dave Patrick 425.8K Reputation points MVP
    2023-03-20T22:33:00.29+00:00

    I'd first check the cleanup was successful and also that no domain controllers older than 2008 exist, then check the domain health is 100% dcdiag, repadmin tools. Then check the domain functional level is 2008 or higher.

    Get-ADDomain | fl Name,DomainMode
    
    

    Also that event logs are free of errors on existing domain controllers. Then try working through the FRS-DFSR migration again.

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

    1 person found this answer helpful.

  2. DaveVavricka-1259 25 Reputation points
    2023-03-22T19:07:11.3566667+00:00

    I found a TID that helped me thru this.

    Once I got the DFSR Global State to "Eliminated"

    Then set NTFRS to stopped, see pic.

    Then I successfully joined the new DC to the existing domain.

    Set-Service ntfrs -StartupType Disabled
    Stop-Service ntfrs
    

    IUser's image

    1 person found this answer helpful.

  3. DaveVavricka-1259 25 Reputation points
    2023-03-22T19:14:49.93+00:00

    See my lasted post on this issue.

    0 comments No comments