<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>HCL on Why did IT fail</title><link>https://www.why-did-it.fail/tags/hcl/</link><description>Recent content in HCL on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Wed, 12 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/hcl/index.xml" rel="self" type="application/rss+xml"/><item><title>Howto - Query host Driver and Firmware via vCenter API</title><link>https://www.why-did-it.fail/blog/2022-05-how-to-query-hcl-api/</link><pubDate>Wed, 12 Oct 2022 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2022-05-how-to-query-hcl-api/</guid><description>Yet again, customer questions make the best blog posts. This time, it&amp;rsquo;s about retrieving the firmware and drivers from an ESXi host.
So far, the customer uses esxcli which required either PowerCLI or direct SSH access, both were not the preferred choices in this case.
High-level overview Starting with vSphere 7, vSphere Lifecycle Manager (vLCM) can handle this task. This blog post will show you how to create a HCL report for a given host which contains all the required information about firmware and drivers, as well as the bonus information about the support status of the system and devices.</description></item></channel></rss>