Release Notes

Table Of Contents

● Configure the OpenManage Enterprise proxy and manage storage alerts for the repositories.

Installation

See the Update Manager 1.0 User Guide for more information on installation.

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.

Issue 2

Audit logs are not generated when the version number of a repository is incremented.

Issue 3

The alert and audit logs do not provide enough information for an unsuccessful repository refresh job that is caused by

insufficient storage.

Issue 4

In Update Settings, the Automatic updates option is not supported for downloading the plugin.

Issue 5

The source name is displayed as N/A for Update Manager generated alerts.

Issue 6

Catalogs that are created by Update Manager cannot be updated using the Check for update button on the Catalog

Management page.

Issue 7

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.

Issue 8

The appliance may become unresponsive if the base catalog fails to download during repository creation.

Resolution

The base catalog has failed to download due to network latency or any other issue. Refresh the browser to reload OpenManage

Enterprise again.

Issue 9

The catalog versions are not displayed in the Overview and Repository page for repositories that are created with a SUU

catalog.

Issue 10

FX2/FX2s bundles are not added to a repository when the repository is created with older ESXi catalogs(19.05.30, 19.04.00,

19.01.18, 18.12.00, 18.07.27, 18.07.01, 18.01.26, 17.11.0).

Issue 11

Audit logs are not generated if the update manager-specific jobs are interrupted.

Issue 12

Only the default port number (80) is supported for HTTP shares with IPv6 address.

Issue 13

If a repository is created using a base catalog from a network share, and if the new catalog does not have the same name as the

base catalog the refresh operation is unsuccessful.

Issue 14