Baseline update 2405 is coming up!
The Azure Stack HCI, version 23H2 includes multiple release trains: 2306 (limited release), 2311, and 2402 and now 2405. Each release train includes a baseline build and subsequent updates.
- Baseline build: The baseline build is the initial version of the software on a release train. Before you upgrade to the next version on the same train, you must deploy the baseline build.
- Update build: An update build includes the incremental updates from the most recent baseline build.
The following diagram illustrates the release trains, their associated baseline builds, and update paths.
- During cluster deployments that use a large Active Directory, an issue that can cause timeouts when adding users to the local administrator group, is fixed.
- New ARM templates are released for cluster creation that simplify the dependency resource creation. These templates include some fixes that addressed the missing mandatory fields.
- The secret rotation PowerShell command?Set-AzureStackLCMUserPassword?supports a new parameter to skip the confirmation message.
- Improved the reliability of secret rotation when services aren't restarting in a timely manner.
- Fixed an issue so that the deployment is enabled when a disjoint namespace is used.
- Fixed an issue in deployment when setting the diagnostic level in Azure and the device.
- A new PowerShell command is released that can be used to update the SBE partner property values provided at deployment time.
- Fixed an issue that prevents the update service to respond to requests after an SBE only update run.
- An issue is fixed that prevents a node from joining Active Directory during an add server operation.
- Improved the reliability of Network ATC when setting up the host networking configuration with certain network adapter types.
- Improved reliability when detecting firmware versions for disk drives.
- Improved the reliability of update notifications for health check results sent from the device to AUM (Azure Update Manager). In certain cases, the message size could be too large and caused no results to be shown in AUM.
- Fixed a file lock issue that can cause update failures for the trusted launch VM agent (IGVM).
- Fixed an issue that prevented the orchestrator agent from being restarted during an update run.
- Fixed a rare condition where it took a long time for the update service to discover or start an update.
- Fixed an issue for Cluster-Aware Updating (CAU) interaction with the orchestrator when an update in progress is reported by CAU.
- The naming schema for updates was adjusted to allow the identification of feature versus cumulative updates.
- Improved the reliability of reporting the cluster update progress to the orchestrator.
- Resolved an issue where the Azure Arc connection was lost when the Hybrid Instance Metadata service (HIMDS) restarted, breaking Azure portal functionality. The device now automatically reinitiates the Azure Arc connection in these cases.
- When viewing the readiness check results for an Azure Stack HCI cluster via the Azure Update Manager, there may be multiple readiness checks with the same name.
- In some instances, during the registration of Azure Stack HCI servers, this error may be seen in the debug logs: Encountered internal server error. One of the mandatory extensions for device deployment may not be installed.
- There is an intermittent issue in this release when the Azure portal incorrectly reports the update status as Failed to update though the update is complete.
Thanks for reading! Please send me any comments or anything you like to add in the next edition.
Microsoft MVP Windows Server | Azure Hybrid & Migration, RCDA Trainer, CGI Luminary, Director Consulting Expert
6 个月Thanks for putting this together and sharing to the community! #sharing #sharingiscaring
Thank you for this great service, Darryl! In the blog roll, you might want to include the one from Kenny about Azure Arc enabled VMs next time.