loading

Check Current Version & Discover Updates

Connect to cluster and check for available updates

Prerequisites
Connect to Your Azure Local

Open a remote PowerShell session to one machine in the system using the deployment user account.

PowerShell Commands
$cred = Get-Credential
Enter-PSSession -ComputerName "YOUR_CLUSTER_NODE" -Credential $cred

Sign in with the deployment user account created during Active Directory prep.

Confirm Software and Verify System Health

Ensure the system is on Azure Local 2311+ and is healthy before proceeding.

PowerShell Commands
whoami
Get-SolutionUpdateEnvironment
Important Checks:
  • Record CurrentVersion
  • Verify HealthState is Success; if Failure/Error/Warning, troubleshoot readiness first
Discover Available Updates

List update candidates and inspect details of the one you plan to install.

PowerShell Commands
Get-SolutionUpdate | Where-Object {$_.State -like "Ready*" -or $_.State -like "Additional*"} | FL DisplayName, Description, ResourceId, State, PackageType
Get-SolutionUpdate | FL DisplayName, Description, ResourceId, State, PackageType
$Update = Get-SolutionUpdate -Id RESOURCE_ID
$Update.ComponentVersions

You may see both Solution and SBE (Solution Builder Extension) items.

If the expected update isn't Ready, remove filters to see non-ready states.

Review Release Notes

Check release notes and known issues for the target version

Content Not Available

The content for this step (ID: review-release-notes) is not yet available.

Expected partial: ../installation/step-release-notes-review

Download SBE Update Package

Required Download the latest SBE package manually

When to Use This Method

Import SBE packages manually if:

  • The update reports AdditionalContentRequired
  • You received a private build
  • You want to avoid online download of the SBE
  • Download connector is not enabled or fails
Download Required Files

You'll need these files for manual import. Download them to a local folder on the cluster node first.

For example C:\SBE

Browse the Update Catalog

Every SBE package includes three files:

  1. SBE_Discovery_DataON.xml
  2. SBE_DataON_<family>_<version>.xml
  3. SBE_DataON_<family>_<version>.zip
Open Update Catalog
File Access Required

Login required to access and download SBE package files.

Login
Import SBE Packages Mnaually

First create a folder on the cluster shared volume (CSV) that will hold all the SBE files.

Import Commands
New-Item C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import -ItemType Directory

Then run the below command to manually add the SBE update files to the cluster.

Import Commands
Add-SolutionUpdate -SourceFolder C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import
Step-by-Step Import Process
1
Download Files

Download all required SBE package files using the download section above

2
Create Import Directory

Run the first command to create the import directory on your cluster storage

3
Copy Files

Copy downloaded files to the created import directory on the cluster

4
Import Updates

Run the Add-SolutionUpdate command to import the packages

Important Notes:
  • Ensure all required files are downloaded before running import commands
  • The import directory will be created automatically if it doesn't exist
  • Files must be placed in the correct cluster storage path
  • Verify file integrity before importing
  • Check cluster storage space before copying large files
Troubleshooting
Import Directory Access Issues

If you cannot create the import directory, ensure you have administrative privileges and the cluster storage is accessible.

File Copy Failures

Verify sufficient disk space and that no files are in use or locked before copying to the import directory.

Add-SolutionUpdate Errors

Ensure all files are properly copied and the path exists. Check that you're running PowerShell as an administrator.

Check Update Readiness

Verify packages are imported and run health checks

Download & Health Check

The below commands start the preparation of the update by downloading packages and run readiness checks without starting installation.

Predownload & Readiness Check

The below commands start the preparation of the update by downloading packages and run readiness checks without starting installation.

Predownload Commands
Get-SolutionUpdate | Where-Object {$_.PackageType -eq 'SBE' -and $_.State -eq 'Ready' -and $_.Sbeversion -eq 'VERSION' } | Start-SolutionUpdate -PrepareOnly
Get-SolutionUpdate -Id RESOURCE_ID | ft Version,State,UpdateStateProperties,HealthState

If SBE packages are imported already with Add-SolutionUpdate, PrepareOnly performs health-checks only.

For subsequent SBE updates with download connector enabled, PrepareOnly performs downloads and health-checks

With download connector:

You should see the latest SBE package available for your system. The download connector will automatically download:

  • SBE_Discovery_DataON.xml
  • SBE_DataON_<FAMILY>_<VERSION>.xml
  • SBE_DataON_<FAMILY>_<VERSION>.zip

Files will be placed in: C:\ClusterStorage\Infrastructure_1\SU1_Infrastructure_1\Updates\Packages\<VERSION>

States You May See During This Process
Downloading

System is downloading required packages

HealthChecking

Running pre-installation health checks

ReadyToInstall

System is ready to proceed with installation

HealthCheckFailed

Issues detected - troubleshoot before proceeding

Troubleshooting Common Issues

This usually happens when the current SBE version is older than 4.1.2411.xxx.

Solution: Go back to Step 5 (Import Files) and manually import the SBE packages first.

Health check failures must be resolved before proceeding with installation.

Actions:
  • Check cluster node health and network connectivity
  • Verify sufficient disk space on all nodes
  • Review Windows Event Logs for specific error details
  • Contact support if issues persist

Download time depends on network speed and package size.

Tips:
  • Monitor progress with the status command above
  • Ensure stable network connectivity
  • Consider manual import (Step 3) for faster deployment

Start Installation

Begin the update installation process

Important Notice
  • Machines may reboot during installation
  • PowerShell sessions can drop and need re-establishing
  • Save the Instance ID for troubleshooting reference
  • Monitor progress preferably in Azure portal
Start the Installation

Begin installation. If you skipped PrepareOnly, Start-SolutionUpdate will download and health-check first.

Installation Command
$InstanceId = Get-SolutionUpdate -Id RESOURCE_ID | Start-SolutionUpdate
Important: Save the $InstanceId for troubleshooting reference. This ID helps track your specific installation.
Installation Process Flow
1
Command Execution

Start-SolutionUpdate command is executed

2
Download Phase

If PrepareOnly was skipped, downloads occur now

3
Health Checks

Final pre-installation validation

4
Installation Begins

Actual update installation starts

5
Node Updates

Each cluster node is updated sequentially

6
Completion

Installation completes and verification begins

Track Progress & Verify

Monitor installation and verify completion

PowerShell Progress Monitoring

Use these commands to track installation progress via PowerShell.

Monitoring Commands
Get-SolutionUpdate -Id RESOURCE_ID | ft Version,State,UpdateStateProperties,HealthState
Tip: If monitoring with PowerShell, connect to the last server updated to minimize session drops during reboots.
Installation States You May See
Downloading

Downloading required packages (if not already done)

Preparing

Preparing packages for installation

HealthChecking

Final health validation before installation

Installing

Installation in progress - nodes may reboot

Installed

Installation completed successfully

Resume Installation (If Needed)

If a previous installation failed or was interrupted, you can resume using these commands.

Resume Commands
Get-SolutionUpdate -Id RESOURCE_ID | Start-SolutionUpdate
Get-SolutionUpdate -Id RESOURCE_ID | Start-SolutionUpdate -IgnoreWarnings
Use -IgnoreWarnings to resume after readiness checks that are in Warning state if acceptable.
Progress Tracking Tips
Be Patient

Installation can take 1-4 hours depending on cluster size

Check Periodically

Run status commands every 15-30 minutes if using PowerShell

Keep Records

Note down the Instance ID and any error messages

Final Installation Verification

Confirm solution version and OS version post-install to ensure successful completion.

Verification Commands
Get-SolutionUpdateEnvironment | ft State, CurrentVersion
cmd /c ver
Expected Results:
State: AppliedSuccessfully
OS build: Matches the installed recipe