Task 05: Deploy Windows Admin Center
This task is deferred. The toolkit does not run it, and its scripts are parked in scripts/deferred of azurelocal-toolkit as they were: they are not maintained and may not work. The page is kept for reference and will be rewritten when the task comes back.
DOCUMENT CATEGORY: Runbook
SCOPE: Windows Admin Center deployment and configuration
PURPOSE: Establish web-based management portal for Azure Local cluster operations
MASTER REFERENCE: Microsoft Learn - WAC
Status: Active
Overview
Windows Admin Center (WAC) provides a web-based management interface for Azure Local clusters. WAC runs on its own dedicated management server and is used for cluster health monitoring, VM management, storage operations, and Azure hybrid integration.
WAC runs on a dedicated management server (landing_zone.virtual_machines[]), not on the jumpbox. This is intentional — WAC has specific port and TLS requirements that are cleanest on a standalone host. The jumpbox is a separate server used for RDP/SSH access and admin tooling.
Server Requirements
Jumpbox / Utility Server
The jumpbox must exist and be accessible before deploying WAC. WAC uses PSRemoting to install on the WAC server, and you need a machine with line-of-sight to the management network.
The jumpbox server is deployment-agnostic. Set jumpbox_deployment_target in your variables to azure, azurelocal, or onprem.
Jumpbox requirements:
| Requirement | Value |
|---|---|
| OS | Windows Server 2019 or later |
| Domain membership | Recommended (domain-joined) |
| Network access | Line-of-sight to WAC server and Azure Local cluster nodes |
| Deployment target | azure | azurelocal | onprem |
Capture jumpbox details in infrastructure.yml:
compute:
vms:
management:
jumpbox:
jumpbox_hostname: "jumpbox01"
jumpbox_ip: "10.20.1.20"
jumpbox_fqdn: "jumpbox01.corp.example.com"
jumpbox_deployment_target: "azure" # azure | azurelocal | onprem
WAC Server
WAC requires its own dedicated Windows Server host.
The WAC server is deployment-agnostic. Set wac_deployment_target in your variables to azure, azurelocal, or onprem.
WAC server requirements:
| Requirement | Value |
|---|---|
| OS | Windows Server 2019 or later |
| vCPU | 4+ recommended |
| RAM | 8 GB+ recommended |
| Domain membership | Recommended (domain-joined) |
| Inbound port | TCP 443 (HTTPS — WAC gateway) |
| Outbound | Internet access for WAC MSI download and Azure registration |
| Network access | Line-of-sight to Azure Local cluster nodes |
| Deployment target | azure | azurelocal | onprem |
Capture WAC server details in infrastructure.yml:
wac:
wac_hostname: "wac01"
wac_ip: "10.20.1.21"
wac_fqdn: "wac01.corp.example.com"
wac_port: 443
wac_deployment_target: "azure" # azure | azurelocal | onprem
Configuration Summary
| Setting | Value | Variable |
|---|---|---|
| WAC Server | Dedicated management host | landing_zone.virtual_machines[] |
| WAC IP | WAC server IP | landing_zone.virtual_machines[] |
| WAC URL | https://<wac_fqdn> | landing_zone.virtual_machines[] |
| WAC Port | 443 (HTTPS) | landing_zone.virtual_machines[] |
| Certificate | Self-signed (initial) | Auto-generated |
| Version | Latest stable | Microsoft Download Center |
Required WAC Extensions
| Extension | Purpose |
|---|---|
| Cluster Manager | Azure Local cluster management |
| Azure Hybrid Center | Azure Arc and hybrid integration |
| Azure Monitor | Monitoring integration |
| Virtual Machines | VM lifecycle management |
| Storage | Storage pool and volume management |
| Networking | SDN and network management |
Prerequisites
- WAC server provisioned and accessible (see Server Requirements above)
- Jumpbox provisioned and accessible (see Server Requirements above)
- Variables captured in
infrastructure.yml(landing_zone.virtual_machines[]) - Internet access from WAC server (for MSI download and Azure registration)
- Domain admin credentials available
Values from infrastructure.yml
The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.
Execution Options
- WAC Web UI
- Orchestrated Script
WAC Web UI
When to use: Standard installation via GUI installer on the WAC server
Procedure — Download and Install
-
Connect to WAC server via Bastion, RDP through jumpbox, or direct RDP
-
Download WAC:
- Open Edge/Chrome on the WAC server
- Navigate to: https://aka.ms/wacdownload
- Download the latest MSI
-
Run MSI installer:
Setting Value Port 443Use WinRM (HTTPS) Checked Generate self-signed cert Checked Allow WAC to modify TrustedHosts Checked -
Complete installation — WAC service starts automatically
Procedure — Initial Configuration
-
Access WAC: Open
https://localhoston the WAC server, orhttps://<wac_fqdn>from the jumpbox -
Add Cluster Connection:
- Click Add → Server clusters
- Cluster name: from
cluster.name - Credentials: Use domain admin
-
Install Extensions:
- Navigate to Settings → Extensions
- Install or update: Cluster Manager, Azure Hybrid Center, Azure Monitor, Virtual Machines, Storage, Networking
Procedure — Azure Integration
-
Register WAC with Azure:
- Settings → Azure → Register
- Sign in with Azure AD credentials
- Select the management subscription
- Grant required permissions
-
Enable Azure Monitor:
- Cluster → Azure Monitor → Enable
- Select Log Analytics workspace (from
landing_zone.log_analytics.name)
Validation
- WAC accessible at
https://<wac_fqdn> - Cluster connection healthy — green status
- All extensions installed and current
- Azure registration complete
- Azure Monitor forwarding data
PowerShell
When to use: This task is parked and nothing runs it. The scripts below are under
scripts/deferredand they still read an older configuration layout.
Script
| Script | What it does |
|---|---|
scripts/deferred/windows-admin-center/phase-02-monitoring-observability/task-05-deploy-wac/powershell/Deploy-WindowsAdminCenter.ps1 | Deploy Windows Admin Center (WAC) to the management server via PSRemoting. Supports -WhatIf. |
Requires: PowerShell 7.
Validation
- WAC service running:
Get-Service ServerManagementGateway - Web UI accessible:
https://<wac_fqdn>orhttps://<wac_ip> - Cluster connection established and shows healthy status
- Extensions installed and current version
- Azure registration completed
Troubleshooting
| Issue | Root Cause | Remediation |
|---|---|---|
| MSI download fails | No internet from WAC server | Verify outbound internet access (NAT, firewall rules) |
| WAC service not starting | Port conflict on 443 | Check if IIS or other service uses port 443 |
| Cannot connect to cluster | CredSSP/Kerberos | Enable CredSSP or use constrained delegation |
| Azure registration fails | Missing permissions | Ensure Global Admin or App Administrator role |
| Extensions fail to install | WAC version mismatch | Update WAC to latest version first |
| Certificate warning | Self-signed cert | Expected for initial setup — replace with CA cert in production |
| PSRemoting fails from jumpbox | WinRM not enabled on WAC server | Run Enable-PSRemoting -Force on WAC server |
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2026-04-02 | Azure Local Cloud | Initial version |
Navigation
| Previous | Up | Next |
|---|---|---|
| Task 04: Setup Alerting | Phase 02: Monitoring & Observability | Task 06: OMIMSWAC Monitoring |