If you are interested in evaluating Microsoft Windows 11, in addition to the ISO image, you can now download a pre-configured Windows 11 image (OVF) that can run on any VMware Desktop Hypervisor (Workstation, Player and Fusion) for 90 days!
Per the documentation, the pre-built image includes the following:
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.
It's finally here!
Based off of Windows 11 Pro 22H2, tiny11 has everything you need for a comfortable computing experience without the bloat and clutter of a standard Windows installation.
https://t.co/yM1Ip2ljjB pic.twitter.com/Tg5PWUZU1Q— NTDEV @*protected email* (@NTDEV_) February 2, 2023
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.
🙌 Updated Tiny 11 Arm64 (tiny11a64 r1.iso) now works perfectly with @esxi_arm 💪
Thanks @NTDEV_ for the Arm version & quick fix!#ESXionARM pic.twitter.com/03TV69wMIq
— William Lam (@*protected email*) (@lamw) February 16, 2023
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.
The ESXi-Arm team has just released v1.11 of the ESXi-Arm Fling and one of the most exciting new capability is that you can now run Windows 11 Arm using an ESXi VM! There is also a TON of new features, so definitely check out the official ESXi-Arm Blog post announcement for more details.
One of the requirements for running Windows 11 Arm is the need for a Trusted Platform Module (TPM). Luckily, the latest ESXi-Arm v1.11 also now supports adding a vTPM to a guest and a requirement for setting this is a Key Management Server (KMS). Currently, the ESXi-Arm Fling is based on vSphere 7.0 (GA) and you can either use an existing compatible KMS (which you can look through VMware KMS Compatibility List) or for lab/testing purposes, you can use my KMIP Docker Container, which was also updated recently to support both amd64 and arch64 architecture.
For those interested in quickly setting this up and using my KMIP Docker Container for the KMS component, below is a quick walkthrough on how to set this up.
UPDATE (10/16/23) - vCenter Server may not be needed as you can use ESXi vSphere API to manually add encryption keys for use with vTPM, at least for x86. This same technique might also work with ESXi-Arm, for more information please see this blog post HERE.
Note: While vSphere 7.0 Update 2 introduced an embedded Native Key Provider (NKP) within vCenter Server, it can not be used with ESXi-Arm as both ESXi and vCenter must be running 7.0 Update 2 and the ESXi-Arm Fling is based on 7.0 GA.