Release Notes

Limitations
Topics:
• Limitations on Microsoft Windows operating systems
•
Limitations on Linux operating system
• Limitations on VMware ESXi operating systems
Limitations on Microsoft Windows operating systems
● Do not specify user profile folders (C:\Users\administrator\Desktop) as custom installation paths for installing iDRAC
Service Module. 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.
● When iDRAC Service Module is installed on Microsoft Windows operating systems using OS DUP, then the iSM Modify and
Repair operation from the Add/Remove programs throws and error:
Original source path of the file is now found
You can unzip the iSM DUP, double-click the MSI, and run repair.
Tracking number : 115250
Limitations on Linux operating system
● Feature Lifecycle Log Replication on OS log shows one-hour difference in the EventTimeStamp displayed in OS log when
daylight saving is applied.
Tracking number: BITS088419
● When iDRAC Hard Reset is disabled in iDRAC and you perform iDRACHardReset from the Hypervidor operating systems
such as Citrx Xen, the result indicates success although iDRAC is not reset.
Tracking number: 87572
● In GNOME enabled Linux variants, if 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 Lifecycle Logs if the operating system is not awake
before watchdog expiry time.
Tracking number: 117904
● iSM starts communication with iDRAC using IPv4 stack by default. If you bring down OS-BMC Passthrough Host side
interface using ifconfig<interface-name>down, the communication will switch to IPv6 once the interface is brought up.
Tracking number: 117517
Limitations on VMware ESXi operating systems
● iDRAC Hard Reset using winrm command requires iDRAC Service Module to be in running state.
Tracking number: 132478
● The iDRAC Access via Host OS 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 Passthru in the USB NIC mode.
5
12 Limitations