Users Guide

A repository must be refreshed in any one of the following scenarios:
● When changes are made to the catalog present in the repository.
● When new devices are added to or removed from groups assigned to a device manager user.
● When the scope is changed for a user with device manager privileges.
● When devices are added or removed from the Devices section in OpenManage Enterprise.
You can refresh the catalog automatically or manually. Select the automatic refresh schedule when a repository is created.
When the automatic refresh task is complete, the Last Run Date/Time and Next Run Date/Time display on the jobs page for
the selected refresh job.
To manually refresh a repository, perform the following steps.
Steps
1. From Plugins go to Update Management and the click Repository.
2. Select the check box next to the repository.
3. Go to the right side of the page and click on the icon next to Last Updated.
The date and time of the last catalog update is displayed if the catalog was previously updated.
Results
The catalog that is associated with the repository is updated to the latest available version at the default repository location
in OpenManage Enterprise. The catalog version is also updated in the Catalog Management page under Firmware/Driver
compliance. The latest baseline and update packages are used to generate a baseline compliance report. The repository is
updated and its version increments by 0.01.
If any device bundles or update packages were previously deleted, the repository refresh job updates the repository along
with the deleted bundles and update packages. The new version of the generated catalog contains the details of the deleted
components, and the same catalog is used to generate the compliance report.
If you add or remove devices from a group, or components from a device in OpenManage Enterprise before the refresh
operation, the changes are reflected in the repository after it is refreshed.
The repository does not refresh successfully if there is insufficient storage space, and the respective alert and audit logs are
generated.
NOTE:
For users with device manager privileges, if any groups present in the repository are removed from the User Scope
by the administrator, they will not reflect in the repository after it is refreshed.
NOTE: Scope changes made to a device manager user is only reflected on the latest version of the repository.
NOTE: If all of the device groups are removed from the assigned scope for a device manager user, the repository refresh
job will fail.
20 Manage repositories