6.7

Table Of Contents
Verify That vCenter Server Can Communicate with the Local Database
If your database is on the same machine on which vCenter Server is to be installed, and you changed the
machine name, verify the configuration. Make sure that the vCenter Server DSN is configured to
communicate with the new name of the machine.
Changing the vCenter Server computer name impacts database communication if the database server is
on the same computer with vCenter Server. If you changed the machine name, you can verify that
communication remains intact.
If your database is remote, you can skip this procedure. The name change has no effect on
communication with remote databases.
After you rename the server, verify with your database administrator or the database vendor that all
components of the database are working.
Prerequisites
n
Make sure that the database server is running.
n
Make sure that the vCenter Server computer name is updated in the domain name service (DNS).
Procedure
1 Update the data source information, as needed.
2 To test this condition, ping the computer name.
For example, if the computer name is host-1.company.com, run the following command at the
Windows command prompt:
ping host-1.company.com
If you can ping the computer name, the name is updated in DNS.
vCenter Server communication is confirmed. You can continue to prepare other components of your
environment.
Preparing for Upgrading the Content Library
When upgrading from vCenter Server version 6.0 or earlier, you must prepare your environment before
upgrading the Content Library to prevent pre-check errors.
If you are upgrading from vCenter Server version 6.0, your environment must meet upgrade requirements
for the Content Library:
n
All ESXi hosts from the source vCenter Server inventory must be supported by the destination
vCenter Server 6.7.
n
The source vCenter ServerContent Libraries must be backed by either Remote File System or
Datastores. You cannot use libraries backed by local file system of the vCenter Server.
vCenter Server Upgrade
VMware, Inc. 51