Release Notes
• DRM does not support multiuser execution. You cannot run DRM simultaneously on the same system with two separate remote/local
sessions.
• The size of the repository that is created is not displayed in the output if the catalog used for creation does not contain the size
information for DUPs.
• DRM current version cannot discover the Microsoft Exchange Web Service URL from the email ID. User has to manually update the
data for email configuration. Consult Users Guide for process for finding the Microsoft Exchange Web URL.
• Repository refresh shows dates 1 to 30 for all months. For February if 30 is selected, the refresh happens on the last day of the
month.
• 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.
Known Issues
Issue 1
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 2
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 3
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 4
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 5
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 6
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 7
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 8
During upgrade, the installer displays the default path even if the previous installation was on a custom path.
Resolution- You can upgrade DRM in default path or change it to custom path again. If you provide a different location, manually delete
the old files in previous path.
Issue 9
After repair when you chose to restart the system, the system does not restart automatically.
Dell EMC Repository Manager 3.3 Release Notes
3