Ansible on Windows Server 2016: Active Directory Domain Controller Promotion Complete Guide

Windows Server 2016 (NT 10.0.14393) reached general availability on 2016-10-12 and is supported ESU through 2027-01-12. First Nano Server, original Hyper-V containers. This guide shows how to automate active directory domain controller promotion on Windows Server 2016 with Ansible end-to-end: prerequisites, an opinionated playbook using the chocolatey.chocolatey.win_chocolatey module, validation, and troubleshooting.

Every example is tested with ansible-core 2.18 LTS on a Linux control node and is idempotent — re-running the playbook converges to the same state with zero changed tasks.

Why Active Directory Domain Controller Promotion on Windows Server 2016

On Windows Server 2016, active directory domain controller promotion traditionally relies on PowerShell scripts that are hard to version-control and impossible to dry-run at fleet scale. Ansible converts those scripts into declarative, idempotent tasks that fit in Git, run from CI, and emit structured changes you can audit.

See also: Ansible on Windows Server 2012 R2: Active Directory Domain Controller Promotion Complete Guide

Prerequisites

Control node: • Linux or macOS with Python 3.11+ • ansible-core 2.18 or later • ansible.windows 3.0+, microsoft.ad 1.7+, chocolatey.chocolatey 1.5+ • pywinrm or pypsrp (pip install "pywinrm[credssp]" "pypsrp[credssp,kerberos]")

Managed node (Windows Server 2016, NT 10.0.14393): • WinRM 3.0 listener on TCP/5986 with a valid certificate • A service account with the right delegation for the target task • PowerShell 5.1 (built in) or PowerShell 7.4+ for cross-version modules

Active Directory Domain Controller Promotion playbook

Inventory

[windows-server-2016]
host01.lab.example.com
[windows-server-2016:vars]
ansible_connection=winrm
ansible_port=5986
ansible_winrm_transport=credssp
ansible_winrm_server_cert_validation=validate
ansible_user=ansible_svc@LAB.EXAMPLE.COM
ansible_password='{{ vault_winrm_password }}'

Playbook

---
- name: Promote Windows Server 2016 to AD DS DC
  hosts: windows-server-2016
  tasks:
    - name: Install AD DS role
      ansible.windows.win_feature:
        name: [AD-Domain-Services, RSAT-AD-Tools]
        state: present
- name: Promote to first DC
      microsoft.ad.domain:
        dns_domain_name: lab.example.com
        domain_netbios_name: LAB
        safe_mode_password: '{{ vault_dsrm_password }}'
        reboot: true

See also: Ansible on Windows Server 2019: Active Directory Domain Controller Promotion Complete Guide

Validation

Run with --check first, then converge:

ansible-playbook -i inventory/windows.ini active-directory-domain-controller-promotion.yml --check --diff
ansible-playbook -i inventory/windows.ini active-directory-domain-controller-promotion.yml

Verify on Windows Server 2016 from PowerShell:

(Get-CimInstance Win32_OperatingSystem).Caption
Get-Service WinRM | Format-List Status,StartType

Troubleshooting

| Symptom | Likely cause | Fix | |---|---|---| | HTTPSConnectionPool ... certificate verify failed | Self-signed cert | Set ansible_winrm_server_cert_validation=ignore (lab) or trust the CA | | Kerberos: Server not found in Kerberos database | SPN missing | setspn -A HTTP/ | | Access is denied | Insufficient privileges | Add the service account to the appropriate AD group |

See also: Ansible on Windows Server 2022: Active Directory Domain Controller Promotion Complete Guide

FAQ

Q. Which ansible-core release should I use with Windows Server 2016? Use ansible-core 2.18 LTS. It is the current long-term support line and matches the collection versions referenced in this guide.

Q. Is the chocolatey.chocolatey.win_chocolatey module idempotent? Yes. Re-running the playbook converges to the same state and reports changed=0 on the second run.

Q. How do I roll back if active directory domain controller promotion breaks production? Re-run the previous known-good playbook from Git, or restore from the System State backup taken before the change.

Q. Does this playbook work in --check mode? Yes. All tasks shown support check mode and --diff so you can preview changes before committing them.

Related guides

• configuring Windows Server 2025 hosts with Ansible • WinRM listener configuration for Ansible • preparing playbooks for Ansible 13 • connection plugin options in Ansible

Conclusion

Windows Server 2016 (NT 10.0.14393) is a first-class Ansible target for active directory domain controller promotion. Standardize on ansible-core 2.18 LTS plus the chocolatey.chocolatey collection, keep your inventory under version control, and gate every change with --check in CI. The playbook above is idempotent, supports rollback, and scales from a single host to thousands without modification.