Skip to main content

Phase 03: OS Configuration

Runbook Platform

DOCUMENT CATEGORY: Runbook
SCOPE: Post-installation OS configuration
PURPOSE: Prepare nodes for Azure Arc registration
MASTER REFERENCE: Microsoft Learn - Install the Azure Local operating system

Status: Active Estimated Time: 45-60 minutes (all nodes) Last Updated: 2026-11-08


Overview​

Start here: the automated run​

OS configuration always starts after the OS install, whichever way it was done. The toolkit does the whole phase for the whole cluster in one run: it reads each node, changes only what differs from the master infrastructure.yml, and reports. Use it unless you cannot; the manual tasks below do the same work one setting at a time.

PageWhat it gives you
Which method did I use?The decision flow from the OS install (azurelocal-ztp or a manual ISO install) to ARM Deploy, method detection, and how to tell which method you used
Automated OS configuration (one run)The commands (standalone and from a GitHub or GitLab pipeline), the master-file keys, clear_storage, the SBE package and its pre-cluster checks, the SBE delivery route, exit codes, access and connectivity, and troubleshooting
How the run worksEvery step in the order it runs, what counts as a change, restarts, the three management address modes, SAN-only steps

Decision flow from the OS install method to OS configuration and on to ARM Validate and ARM Deploy.

Installed with simplified machine provisioning?

Provisioning sets the host name, registers the machine with Arc and installs the mandatory extensions. azurelocal-ztp ends at the Handoff: it does not install the OEM drivers or the SBE, set DNS or time, create the deployment administrator, or turn DHCP and the default gateway off on the other ports, and in management Modes B and C the static address is not in place. The automated run does all of that, starting from the handoff. See the decision matrix for each task, and check Microsoft Learn and your OEM's deployment guide for your build before Validate.


Manual tasks​

This stage configures the Azure Stack HCI operating system on all cluster nodes with the settings required for Azure Local deployment. All steps can be performed remotely once WinRM is enabled.

Objective: Configure the Azure Local operating system on each node with network settings, remote management, and baseline configuration required for cluster deployment.

Tasks:

  1. Enable WinRM for PowerShell remote management
  2. Enable RDP for graphical remote access
  3. Configure static IP addresses on management adapters
  4. Disable DHCP on management adapters
  5. Configure DNS server addresses
  6. Verify DNS client configuration
  7. Configure NTP time synchronization
  8. Enable ICMP firewall rules for network diagnostics
  9. Disable unused network adapters
  10. Set node hostnames
  11. Clear previous storage configuration (conditional — redeployments on used hardware; local disks only, never SAN LUNs)
  12. Install FC HBA drivers or OEM iSCSI adapter drivers (conditional — disaggregated SAN deployments)
  13. Verify MPIO, register and claim the vendor MSDSM (conditional — disaggregated SAN deployments)
  14. Verify SAN LUN presentation (conditional — disaggregated SAN deployments)
  15. Optional: Run complete combined script (Tasks 02–10)
  16. Phase 03 Verification

Validation:

  • Remote management operational (WinRM and RDP)
  • Static network configuration applied
  • DNS resolution functional
  • Time synchronization configured
  • Nodes accessible and properly named

Outcome: All nodes configured with proper network settings, remote management enabled, and ready for Azure Arc registration (Stage 13).


Configuration Workflow​

flowchart TD
A[Start: OS Installed] --> B[Enable WinRM]
B --> C[Enable RDP]
C --> D[Static IP]
D --> E[Disable DHCP]
E --> F[DNS Config]
F --> G[Verify DNS]
G --> H[NTP Config]
H --> I[Enable ICMP]
I --> J[Disable Unused NICs]
J --> K[Hostname]
K --> L[Storage Cleanup T11]
L --> M{Storage Type?}
M -->|S2D or hybrid S2D + SAN| N[Combined Script T15]
M -->|Disaggregated SAN| O[FC HBA or iSCSI adapter drivers T12]
O --> P[MPIO & MSDSM T13]
P --> Q[Verify LUN Presentation T14]
Q --> N
N --> R[Phase 03 Verification T16]
R --> S[Ready for Arc Registration]

Steps Overview​

StepDescriptionTimeApplies To
Task 01Enable WinRM for Remote Management5 minAll
Task 02Enable RDP (Remote Desktop Protocol)5 minAll
Task 03Configure Static IP Address10 minAll
Task 04Disable DHCP on Management Adapter5 minAll
Task 05Configure DNS Servers5 minAll
Task 06Verify DNS Client Configuration5 minAll
Task 07Configure Time Synchronization (NTP)5 minAll
Task 08Enable ICMP (Ping)5 minAll
Task 09Disable Unused Network Adapters5 minAll
Task 10Configure Hostname5 minAll
Task 11Clear Previous Storage Configuration (local disks only)5 minRedeployment on used hardware
Task 12Install FC HBA Drivers (and iSCSI adapter drivers)15 minDisaggregated SAN only
Task 13Verify MPIO, Register and Claim Vendor MSDSM15 minDisaggregated SAN only
Task 14Verify SAN LUN Presentation10 minDisaggregated SAN only
Task 15Complete Combined ScriptN/AOptional
Task 16Phase 03 Verification10 minAll

Prerequisites​

RequirementDescription
OS installedStage 11 completed
iDRAC accessConsole access for initial config
IP planningStatic IPs assigned per node
DNS serversEnterprise DNS available
NTP serverTime source identified

Variables from infrastructure.yaml​

The following variables are used during OS configuration:

VariableDescriptionExample
NODE_XX_IPStatic IP address for each node192.168.200.11
NODE_XX_NAMEHostname for each nodeazlocal-node01
MANAGEMENT_GATEWAYDefault gateway IP192.168.200.1
MANAGEMENT_SUBNET_PREFIXSubnet prefix length24
DNS_PRIMARY_IPPrimary DNS server IP192.168.200.2
DNS_SECONDARY_IPSecondary DNS server IP192.168.200.3
NTP_SERVERNTP server IP or hostnamepool.ntp.org

Network Configuration Reference​

Example Node Configuration:

NodeManagement IPGatewayDNS1DNS2
NODE0110.x.x.1110.x.x.110.x.x.210.x.x.3
NODE0210.x.x.1210.x.x.110.x.x.210.x.x.3
NODE0310.x.x.1310.x.x.110.x.x.210.x.x.3
NODE0410.x.x.1410.x.x.110.x.x.210.x.x.3

Automation Options​

Manual: Follow each step in sequence.

Automated, the whole phase: the automated run covers every task on this page for every node, with method detection, a plan, an approval gate and a verification pass.

Automated, Tasks 02–10 only: Task 15: Combined Script.

Disaggregated SAN deployments: Run Tasks 12–14 after Task 11 before running the combined script. Zone the FC fabric and unmask the infrastructure and performance history LUNs now, before Arc registration, and leave them RAW. On iSCSI with 2610, do not enable iSCSI on the machines first; the deployment wizard configures it.

Hybrid (Storage Spaces Direct + SAN): Skip Tasks 12–14 for the initial deployment. Learn attaches the SAN after the initial deployment (2604 or later) and says: "don't zone in FC HBA World Wide Names (WWNs) until after the Azure Local deployment." Follow Connect an external storage array to Azure Local once the cluster is deployed.


Validation Checklist​

CheckRequired
WinRM responds✅
RDP accessible✅
Static IP configured✅
DNS resolution works✅
Time synchronized✅
Hostname correct✅
FC HBA ports visible (disaggregated SAN only)⚙️
MPIO verified, vendor registered and claimed (disaggregated SAN only)⚙️
Infrastructure and performance history LUNs RAW (disaggregated SAN only)⚙️

Next Stage​

After completing OS configuration:

All Steps Complete?Next Action
✅ Yes, installed from the ISOProceed to Phase 04: Arc Registration, unless the automated run already registered the nodes
✅ Yes, installed with simplified provisioningSkip Phase 04: the machines are already Arc-connected. Go to Phase 05: Cluster Deployment after Active Directory preparation
❌ NoComplete remaining configuration steps

References: