Release Notes

Workaround:
As a workaround, after the CAU job is completed, restart the cluster node or nodes where AHCI controller is an applicable
update and refresh the inventory.
● Issue 33
Description:
In the Maintenance Center page, while performing Run Update using Cluster Aware Update method, user cannot
update the firmware version of operating system driver pack.
Workaround:
As a workaround, you can update the operating system driver pack from iDRAC console, or can directly run the DUP on the
node operating system.
● Issue 34
Description:
In Modular Systems view, Operational Template Compliance Summary displays noncompliant with zero noncompliant
attributes for MX7000.
Cause:
If MX7000 discovered in OMIMSSC is at 1.10.00 firmware version, attributes present under following specified groups cannot
be configured using modular system type Operational Template and these attributes should be modified outside of
OMIMSSC.
○ LocalAccessConfiguration
○ TimeConfig
○ Power
○ SessionConfiguration
Workaround:
Recapture the Operational Template and rerun the compliance.
● Issue 35
Description:
In the Maintenance Center page, on performing import device profile, using vFlash as a Protection Vault, imported
firmware version of few components may not reflect .
Workaround:
As a workaround, perform a refresh inventory after successful import of device profile.
● Issue 36
Description:
Operating system deployment in SCVMM fails with an error message: Invalid data manager state found for
host . Reason being, managed node does not boot to installed operating system since the WinPE image is not
disconnected.
Workaround:
On completion of operating system installation in SCVMM, before the manage node boots to installed operating system,
disconnect the attached WinPE image.
To disconnect run the following WinRM command: winrm i DetachISOImage http://schemas.dmtf.org/wbem/
wscim/1/cim-schema/2/root/dcim/DCIM_OSDeploymentService?
CreationClassName=DCIM_OSDeploymentService+Name=DCIM:OSDeploymentService
+SystemCreationClassName=DCIM_ComputerSystem+SystemName=DCIM:ComputerSystem -u:<username>
-p:<password>-r:https://<ip address> -SkipCACheck -SkipCNCheck -encoding:utf-8 -a:basic
● Issue 37
Description:
After applying Update Rollup for SC2012 R2 VMM, SC2016 UR9, and SC2019 UR1, if you try to open the already installed
OMIMSSC console, SCVMM displays an error message for security reasons, and you cannot access the OMIMSSC console.
Workaround:
12
OpenManage Integration Version 7.2.1 for Microsoft System Center Release Notes