Task 03: Monitor Bootstrap Process
DOCUMENT CATEGORY: Runbook SCOPE: Monitor Arc registration bootstrap status and handle OEM image updates PURPOSE: Monitor Arc registration bootstrap status and handle OEM image updates MASTER REFERENCE: Azure Arc Agent Installation
Status: Active
Overview
After Arc registration is initiated (Task 02), the bootstrap process runs in the background on each node. It first scans, downloads, and installs OEM updates (which may trigger automatic reboots), then completes Arc configuration. This task monitors all nodes through the full lifecycle until they report Succeeded.
Watch the bootstrap with Azure Local Sonar. The toolkit has no monitoring script of its own for it. On a single node you can also read the status with the commands in the Direct tab (the bootstrap status, the Arc agent, the download folder and the bootstrap log).
If a node reboots during registration, do not restart the registration script. The bootstrap service resumes automatically using cached SPN credentials. Sonar shows the node as unreachable until it comes back online.
Prerequisites
| Requirement | Details |
|---|---|
| Task 02 initiated | Arc registration started on all target nodes |
| Node access | RDP or console (Direct tab), or a machine that can reach the nodes (Azure Local Sonar) |
| Azure sign-in | Connect-AzAccount, for the Azure-side view in Sonar |
Variables from infrastructure.yml
| Path | Type | Description |
|---|---|---|
nodes[].network_adapters[].ip_address | string | Node management IPs for PSRemoting |
azure.subscription_id | string | Subscription ID for Azure queries |
azure.resource_group | string | Resource group for Arc machine lookups |
Bootstrap Phases
| Phase | Sub-Phase | Description | Duration |
|---|---|---|---|
| Update | Scan | Scans for available LCM/OEM updates | 1-5 min |
| Update | Download | Downloads packages to C:\bootstrap | 10-40 min |
| Update | Install | Installs updates, may trigger reboot | 5-15 min |
| (reboot) | — | Node reboots if OS update applied | 2-5 min |
| ArcConfiguration | ArcRegistration | Registers node with Azure Arc | 5-10 min |
- Direct (On Node)
- Orchestrated Script
Run on each node individually via RDP or console.
# Task 03 - Check Bootstrap Status (run on each node)
$status = Get-ArcBootstrapStatus
$status.Response | Select-Object Status, StartTime, EndTime
# Show detailed phases
if ($status.Response.DetailedResponse) {
foreach ($phase in $status.Response.DetailedResponse) {
Write-Host "$($phase.Name): $($phase.Status)"
if ($phase.DetailedResponse) {
$phase.DetailedResponse | ForEach-Object { Write-Host " $($_.Name): $($_.Status)" }
}
}
}
# Check Arc agent
Get-Service himds | Select-Object Name, Status
& "$env:ProgramFiles\AzureConnectedMachineAgent\azcmagent.exe" show
# Check download progress
if (Test-Path "C:\bootstrap") {
Get-ChildItem "C:\bootstrap" -Recurse -File |
Measure-Object -Property Length -Sum |
Select-Object Count, @{N='SizeMB'; E={[math]::Round($_.Sum / 1MB, 1)}}
}
Azure Local Sonar
When to use: Watch all nodes at once from any machine that can reach them. Sonar only reads: it changes nothing.
Connect-AzAccount
./Start-AzlSonar.ps1 -InfrastructureFile ./infrastructure.yml
Leave it open until every node reports that the bootstrap succeeded. Sonar reads the node addresses, the subscription and the resource group from infrastructure.yml.
Expected Status Values
| Status | Meaning | Action |
|---|---|---|
Update: Scan | Scanning for OEM updates | Wait |
Update: Download | Downloading update packages | Wait — check download progress |
Update: Install | Installing updates | Wait — reboot may follow |
UNREACHABLE | Node is rebooting | Wait — auto-resumes after reboot |
InProgress | Arc registration running | Wait for completion |
Succeeded | Node registered with Azure Arc | Proceed to Task 04 |
Failed | Registration or update failed | Collect logs, troubleshoot |
Troubleshooting
Collect Support Logs
# Run on the failed node (RDP/console)
Collect-ArcBootstrapSupportLogs -OutputPath "C:\Logs\ArcBootstrap"
Check Validation Report
# Check validation report on failed node
$reportPath = "C:\Windows\System32\Bootstrap\DiagnosticsHistory\Bootstrap\AzStackHciEnvironmentReport.json"
if (Test-Path $reportPath) {
$report = Get-Content $reportPath -Raw | ConvertFrom-Json
$report.TestResults | Where-Object { $_.Status -ne "Succeeded" } |
Select-Object Title, Status, @{N='Message';E={$_.AdditionalData.Message}}
}
Inspect Bootstrap Logs
# Tail the latest bootstrap log on a node
$logDir = "C:\Windows\System32\Bootstrap\Logs"
$latest = Get-ChildItem $logDir -Filter *.log -ErrorAction SilentlyContinue |
Sort-Object LastWriteTime -Descending | Select-Object -First 1
if ($latest) { Get-Content $latest.FullName -Tail 30 }
Common Issues
| Issue | Resolution |
|---|---|
| Node unreachable 10+ min | Check iDRAC/BMC console — verify node is booting, not stuck |
| Download stalled (no size change) | Check network connectivity (Task 01), proxy settings, DNS |
| Auth failed after reboot | SPN token cache expired — re-run Task 02 on that node |
| Validation failures | Review AzStackHciEnvironmentReport.json — fix prerequisites, re-run Task 01 |
himds service not running | Bootstrap incomplete — wait for ArcConfiguration phase |
Arc agent shows Disconnected in Azure | Check node clock sync (NTP), outbound connectivity |
| Timeout (90+ min, no progress) | Collect support logs, open Microsoft support case |
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.
Navigation
← Task 02: Register Nodes with Arc · Task 04: Verify Arc Registration →
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2025-03-25 | Azure Local Cloud | Initial release |