6.7

Table Of Contents
After Upgrading or Migrating
vCenter Server 5
After you upgrade to vCenter Server, consider the post-upgrade options and requirements.
n
You can review the database upgrade logs. See Collect Database Upgrade Logs.
n
Complete any component reconfigurations that might be required for changes during upgrade.
n
Verify that you understand the authentication process and identify your identity sources.
n
If you migrated vCenter Server on Windows to a target vCenter Server Appliance and you use any
local OS user names to log in to the vCenter Single Sign-On, you must recreate them and reassign
permissions in the Platform Services Controller appliance.
n
If you performed an upgrade, upgrade any additional modules that are linked to this instance of
vCenter Server, such as Update Manager. If you performed a migration from vCenter Server on
Windows to a vCenter Server Appliance, the Update Manager module is migrated as well.
n
Optionally, upgrade or migrate the ESXi hosts in the vCenter Server inventory to the same version as
the vCenter Server instance.
n
If you use Update Manager in your vCenter Server deployment, and Update Manager and
vCenter Server were running on separate machines prior the migration, consider to shut down or
delete the Update Manager host machine after the migration is complete. Before disposing of the
Update Manager host machine, take into account the following:
n
You might need the host machine for rolling back purposes of your upgraded or migrated
environment.
n
You might have other software that runs on that machine.
This chapter includes the following topics:
n
Verify Your vCenter Server Appliance Upgrade or Migration Is Successful
n
Log in to vCenter Server by Using the vSphere Client
n
Install the VMware Enhanced Authentication Plug-in
n
Uninstall the TLS Configuration Utility on Windows
n
Collect vCenter Server Log Files
n
Identity Sources for vCenter Server with vCenter Single Sign-On
n
Reregister Solution in vCenter Server after Upgrade or Migration
VMware, Inc.
197