WilliamLam.com

How to delete an ESXi component in vSphere Lifecycle Manager (vLCM) depot?

by // 12 Comments

vSphere Lifecycle Manager (vLCM) allows users to upload an ESXi component into its depot using the Import Updates operation in the vSphere UI, but deleting an ESXi component from the vLCM depot is currently not possible when using the vSphere UI.


However, using the vLCM REST API we can delete an ESXi component from the vLCM depot with the Settings Depots Offline APIs. To demonstrate these specific vLCM REST APIs, I will be using PowerCLI (Connect-CisServer) but you can also use the vLCM REST API directly via any REST Client.

[Read more...]

Quick Tip - Changes to building custom ESXi images in vSphere 8

by // 2 Comments

Historically, when a new version of ESXi is released, customers will use vSphere Image Builder either through the vSphere Image Builder UI or PowerCLI Image Builder cmdlets to create a custom ESXi image to include additional drivers such as the USB Network Native Driver for ESXi Fling.

Note: The current version of the USB Network Native Driver for ESXi Fling is not compatible with ESXi 8.0 and a new version of the driver will be needed. There is currently no ETA on when a new version will be available.

Typically, customers will use their existing vCenter Server deployment, which is usually running an older version to create their new custom ESXi image. This means you are importing a newer ESXi release into your vCenter Server or in the case of the PowerCLI Image Builder cmdlets, you are using an older release of PowerCLI. While this may have worked with previous releases, the assumption that vSphere Image Builder is "forward" compatible with future releases of ESXi is actually an incorrect assumption that many have made, including myself.

I bring this up because in vSphere 8, there have been changes in ESXi where this incompatibility will be observed when attempting to create a custom ESXi 8.0 image using a non-compatible vCenter Server or a PowerCLI release.

[Read more...]

Quick Tip - TPM 2.0 connection cannot be established after upgrading to ESXi 8.0

by // 12 Comments

There has been several reports from folks internally and within the community that after upgrading to ESXi 8.0, they are now seeing the following TPM error message:

TPM 2.0 device detected but a connection cannot be established.


The common theme between all these reported cases that I have seen is that they are all using an Intel NUC. While the Intel NUCs may list TPM support, they do not support either TPM Interface Specification (TIS) for TPM 1.2 or the First In, First Out (FIFO) for TPM 2.0, which are industry standards for communicating with a TPM device that ESXi uses.

[Read more...]