Release Notes
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.
On Linux Operating Systems, when iDRAC Service Module 2.3.0 and iDRAC Service Module 2.3.0.1 patch are
installed, then to uninstall iDRAC Service Module completely, the iDRAC Service Module 2.3.0.1 patch has to be
uninstalled before uninstalling iDRAC Service Module 2.3.0.
The iDRAC Access via Host OS feature is not supported on VMware ESXi Operating Systems.
When Local RACADM set is disabled through iDRAC interfaces,
The iDRAC Service Module will fail to configure the OS to iDRAC Pass-through in the USB NIC mode.
If OS to iDRAC Pass-through in the USB NIC mode is already configured, Watchdog feature does not work
resulting in ASR000 event.
iDRAC Service Module functionality is restored when "Local racadm set" is enabled.
When you use iDRAC Service Module 2.3 for WMI queries over winrm, additional properties with null value is
observed. This does not affect the functionality and it can be ignored.
If iDRAC Service Module 2.3.0 is installed on a Linux OS with the iDRAC Access via Host OS feature enabled,
you have to to remove the rules of the previous port when upgrading from 2.3.0 to 2.4.0.
When the iDRAC's USB NIC is not functioning, the iDrac Service Module installer is completing the installation
and starting the iDRAC Service Module process without any notification about the failure to start the
communication with the iDRAC. This issue is observed during iDRAC Service Module is installed using setup.sh
command the iDRAC.
Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.