Users Guide

Why would I use the Dell Repository Manager to create the catalog
that LifeCycle Controller uses, instead of just using the catalog on
the Server Update Utility (SUU)?
Since, SUU supports Dell systems from Dell PowerEdge 8th generation systems to the most current systems, the catalog
size on SUU is greater (over 7 GB), than the catalog size on the Dell Repository Manager. In the Dell Repository Manager
you can select the systems that you want to manage, thereby decreasing the catalog size (PowerEdge R710 = 729 MB).
When I select Schedule Automatic Search, there is a pop-window
that appears with the following message: Dell Repository Manager Fatal
UI, Error: Dell Repository Manager has encountered an error
.
DRM creates a Windows Scheduler task behind the scenes to perform automatic search of the Dell update files. The
error can occur when you open the Schedule Automatic Search screen and set a Start Date that is set in the past. You
can change the Start Date on the Windows Task to a future date.
1. Launch Windows Task Scheduler from Programs Menu.
2. Navigate and click on the Task Scheduler library node on the left pane.
3. Search for DellRepositoryManagerDataCenterVersion-FindNewUpdates-... task. This is a Windows tasks that is
created by DRM.
4. Click Properties.
5. Select the Triggers tab.
6. Search for the trigger that you specified using DRM. Edit this trigger and change the Start date to a future time.
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. For
further use of the DUPs, DRM will fetch them from this location and will NOT re-download.
61