---
name: vmwaresolutions-vum-metadata
title: Collecting the metadata
description: As of 17 July 2025, new automated installations of Red Hat&reg; OpenShift&reg; for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
last-updated: 2025-11-04
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Collecting the metadata
{: #vum-metadata}

As of 17 July 2025, new automated installations of Red Hat&reg; OpenShift&reg; for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

VMware® Update Manager (VUM) downloads metadata about the upgrades, patches, or extensions through a predefined automatic process that you can modify. At regular configurable intervals, VUM contacts VMware, or third-party sources, to gather the latest metadata about available upgrades, patches, or extensions. However, the default settings from VMware are acceptable for use in the VMware Cloud Foundation for Classic - Automated instance you can change them as needed for your enterprise requirements.

VUM displays system-managed baselines that are generated by vSAN™. The system-managed baselines automatically update their content periodically, which requires VUM to have constant access to the internet. The vSAN system baselines are typically refreshed every 24 hours.

You can use the system-managed baselines to upgrade your vSAN clusters to recommended critical patches, drivers, updates, or the latest supported ESXi™ host version for vSAN.

For most enterprises, the VMware default settings for VUM are considered to be suitable. The following information provides how to change these settings if your enterprise would like to use different settings.

## Download schedule
{: #vum-metadata-download-schedule}

Updates are virtual appliance upgrades, host patches, and extensions and by default VUM downloads updates daily. To change the download schedule, access the vSphere® Web Client. Go to **Home** > **Update Manager** > **Manage** > **Settings**, and select **Download Schedule**, and then click **Edit**.

## Notification check schedule
{: #vum-metadata-notif-check-schedule}

Notifications are information about patch recalls, new fixes, and alerts and by default VUM downloads notifications on an hourly basis. To change the notification check schedule, access the VMware vSphere® Web Client. Go to **Home** > **Update Manager** > **Manage** > **Settings**, and select **Notification Check Schedule**, and then click **Edit**.

## Virtual machine settings
{: #vum-metadata-vm-settings}

To change the virtual machine (VM) Settings, access the vSphere Web Client. Go to **Home** > **Update Manager** > **Manage** > **Settings**, and **VM Settings**, and then click **Edit**.

## Host and cluster settings
{: #vum-metadata-host-settings}

To change the Host/cluster Settings, access the vSphere Web Client. Go to **Home** > **Update Manager** > **Manage** > **Settings**, and **Host/Cluster Settings**, and then click **Edit**.

## Related links
{: #vum-metadata-related}

* [VMware HCX solution architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx-archi-intro&format=markdown#hcx-archi-intro)
* [VMware Solutions on IBM Cloud Digital Technical Engagement](https://www.ibm.com/solutions/virtualization){: external}