Additional domain joining issue

Antony Maxwin 281 Reputation points
2022-06-21T07:49:27.3+00:00

hi
I have 2016 AD server, when i tried to join 2019 as Additional domain controller it says unable to verify whether schema master completed a replication after last reboot, then i found that earlier there was a 2008 ADC but that one is not present now, because of some hardware issue they removed this from network. so I how i do a propel removel of this 2008 server from 2016 Active directory. this 2008 not listing in 2016 Active directory , but whenever i try to add 2019 server i am always getting the replication error, how i can resolve this.

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,855 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous
    2022-06-21T12:19:06.367+00:00

    You can perform cleanup to remove the remnants of non-existent domain controllers.
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
    https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

    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
    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 or 2022, 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 upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. Limitless Technology 39,786 Reputation points
    2022-06-23T09:10:32.13+00:00

    Hi there,

    You can perform metadata cleanup on a domain controller in the domain of the domain controller that you forcibly removed.

    Metadata cleanup removes data from AD DS that identifies a domain controller to the replication system.

    Metadata cleanup also removes File Replication Service (FRS) and Distributed File System (DFS) Replication connections and attempts to transfer or seize any operations master (also known as flexible single master operations or FSMO) roles that the retired domain controller holds.

    Clean up Active Directory Domain Controller server metadata https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup Step-By-Step: Manually Removing A Domain Controller Server

    https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564 Hope this resolves your Query !

    ----------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.