Release Notes

• It is recommended not to launch the application from multiple user contexts. Occasionally there is certain unexpected GUI behavior

because of insufficient permissions to the temp folder(C:\windows\temp or /tmp).

• Creating a repository from inventory file and with available catalog using CLI is not supported when catalog and inventory are placed in

different network location.

• Comparison shows some downgrades and upgrades for DUPs incorrectly. Check the properties of DUPs in the right pane of the UI for

devices supported before revising the component.

• Refresh inventory feature is not supported for any repository that is created using a local inventory.xml file.

• In DRM GUI, using the import feature you can import only one DUP at a time, whereas in CLI, you can import multiple DUPs.

• Multiple iDRAC versions are displayed when creating a manual repository through GUI on 13G servers using the IDSDM DUPs.

• IDSDM DUPs are not listed when creating a repository on 13G servers having IDSDM firmware DUPs.

• Import repository job fails if you have selected the FX2 Chassis System Management DUPs.

• After establishing a successful connection through the proxy configuration in the Network Preferences section, the same password is

used for further connections from cache regardless of any changes made to it.

• Custom script name for smart bootable ISO should not be apply_bundles.sh.

• Remote access to DRM is not supported.

Known Issues

Issue 1

DRM becomes unresponsive and the error message "DRM connection lost" is displayed.

Resolution- Press CTRL+F5 keys, or relaunch the application to reestablish the service connection.

Issue 2

You cannot downgrade to a lower version of DRM using the current DRM installer.

Resolution- To install an earlier version of DRM, first uninstall the newer version manually through Add or Remove Programs in Windows

Control Panel and then run the installer of the desired version.

Issue 3

Mapped network path for a user is not accessible in DRM as a location with Microsoft Windows. The mapped network path is only

available to download the log in zip format.

Resolution- Provide the network path along with authentication.

Issue 4

Random program files of DRM are deleted when Microsoft Windows goes for a hard system reset.

Resolution- Repair or reinstall the application to update the missing files.

Issue 5

Some of the repositories from DRM 2.x may not be migrated to DRM 3.x, if the DRM 2.x application is up and running during DRM 3.x

installation.

Resolution- Remove the database files, close the DRM 2.0 application, and then install DRM 3.0

Issue 6

If the application GUI is kept open during uninstallation, a message is displayed which indicates a system restart is required but system

does not reboot even after consent for the same.

Resolution- Uninstall DRM only after closing the application GUI.

Issue 7

Share folders of an SMB 2 server cannot be enumerated in browse for location windows.

Resolution- Provide the share name along with IP or system name and the folders can be browsed.

Issue 8

Store Clean-up job fails for an SMBv2 share if the store contains at least one file apart from folders.

Resolution-Delete the individual files manually and then run the store cleanup job for the rest of the content.

Issue 9

During upgrade, the installer displays the default path even if the previous installation was on a custom path.

Release Type and Definition