Skip to main content

Choose Your Route: ISO or Simplified Provisioning

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Choosing the OS installation route, and the OS steps each route needs PURPOSE: Know which phases and tasks to run before cluster Validate MASTER REFERENCE: Microsoft Learn — Install the OS and Simplified machine provisioning

Status: Active


Overview​

Every machine has to reach the same state before cluster Validate: the Azure Local OS installed, the OEM's drivers and Solution Builder Extension (SBE) in place, one static management address with one default gateway, the right DNS and time, and an Azure Arc machine with its mandatory extensions. Part 4 gets there by one of two routes:

RouteHow the OS gets thereStatus
ISO or OEM imageYou install from the Microsoft ISO or your OEM's image (Manual OS Installation), configure the OS (Phase 03), then register with Arc (Phase 04)GA
Simplified machine provisioningAzure installs the OS and registers the machine with Arc. You do it in the portal, then Task 06, or end to end with the azurelocal-ztp automationPreview, East US only, no Arc gateway

Simplified provisioning does not do everything Phase 03 does. It leaves Microsoft's inbox network drivers, an empty C:\SBE, DHCP, and a default gateway on more than one adapter. Those still have to be fixed before Validate. The decision matrix below lists each step.

Check Microsoft and your OEM before Validate

OS requirements change between Azure Local releases and between OEM images. Before you run Validate, check Microsoft Learn's OS installation steps and your OEM's deployment guide for your build and hardware, for example Dell's deployment and operations guide. This page is a map, not a replacement for them.


The flow​

Flow chart of Part 4. After Phase 01, the route splits on how the OS is installed. The ISO or OEM image route runs Phase 02 install, all Phase 03 OS configuration tasks and Phase 04 Arc registration. The simplified provisioning route runs Phase 02 simplified provisioning, then either the azurelocal-ztp Prepare stage or simplified provisioning Task 06 by hand, and skips Phase 04. Both routes meet at Phase 05 cluster deployment and Phase 06 post-deployment.

Select the diagram to open it full screen and zoom. Source: cluster-deployment-routes.drawio.


Which route​

QuestionISO or OEM imageSimplified provisioning
Production deployment today✅ Use this⚠️ Preview
Hardware on Microsoft's validated list for simplified provisioningAny catalog hardwareDell AX-650 and AX-750, Lenovo ThinkAgile MX650 V3 and V4, HPE ProLiant DL360 Gen11 (Learn)
Arc gateway✅ Supported❌ Not supported in the preview
Region of the provisioning resourcesAny supported regionEast US only
No one at the consoleNeeds BMC console work per machineAzure does the install. With azurelocal-ztp, no USB stick either
Arc machine nameThe host name<device-id>-1, named by the service. See the known issue

Decision matrix​

Each row is a step that has to be done, or checked, before cluster Validate. Columns:

  • ISO / OEM image: you install from an ISO and follow Phases 02 to 04.
  • Simplified, portal: you provision with Microsoft's simplified machine provisioning in the portal.
  • Simplified, azurelocal-ztp: you run the azurelocal-ztp automation through its Prepare stage.

Legend: You = a step you run · Microsoft = done by the provisioning service · ZTP = done and checked by azurelocal-ztp · Optional · n/a.

On the portal path, Simplified Provisioning Task 06: Prepare Machines for Validate covers the You rows of the OS configuration table.

Before the OS​

StepISO / OEM imageSimplified, portalSimplified, azurelocal-ztpSource
BIOS settings: virtualization, Secure Boot, TPM, system profileYou (Phase 01)You. Secure Boot and TPM are requiredYou. ZTP doesn't check BIOS settingsLearn, Dell BIOS and iDRAC
NIC settings for RDMA, for example "NIC + RDMA Mode" on Intel E810You (Phase 01)YouYouDell deployment guide
Firmware at the OEM support-matrix levelYou. Some OEM images update firmware during imagingYouYou. ZTP doesn't update firmwareLearn, Dell SBE release notes: the SBE can't update firmware or drivers during deployment
Active Directory: OU and LCM userYou (Part 3)YouYouLearn
DHCP reservation for each management MACOptionalRecommendedYou. Prepare signs in on that address before it makes it staticLearn decision 8

Install and Arc​

StepISO / OEM imageSimplified, portalSimplified, azurelocal-ztpSource
Install the OSYou (Phase 02)MicrosoftMicrosoft, started by ZTPLearn
Local administrator password, the same on every machineYouMicrosoft, from the site's Key Vault secretMicrosoft, from the site's Key Vault secretLearn
Host nameYou (task 10)Microsoft, from the machine name you giveMicrosoft, from cluster_nodes[].nameLearn, seen on live runs
Remove virtual mediaYouYou: take out the USB stick, disable USB boot in the BIOSZTP ejects the virtual USBLearn
Register with Azure Arc and install the mandatory extensionsYou (Phase 04)Microsoft. Skip Phase 04Microsoft. Skip Phase 04Learn

OS configuration (Phase 03)​

StepISO / OEM imageSimplified, portalSimplified, azurelocal-ztpSource
WinRM for remote managementYou (task 01)Already onAlready onSeen on live runs
OEM driversYou, unless your OEM image includes themYou. Provisioning leaves Microsoft's inbox driversZTP installs the network drivers from the SBELearn, inbox drivers aren't supported
SBE files in C:\SBEYou, unless your OEM image includes themYouZTP, with the hash checked against the OEM's manifestLearn, Dell SBE release notes
Static management IPYou (task 03)You. Provisioning uses DHCPZTPLearn
One default gateway, on the management adapter onlyYou (task 04)You. Live runs had a gateway on two adaptersZTPLearn decision 8
DNS servers that resolve your domainYou (tasks 05 and 06)Check: provisioning takes them from DHCPZTPLearn. DNS can't change after deployment
Time serverYou (task 07)Set the site's time server, or set it on each machineZTP sets onprem.ntp_servers and waits for syncLearn
Keep the iDRAC USB NIC (Remote NDIS) enabled, with DHCPLeave it aloneLeave it aloneLeft aloneDell SBE release notes: SBE health checks need it
Disable disconnected adaptersYou (task 09)OptionalOptional. Not needed when every port is cabledDell deployment guide
RDPOptional (task 02)OptionalOptional, not doneLearn, Dell
ICMP (ping)Optional (task 08)OptionalOptional, not doneDell
Clean non-OS drivesYou, on reused hardware (task 11)Check on reused hardwareCheck on reused hardware. ZTP doesn't wipe drivesLearn
Don't install Windows updates before deploymentDon'tDon'tZTP doesn'tLearn
Domain join before deploymentOptional from 2604OptionalNot done. Deployment joins the machinesLearn
Deployment admin accountYouYouZTP creates credentials.local_admin_usernameLearn ARM template parameters
What "seen on live runs" means

Rows marked that way were read from two Dell AX-760 machines right after simplified provisioning, before any change: inbox drivers, an empty C:\SBE, DHCP on the management adapter, a default gateway on two adapters, DNS from DHCP, and time.windows.com as the time source. Cluster Validate then passed after the azurelocal-ztp Prepare stage, without RDP, ICMP, disabled adapters or a drive wipe.


Known issue: Arc machine names at Deploy​

Simplified provisioning names each Azure Arc machine <device-id>-1, not after the host. On build 12.2690.1003.15, cluster Deploy failed at Deploy Arc infrastructure components with ParentResourceNotFound: that step installs an Arc extension on the Arc machine named after the host, and no such machine exists. Validate passes, because the deployment content that runs this step is only downloaded when Deploy starts, and Validate's Arc checks use the resource IDs you pass in.

Before you deploy on the simplified route, check the troubleshooting page and Microsoft's known issues for your build. The ISO route isn't affected, because the Arc machine carries the host name.


← Part 4 overview↑ Part 4: Cluster DeploymentPhase 01: Hardware Provisioning →

References​


VersionDateAuthorChanges
1.02026-11-06Azure Local CloudInitial release