WilliamLam.com

Retrieving detailed vSphere Lifecycle Manager (vLCM) Image information from vSphere Cluster using PowerCLI

by // Leave a Comment

As more and more users are adopting vSphere Lifecycle Manager (vLCM) to simplify the lifecycle and configuration management of their ESXi hosts, you may want to get more information about a given vLCM image that has been associated with a specific vSphere Cluster.

While you can certainly get this information using the vSphere UI, you can also get this detailed information by using the vLCM REST API, which can easily be consumed using variety of vSphere SDK Clients including PowerCLI.

For inventory and/or auditing purposes, automation is typically the answer, especially at scale. I will not bore you with the details, but I recently created the following PowerCLI function called Get-vLCMClusterImageInformation and given the name of a vLCM-enabled vSphere Cluster, it will provide you with the associated ESXi base image and all Solutions and Components that is associated with a given image.

UPDATE (02/06/25) - The script has also been updated to also include information for a vLCM image that has integrated with an Hardware Support Manager (HSM) to provide firmware information.

[Read more...]

Preserving VM snapshot hierarchy across vCenter Servers

by // Leave a Comment

On occasion, you might find yourself needing to take multi-level VM snapshots for various testing or development purposes, not an uncommon task for IT administrators.

In the past, if you needed to move the VM and preserve its snapshot hierarchy, it was usually difficult and involved manual tasks to unregister the VM and copying its files to the destination environment.


At VMware Explore last year, I had a customer who shared a nice tidbit regarding this topic with me that I was recently reminded of. By performing a Cross vCenter vMotion (not clone), the VM snapshot hierarchy is automatically preserved.

You of course can use the vSphere API and PowerCLI to initiate a Cross vCenter vMotion OR you can easily perform this operation by using the Advanced Cross vCenter vMotion capability that is built right into the vSphere UI, which can also be useful if you need to quickly cold migrate some workloads from older vSphere releases.

After authenticating into my source vCenter Server which is running vSphere 7.0 Update 3o, I simply select my VM with snapshots and perform a migration (not clone) and in a few minutes, it is now running in my vSphere 8.0 Update 2 destination vCenter Server!

Automating counting cores & TiBs for new VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) SKUs

by // 50 Comments

Happy New Year! ???

At the end of 2023, we announced two new offerings called VMware vSphere Foundation (VVF) and VMware Cloud Foundation (VCF) that drastically simplifies our overall vSphere-based portfolio and licensing model.

To help our users understand the new licensing model which uses both CPU cores and TiB (for vSAN storage sizing), I have created a PowerCLI function (Get-FoundationCoreAndTiBUsage) that will inventory your existing vSphere environment and provide a detailed report on the number of CPU Core and/or TiB license count that would be required whether you are considering the VVF or VCF offering.


For those familiar with my previous versions of the vSphere and vSphere+ core counting scripts, this function works in a very similar manner with the output configurable using either console or outputting it to an excel spreadsheet for further processing. For more details on the calculations, where to download and how to use the PowerCLI function, please see VMware KB 95927.