Release Notes
Issue 4
Description: On Microsoft Windows Nano operating system, when iDRAC Service Module 2.4.0 Appx is installed; a critical App-Model-
Runtime message is seen. However, there is no change in the functionality.
Issue 5
Description: On Linux Operating system, NVMe Safe removal operation from iDRAC interfaces (GUI/racadm/wsman) may fail on systems
having other pci devices along with NVMe. This issue is observed on blade chassis.
Issue 6
Description: "Unknown: " error entries are repeatedly logged in the Syslog folder of the ESXi system. The existing logs overwrite other
important events logged previously. This is caused when the virtual switch (vSwitchiDRACvusb) is automatically removed. The issue
occasionally occurs during system shutdown or if an administrator disables the OS to iDRAC Pass-through over USB or enables the OS to
iDRAC Pass-through over LOM.
To stop the repetitive "Unknown:" error entries in the syslog without rebooting the virtual machines or the ESXi hypervisor, perform the
following steps:
1. ps | grep vmsyslogd (and note the CID number)
2. kill -15 <CID number>
3. /etc/init.d/sfcbd-watchdog restart
Installation
• To install iDRAC Service Module on Windows Server 2008 R2 SP1 Core, Microsoft Windows Server 2012 Core and Microsoft
Windows Server 2012 R2 Core, Windows-on-Windows (WOW) mode must be enabled.
• You must login to the system as an administrator or choose the Run as administrator option to install iDRAC Service Module.
• On the Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems, to perform an Express Install execute dcism-
setup.sh -x from the SYSMGMT/iSM/linux directory.
For more information on installation instructions, including silent installation options, see the iDRAC Service Module Installation Guide.
Limitation
• Do not specify user profile folders such as a desktop folder (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.
• On systems running Microsoft Windows Server 2008 Service Pack 2 operating system, a warning message about the Dell Self-Signed
Certificate for registering the Dell iDRAC Virtual USBNIC Device is displayed during iDRAC Service Module installation. Click Install to
proceed with the installation (BITS113354).
• When OS to iDRAC Pass-through in the USB NIC mode is enabled with USB 3.0 enabled in BIOS, iDRAC Virtual USB NIC driver does
not load automatically on Microsoft Windows 2008 R2 SP1. The Intel USB 3.0 xHCI driver on Microsoft Windows 2008 R2 SP1 Host
OS is not recognizing the RNDIS configuration during enumeration. This issue is specific to USB 3.0 and Microsoft Windows 2008 R2
SP1. To resolve the issue, manually load the Microsoft RNDIS driver on the Host OS (BITS239254).
• Lifecycle Controller logs are not seen 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 (BITS113354).
• On Dell’s 12th generation of PowerEdge servers with iDRAC firmware version 1.57.57 or earlier, Windows Management
Instrumentation (WMI) feature is not active by default. The WMI feature is automatically activated when iDRAC firmware version
2.10.10.10 or later is installed (BITS113354).
• On Windows operating system, a feature that is enabled using the installer and disabled using any interface other than the installer, can
only be enabled using the same interface or the installer in GUI mode (BITS180635).
• If iDRAC Service Module 2.0 or later is used with an iDRAC firmware version prior to 2.10.10.10, the WMI interface may stop
responding. It is recommended to upgrade to the latest iDRAC firmware or reset the iDRAC (BITS178203).
• When iDRAC Service Module 2.3 is used for WMI queries through WinRM, additional properties with null value may be observed. This
can be ignored.
• Feature Lifecycle Log Replication on OS Log shows one-hour difference in the EventTimeStamp displayed in OS log, when daylight
saving is applied.
iDRAC Service Module 2.4 Release Notes
3