Custom installations of vCenter Server 5.1 or 5.5 for Windows that have services located across multiple machines are upgraded and migrated (if required) to the vCenter Server system during the upgrade process.

If all vCenter Server 5.x services are deployed in the same system, they are upgraded in place without any need for configuration after upgrade. However, if you have one or more services deployed remotely, the software migrates your service or services to the vCenter Server virtual machine or physical server during upgrade. Some services require reconfiguration or other actions after upgrade. vCenter Server 5.x for Windows services that are migrated to become part of the vCenter Server group of services during the upgrade process include:

  • Inventory Services

  • vSphere Web Client

  • vSphere Auto Deploy

  • vSphere Syslog Collector

  • vSphere ESXi Dump Collector

vCenter Server and vCenter Single Sign-On are the only services that are not migrated. vCenter Single Sign-On instances are upgraded in place to become part of an external Platform Services Controller if they are deployed on a system other than the system where the vCenter Server resides.

Figure 1. Component Services Migrated to vCenter Server Group of Services


vCenter Server 5.1 or higher components are migrated to the vCenter Server group of services in 6.0


Table 1. vCenter Server 5.x Distributed Service Migration During Upgrade

Service Name

Service Location Before Upgrade

Service Location After Upgrade

Post Upgrade Actions

vCenter Inventory Service

Not installed on the vCenter Server system

Installed on the vCenter Server system

vCenter Inventory Service 5.x data is copied to the Inventory Service 6.0 instance that is installed with vCenter Server 6.0. You do not need to copy it manually.

vCenter Inventory Service 5.x is still running but no longer used. It must be manually stopped and removed.

vSphere Web Client

Not installed on the vCenter Server system

Installed on the vCenter Server system

vCenter Server 5.x data is copied to the vSphere Web Client 6.0 instance that is installed with vCenter Server 6.0.

vSphere Web Client 5.x is still running but no longer used. It must be manually stopped and removed.

vSphere Auto Deploy

Not installed on the vCenter Server system

Migrated to vCenter Server system

vSphere Auto Deploy data is copied to the Auto Deploy 6.0 instance that is installed with vCenter Server 6.0.

Repoint vCenter Server DHCP settings to the migrated vSphere Auto Deploy service.

vCenter Server

vSphere Auto Deploy 5.x is still running but no longer used. It must be manually stopped and removed.

vSphere Syslog Collector

Not installed on the vCenter Server system

Installed on the vCenter Server system

Data is not migrated. Configurations for ports, protocols, and rotation log size are preserved.

  • ESXi system information might remain on an old system until you relocate it.

  • ESXi hosts might require reconfiguration to point to the new vSphere Syslog Collector server.

vSphere ESXi Dump Collector

Not installed on the vCenter Server system

Installed on the vCenter Server system

Data is not migrated.

  • ESXi core dump data might remain on an older system until you migrate it.

  • ESXi hosts might require reconfiguration to point to the new vSphere ESXI Dump server.

For more information about upgrade scenarios, see vCenter Server Example Upgrade Paths. For information about service reconfigurations that are required after upgrade, see Reconfigure Migrated vCenter Server Services After Upgrade