Dell OpenManage Integration with Microsoft Windows Admin Center Version 3.0 Release Notes

PDF

Known issues

The following issues remain unresolved in this release:

Table 1. Known issues in OpenManage Integration with Microsoft Windows Admin Center 3.0
Issue ID	Functional area	Description	Workaround/Resolution
262144	Hardware update	During hardware updates using a DRM catalog with DSU 2.0.2, server update or Cluster-Aware Update may fail for clusters based on YX6X (16G) PowerEdge servers.	When selecting or unselecting components in the Fix Compliance window, ensure to unselect the OS driver components and then proceed with the update.
264638	Hardware update	During hardware updates using DSU 2.0.2 and IC invcol_T4M1J_WIN64_23_03_00_44_A00, server update or Cluster-Aware Update may fail.	When selecting or unselecting components in the Fix Compliance window, ensure to unselect the not applicable components and then proceed with the update. See the user's guide troubleshooting section to learn more about the not applicable components.
264634	Hardware update	During hardware updates using DSU 2.0.2 and IC invcol_T4M1J_WIN64_23_03_00_44_A00, Cluster-Aware Update may intermittently fail for clusters with an error in the log file stating "Invalid --input-inventory-file path is given"	Retry the hardware updates.
257967	Hardware update	When using the DRM catalog (offline catalog) to perform hardware updates on a server or cluster, the compliance report generation may fail.	Navigate away from the feature and retry the operation.
244558	Overview	In the Overview page, CPU Core section displays "No Information Available" even when the details are retrieved until you navigate to the CPU Core page.	When the CPU Core section in the Overview page shows no information available, do the following: Ensure the inventory is retrieved successfully. Click View > Configure > CPU Core to go to the CPU Core Management page to generate the CPU core configuration details. Once the details are available in CPU Core Management page, the details will also be available in CPU Core section in the Overview page for remainder of session.
244490	User Interface	While using the extension, when you click the back or forward button in the browser, the selections in the View menu don't change, but the content of the page changes.	Select the item from the View menu again to match with the page content.
247124	Cluster creation using OpenManage Integration snap-in	While creating a cluster using OpenManage Integration snap-in, the license status in the Update Checklist section may show as critical, even if the licenses are installed on nodes.	This happens when one of the prerequisites for cluster creation fails. Follow the recommendations to resolve the non-compliant prerequisites and try again.
243406	Prerequisite check	When the WinRM port is disabled on any cluster node, the "Access Windows Admin Center locally" prerequisite check may incorrectly show as compliant.	Enabling WinRM ports is one of the primary requirements for using OpenManage Integration for successful monitoring and management operations. If the WinRM port for any target node is not accessible by OpenManage Integration, none of the features will work. Once the prerequisite is addressed, this check functions properly.
229419	HCP Compliance and CPU Core for Single node HCI	For Single node HCI, configure cluster inputs in HCP compliance and infrastructure lock in CPU core are allowed.	HCP compliance and CPU core features are disabled for single node HCI clusters. If the infrastructure lock is disabled using the Disable option, it can be re-enabled from the Security menu.
231314	Azure-Integration	For on-premise HCP, notification for any new policies appear only when the Dell OpenManage Integration extension is launched for the first time. After that, the notification does not appear on the cluster.	The notification remains in the notification tab and can be accessed until the browser is reopened. As a workaround, the notification appears every time you use a feature in Azure. This can be taken as a reminder to generate on-prem compliance as well.
231489	Security and Cluster recommendation	For clusters created from YX2X or YX3X nodes, a critical banner message about licensing is displayed in the Security, Cluster recommendation, and Configure page.	The features requiring the OMIWAC Premium license are not supported for clusters made of YX2X or YX3X models. For more information about supported models, see OMIMSWAC user guide.
251421	Expand cluster	In License Availability section, if you click Check repeatedly, new nodes and cluster nodes license check results may show unknown even when the license is present on the nodes.	When license check shows unknown for any node even when the license is present on the node, click Refresh to resolve the issue.
250249	Cluster-Aware Updating	For Azure Stack HCI cluster with 22H2 OS, Cluster-Aware Updating (CAU) run options does not get reset after the update is performed.	There is no impact to OMIMSWAC Hardware Updates or Microsoft WAC Updates flow even if the CAU run options are not reverted. However, OMIMSWAC keeps a backup of the previous options in C:\Windows\Temp folder with the name CAUClusterRoleBackup_<timestamp>.xml. Detailed instructions are provided in the user's guide troubleshooting section to revert the CAU run options.
248593	Hardware Symmetry Check	For Hardware Symmetry check in any flow, if any of the categories collapsed, the Show Details link (if present) under Details column does not work.	Go to another page and come back to the respective page containing Hardware Symmetry check details again to see show details.
249231	User Interface Text	Certain header texts do not appear as bold, as intended, in non-English languages.	There is no functionality impact for this. The texts come in different fonts, for distinguishing them from other texts.
231314	HCP Compliance	Notification for any new policies appear only on the first time that the Dell extension is launched, and after that the notification does not appear for any cluster.	The notification remains in the notification tab and can be accessed until the browser is reopened. As a workaround, for Azure features the notification comes every time you use it. This can be taken as a reminder to generate on-prem compliance as well.
231489	Security and Cluster Recommendation	Configuring security and cluster recommendation features are not supported for clusters made up of YX2X or YX3X nodes.	The features requiring the OMIWAC Premium license are not supported for clusters made of YX2X or YX3X models. For more information about compatible models, see the Compatibility Matrix in the OMIMSWAC user guide.