Active Directory upgrade Windows Server 2008 to Windows Server 2019

Yankee30 206 Reputation points
2021-02-08T19:17:42.323+00:00

We’re planning to upgrade our AD infrastructure from Windows Server 2008 to Windows server 2019, current domain and forest functional level are Windows server 2008.

The plan is to bring in a Additional Domain Controller(ADC) with Win2019 with temp name and once the replication is done. Demote the Win2008 box, rename it and change the ip.
Then rename and change the IP of Win2019 ADC using netdom to same as the original Win2008 While I have a couple of questions.

  1. Do we need to upgrade the schema version for the above process since eventually we plan on to upgrade all DC’s to Win2019 ?
  2. Do we need to run adprep, domain prep,forestprep in this case?
  3. What are all the checks I can perform to call that replication to new ADC is completed and now I can rename it, like match the NTDS DB size and what else?
  4. What all check I can do to confirm that win2008 is properly and completely demoted before I use that name on Windows2019 AD?
  5. Please help to identify what all should be the pre & post checks?
  6. If you have any other tips as well please share.

Thanks in advance.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,832 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,732 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2021-02-08T19:26:17.1+00:00

    The much simpler / safer method would be to move roles off to another, decommission demote, stand up the new one with correct name and addressing. When you add a new 2019 domain controller, adprep and schema update happens automatically.

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

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

    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.