Frequently asked
questions
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.
To avoid this situation, close
the newly created repository and open it from My Repositories before choosing Copy To option to duplicate
bundle(s).
Where is the Dell Repository
Manager runtime log located?
Dell Repository Manager creates
two log files at runtime:
- DellRepositoryManager_Server.svclog/.log — Data Center Version
- DellRepositoryManager_Client.svclog/.log — Business Client Version
The log file is located at C:\Users\<user
name>\AppData\ Local\RepositoryManager\Log.
I see an update present
in www.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 www.dell.com/support before
the contents of the repository on www.dell.com/support are updated.
The new www.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.
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 <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 should 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 the
Start
Date 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 fetches them from this location and will NOT re-download.
How to edit the ‘.sh’
file in Linux deployment script bundle? Is there any recommended tool
to edit this file?
Notepad++ is the best editor for editing
files especially which are Linux based ones on a Windows OS. If it
is on a Linux OS, vi editor is recommended.
Why am I seeing Error parsing inventory data from file error message while creating
the new repository for CMC Inventory?
There
can be three different scenarios, where user encounters with this
error message:
- If the user does not have the proper administrative
rights, DRM does not fetches the files from the CMC folder. The error
message is displayed. This error blocks the new repository creation
process.
- If the inventory file is stored in any of the network
share, and if DRM is not able to connect to that particular network
share this error is displayed.
- If the inventory file is in read-only format, DRM
fails to fetch those files and the error message is displayed, the
repository creation process fails.
While using OME, why
is the component getting updated when it is removed from a particular
bundle?
OME uses all the components that are
within a Repository, it does not organize the updates by Bundles. To
insure that the Repository used by OME does not contain the update
be sure to select the Remove from Repository option when deleting an update. In case, if you are using the catalog
created by DRM with OME, OME does not recognize the bundles separately,
it just recognizes the entire catalog as one single file. This is
how OME works. At any time, if you remove a component from the OME
bundle but not from the Repository then OME contemplates that the
components is still there and compares it against the available updates.
The database is corrupted
or invalid. How do I fix this?
To fix the database:
- Remove the corrupted database before you recreate
a new database. Navigate to %localappdata%\RepositoryManager\Database\RepositoryManager.sdf to delete the database.
- After the database is removed, restart the Dell Repository
Manager.
A new database is created.