In Windows Admin Center, select Updates from the Tools pane at the left. If you've successfully joined the preview channel, feature updates will be displayed.
Select Install. A readiness check will be displayed. If any of the condition checks fail, resolve them before proceeding.
When the readiness check is complete, you're ready to install the updates. Unless you want the ability to roll back the updates, check the optional Update the cluster functional level to enable new features checkbox; otherwise, you can update the cluster functional level post-installation using PowerShell. Review the updates listed, and select Install to start the update.
You'll be able to see the installation progress as in the screenshot below. Because you're updating the operating system with new features, the updates may take a while to complete. You can continue to use Windows Admin Center for other operations during the update process.
Note
If the updates appear to fail with a Couldn't install updates or Couldn't check for updates warning, or if one or more servers indicates couldn't get status during the updating run, try waiting a few minutes and refreshing your browser. You can also use Get-CauRun to check the status of the updating run with PowerShell.
When the feature updates are complete, check if any further updates are available and install them.
To install a preview version using PowerShell, follow these steps.
Run the following cmdlets on every server in the cluster:
To test whether the cluster is properly set up to apply software updates using Cluster-Aware Updating (CAU), run the Test-CauSetup cmdlet, which will notify you of any warnings or errors:
Test-CauSetup -ClusterName Cluster1
Validate the cluster's hardware and settings by running the Test-Cluster cmdlet on one of the servers in the cluster. If any of the condition checks fail, resolve them before proceeding to step 4.
Test-Cluster
Run the following cmdlet with no parameters on every server in the cluster:
Set-PreviewChannel
This cmdlet will configure your server to receive builds sent to the ReleasePreview-External audience. If your server wasn't already configured for flight signing, you'll need to restart after opting in. The module's output will tell you if you need to restart.
Inspect the output of the above cmdlet and verify that each server is offered the same Feature Update, which should be the case.
You'll need a separate server or VM outside the cluster to run the Invoke-CauRun cmdlet from.
Important
The system on which you run Invoke-CauRun must be running either Windows Server 2022, Azure Stack HCI, version 22H2, or Azure Stack HCI, version 21H2 with the May 20, 2021 preview update (KB5003237) installed.