Updated docs with SBE related content per Dan DeFolo

Author: ronmiab

azure-stack/hci/known-issues-2408-1.md

@@ -41,6 +41,9 @@ The following issues are fixed in this release:
 | Update <!--28489253--> | MOC node agent would get stuck in a restart pending stage during the update MOC step. ||
 | Update <!--29075839--> | Required permissions were not granted when upgrading which caused update to fail later. ||
 | Upgrade <!--29346181--> | Added validation to check for an IPv6 address. ||
+| Update | SBE interfaces wouldn't execute on all the servers if the hostname in the cluster was a subset of another hostname. ||
+
+Use appropriate host naming conventions.
 
 ## Known issues in this release
 

azure-stack/hci/known-issues-2408.md

@@ -53,6 +53,9 @@ The following table lists the known issues in this release:
 | Security <!--29333930--> | The SideChannelMitigation security feature may not show an enabled state even if it's enabled. This happens when using Windows Admin Center (Cluster Security View) or when this cmdlet returns *False*: `Get-AzSSecurity -FeatureName SideChannelMitigation`. | There's no workaround in this release to fix the output of these applications. <br> To validate the expected value, run the following cmdlet: <br> `Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management' -name "FeatureSettingsOverride*"`<br> The expected output is: <br> FeatureSettingsOverride: 83886152<br> FeatureSettingsOverrideMask: 3 <br> If your output matches the expected output, you can safely ignore the output from Windows Admin Center and `Get-AzSSecurity` cmdlet.|
 | Arc VM management | The Mochostagent service might appear to be running but can get stuck without updating logs for over a month. You can identify this issue by checking the service logs in `C:\programdata\mochostagent\logs` to see if logs are being updated. | Run the following command to restart the mochostagent service: `restart-service mochostagent`. |
 | Upgrade <!--29319539--> | When upgrading the stamp from 2311 or prior builds to 2408 or later, add node and repair node operations may fail. For example, you could see an error: `Type 'AddAsZHostToDomain' of Role 'BareMetal' raised an exception`. | There's no workaround in this release. If you encounter this issue, contact Microsoft Support to determine next steps. |
+| Update | When installing an SBE update for your Azure Stack HCI system, some SBE interfaces aren't executed on all the servers if the hostname in the cluster is a subset of another hostname. For example, host-1 is a subset of host-10. This could result in failures in the CAU scan or CAU run. | Use appropriate host naming conventions. |
+
+Use appropriate host naming conventions.
 
 ## Known issues from previous releases
 

azure-stack/hci/whats-new.md

@@ -68,6 +68,14 @@ This release contains the following changes for Arc VM management:
 
 For more information, see the [Fixed issues list in 2408](./known-issues-2408.md#fixed-issues).
 
+## SBE changes
+
+This release contains the following changes for SBE:
+
+- **Reduced deployment times**: Starting in this release, SBE extension interfaces are executed more efficiently leading to reduced Azure Stack HCI deployment times.
+- **CAU plugin**: Starting in this release, SBE extensions utilize a new CAU plugin that supports enhancements. Check with your hardware vendors to determine if and how they use this plugin.
+- **Improved error details**: Starting in this release, failures or exceptions that involve hardware vendor SBE will include the SBE publisher, family, and version at the beginning of the exception string. Provide this information to your hardware vendor for proper information on the exception.
+
 ## [2405 releases](#tab/2405releases)
 
 The 2405 release train includes the following releases: