WilliamLam.com

Finding vCenter Cloud Gateway Deployments in your environment

by // Leave a Comment

After publishing my recent article on how to audit vCenter Cloud Gateway and vCenter Server registrations for the vSphere+ Cloud Service, I thought it would also be useful to share some tips on how you can easily find your existing vCenter Cloud Gateway (VCGW) deployment(s) within your environment?

You might wonder, do I not already know about my VCGW deployment(s) or for that matter any other solution that is deployed within my own infrastructure? Yes, that would ideally be the case and you should also be able to look that up in your change management database (CMDB). However, over the years in speaking to many customers and hearing about some of the requests from our field teams, I have come to learn that this nirvana state does not exist for many of our customers.

In some organizations, it has been described as the wild wild west where teams of administrators with access to their vSphere environment can deploy any number of solution without ever communicating amongst each other to organizations that provide shared infrastructure access to other small teams and/or companies with a simliar set of challenges. Net net, it is certainly possible that solutions like the VCGW gateway may have been deployed or potentially even retired but have not been removed from your environment.

[Read more...]

Create Windows 11 Virtual Appliance using Tiny 11 with only 2GB memory

by // Leave a Comment

I recently came to learn about a really cool project called Tiny 11 which is a stripped down version of Windows 11 Pro 22H2 that can run with just 2GB of memory and 8GB of storage. While you would probably not use this for production workloads, it could be interesting for those with homelabs and can even for demo purposes.

Disclaimer: Tiny 11 is not an official project from Microsoft, use at your own risk. If you are interested in creating an optimized Windows 10 or 11 image, you can also check out these VMware resources here and here to produce a similiar size image using official Microsoft tools and images.

UPDATE (02/16/23) - There is now an Arm version for Tiny 11, which is great for anyone using the ESXi-Arm Fling and the technique in this blog post would also apply.

After performing a manual installation of Tiny 11, I thought it would be neat if I could build a Virtual Appliance (OVA) for Tiny 11 and also add custom OVF properties, which would allow anyone to customize the OS further without having to rely on any external tooling.

In fact, I had demonstrated this concept back in 2019 using Windows Server 2016 in this blog post and I figure it should be easy enough to also do the same for Tiny 11 or even standard Windows 11! With a bit of trial/error, I was indeed able to create a simple Tiny 11 OVA that includes the following OVF properties as shown in the screenshot below.


My initial goal was to fully automate the building of a Tiny 11 OVA with custom OVF properties using Packer. However, after many attempts, I was not able to figure out the correct autoattended.xml configuration and decided on a semi-manual approach which is detailed in the instructions below. If anyone is able to figure out how to get Tiny 11 installed via Packer, then I may revisit this topic and automate the remainder of the setup.

Note: The instructions below are not specific to Tiny 11 in any way and is also applicable to standard Windows 10 or 11 image.

[Read more...]

Quick Tip - Inventory core count for vSphere+, vSAN+ & VCF+ Cloud Service

by // 3 Comments

vSphere+ and vSAN+ was launched last year as a new cloud service and the unit of consumption are CPU cores, which needs to be determined prior to purchasing a subscription for either cloud services. To help customers inventory their existing vSphere and vSAN CPU core usage, especially useful for general visibility and planning purposes, I had developed a simple PowerCLI function that was published last year as a VMware KB article (89116).

In recent weeks, I had noticed an increased number of inquiries from our field and customers on how to assess their existing vSphere and vSAN environment for transition to vSphere+ and vSAN+ and I realized that many folks may not have been aware of the scripts and the KB article that was available.

Once you have downloaded the PowerCLI script, imported the function and connect to an existing vCenter Server environment, you can then use the Get-vSpherePlusCPUSocketToCoreUsage function which will automatically retrieve all ESXi hosts within your vCenter Server and display the current CPU core usage, vSphere+ Cores and vSAN+ Cores required as shown in the example screenshot below.

[Read more...]