8.0
Table Of Contents
- vCenter Server Installation and Setup
- Contents
- About vCenter Server Installation and Setup
- Introduction to vSphere Installation and Setup
- Deploying the vCenter Server Appliance
- File-Based Backup and Restore of vCenter Server
- Image-Based Backup and Restore of a vCenter Server Environment
- After You Deploy the vCenter Server Appliance
- Log In to vCenter Server by Using the vSphere Client
- Install the VMware Enhanced Authentication Plug-in
- Repoint vCenter Server to Another vCenter Server in a Different Domain
- Repoint a Single vCenter Server Node to an Existing Domain without a Replication Partner
- Repoint a vCenter Server Node to an Existing Domain with a Replication Partner
- Repoint a vCenter Server Node to a New Domain
- Syntax of the Domain Repoint Command
- Understanding Tagging and Authorization Conflicts
- vCenter Server Domain Repoint License Considerations
- Troubleshooting vCenter Server Installation or Deployment
Time inconsistencies in vSphere can cause the first boot of a component in your environment to
fail at different services depending on where in the environment time is not accurate and when
the time is synchronized. Problems most commonly occur when the target ESXi host for the
destination vCenter Server is not synchronized with NTP or PTP. Similarly, issues can arise if the
destination vCenter Server migrates to an ESXi host set to a different time due to fully automated
DRS.
To avoid time synchronization issues, ensure that the following is correct before installing,
migrating, or upgrading a vCenter Server instance.
n The target ESXi host where the destination vCenter Server is to be deployed is synchronized to
NTP or PTP.
n The ESXi host running the source vCenter Server is synchronized to NTP or PTP.
n When upgrading or migrating from vSphere 6.7 to vSphere 8.0, if the vCenter Server
appliance is connected to an external Platform Services Controller, ensure the ESXi host
running the external Platform Services Controller is synchronized to NTP or PTP.
n If you are upgrading or migrating from vSphere 6.7 to vSphere 8.0, verify that the source
vCenter Server or vCenter Server appliance and external Platform Services Controller have the
correct time.
Verify that any Windows host machine on which vCenter Server runs is synchronized with
the Network Time Server (NTP) server. See the VMware knowledge base article at https://
kb.vmware.com/s/article/1318.
To synchronize ESXi clocks with an NTP or a PTP server, you can use the VMware Host Client.
For information about editing the time configuration of an ESXi host, see topic
Edit the Time
Configuration of an ESXi Host in the VMware Host Client
in the
vSphere Single Host Management -
VMware Host Client
documentation.
To learn how to change time synchronization settings for vCenter Server, see topic
Configure
the System Time Zone and Time Synchronization Settings
in the
vCenter Server Configuration
documentation.
To learn how to edit the time configuration for a host by using the vSphere Client, see topic
Editing the Time Configuration Settings of a Host
in the
vCenter Server and Host Management
documentation.
System Clock Synchronization Between the Client and Server
To establish a secure TLS connection to a vCenter Server (the server), the system where you
are running the CLI installer (the client) must not have its system clock slower or faster than the
server's system clock by an acceptable limit (tolerance).
See Table 2-2. Client Clock Tolerance for specific values for each deployment scenario.
Note The client clock values are applicable only for vCenter Server 6.7 and later.
vCenter Server Installation and Setup
VMware, Inc. 23