Release Notes

Limitations on Microsoft Windows operating systems
● During iDRAC Service Module installation, do not specify your desktop user profile's folder path in the custom installation
path. For example, C:\Users\administrator\Desktop must not be used in the custom installation path. This is because
services running on the system account cannot access such folders.
● You cannot view Lifecycle Controller logs in the new folder in the Event Viewer (169898) if you have recently changed
the folder name of the Lifecycle Controller logs in the Event Viewer. Microsoft recommends that you reboot the operating
system to be able to view the Lifecycle Controller logs under the new view name.
JIT-115250
When iDRAC Service Module is installed on systems running Microsoft Windows operating systems using an OS DUP, then the
iSM Modify and Repair operation from the Add/Remove programs will throw an error, original source path of the file is not
found . You can extract the iSM DUP file, double click the MSI file, and run repair.
Limitations on Linux operating systems
BITS088419
Description: Lifecycle Log Replication feature in operating system log shows one-hour difference in the EventTimeStamp
displayed in operating system log when daylight saving time is in effect.
JIT-87572
Description: When the iDRAC HardReset option is disabled in iDRAC and you can perform a iDRACHardReset operation from
the hypervisor operating systems such as Citrix Xen , the result indicates success although iDRAC is not reset.
JIT-117904
Description: In GNOME-enabled Linux variants, if the auto-suspend feature is enabled, the operating system gets into
suspended state after a certain idle time. This logs a message, Watchdog Timer Expired, in the Lifecycle Log, if the operating
system is not awake before the watchdog expiry time is reached.
JIT-117517
Description: iSM start communications with iDRAC using IPv4 stack by default. If you bring down the OS-BMC Passthrough,
host side interface using ifconfig <interface-name> down, the communication will switch to IPv6 once the interface is
brought up.
Limitations and workarounds on VMware ESXi operating systems
iDRAC access through the host operating system feature is not supported on VMware ESXi operating systems.
When local racadm set is disabled through iDRAC interfaces:
● iDRAC Service Module fails to configure the OS-to-iDRAC Passthrough in USB NIC mode.
● iDRAC Service Module functionality is restored when local racadm set is enabled.
EventID for Lifecycle Controller logs replicated into the operating system log is 0 for some past events.
TrapID for in-band SNMP traps is 0 for some past traps.
JIT-91716 and JIT-90475
Description: WSMan commands for remote iDRAC hard reset and remote enabling or disabling of InBandSNMPTraps features
are not functional on VMware ESXi 6.7 or later.
Workaround: Stop and start WBEM in ESXi 6.7 and later using the following commands:
3