Introduction & Configuration
Learn about SBE and select your setup
First-Time SBE Installation
Complete installation guide for deploying SBE for the first time
Prerequisites:
- Azure Local 23H2 (2311.2) or later deployed and registered in Azure
- Administrative access to the cluster
- Network access to download SBE packages from DataON portal
Overview of Steps:
- Introduction & Configuration - Learn about SBE and select your setup
- Connect & Discover Updates - Establish connection and discover available updates
- Download SBE Package - Download the initial SBE package manually from the portal
- Check Update Readiness - Verify packages are imported and run health checks
- Install & Track Progress - Start installation and monitor progress until completion
- Setup Automatic Updates (Optional) - Configure automatic download connector for future updates
Important Notes:
- First-time installation always requires manual download of the initial package
- Automatic download connector can be configured after installation for future updates
- Allow sufficient time for health checks and installation (see time estimates in Step 1)
Quick Links:
DataON Solution Builder Extension (SBE) Update Package
This installation guide will walk you through the complete process of updating your DataON Azure Stack HCI cluster with the latest SBE version. The Solution Builder Extension provides essential firmware packages that ensure optimal performance, security, and compatibility for your DataON hardware and Azure Stack HCI environment.
Supported Models
Ready for multiple series
Select a model family in the previous page or use the update catalog to see model-specific details.
Connect & Discover Updates
Establish connection and discover available updates
Prerequisites
Connect to Your Azure Local
Open a remote PowerShell session to one machine in the system using the deployment user account.
$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.
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.
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.
Download SBE Package
Required Download the initial SBE package manually from the portal
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
Import SBE Packages Mnaually
First create a folder on the cluster shared volume (CSV) that will hold all the SBE files.
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.
Add-SolutionUpdate -SourceFolder C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import
Step-by-Step Import Process
Download Files
Download all required SBE package files using the download section above
Create Import Directory
Run the first command to create the import directory on your cluster storage
Copy Files
Copy downloaded files to the created import directory on the cluster
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.
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.xmlSBE_DataON_<FAMILY>_<VERSION>.xmlSBE_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
Install & Track Progress
Start installation and monitor progress until completion
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.
$InstanceId = Get-SolutionUpdate -Id RESOURCE_ID | Start-SolutionUpdate
Track Installation Progress
Use these commands to track installation progress via PowerShell.
Get-SolutionUpdateRun -InstanceId $InstanceId
Get-SolutionUpdateRun -InstanceId $InstanceId | FL *
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.
Get-SolutionUpdate -Id RESOURCE_ID | Start-SolutionUpdate -Rerun
-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
Monitor Regularly
Check status every 15-30 minutes during installation
Use Azure Portal
Azure portal provides real-time progress visualization
Review Logs
Check installation logs if issues occur
Final Installation Verification
After installation completes, verify the new version is active.
Get-SolutionUpdateEnvironment
Get-SolutionUpdate | FL DisplayName, State, InstalledDate
Verify These Items:
- CurrentVersion matches the installed update version
- HealthState is "Success"
- State for the update shows "Installed"
- InstalledDate is recent (today's date)
Installation Complete!
Your SBE installation has been successfully completed. The cluster is now running the updated version.
Setup Automatic Updates (Optional)
Optional Configure automatic download connector for future updates
Installation Complete!
Congratulations! Your initial SBE installation is complete. This optional step helps you configure automatic downloads for future updates.
Now that SBE is installed, you can optionally configure automatic package downloads to simplify future updates.
Benefits of Automatic Downloads
Configuration Process
Verify Prerequisites
Ensure your SBE version is 4.1.2411.xxxx or higher and cluster is registered
Check Current Status
Run Get-SolutionExtensionProperty to check if download connector is already enabled
Enable Download Connector
If not enabled, run the configuration command to enable automatic downloads
Verify Configuration
Confirm the setting is applied by re-running the status check command
Important Notes
- This step is completely optional
- If skipped, you can manually download packages for future updates
- Can be configured later if needed