The following table lists known issues and workarounds related to OpenManage Integration with Microsoft Windows Admin Center with Microsoft HCI Solutions from Dell Technologies clusters.
|Resolution or workaround
Running Test-Cluster fails with network communication errors.
With USB NIC enabled in iDRAC, if you run the Test-Cluster command to verify the cluster creation readiness or cluster health, the validation report includes an error indicating that the IPv4 addresses assigned to the host operating system USB NIC cannot be used to communicate with the other cluster networks.
|This error can be safely ignored. To avoid the error, temporarily disable the USB NIC (labeled as Ethernet, by default) before running the Test-Cluster command.
The USB NIC network appears as a partitioned cluster network.
When the USB NIC is enabled in iDRAC, cluster networks in the failover cluster manager show the networks associated with the USB NIC as partitioned. This issue occurs because the cluster communication is enabled by default on all network adapters, and USB NIC IPv4 addresses cannot be used to communicate externally, which, therefore, breaks cluster communication on those NICs.
| Remove the USB NIC from any cluster communication by using the following script:
|While triggering full stack updates, the Tests Summary page might appear.
As a workaround, verify whether the pre-update or post-update scripts are part of the cluster role. If they are present, remove the scripts from the cluster node by running the following command in PowerShell:
For more information about the prerequisites required for a cluster update, see Update Azure Stack HCI clusters.
|The update status takes a long time to refresh.
|During full stack cluster updates, the update status shown in the Updates page might take a long time to refresh. If this issue occurs, it is recommended that you stay on the Updates page and wait for the update to complete. The update status will automatically be displayed once the update is complete.
|When using CredSSP authentication to run scripts on a remote machine, the update job might fail with an error. This failure occurs because CredSSP has been disabled in the gateway machine.
|To resolve the issue, follow these steps: