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
After You Deploy the vCenter
Server Appliance
5
After you deploy the vCenter Server appliance, consider these post installation options before
adding inventory for the vCenter Server to manage.
If you plan to install Windows 11 as a guest operating system on a virtual machine, you must
configure a key provider. Installing Windows 11 requires a Trusted Platform Module (TPM) 2.0.
When installing Windows 11 as a guest operating system on a virtual machine, instead of using
a physical TPM, you can use a virtual Trusted Platform Module (vTPM). A vTPM is a software-
based representation of a physical TPM 2.0 chip. A vTPM depends on virtual machine encryption
to secure vital TPM data, and so requires that you configure a key provider. For information
about the key providers supported by vSphere, see the Virtual Machine Encryption chapter
in the
vSphere Security
documentation. The easiest way is to configure a VMware vSphere
®
Native Key Provider
™
. vSphere Native Key Provider is included in all vSphere editions and does
not require an external key server. For information about configuring a vSphere Native Key
Provider, see Configuring and Managing vSphere Native Key Provider chapter in the
vSphere
Security
documentation. As with all security solutions, consider the system design, implementation
considerations, and tradeoffs of using vSphere Native Key Provider.
For information about configuring the vSphere Authentication Proxy service, see
vSphere
Security
.
For information about upgrading vCenter Server, see
vCenter Server Upgrade
.
This chapter includes the following topics:
n Log In to vCenter Server by Using the vSphere Client
n Install the VMware Enhanced Authentication Plug-in
n Repoint vCenter Server to Another vCenter Server in a Different Domain
Log In to vCenter Server by Using the vSphere Client
You can use the vSphere Client to log in to vCenter Server and manage your vSphere inventory.
Тhe vSphere Client is automatically installed as part of the vCenter Server appliance deployment.
This way, the vSphere Client always points to the same vCenter Single Sign-On instance.
VMware, Inc.
71