Dell Repository Manager Version 2.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. 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. Copyright © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Overview................................................................................................................. 5 What is new in this release.................................................................................................................... 5 Accessing documents from Dell support site...................................................................................... 6 Other documents you may need........................................................................
If I export a bundle using Export to light weight deployment scripts, am I going to redownload the DUPs which are already in my system? .................................................................... 30 How to edit the ‘.sh’ file in Linux deployment script bundle? Is there any recommended tool to edit this file?....................................................................................................................................
Overview 1 The Dell Repository Manager (DRM) ensures that the Dell systems are up-to-date with the latest BIOS, driver, firmware, and software.
• User readable log files — Now, you can view the user log files, such as, .svlog and .log files. • Download Optimization — DRM supports concurrent download of DUPs while creating update packages. By default, you can concurrently download up to 5 DUPs and you may configure the number up to 10. • Significant overall performance improvement. • Version 2.2 onwards DRM supports catalog files in .gz format.
• Dell OpenManage Server Administrator Installation Guide* • Dell OpenManage Essentials User's Guide * This guide is also found on the Dell Systems Management Tools and Documentation DVD.
User scenarios 2 This section describes the various features of the Dell Repository Manager (DRM) and the user scenarios.
Downloading the updates for the systems, which are not there in the Dell Online Catalog Currently, the Dell Online Catalog does not contain updates for systems that are not listed on FTP Catalog or Dell Online Catalog. You can download the updates for those unlisted systems, using the Dell Repository Manager. For example, to download the updates for Dell PowerVault MD3420, which is not listed in the Catalog, do the following: 1. In the Dell Repository Manager window, click Search Dell Support Site.
DUP Dependencies DRM 1.9 onwards, DRM supports DUP Dependency. This feature articulates the relationship between two different DUPs. SUU enables certain rules and submissions to determine if a set of conditions or requirements are met. These conditions or requirements are called dependencies. Dependency exists when a DUP of a particular kind has a dependence on additional DUP for further execution. This helps the users to determine, which DUP to install first and which one to follow.
The following flow chart describes the process in detail.
Creating repository with Modular Chassis Inventory Starting DRM 2.0, you can create a new repository using Modular chassis inventory. You can choose the repository (Dell Online Catalog, Local Source Repository, or any Custom Repository) which you wish to use as a Base repository. You have the option to include additional components in the Modular repository using DRM. For more information, see Dell Repository Manager Data Center User’s Guide.
The following flow chart describes the process in detail.
Creating a repository using Dell Generic Inventory Starting DRM 1.8, you can create a new repository using the Dell Generic Inventory. You can choose the repository (Dell Online Catalog, Local Source Repository, or any Custom Repository) which you want to use as a Base repository. You have the option to include additional components while creating a repository using the Dell Generic Inventory.
Center User’s Guide.
Using FileStore to save disk space in system drive (C: Drive) Starting DRM 1.6, the configurable FileStore feature helps the user to save disk space on the system hard disk. The default file location for the FileStore is C:\Users\\AppData\Local \RepositoryManager\FileStore. However, the FileStore can be moved to a different location after DRM is installed on the system. NOTE: • FileStore cleanup — FileStore cleanup helps you to remove any unused cached files from FileStore location.
Searching the Dell Support Site for updates On DRM 1.6 and later, you can search the Dell support site for the latest catalog files and Dell Update Packages (DUPs) and non DUP packages. These updates can be exported to an existing or a new repository. You can search the Dell Support Site using the following methods: • Automated Search • Manual Search For more information, see Dell Repository Manager Data Center User’s Guide.
Export updates to LightWeight Deployment Package LightWeight Deployment Package (LWDP) provides scripts (batch and shell) to apply the updates (DUP) for multiple products in an automated manner. DRM generates the batch file for the user. The file is located in the same folder along with the DUPs. After you copy the LWDP file to the system, it provides necessary updates (drivers, BIOS, and firmware) to the system. The script provided by Dell is used to apply all the updates.
Updating the local repository The Local Repository can be updated with the latest available updates (DUPs). The selected repository compares against the latest catalog file, which consists the latest available updates. You have the options to update the repository with all the available DUPs for the system. Also, you can choose a specific DUP as per the requirement. Different DUPs exist for newer version, changed files, obsoleted files, and other files in the source screen.
Creating Bootable CD or USB Keys for updates You can create bootable USB keys for updates, using any third party or free tool. You can start your managed system by the bootable CD or USB storage. After the system starts, it automatically runs the selected updates. After the update is complete, you can remove the CD or USB storage, and reboot the system to your host operating system.
You can use the bootable ISO to apply the updates if: • You have a server running an operating system that is not supported by Dell Repository Manager, such as Berkeley Software Distribution (BSD), Solaris, or older versions of Microsoft Windows, RedHat Linux or SUSE Linux. • You are using Linux versions such as Ubuntu or Debian. • You prefer to perform updates (regardless of OS) in an out-of-band method. To create bootable USB keys, using the tool - UNetBootIn as an example: 1.
The following flow chart describes the process in detail.
Launching DRM using command line options Navigate to the location where DRM is installed in the system. By default, for 64–bit DRM is installed at c: \Program Files (x86)\Dell\Dell Repository Manager. For 32–bit the DRM is installed at c: \Program Files\Dell\Dell Repository Manager. Go to Start → Run, type cmd and press enter. Run the Dell Repository Manager using the following command: • RepositoryManager.exe -server — Launches the application in Data Center version.
The available options are: • Appliance Administrator Password: • Reqistered vCenter Server IP or Host: • vCenter Server Username: • vCenter Server Password: NOTE: Based on the version of the Dell virtual appliance, you may have to enter the Dell Management Appliance administrator password. If this box is grayed out, the password is not required. 6. Click Connect. The Please wait while getting inventory from Dell Management Appliance... window is displayed while getting list of systems.
Frequently asked questions 3 This section lists some frequently asked questions about Dell Repository Manager. While copying DUPs to a new repository immediately after creating a new repository, unspecified supported platforms message is displayed. What do i do now? Immediately after creating a New Repository, if you use Copy To option to duplicate bundle(s) from the newly created repository to another new repository; you may encounter some data loss.
NOTE: The Unassigned Components option is not displayed if the repository does not have any unassigned components. How do I edit the search criteria of the filter that I created? In the left pane of Dell Repository Manager, select the filter criteria from Filter by: list: You can edit the filter criteria for these features or specify new criteria.
7. Once the Start date has changed, re-launch DRM to make any changes to Automatic Search. If I export a bundle using Export to light weight deployment scripts, am I going to re-download the DUPs which are already in my system? Whenever a DUP is downloaded, it is stored locally in a file system [%localappdata%\RepositoryManager \FileStore] location. It is not stored using the DUP file name in that location, hence it is not traceable with the exact DUP names.
2. After the database is removed, restart the Dell Repository Manager. A new database is created.
