Study guide

7.5 ESXi Host Configuration: Time, Services, Product Locker & Boot Options

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

7.5 ESXi Host Configuration: Time, Services, Product Locker & Boot Options

Key Takeaways Explain This Topic AI

An ESXi host's clock can be set manually or synchronized with NTP or with the Precision Time Protocol (PTP), which supports software and hardware timestamping for higher accuracy.

Host services such as SSH, the ESXi Shell, NTP, and PTP each have a startup policy (start and stop with the host, manually, or with port usage) under Configure > System > Services.

The Product Locker holds VMware Tools ISO images; pointing UserVars.ProductLockerLocation on every host at one shared-datastore directory centralizes VMware Tools updates.

Quick Boot is enabled in the vSphere Lifecycle Manager remediation settings and restarts ESXi without a full hardware reboot on compatible platforms.

To boot ESXi securely, enable UEFI Secure Boot in the server firmware after checking the host with /usr/lib/vmware/secureboot/bin/secureBoot.py -c, and use a TPM 2.0 for attestation.

Last updated: September 2026

7.5 ESXi Host Configuration: Time, Services, Product Locker & Boot Options

Objective 4.19 lists five ESXi setup tasks: time, services, Product Locker, lockdown mode, and the firewall. Lockdown mode and the firewall are covered in Section 6.4. This section covers the rest, plus the boot options in objective 4.17.

Time Configuration (4.19.1)

Accurate time underpins everything in vSphere. SSO tokens, Kerberos and LDAPS authentication, certificate validity, vSAN and HA coordination, and log correlation all depend on it. Configure time under Host > Configure > System > Time Configuration :

  • Method When to Use It
  • Manual Labs only; the clock drifts

NTP (Network Time Protocol) The standard choice: list one or more NTP servers and set the NTP service to start and stop with the host

PTP (Precision Time Protocol) Workloads that need sub-millisecond accuracy; supports software or hardware timestamping on a PTP-capable NIC for highly accurate synchronization

Good practice:

Point ESXi hosts, vCenter Server (configured in the VAMI), and your domain controllers or identity provider at the same time source. Use the same mechanism across the environment so authentication and logs line up.

From the command line, ESXi 7.0 and later can configure NTP with esxcli system ntp set --server=<ntp-fqdn> --enabled=true .

Host Profiles can enforce the same NTP settings across a cluster (Section 7.3).

Service Configuration (4.19.2)

Under Host > Configure > System > Services , each service can be started, stopped, or restarted , and has a startup policy :

  • Startup Policy Behavior
  • Start and stop with host Always running (typical for NTP)
  • Start and stop manually Runs only when an admin starts it (recommended for SSH and ESXi Shell)
  • Start and stop with port usage Starts when its firewall ruleset's ports are opened

Security-relevant services include SSH ( TSM-SSH ), the ESXi Shell ( TSM ), the CIM server , SNMP , NTP , and PTP . Keep SSH and the ESXi Shell stopped unless you are troubleshooting, and pair them with the shell timeouts described in Section 6.4.

Product Locker (4.19.3)

The Product Locker is the location on each host that holds the VMware Tools ISO images (and floppy images) that VMs mount when you install or upgrade Tools. By default it lives in the host's ESX-OSData volume ( /productLocker ). With many hosts, that means many copies to keep current.

Centralize it:

Create a dedicated directory on a shared datastore that is used only for the Tools repository, for example /vmfs/volumes/<shared-datastore>/productLocker .

Copy the vmtools and floppies content into it, or the newer Tools packages you want to standardize on.

On every host, set the advanced setting UserVars.ProductLockerLocation to that path ( Configure > System > Advanced System Settings ).

Reboot the host, or refresh the location through the API, so the /productLocker link points to the shared path.

Benefits: one place to update VMware Tools for the whole environment, a consistent Tools version across hosts, and less data on each host. Auto Deploy hosts provisioned with an image profile that has no Tools rely on a shared Product Locker.

  • ESXi Boot Options (4.17)
  • Firmware Boot Mode

ESXi 8.0 boots with UEFI ; support for legacy BIOS boot is limited, so use UEFI on new installations. UEFI is also required for Secure Boot.

Quick Boot (4.17.1)

Quick Boot restarts ESXi without a full hardware reboot , skipping firmware POST and device initialization (Section 7.1):

Check compatibility with /usr/lib/vmware/loadesx/bin/loadESXCheck.py . Broadcom KB 52477, one of the exam guide's references, explains the requirements.

Enable Quick Boot in Lifecycle Manager > Settings > Host Remediation (for images and baselines).

If a host or its drivers are not compatible, vLCM falls back to a normal reboot.

Securely Booting ESXi (4.17.2)

UEFI Secure Boot : the firmware verifies the ESXi boot loader, which verifies the kernel, which verifies every VIB signature. Run /usr/lib/vmware/secureboot/bin/secureBoot.py -c before enabling it on an upgraded host, because a CommunitySupported VIB would stop the host from booting.

TPM 2.0 : with a TPM enabled in the firmware, vCenter can remotely attest the host's boot measurements, and vSphere Trust Authority can gate keys on attestation (Section 6.4).

Secure ESXi configuration (vSphere 7.0 Update 2 and later): on hosts with a TPM, ESXi protects its configuration encryption key with the TPM. You can also require Secure Boot enforcement and allow only installed binaries to execute ( esxcli system settings encryption set ). Record the recovery key.

Other Boot Paths

Auto Deploy PXE-boots hosts and applies host profiles (Section 7.3).

Boot from SAN (FC, FCoE hardware adapters, or iSCSI) lets hosts boot from a LUN instead of local media.

Installer boot options (press Shift+O at the installer's boot prompt) include systemMediaSize to size ESX-OSData (Section 1.1).

Exam Traps

Same source everywhere. When SSO logins or AD joins fail intermittently, check that ESXi, vCenter, and the identity provider use the same time source before chasing certificates.

Product Locker changes apply per host. Setting the path on one host does not change the others; use a script, PowerCLI, or Host Profiles for consistency.

Quick Boot is a remediation setting, not a BIOS option you enable on each server.