This section
lists some frequently asked questions about the Dell Repository Manager.
Where is the Dell Repository
Manager runtime log located?
Dell Repository Manager creates
two log files at runtime:
-
DellRepositoryManager_Server.svclog — Data
Center Version
-
DellRepositoryManager_Client.svclog — Business
Client Version
The log file is located in
C:\Users\<user name>\AppData\
Local\RepositoryManager\Log.
I see an update present
in dell.com/support but when I install the repository from ftp.dell.com
using the Dell Repository Manager, I do not see that update.
The Dell online repository, which is supported by Dell OpenManage,
is released monthly and is qualified by the Dell testing process.
Occasionally, updates may be available on
dell.com/support before
the contents of the repository on
ftp.dell.com are updated.
The new
dell.com/support feature of Dell Repository
Manager can search the latest update(s) from the Dell support site.
You can use Dell Repository Manager to add the new updates into your
repository.
How do I view the unassigned
components in a repository?
- Select a repository and click the
Components tab.
- From the
Display from bundles drop-down
list, select
Unassigned Components.
The
Dell Repository Manager displays the 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
<Bundles/Components> by: list: You can edit the filter
criteria for these features or specify new criteria.
Can the Dell Repository
Manager be run through a Proxy Server?
Yes, install Dell Repository
Manager inside the firewall and connect to a catalog located outside
the firewall (ftp.dell.com or a local repository) through a proxy
server. You can use the proxy server settings of Internet Explorer.
If the proxy settings for Internet Explorer are not working, the proxy
can be set in DRM. You can then use Dell Repository Manager to customize
the catalog as per the requirement and store the customized catalog
inside the firewall.
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.
- Launch
Windows Task Scheduler from
Programs Menu.
- Navigate and click on the
Task Scheduler library node on the left pane.
- Search for
DellRepositoryManagerDataCenterVersion-FindNewUpdates-... task.
This is a Windows tasks that is created by DRM.
- Click
Properties.
- Select the
Triggers tab.
- Search for the trigger that you specified using DRM. Edit this
trigger and change the
Start date to a future
time.
- 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.