Dell Repository Manager

Welcome willisdell.

Dell Repository Manager (DRM) is designed to manage repositories per login account. The repository data, as well as file store, is saved in %localappdata% folder. Another user would not be able to see your data unless they login by your credential.

One workaround to share a repository among users is to export your repository to a local folder. This action will create a repository description file (catalog.xml) and copy all included update files to the destination. Then, you share this folder with other users. Another user, may have to "Import this repository into their DRM instance in order to view and manage. But this folder can be used directly by a system management console, i.e. Dell OpenManage Essentials.

I have exported the repository to a different location F:\Dell\RepositoryManager. It has created a series of folders Database,DRMScheduler,Filrestore,Log,Payloads,Searcher,Settings. When I then try and run up Repository Manager another user and try and import the Repository it cannot find a settings.xml or a catalog.cab file in the F:\Dell\RepositoryManager file directories. I am obviously missing something here ?

Please check if you can import the repository with these steps:

1. In the Dell Repository Manager, click on My Repositories Import Legacy Repository window is displayed.

2. The Import Repository window is displayed.

3. Click Browse to navigate to the location of the file.

4. Under Select the repository content to import:, select one of the following.

5. Import only the catalog reference file (e.g. catalog.xml)

6. Import the catalog reference file and download the actual update files contained within it

7. Click Import.

8. A pop-up window appears indicating that the job has been added to the Jobs Queue.

9. Click OK to close it.

To view the component(s) in this repository, click My Repositories, select the imported repository, and click Open. The bundle(s) are displayed in the Bundle(s) tab and the component(s) are displayed in the Components tab.

Let us know the situation once you perform these steps, so that we can try to help you further.

The import utility requires a catalog reference file, the export command has created the above directory structure but there is no catalog file in the file structure. No - xml file - no import ?

Willisdell,

I may mislead you by mentioning "Export". I should say "Save" repository to a specific folder, then DRM will create catalog.xml (or catalog.cab) and copy all referred update files into there as well.

After you open a repository, you may find the "Save" button in that opened repository tab.

We are having a similar issue, I exported a repo on a UNC share which is being used by VMware Plugin and OME. 

The other admins can import he repo from the catalog.xml but it is read only to them. They have full control permissions on the share. 

I also would like to replicate this repo to another UNC path in a remote data center.

We have tools to replicate the data over the WAN and have repomanager installed in the other data center.

  What would I need to to to make a replicated repo functional to other OME, installs ?  I exported the Catalog.xml and made a copy and updated to reflect the new UNC path.

 The repo seems to have imported ok into the remote repo manager but all updates from OME and VMware plugin are failing in the remote install.

If you want to replicate all the repo's from one server to another, use the following steps

Click Run

Type %localappdata% and a window pop's up where you will find the RepositoryManager  -> Database -> RepositoryManager.sdf.

replace this SDF file in the same location on another server and restart the Repository Manager.  So this way all the repositories will be replicated to another server.

Please let us know incase if you got your answer.

Regards,

Chandrasekhar G

What would I need to to to make a replicated repo functional to other OME, installs ?  I exported the Catalog.xml and made a copy and updated to reflect the new UNC path.

 The repo seems to have imported ok into the remote repo manager but all updates from OME and VMware plugin are failing in the remote install.

Once you exported catalog in to the  location, make sure that the corresponding DUP's need to have the same location other wise it will fail to update.

I'm not sure what the roll of the %localappdata% Repository Manager Database is in the replicated repo ?

From my understanding:

• I should be able to manage all my repo updates, from the "Master" install of Repo Manager then export the Repo to a UNC share including all files, catalogs and then copy that to a new UNC at a remote data center.
• Clients can use a properly exported copy of a repo regardless of a repository manager instance. I should be able to create a Repo, copy it to a new share and with "some modification" use the copy in a remote data center.  

The question on the last one is what does one need to modify when you copy your exported repo to a new location?

Sneedy,

Base location is used as the Absolute path and the other updates paths in the catalog are relative to that. By default when DRM saves a catalog.xml or .cab, BaseLocation is left empty which is interpreted as the location of the catalog itself. 

Hence if the catalog that you saved didn't have any baselocation, pls leave it as is and copy the entire folder to a different location (local or network). For better clarity, I'm putting down the steps to reuse saved catalogs from different locations:

1. Create a empty folder with appropriate name

2. Save Full repository into the newly created folder

3. Copy the entire folder to any location (network or local) and deploy

Read permissions on the copied folder might be required when using network locations, ensure that and there shouldn't be a difficulty in using the repository with OME or Spectre

Let us know if this helped you in the task

Thanks,

Krishna