Insights /Active Directory and Group Policy

Moving domain controllers from Windows Server 2016 or 2019 to 2025: in-place or side-by-side?

Prefer a new Windows Server 2025 domain controller, replication validation, FSMO transfer and controlled demotion of the old DC rather than defaulting to in-place upgrade.

Moving domain controllers from Windows Server 2016 or 2019 to 2025: in-place or side-by-side?
Key assessment

Establish a factual baseline with “new Windows Server 2025 domain controller” and “AD/DNS replication health”, then move to “FSMO roles”. Use identity, name resolution, replication and policy as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking new Windows Server 2025 domain controller, AD/DNS replication health and FSMO roles independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · new Windows Server 2025 domain controllerChecking new Windows Server 2025 domain controller helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of new Windows Server 2025 domain controller. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
02 · AD/DNS replication healthChecking AD/DNS replication health helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of AD/DNS replication health. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
03 · FSMO rolesChecking FSMO roles helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of FSMO roles. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
04 · SYSVOL/NETLOGONChecking SYSVOL/NETLOGON helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of SYSVOL/NETLOGON. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
05 · demotion of legacy domain controllersChecking demotion of legacy domain controllers helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of demotion of legacy domain controllers. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.
06 · in-place upgrade riskChecking in-place upgrade risk helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline.Record the actual state of in-place upgrade risk. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes.

Investigation and change sequence

  1. Capture a baseline for new Windows Server 2025 domain controller and AD/DNS replication health and compare it with a known-good system.
  2. Correlate evidence from FSMO roles and SYSVOL/NETLOGON to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to demotion of legacy domain controllers, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check in-place upgrade risk and the real business workflow. Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.

Validation and rollback evidence

  • Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
  • Recheck demotion of legacy domain controllers and in-place upgrade risk against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming new Windows Server 2025 domain controller is sufficient while overlooking AD/DNS replication health and dependent checks.
  • Changing several settings before preserving the original evidence for FSMO roles.
  • Do not replace root-cause analysis with destructive directory operations or forced rebuilds.

Common questions and acceptance criteria

What should be checked first?

Begin with new Windows Server 2025 domain controller and AD/DNS replication health. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousvSphere 7 is out of general support: upgrade to vSphere 8 or move to another platform?NextMigrating SQL Server 2016 to 2022 or 2025: compatibility, downtime and rollback planning

Need an assessment based on the actual environment?