Upgrading Update Manager that Runs on Windows

You can upgrade to Update Manager 6.7 only from Update Manager versions 6.0 or 6.5 that are installed on a 64-bit Windows operating system.

If you are switching from using a vCenter Server system of version 6.0 or version 6.5 that runs on Windows to a vCenter Server Appliance 6.7, this is a migration process. For detailed information on Update Manager migration process, read Migrating Update Manager from Windows to vCenter Server Appliance 6.7, or see the Migration chapter in vSphere Upgrade documentation.

If you are running Update Manager of a version earlier than 5.5, or Update Manager that runs on a 32-bit platform, you cannot perform a direct upgrade to Update Manager 6.7. You must use the data migration tool that is provided with Update Manager 5.0 installation media to upgrade your Update Manager system to Update Manager 5.0 running on a 64-bit operating system, and then perform an upgrade from version 5.0 or version 5.1 to version 5.5 before upgrading to version 6.7. For detailed information how to use the data migration tool, see the Installing and Administering VMware vSphere Update Manager documentation for Update Manager 5.0.

When you upgrade Update Manager, you cannot change the installation path and patch download location. To change these parameters, you must install a new version of Update Manager rather than upgrade.

Previous versions of Update Manager use a 512-bit key and self-signed certificate and these are not replaced during upgrade. If you require a more secure 2048-bit key, you can either perform a new installation of Update Manager 6.7, or use the Update Manager Utility to replace the existing certificate. For more information about how to use the Update Manager Utility, see the Reconfiguring VMware vSphere Update Manager documentation.

Scheduled tasks for virtual machine patch scan and remediation are retained during the upgrade. After the upgrade, you can edit and remove scheduled scan tasks that exist from previous releases. You can remove existing scheduled remediation tasks but you cannot edit them.

You must upgrade the Update Manager database during the Update Manager upgrade. You can select whether to keep your existing data in the database or to replace it during the upgrade.

The Java Components (JRE) required by Update Manager are installed or upgraded silently on the system when you install or upgrade Update Manager. You can upgrade the Java Components separately from an Update Manager upgrade procedure to a version of the Java Components that is released asynchronously from the Update Manager releases.