DELL EMC Repository Manager Version 3.4.2 Release Notes User Guide
- June 9, 2024
- DELL EMC
Table of Contents
Dell EMC Repository Manager Version 3.4.2
Release Notes
Release Type and Definition
Topics:
- Importance
- What is new in this release
- Enhancements
- Fixes
- Prerequisites for installing DRM
- Known Issues on Microsoft Windows Operating Systems
- Known Issues
- Installation Instructions
- Contacting Dell
- Copyright
The Dell EMC Repository Manager (DRM) ensures that the Dell EMC systems are up-to-date with the latest BIOS, driver, and firmware.
Current Version 3.4.2
Previous Version 3.4.1
Importance
OPTIONAL: It is recommended that you review specifics about the update to
determine if it applies to your system. The update contains changes that
impact only certain configurations or provides new features that may or may
not apply to your environment.
What is new in this release
See Enhancements section for the latest updates in this release.
Enhancements
This section describes the enhancements that are made in this release to DRM.
- Upgraded DRM java Runtime Environment (JRE).
- Catalog import supports new Public Keys.
- Addressed the matter of DRM not installing on certain x86 hardware.
Fixes
No fixes provided in this release.
Prerequisites for installing DRM
This section lists the specific prerequisites to be considered before
installing DRM.
Hardware requirements
Table 1. Hardware requirements
Requirement | Details |
---|---|
Processor | 1 GHz Pentium processor or equivalent |
RAM | 4 GB |
Hard Disk | 1 GB of available space |
Display | 1024 x 768 high color, 32-bit |
Optical Drive (Optional) | CD/DVD writer |
Architecture or Platforms for laptops | x86 |
Software requirements
DRM works on a wide range of Operating Systems for Windows and Linux. Listed are the specific Operating Systems that DRM is tested with:
- Microsoft Windows Server 2019
- Microsoft Windows Server 2022
- Microsoft Windows 10
- Microsoft Windows 11
- RedHat Enterprise Linux 7.9
- RedHat Enterprise Linux 8.5
- SUSE Linux 15
- Ubuntu 20.04
Optional requirements
-
Internet connectivity— To access, create, work with bundles, update catalogs, plug-ins, and repositories.
NOTE: You can use the local repositories on DRM without internet connectivity. -
CD/DVD or USB burning software— To create a bootable CD/DVD or bootable USB.
Known Issues on Microsoft Windows Operating Systems
- Few of the options for creating shortcut links for DRM are missing while interactive installation.
- Some files and copied shortcut are not deleted after uninstall, If application is not closed before uninstall process.
Known Limitations
- Localization is not supported in DRM.
- The Confirm password field is not displayed for database password during installation or upgradation of DRM versions above 3.3.2 through CLI.
- Proxy password does not support special characters (“@” and “:”) to set the proxy in CLI.
- Repository creation using integration fails when password contains special character :.
- Special character ” must be used with an escape character \ as \” to set any passwords through CLI.
- If you refresh a repository that is created using Non-enterprise catalogs (vSAN catalog, or MX validated stack catalog), refers to Enterprise catalog and then perform updates based on the data available in Enterprise catalog. However, does not use the latest version of catalog which was used to create repository.
- DRM should not be installed on a network share.
- Remote access to DRM is not supported.
- On Linux Operating Systems, DRM cannot be installed on a custom folder or location other than /opt/dell.
- DRM does not support multiuser execution. If DRM is installed for all users, it can be launched and used in only one of the user 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 i n v e n t o r y . x m l 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.
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 wanted 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
login .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
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, delete the old files in previous
path manually.
Issue 7
Share folders of an SMB 2 server cannot be enumerated in browse for location
windows.
Resolution- Provide the share name along with an 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
Bin files in the temporary folder are not getting deleted immediately.
Resolution- The files get deleted once the service is idle. Alternately, you
can delete the files manually from the folder.
Issue 10
Component is not deleted from a repository with the DRM delete command.
Resolution- Ensure that there is no space between the comma and the component
name in the command, and then run the command.
Issue 11
Proxy password is not displayed when refreshing an inventory.
Resolution- Enter the proxy password and then click Refresh.
Issue 12
While scheduling a repository job, the time is displayed as “0-1:00” when the
down arrow key is clicked. After clicking it again, it turns to “0-2:00” and
so on.
Resolution-Use the up arrow key to set the hour value.
Issue 13
After repair when you chose to restart the system, the system does not restart
automatically.
Resolution- Restart the system manually.
Issue 14
If you are using h o m e path as your target location for exporting a file
from DRM in Linux operating system, the browse window becomes unresponsive.
Resolution- Remove the trailing slash, and then export the file.
Issue 15
If you have already used/home/for exporting a file and the browse window
becomes unresponsive.
Resolution-Delete the directory:/var/dell/drm/config, and then continue using
DRM.
Issue 16
If you upgrade DRM to the latest version and use different installation
paths other than the previously used installation path, the following issues
may occur:
-
An error message while accessing OLH:
Lost connection.Waiting for DRM service to reconnect. -
DRM version is not updated in CLI.
Resolution- Use same installation path as used before for updating DRM.
Issue 17
OLH does not work in DRM, when launched through CLI on Linux operating system.
Resolution- Recommends you to launch DRM through CLI using the same user
session as the logged-in user.
Issue 18
The generated catalog after import of iDRAC dependency DUP to an existing
repository in DRM fails even after upgrading to DRM version 3.4.1 or above.
Resolution- Create a new repository in DRM version 3.4.1 or above and import
an iDRAC dependency DUP and then export the catalog.
Issue 19
DRM application does not launch using the created shortcut icon in Linux
Operating Systems after install or upgrade of DRM to the latest version.
Resolution- Launch DRM using CLI command or
Use the following commands:
-
For RHEL:
1. chowndrm.Desktop (Currently logged-in user)
2. chmod +x drm.Desktop
3. Double-click the icon. Then click Trust Launcher. -
For Ubuntu or SLES:
1. Copy the drm.Desktop file to the Desktop directory of the user.
NOTE: Desktop icons must be enabled from the system settings.
2. Right Click the icon and then select Allow Launching.
Issue 20
Unable to delete the selected repositories in DRM.
Resolution- Perform the delete operation again on the selected repositories.
Installation Instructions
- For more information about installation instructions on Microsoft Windows operating system, see Dell EMC Repository Manager Quick Installation Guide.
Contacting Dell
NOTE: If you do not have an active Internet connection, you can find
contact information on your purchase invoice, packing slip, bill, or Dell
product catalog.
Dell provides several online and telephone-based support and service options.
Availability varies by country and product, and some services may not be
available in your area.
To contact Dell for sales, technical support, or customer service issues:
- Go to Dell.com/support.
- Select your support category.
- Verify your country or region in the Choose a Country/Region drop-down list at the bottom of the page.
- Select the appropriate service or support link based on your need.
Copyright
© 2018 – 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell
Technologies, Dell, and other trademarks are trademarks of
Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their
respective owners.
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better
use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss
of data and tells you how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal
injury, or death.
Rev. A00
June 2022