Automated OS Configuration (One Run)
Configure every node's OS in one run with the azurelocal-toolkit: standalone or from a GitHub or GitLab pipeline, with method detection, plan, approval, apply and verify, the master-file keys it reads, clear_storage, exit codes and troubleshooting.
Choose Your Route: ISO or Simplified Provisioning
Two routes lead to the same Azure Local cluster deployment. A flow chart and a decision matrix show which OS installation, OS configuration and Arc registration steps each route needs before Validate.
How the OS Configuration Run Works
Every step of the automated OS configuration run in the order it executes: what is read first, what counts as a change, the idempotent re-run, the restart points, the three management address modes, the SAN-only steps, the SBE route, the retry on state Unknown, per-node continue on failure and the plan, approval, apply and verify stages.
Task 01: Enable WinRM for Remote Management
Enable Windows Remote Management on all Azure Local nodes via iDRAC Virtual Console. Must run locally on each node — WinRM cannot be enabled remotely before it exists.
Task 02: Enable RDP
Enable Remote Desktop Protocol on all Azure Local nodes for graphical remote access during configuration and troubleshooting.
Task 03: Configure Static IP Address
Configure static IP addresses on the management network adapter for each Azure Local cluster node using explicit values from infrastructure.yml.
Task 04: Disable DHCP on All Adapters
Disable DHCP on all network adapters except virtual and management adapters to lock in static IP configuration across all Azure Local cluster nodes.
Task 05: Configure DNS Servers
Configure primary and secondary DNS server addresses on the management NIC of each Azure Local cluster node using explicit values from infrastructure.yml.
Task 06: Prepare Machines for Validate
After simplified machine provisioning, install the OEM drivers and SBE, set one static management address with one default gateway, DNS and time, and check every machine before cluster Validate.
Task 06: Verify DNS Client Configuration
Verify that DNS servers are correctly configured on the management NIC of each Azure Local node and that critical Azure endpoints resolve successfully.
Task 07: Configure Time Synchronization (NTP)
Configure the NTP time source on each Azure Local node using w32tm — required for Kerberos authentication and AD domain operations.
Task 08: Enable ICMP (Ping)
Enable ICMPv4 and ICMPv6 inbound firewall rules on each Azure Local node to allow ping for network diagnostics and connectivity validation.
Task 09: Disable Unused Network Adapters
Disable network adapters not used for management to prevent configuration issues during cluster deployment
Task 10: Configure Hostname
Set the computer hostname for each node according to naming standards
Task 11: Clear Previous Storage Configuration (Conditional)
Clear previous Storage Spaces Direct configuration if redeploying on existing hardware
Task 12: Install FC HBA Drivers (Conditional)
Install Fibre Channel HBA drivers (or the dedicated iSCSI adapter drivers) on Azure Local nodes for SAN disaggregated deployments, and get the zoning timing right for disaggregated versus hybrid
Task 13: Configure MPIO and Vendor MSDSM (Conditional)
Verify Windows Multipath I/O, register the SAN vendor with MSDSM and claim the array's disks, for Fibre Channel and iSCSI SAN disaggregated deployments on Azure Local 2610
Task 14: Verify SAN LUN Presentation (Conditional)
Verify SAN LUN presentation (Fibre Channel or iSCSI) and confirm the infrastructure and performance history LUNs are RAW before Azure Local disaggregated deployment
Task 15: Complete Combined Script (All Steps)
Optional combined script that runs Tasks 02–10 in a single execution for faster deployment
Task 16: Phase 03 Verification
Read-only verification of all Phase 03 OS Configuration tasks (01–15) across all cluster nodes
Which Provisioning Method, Then OS Configuration
A decision flow from the way the OS was installed (azurelocal-ztp simplified provisioning, or a manual ISO install) to OS configuration, method detection, the two paths, the converge check, ARM Validate and ARM Deploy, and how to tell which method you used.