A second controller is useful when it adds a tested directory service in a sensible failure domain. Promotion copies the existing directory state; it does not repair an unhealthy source or provide an independent historical backup. Establish health and compatibility before adding another replication participant.
This guide covers authorised writable-controller deployment on Windows Server 2019, 2022 or 2025. Netcloud24 prepares agreed directory services in a Managed environment. Customers should request the required resilience through the service process rather than promote controllers themselves. RODCs and new domains require separate procedures.
Check the version boundary first
Inspect existing domain and forest functional levels. The newest level for 2019 and 2022 is 2016. A 2025 controller supports 2016 or 2025 levels; a 2025-level environment cannot host 2019 or 2022 controllers.
A domain still operating at the 2012 R2 level needs a supported compatibility plan before a 2025 controller is introduced. Do not assume promotion automatically raises levels or resolves older dependencies.
Confirm SYSVOL replication uses the supported DFSR design. A legacy FRS arrangement needs its own completed migration before introducing releases that do not support it. Do not force promotion around that prerequisite.
Use Microsoft’s interoperability matrix and controller upgrade guidance for the actual estate.
Establish existing health and recovery
From an authorised current controller or supported management session:
Get-ADDomain | Select-Object DNSRoot, DomainMode, PDCEmulator, RIDMaster
Get-ADForest | Select-Object Name, ForestMode, SchemaMaster
Get-ADDomainController -Filter *
repadmin /replsummary
dcdiag /test:dns /v
Resolve persistent replication, directory DNS or SYSVOL failures. Confirm required shares and a healthy source. Record explained historical warnings separately from current blocking faults.
Verify role-appropriate backups and the directory recovery procedure. Another controller replicates unwanted changes too, so it is not a replacement for protected recovery points.
Plan placement and preparation permissions
Select the correct AD site and verify subnet definitions match the new network. Sites affect replication and client discovery; choosing a descriptive hostname does not establish topology.
Review host, storage, power and network dependencies against the availability requirement. Keep directory traffic on approved private paths rather than exposing authentication infrastructure publicly.
Routine additional-controller promotion requires appropriate domain administrative permissions. The first controller of a newer Windows release may also require schema and domain preparation, forest-level rights and connectivity to the relevant FSMO holders.
Arrange those steps with the directory owner. Do not add permanent broad privileges solely because the promotion tool reports a missing permission. Schema preparation has a different scope from an ordinary member join.
Build the prospective controller as a healthy member
Patch and license the selected release, assign its unique approved name and configure its static network allocation. Point DNS to healthy existing internal directory resolvers during preparation, not solely to the new machine’s not-yet-installed DNS service.
Verify time, console recovery and the management path. Join the intended domain through the approved member-server procedure and check its secure channel while it is still a member.
Review applications and applied policy. Do not inherit a general-purpose workload onto the controller accidentally. Confirm security and backup agents support the new role.
Add AD DS and collect the right secrets
Install-WindowsFeature -Name 'AD-Domain-Services' -IncludeManagementTools
Get-WindowsFeature -Name 'AD-Domain-Services'
Review the result before promotion. The installed role is only the component stage. Prepare the domain authorisation and a separate DSRM recovery password:
$credential = Get-Credential -Message 'Enter the approved promotion identity'
$dsrm = Read-Host 'Enter the new controller DSRM password' -AsSecureString
$promotion = @{
DomainName = 'ad.business.example.org' # Replace with the existing domain.
SiteName = 'UK-Primary' # Replace with a verified existing site.
Credential = $credential
SafeModeAdministratorPassword = $dsrm
InstallDns = $true
}
The values are illustrative. Review global-catalog, database-path and replication-source decisions under the approved architecture. The example describes an ordinary writable-controller arrangement with DNS, not a universal branch-office or RODC template.
Test before making the directory change
Test-ADDSDomainControllerInstallation @promotion
Read preparation, permission and DNS results in full. Confirm healthy replication data and connectivity to required role holders. A warning needs an explanation, and a failure should be fixed rather than hidden with SkipPreChecks.
Once approved, start the actual promotion:
Install-ADDSDomainController @promotion
Review prompts and allow the required restart. Keep console access available. A deliberately unrestarted intermediate configuration should not receive normal client traffic.
Validate completed initial synchronisation
Get-ADDomainController -Filter *
repadmin /replsummary
repadmin /showrepl
dcdiag /test:dns /v
Get-SmbShare -Name 'SYSVOL','NETLOGON'
Expect the controller in its intended site, relevant replication health and required shares. Investigate persistent Directory Service, DNS Server or DFS Replication failures. Operating-system startup alone does not establish that promotion finished properly.
Test directory service records through the designed DNS path and confirm controller advertising. Use representative client authentication and resolution checks before changing clients to rely on the new instance.
Do not prematurely remove every old resolver or controller while testing. Stage DNS or DHCP changes only after the new service is accepted, with a record of the intended client migration.
Integrate ownership without moving roles automatically
Add monitoring, role-appropriate backups and secure recovery records for the new controller. Verify its DNS client and external-resolution design after DNS installation.
Time settings should follow its actual domain role. A new controller does not automatically need unrelated external NTP peers or an immediate FSMO transfer. Those are separate planned decisions.
Keep the existing controller’s retirement as a distinct change. Review role holders, application bindings, name resolution and client dependencies before demotion.
Retain evidence from both the new controller and its source partners. A local success message can coexist with a partner that has not received the expected changes. Compare naming contexts, timestamps and the actual failing connection before requesting forced synchronisation. Escalate persistent inconsistencies through the directory owner instead of repeatedly changing topology during acceptance.
Use supported repair or removal
For prerequisite failure, correct the underlying condition. For partial promotion, preserve deployment logs and assess the supported recovery path before repeating commands or deleting objects.
After successful promotion, use orderly demotion to remove a controller. Forced removal and metadata cleanup are separate recovery procedures when normal demotion is unavailable, not routine shortcuts.
Record site, partners, validation and any outstanding resilience actions. See replication diagnosis, safe removal and Microsoft’s promotion and prerequisite-test references.
Designing and promoting the first controller in a new AD forest
Prepare a new Active Directory forest with reviewed naming, functional levels and recovery. Install AD DS, run prerequisite checks, promote…
Creating protected organisational units with clear policy boundaries
Create an AD organisational unit for a defined delegation or policy purpose. Review inheritance, use a protected creation, verify placement…
Provisioning an Active Directory user without exposing credentials
Provision an approved AD user through unique identifiers, a secure credential prompt and staged access review. Verify group membership,…
Separating staff roles from resource permissions with AGDLP
Apply AGDLP by separating individual accounts, business-role groups and resource entitlements. Inventory existing permissions, build the…
Enabling AD Recycle Bin as an irreversible forest change
Plan AD Recycle Bin as an irreversible forest feature. Verify prerequisites, scope and replication, understand pre-existing deletion limits…