Release Notes

○ To view repository
○ To refresh, or update repository
● Edit repository name and baseline name.
● Transfer of ownership for repositories from one Device Manager to another Device Manager.
● Storage settings enhancements to provide more than 10 GB of storage.
● GUI enhancements to ensure better usability.
Installation
See the Update Manager 1.1 User Guide for more information on installation.
Fixes
● Audit logs are not generated when the version number of a repository is incremented.
● After you apply Advanced filters, the Delete tab deletes the complete repository version, which does not contain any items
as per selection.
● The storage-based alerts generated by the Update Manager plugin are categorized as Repository Refresh in the
Subcategory of the alert logs.
● The creation of repository fails when the word Catalog is used in uppercase 'C' instead of lowercase 'c'.
● Incorrect value shown for Repository size and considered for storage computation when same DUP is present in multiple
bundles.
● Repository of more than 10 GB cannot be created.
Limitations
● The catalog versions are not displayed in the Overview and Repository page for repositories that are created with an SUU
catalog.
● The source name is displayed as N/A for Update Manager generated alerts.
● Same time is displayed for the Last Run Date/Time and Next Run Date/Time fields on the job details section for the
scheduled refresh and download jobs.
● Audit logs are not generated if the update manager-specific jobs are interrupted.
● Only the default port number (80) is supported for HTTP shares with IPv6 address.
● Plan to run less than 15 jobs exactly at same time. Only 15 refresh jobs can run in parallel.
Known Issues
Issue 1
If a repository is created using a base catalog from a network share, and if the new catalog does not have the same name with a
higher version as the base catalog the refresh operation is unsuccessful.
Resolution
For catalogs from offline network share, ensure that the new version of catalog has the same filename as the older version and
a higher version number.
Issue 2
The alert and audit logs do not provide enough information for an unsuccessful repository refresh job that is caused by
insufficient storage.
Resolution
View information about the cause of failure from the Audit and Alert logs.
Issue 3
In OpenManage Enterprise, under Update Settings, the Automatic updates option is not supported for downloading the plugin.
Resolution
2