WilliamLam.com

Quick Tip - Additional NVMe vendors (SK Hynix & Sabrent) for ESXi homelab

by // 12 Comments

The Samsung 980 Pro NVMe is a pretty popular SSD model that is used by many within the VMware Homelab Community. However, in recent months, there have been an alarming amount of reports from owners that their 980 Pro NVMe devices have been failing prematurely due to firmware issues.

Samsung has finally acknowledge the problem with a firmware fix and it looks like a simliar fix is also planned for the Samsung 990 Pro NVMe.

While I can not comment on the specific issues with the Samsung 980/990 Pro NVMe devices, I have had my own failures with cheaper Samsung M.2 NVMe devices where I lost my vSAN setup since I only had a single vSAN diskgroup comprised of single cache and capacity SSD for my homelab. While not ideal, this is to be expected since I had no redundancy and consumer hardware can and will fail over time. I ended upgrading both of my SSDs to a Samsung 970 Plus, which luckily is not affected by the firmware issues.

I typically recommend Samsung, Intel and Western Digital NVMe devices as they typically just work with ESXi, especially for homelab purposes where cost is one of the factors. From some of the online posts that I have read about the current Samsung 980/990 Pro issues, it seems that many have lost faith in Samsung and some have even stated that they will no longer consider Samsung for storage purchases.

This was also a simliar sentiment when I recently spoke with a fellow VMware colleague who was also impacted by the firmware issues. As part of our discussion, he had shared a couple of alternative vendors that he has is now using and recommending for his VMware Homelab setup which also includes vSAN. I thought this was good information that could also benefit folks in the community looking for other storage options.

[Read more...]

Automating subscription and usage retrieval for vSphere+ and vSAN+ Cloud Service

by // 2 Comments

As a follow-up from my earlier blog post which helps customers inventory their current on-premises vSphere/vSAN CPU usage for use with vSphere+, vSAN+ and VCF+ Cloud Services, this post will focus on how customers can easily inventory their vSphere+ and vSAN+ subscription usage, both manually and through some automation.


Once your on-premises vCenter Server has been converted into a subscription, all usage and billing information is now managed through the VMware Cloud Console (vmc.vmware.com), rather than the License section of the vSphere UI. In fact, you will find that the vSphere UI will be updated to include a new Subscriptions tab which provides a direct link to both the vSphere+ and vSAN+ Cloud Service.

[Read more...]

Blocking vSphere HTML5 VM Console and allowing only Standalone VM Remote Console (VMRC)?

by // 2 Comments

This was an interesting request that came up on the VMTN community forums asking whether it was possible to block users from accessing the vSphere HTML5 (H5) VM Console in vCenter Server and only allowing access to a VM console through the use of the Standalone VM Remote Console (VMRC) client? What is the use case for this you might ask, well it looks like VM screen resolution was getting change between the two clients and the administrator simply wanted to restrict access to the H5 VM Console and direct users to use only the VMRC Client.

At first, I could not see how this could be accomplished since all of their users already have the "Console interaction" privilege within vCenter Server which allows them to to interact with both VM Console interfaces. I was then reminded of an article that I wrote back in 2021 where a user wanted to restrict access to the vSphere UI interface while still allowing access to vCenter Server through the vSphere API, which used an access policy to restrict access based on a URI endpoint within the vCenter Server Tomcat application configuration.

This gave me an idea to experiment with and see if we could do the same and simply restrict the /ui/vmconsole endpoint which serves the H5 VM Console while still preserving VMRC access.

[Read more...]