Release Notes

Table 6. Known issues on VMware ESXi operating system (continued)
Issue ID Functional area Description Workaround
If the removal fails, then applications
such as iDRAC Service Module and
OpenManage Server Administrator
must be stopped using the
ipmi_si command, and then you
can retry the operation.
Alternatively, the administrator can
also restart the host operating
system to resolve the issue.
192624 Invoke-
iDRACHardReset and
Invoke-FullPowerCycle
The iSM features "Invoke-
iDRACHardReset" and "Invoke-
FullPowerCycle" are not supported when
the "SMM Security Mitigation" is enabled
from the BIOS on VMware ESXi 7.x
operating systems.
Not available.
199162 SupportAssist
registration
SupportAssist registration is not successful
on VMware ESXi operating system, when
the internet connectivity to the server is
configured through the proxy.
Not available.
Limitations
Common limitations
The following limitations are applicable to all the operating systems.
Table 7. Common limitations
Issue ID Functional area Description
158667
159019
158514
158740
Interruption in communication
between iDRAC and iSM.
When the workload on the host increases due to intensive
task requests by the processor, the communication between
iDRAC Service Module and iDRAC is interrupted for a moment
and restored automatically.
Not available Communication between iSM and
iDRAC is not established.
When Federal Information Processing Standards (FIPS) mode
is enabled either on the host operating system or iDRAC,
communication between iSM and iDRAC is not established.
Limitations on Microsoft Windows operating system
Table 8. Limitations on Microsoft Windows operating system
Issue ID Functional area Description
115250 Installing iSM on Microsoft
Windows operating systems.
When iSM is installed on Microsoft Windows operating
systems using an operating system DUP, then the iSM Modify
and Repair operation from the Add/Remove option displays
the following error message: Original source path of
the file is now found.
You can extract the iSM DUP, double-click the MSI, and run
repair.
7