Skip to content
INSIGHTS & GUIDES · NETCLOUD24

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 the first controller and validate directory services before dependency grows.

Read the article ↓
Editorial illustration: How to Create a New Active Directory Forest with PowerShell

A new Active Directory forest creates an identity and security boundary that applications and people may depend on for years. Its namespace, privileged-access model and recovery design should be approved before the first promotion command is run.

This guide is for authorised administrators on Windows Server 2019, 2022 or 2025. Netcloud24 prepares the agreed directory environment for Managed customers; they do not need to create a forest themselves. Adding a controller to an existing domain or joining an ordinary member uses different procedures.

Approve the namespace and role boundaries

Use an appropriate DNS namespace under a domain the organisation controls, with no conflict against existing directory or application names. The example ad.business.example.org is documentation only. Do not reproduce it as a real production namespace.

Choose the short NetBIOS domain name and review application requirements. User sign-in suffixes can need separate planning. Naming is difficult to revisit once accounts, certificates and integrations depend on it.

Use a dedicated supported controller design. A domain controller holds directory-wide trust and should not become an ordinary employee desktop or general application host because spare resources are available.

Assign privileged administration, incident response and forest recovery ownership. Protect emergency credentials and decide how another operator can recover access during the primary administrator’s absence.

Choose compatible functional levels explicitly

Functional levels govern directory capabilities and permitted domain-controller operating systems. They do not directly dictate the Windows release of every member or workstation.

Windows Server 2019 and 2022 have the 2016 level as their newest level. Windows Server 2025 supports the 2016 level and adds a 2025 level, which requires 2025 controllers. Select the highest level supported by the planned controller estate and requirements.

The example below chooses WinThreshold, the PowerShell representation of the 2016 level, for compatibility across the releases covered. An approved all-2025 design may choose differently after confirming the installed module’s accepted values. Do not rely on an inherited default or assume changing levels later is a simple reversible preference.

Check Microsoft’s functional-level matrix when approving the design.

Prepare an appropriate first server

Build and patch the supported release, apply the approved unique hostname and static network allocation, and verify storage health and capacity. Keep independent console access through promotion and restart.

Confirm production licensing before promotion. An evaluation controller cannot use the ordinary in-place evaluation conversion procedure, so avoid creating a known licensing migration problem at the start.

Plan directory database, logs and SYSVOL storage according to the workload and recovery design. Extra partitions copied from an old example do not automatically provide resilience or performance.

Define first-controller DNS bootstrap and post-promotion settings. Internal directory DNS must resolve AD records after creation; unrelated public resolvers are not a substitute. External lookup follows the approved forwarding or recursion design.

Arrange protected backups and plan another controller in an appropriate failure domain. Two VMs sharing the same host and vulnerable storage do not remove all common failure risks.

Install the role as a separate checkpoint

In the approved elevated local administrative session:

hostname
Install-WindowsFeature -Name 'AD-Domain-Services' -IncludeManagementTools
Get-WindowsFeature -Name 'AD-Domain-Services'
Get-Command -Module ADDSDeployment

Review the installation result and any servicing requirement. Adding AD DS components does not yet create a directory. Preserve this distinction so a failed component operation is not confused with a partially completed forest promotion.

Prepare the recovery password and reviewed parameters

DSRM credentials support directory recovery and are not ordinary shared domain-user credentials. Capture the secret through a protected prompt and store it under the approved recovery process:

$dsrm = Read-Host 'Enter the approved DSRM recovery password' -AsSecureString
$forest = @{
    DomainName = 'ad.business.example.org' # Replace with approved owned namespace.
    DomainNetbiosName = 'BUSINESS' # Replace with approved short domain name.
    ForestMode = 'WinThreshold' # Illustrative 2016 functional level.
    DomainMode = 'WinThreshold'
    InstallDns = $true
    SafeModeAdministratorPassword = $dsrm
}

Review names, levels, DNS and any required storage parameters against the specification. No password is embedded in this block, but the session and endpoint still require protection. A secure string is not a reason to execute on an untrusted device.

Run prerequisite testing without bypasses

Test-ADDSForestInstallation @forest

Read every blocking result and assess warnings. A delegation warning can be expected under some DNS designs but should be understood, not dismissed automatically. Do not expose directory records publicly merely because the namespace uses an organisation-owned domain.

Prerequisite tests do not approve the architecture or prove backup recovery. Resolve failures through the supported design rather than adding SkipPreChecks, forced acceptance or broad security exceptions.

Promote and complete startup

When the plan and test results are approved:

Install-ADDSForest @forest

Review confirmation prompts. Promotion normally restarts the machine. Do not suppress that restart and treat the intermediate system as a functioning member or controller. Keep the console available and allow configuration to finish.

For a failure, preserve its exact message and deployment-log context before another attempt. Manually deleting directory database files is not a supported generic way to start over.

Validate identity, DNS and directory shares

After restart, use the approved domain administrative context:

Get-ADForest | Select-Object Name, ForestMode, RootDomain
Get-ADDomain | Select-Object DNSRoot, DomainMode, PDCEmulator
Get-ADDomainController -Filter *
Get-SmbShare -Name 'SYSVOL','NETLOGON'
dcdiag /test:dns /v

Expect the intended names and levels, controller identity and required shares. Examine persistent Directory Service, DNS Server and DFS Replication errors. A successful Windows sign-in alone does not establish complete directory health.

Check service records through the intended internal resolver and test an approved member join. Review the forest-root PDC emulator’s time authority and required firewall boundaries before broad client use.

Complete resilience and recovery before dependency grows

Enable monitored role-appropriate backups and document forest recovery. Verify secure access to DSRM information and backup keys. Add a healthy additional controller and validate replication through its separate procedure.

A single-controller forest has no replication redundancy yet. Record that as an outstanding resilience action rather than interpreting the absence of replication errors as proof of availability.

Removing the last controller can remove the domain itself, so it is not an ordinary rollback after users and applications adopt the forest. Keep naming, levels, sites and support ownership in the final record.

See additional-controller planning and Microsoft’s promotion and prerequisite-test references.


Was this answer helpful?

« Back
Contact

Write to us

Do you have questions about our services or need a quote? Write to us and we will respond as soon as possible.

Contact form

Fields marked * are required.