Migrating Domain Controllers: Taking Over a Domain with a New Controller

An IT technician rests a hand on an old beige tower server under a newer rack-mounted server in a cramped server room.
AI-generated illustration

Updated November 14, 2026 with AI assistance. Vendor references are linked below. Command examples require review for your environment.

Prepare a replacement domain controller

A migration should preserve healthy DNS, directory replication, SYSVOL, authentication and recovery capability. Check the supported operating-system path, forest and domain functional levels, backups and application dependencies before promoting a replacement.

Confirm SYSVOL replication first. Windows Server 2019 introduced a promotion block for domains still using FRS. Do not apply that statement indiscriminately to Server 2016. Complete the supported FRS-to-DFSR migration before introducing a version that requires it.

Promote and validate before moving roles

Use Server Manager or the documented ADDSDeployment cmdlets for the target Windows Server version. After promotion, check DNS registration, replication, SYSVOL and NETLOGON shares, and client authentication. Do not treat a successful wizard as full migration validation.

Transfer FSMO roles while both controllers are healthy

Identify the current holders and transfer only the roles intended for the new controller. The following is an example transfer of the domain’s PDC role, not a command to move every role automatically.

netdom query fsmo
Move-ADDirectoryServerOperationMasterRole -Identity "NEW-DC" -OperationMasterRole PDCEmulator -WhatIf

After an approved transfer, verify the role holder. A seizure is a separate recovery procedure for an unavailable holder; do not add Force as a routine migration shortcut. Review the forest-root PDC time configuration when that role moves.

Demote the old controller normally

Move remaining DNS, DHCP or application dependencies and confirm clients can use the replacement. Use the supported Server Manager demotion workflow or Uninstall-ADDSDomainController for the installed version. The old dcpromo /demote example is not current general guidance. Forced removal and metadata cleanup belong to documented recovery scenarios, not a normal healthy demotion.

Sources