Ansible on Windows Server 2016: Failover Cluster Bootstrap 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 failover cluster bootstrap 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 Failover Cluster Bootstrap on Windows Server 2016

On Windows Server 2016, failover cluster bootstrap 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: Failover Cluster Bootstrap 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

Failover Cluster Bootstrap 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: 2-node Failover Cluster on Windows Server 2016
  hosts: windows-server-2016
  serial: 1
  tasks:
    - name: Install Failover Clustering
      ansible.windows.win_feature:
        name: [Failover-Clustering, RSAT-Clustering-PowerShell]
        state: present
    - name: Create cluster on first node
      ansible.windows.win_shell: |
        if (-not (Get-Cluster -ErrorAction SilentlyContinue)) {
          New-Cluster -Name s2d-cluster `
            -Node {{ groups['windows-server-2016'] | join(',') }} `
            -StaticAddress 10.10.10.50 -NoStorage
          Enable-ClusterStorageSpacesDirect -Confirm:\$false
        }
      run_once: true

See also: Ansible on Windows Server 2019: Failover Cluster Bootstrap Complete Guide

Validation

Run with --check first, then converge:

ansible-playbook -i inventory/windows.ini failover-cluster-bootstrap.yml --check --diff
ansible-playbook -i inventory/windows.ini failover-cluster-bootstrap.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: Failover Cluster Bootstrap 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 failover cluster bootstrap 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

• PSRP and OpenSSH on Windows Server 2025 via Ansible • configuring WinRM for Ansible • Ansible 13 upgrade guide: breaking changes ansible-core 2.20 migration • how Ansible connection plugins work

Conclusion

Windows Server 2016 (NT 10.0.14393) is a first-class Ansible target for failover cluster bootstrap. 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.