By default, VMware Cloud Foundation (VCF) 9.0 will use the optimized Enhanced Data Path (EDP) Standard switch mode when configuring NSX, which will require you to have an EDP capable network adaptor. One way to check whether your network adaptor supports EDP is by using the Broadcom Compatibility Guide (BCG) and ensuring "Enhanced Data Path - Interrupt mode" feature
Alternatively, if you already have ESXi running, you can quickly check by running the following command: esxcfg-nics -e
Parsing complex HTML is definitely challenging, even with PowerShell. I had hoped to use the free tier of ChatGPT and their latest 4o model to help build a PowerShell function for HTML parsing, but I kept running into system limits and the AI often misunderstood what I was asking for.
I finally gave in and purchased the $20 subscription so that I could expand on my 2017 blog post about automating vSphere Global Permissions and add support for listing global permissions, which came at a request from a recent user.
It turns out calling the private vSphere Global Permissions API via the vSphere MOB to show all current vSphere Global Permissions is extremely difficult due to the complex HTML that is rendered by the vSphere MOB. In fact, it took 25 iterations before I finally arrived at the solution using ChatGPT's 4o model. In several of the iterations, it ended up going backwards in progress, so that was pretty annoying!
Not sure if this is the new fancy "vibe coding" trend that I had experienced ... 😅
vCenter Server requires a Key Management Service (KMS) for enabling VM Encryption, vTPM, or vSAN Encryption. Users have the choice of configuring the embedded Native Key Provider (NKP) built into vCenter Server and/or use an external KMS with the Standard Key Provider (SKP) option.
If you have more than one KMS configured in vCenter Server, you can specify one of the KMS key providers to be your default, which will automatically be used for any KMS-related activities. You can switch between the default KMS key provider and you can certainly specify a specific KMS key provider when using the vSphere API to provision a VM that will leverage VM encryption.
So how do you figure out which KMS key provider a VM is using?