iDRAC Service Module 3.0.1 Release Notes
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.
- 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 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).
- Feature Lifecycle Log Replication on OS Log shows one-hour difference in the EventTimeStamp displayed in OS log, when daylight saving is applied. (BITS088419)
- 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.
- EventID for Lifecycle Controller Logs replicated to OS log will be 0 for some of the past events.
- TrapID for In-band SNMP Traps will be 0 for some of the past traps.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\