You can use the Update Manager 6.5 as a service of the vCenter Server Appliance 6.5. The Update Manager server and client components are part of the vCenter Server Appliance.
When you deploy the vCenter Server Appliance, the VMware vSphere Update Manager Extension service starts automatically.
Starting with the vSphere 6.5 release, you cannot connect an Update Manager 6.5 instance that runs on Windows to a vCenter Server Appliance 6.5. Attempts to connect Update Manager during installation on a Windows operating system to a vCenter Server Appliance fail with an error.
The Update Manager extension for the vCenter Server Appliance uses a PostgreSQL database that is bundled with the Appliance. Although the Update Manager and the vCenter Server Appliance share the same PostgreSQL database server, they have separate database instances. If you must reset the Update Manager database, the vCenter Server Appliance database remains intact.
Unlike the Update Manager instance that runs on Windows, with the Update Manager instance that runs in the vCenter Server Appliance you can make certain configurations changes directly from the vSphere Web Client. You can change the values for Download patches on service start, Log Level, SOAP Port, Web Server Port, and Web SSL Port. You can access these settings from , under vSphere Web Client Administration. After you change these settings, restart the VMware vSphere Update Manager service for the changes to take effect.
For Update Manager that runs in the vCenter Server Appliance the only configuration you cannot change from the vSphere Web Client is the certificate that Update Manager uses to authenticate to vCenter Server. You can change the certificate by using the Update Manager Utility.
The Update Manager Utility is also bundled with the vCenter Server Appliance. You can access the Update Manager Utility from the Bash Shell of the vCenter Server Appliance.