Study guide
6.5 vSphere Certificate Management
VMware Certified Professional - Data Center Virtualization VCP-DCV
Track your progress as you read
Finished sections get a check mark.
1 Introduction: VCP-DCV Exam Overview
About the VCP-DCV Exam (2V0-21.23)
2 Chapter 1: vSphere Architecture & Core Platform Technologies
1.1 vSphere 8.x Architecture and Components Overview 1.2 vCenter Server Appliance (vCSA) Architecture & Deployment 1.3 vSphere Distributed Services Engine (DSE) & DPUs 1.4 vSphere Products, Solutions & Workload Platform 1.5 vCenter Topology: SSO Domains & Enhanced Linked Mode 1.6 vSphere with Tanzu: Supervisor, Namespaces, Zones & Lifecycle 1.7 vSphere in the SDDC: vCenter Converter, vSphere Replication & SRM
3 Chapter 2: Compute Resources & Cluster Management
2.1 vSphere High Availability (HA) Architecture 2.2 Distributed Resource Scheduler (DRS) & Resource Pools 2.3 vMotion & Enhanced vMotion Compatibility 2.4 Virtual Machine Advanced Compute Configuration 2.5 Fault Tolerance, Proactive HA & Advanced Cluster Options 2.6 vSphere Cluster Services (vCLS) & Retreat Mode 2.7 Migration Types: Cold Migration, Storage vMotion & Cross vCenter Export
4 Chapter 3: Storage Technologies & VMFS Datastores
3.1 Storage Access Protocols & Multipathing 3.2 VMFS Datastore Architecture & Management 3.3 Storage Policies (SPBM) & Virtual Volumes (vVols) 3.4 Storage DRS & Storage I/O Control 3.5 RDM, PMem, NVMe, NVMe-oF & iSER Use Cases
5 Chapter 4: VMware vSAN Architecture & Operations
4.1 vSAN Core Architecture & Disk Groups 4.2 vSAN Fault Domains & Stretched Clusters 4.3 vSAN Storage Policies & Data Protection 4.4 vSAN Maintenance, Health Checks & Monitoring
6 Chapter 5: Virtual Networking Architecture & Configuration
5.1 Standard Switches (vSS) vs Distributed Switches (vDS) 5.2 Port Group Policies & NIC Teaming 5.3 VLAN Configuration & Security Policies 5.4 Network I/O Control (NIOC) & TCP/IP Stacks
7 Chapter 6: Security, Identity & Access Control
6.1 vCenter Single Sign-On (SSO) & Identity Sources 6.2 Role-Based Access Control (RBAC) & Global Permissions 6.3 Virtual Machine Encryption & Key Management 6.4 ESXi Host Security & vSphere Trust Authority 6.5 vSphere Certificate Management 6.6 VM Firmware, Secure Boot, vTPM & Virtualization-Based Security
8 Chapter 7: Lifecycle Management & Host Configuration
7.1 vSphere Lifecycle Manager (vLCM) Cluster Images 7.2 Baseline-Based Lifecycle Management 7.3 Host Profiles & Cluster Quickstart 7.4 Content Libraries & Virtual Machine Deployment 7.5 ESXi Host Configuration: Time, Services, Product Locker & Boot Options 7.6 vCenter Lifecycle: Update Planner, VAMI Patching & Upgrades 7.7 Virtual Machine Snapshots & VM Creation Methods
9 Chapter 8: Monitoring, Performance Tuning & Troubleshooting
8.1 Performance Monitoring & Metrics 8.2 Command-Line Diagnostics & esxtop 8.3 Log Analysis & Diagnostic Data Collection 8.4 Troubleshooting Common Infrastructure Scenarios 8.5 Alarms & vCenter Appliance Health Monitoring
6.5 vSphere Certificate Management
Key Takeaways Explain This Topic AI
The VMware Certificate Authority (VMCA) issues vCenter's machine SSL certificate, solution user certificates, and ESXi host certificates by default.
Hybrid mode replaces only the machine SSL certificate with one signed by an enterprise CA and leaves VMCA to manage solution user and ESXi certificates.
If policy requires every certificate to be signed by the enterprise CA with no intermediate CA, replace the machine SSL and solution user certificates with custom enterprise-CA certificates.
The vCenter advanced setting vpxd.certmgmt.mode sets the ESXi certificate mode: vmca (default), custom, or thumbprint (a legacy troubleshooting mode).
vSphere 8.0 rejects certificates signed with SHA-1 or other weak algorithms, and upgrade prechecks block the upgrade if such certificates are in use.
Last updated: September 2026
- 6.5 vSphere Certificate Management
- Where vSphere Uses Certificates
Certificate Used For
Machine SSL certificate vCenter's HTTPS endpoint (the reverse proxy on port 443, which serves the vSphere Client and APIs). This is the certificate browsers see
Solution user certificates Service identities (such as machine , vpxd , vpxd-extension , and vsphere-webclient ) that authenticate vCenter services to Single Sign-On
- ESXi host certificates Each host's HTTPS identity ( rui.crt ), used when vCenter connects to the host
- VMCA root (signing) certificate The CA that signs VMCA-issued certificates
STS signing certificate Signs SSO tokens (Section 6.1; vSphere 8 renews a VMCA-generated STS certificate automatically)
Trusted root certificates CA chains that vCenter trusts, such as your enterprise root
vCenter stores certificates in the VMware Endpoint Certificate Store (VECS) . You manage them in the vSphere Client under Administration > Certificates > Certificate Management , or with the certificate-manager utility ( /usr/lib/vmware-vmca/bin/certificate-manager ). The vecs-cli and dir-cli tools cover advanced tasks.
The Four Approaches
Approach Who Signs What Trade-off
VMCA default VMCA's self-signed root signs everything Least effort. Browsers warn until you trust the VMCA root, which you can download from vCenter's landing page
Hybrid An enterprise CA signs the machine SSL certificate ; VMCA keeps signing solution user and ESXi certificates The common, low-overhead choice: users see a trusted certificate and internal certificates stay automated
VMCA as intermediate (subordinate) CA You replace VMCA's signing certificate with one issued by your enterprise CA; VMCA then issues all certificates under your chain Everything chains to your PKI, but VMCA becomes an intermediate CA you must protect
Custom (full external) Your enterprise CA signs every certificate: machine SSL, solution users, and ESXi The most control and the most work. You renew everything yourself
Reading the Official Sample Question
If policy says every solution must use certificates signed by the enterprise CA and no intermediate CAs are allowed in the chain , then:
VMCA as a subordinate CA is ruled out, because it adds an intermediate.
VMCA self-signed certificates are ruled out.
So you replace the solution user certificates and the machine SSL certificates with custom certificates from the enterprise CA .
The Role of the Enterprise PKI (4.13.1)
An enterprise public key infrastructure (PKI) such as Microsoft AD Certificate Services:
Signs certificates that clients already trust. Its root is in every domain-joined browser, so there are no warnings.
Provides the trusted root and intermediate chain , which you add to vCenter's trusted root store and upload when you import a signed certificate.
Publishes revocation information (CRL or OCSP) and enforces certificate templates , such as key usage and validity.
Can act as the parent CA for VMCA in subordinate mode.
Replacing the Machine SSL Certificate (Hybrid Mode)
In Certificate Management , open the Machine SSL Certificate and choose Generate Certificate Signing Request (CSR) .
Submit the CSR to the enterprise CA with the appropriate template.
Choose Import and Replace Certificate and upload the signed certificate together with the CA chain .
vCenter restarts its services. Browsers now trust vCenter through the enterprise root.
Before replacing certificates in an Enhanced Linked Mode group, take the offline snapshots and file-based backups described in Section 1.5.
ESXi Certificate Modes
The vCenter advanced setting vpxd.certmgmt.mode controls how vCenter handles host certificates:
Mode Behavior
vmca (default) vCenter provisions and renews ESXi certificates from VMCA. In the vSphere Client, use Renew or Refresh CA Certificates on a host
custom You install CA-signed certificates on hosts yourself, and vCenter does not overwrite them. Set this before adding hosts that already have custom certificates
thumbprint A legacy mode that checks only the certificate hash. Use it only temporarily for troubleshooting; vCenter 8.x raises an alarm that it is deprecated
Monitoring and Hygiene
vCenter's certificate status alarm warns before certificates expire (30 days ahead by default), and Certificate Management shows expiration dates.
vSphere 8.0 no longer supports certificates signed with SHA-1 or other weak signature algorithms, and upgrade prechecks block the upgrade until they are replaced.
Keep the enterprise root and intermediates in vCenter's trusted root store. A missing intermediate is a classic cause of identity-source and replacement failures (Section 6.1).
certificate-manager Menu Options
The certificate-manager utility on the vCenter appliance offers numbered operations that map directly onto the approaches above:
- Option What It Does Approach
- 1 Replace the machine SSL certificate with a custom certificate Hybrid or full custom
2 Replace the VMCA root certificate with a custom signing certificate and replace all certificates VMCA as intermediate CA
- 3 Replace the machine SSL certificate with a VMCA certificate Back to VMCA-signed
- 4 Regenerate a new VMCA root certificate and replace all certificates VMCA default (new root)
- 5 Replace solution user certificates with custom certificates Full custom
- 6 Replace solution user certificates with VMCA certificates VMCA-signed
- Troubleshooting Certificate Problems
Symptom Likely Cause Fix
Browser warns about vCenter's certificate Machine SSL still signed by VMCA, whose root the browser does not trust Trust the VMCA root, or move to hybrid mode
Import of a signed certificate fails Missing intermediate or root in the uploaded chain Upload the full CA chain, and add the roots to the trusted root store
Hosts disconnect after a CA change Hosts don't trust the new chain, or the host certificates need renewal Refresh CA Certificates and Renew the host certificates (vmca mode), or install new custom host certificates (custom mode)
vSphere Client logins fail with token errors STS signing certificate expired (custom STS, or auto-renewal failed) Refresh or replace the STS certificate (Section 6.1)
Upgrade precheck blocks vSphere 8 A certificate uses SHA-1 or another weak signature Reissue it with SHA-256 or stronger