I encountered another fun adventure recently while upgrading some VMware Horizon 8 Connection Servers to version 2306. The upgrade process itself went smoothly, as you would expect. The installer processed the upgrade and stated that it was completed successfully. I attempted to access the VMware Horizon Administrator web console and found it would not process my smartcard authentication. I then tried to authenticate using an account with a password assigned, and again, the authentication was unsuccessful.

After recently upgrading the VMware Horizon Connection Servers in a VDI environment I am new to managing, end users complained that they could no longer access their virtual desktops. They stated that when they connected via the VMware Horizon Client for Windows, they received an HTTP 421 error similar to the screenshot below. VMware Horizon Windows Client Showing HTTP 421 Error Honestly, I had never heard of the HTTP 421 error code, so I had to look it up.

I recently had the opportunity to begin supporting multiple VMware Horizon 8 virtual desktop environments. Knowing that I wasn’t familiar with the products, I set out to deploy a complete environment in my home lab. This blog post is the first of hopefully several that will walk through the deployment and configuration of the various VMware Horizon and Workspace ONE components. Within this post, I walk through deploying my first Horizon 8 Connection Server and a Connection Server Replica.

On July 26, 2023, the Defense Information Systems Agency (DISA) released the first VMware vSphere 7.0 STIG update. This update includes several minor updates to the checks and fixes across the ESXi, VAMI, vCA EAM, vCA Lookup Service, vCA Photon OS, vCA PostgreSQL, vCA STS, vCA UI, vCenter, and Virtual Machine STIGs.

During recent testing that I was completing within my home lab, I was repeatedly creating and decommissioning VMware vSAN configurations within a single cluster. The first time I completed this process, I was decommissioning a VMware vSAN OSA configuration prior to creating a new VMware vSAN ESA configuration on the cluster. When I went through the process and reached the portion to specify the disks, I found that the disks were unavailable for claiming.