vCenter Server 5.x services that were previously deployed separately from vCenter Server might require reconfiguration after they are migrated to the vCenter Server system during the upgrade process.

About this task

vCenter Server components can no longer be deployed separately. If components of vCenter Server 5.x were previously deployed in different systems from the vCenter Server system, the upgrade software migrates them to the vCenter Server system. In some cases, repointing or other actions are required for the migrated services.

For vCenter Server Appliance 5.5 instances with remote relay of logs to external receivers such as LogInsight or Splunk, the upgrade software migrates the relay configuration to the VMware Syslog Service that is included in vCenter Server Appliance 6.0.

When you are upgrading in a mixed-version environment, vCenter Server 5.x instances that were using the vCenter Single Sign-On instance are not affected. They continue to operate with the upgraded Platform Services Controller instance as they did before the upgrade without any issues or required updates. vCenter Server 5.5 instances continue to be visible to version 5.5 vSphere Web Client, but not to version 6.0 vSphere Web Client instances. See Mixed-Version Transitional Environments During vCenter Server Upgrades.

Procedure

  1. If your vSphere Auto Deploy service was previously installed on a separate machine from vCenter Server, and was relocated during the upgrade process, update your DHCP and TFTP settings to point to your relocated vSphere Auto Deploy service.
    1. Download deploy-tftp.zip and replace the tftp root folder.

      Your configuration can vary based on your TFTP client.

    2. Reconfigure the DHCP .conf file to use the upgraded vSphere Auto Deploy service and its .tramp file.

      Your configuration can vary based on your DHCP setup.

  2. If your vSphere Web Client was previously installed on a separate machine from vCenter Server and was relocated during the upgrade process, update the FQDN and IP address to point to the new location.
  3. If your VMware vSphere Syslog Collector was previously installed on a separate machine from vCenter Server, repoint ESXi hosts to the new location of the vSphere Syslog Collector server, which is the newly upgraded vCenter Server 6.0 for Windows.
  4. If your vSphere ESXi Dump Collector server was previously installed on a separate machine from vCenter Server, repoint ESXi hosts to the new location of the vSphere ESXi Dump Collector server.
  5. To apply the configuration changes for the remote relay of logs to the vSphere Syslog Service service in an upgraded vCenter Server Appliance, restart the service immediately after the upgrade to 6.0 is completed.
  6. To view any vCenter Server 5.5 instances that are not yet upgraded while you have a transitional mixed-version 5.5 and 6.0 environment, restart your legacy vSphere Web Client.
  7. If any vCenter Server 5.x services remain running on separate virtual machines or physical servers, you can shut down and remove them.

    They are not used by vCenter Server 6.0.