VMware, the desktop and server virtualization company, has finally caught up with their competitor, Parallels, and released VMware Fusion with VMware Tools support for Windows 11 late last month.
The July 28 VMware Fusion 22H2 Tech Preview was announced by Michael Roy on the Fusion blog. Now, Mac users with either an M1 or M2 Apple Silicon-based Mac can run Windows 11. Sort of.
First, the good news. With the Fusion 22H2 (aka, second half of 2022) Tech Preview, VMware now includes the first pre-release version of VMware Tools. VMware Tools are the drivers that get injected into the guest operating system to provide emulated hardware compatibility with the host computer’s hardware. The beta release of VMware Tools that comes with the new Fusion beta offers support for a virtual Trusted Platform Module (TPM) 2.0 chip, a Microsoft requirement for Windows 11, drivers for 2D graphics and VMX3 networking drivers. During this beta period, VMware continues to offer Fusion as a free download. New VMware Fusion licenses start at $149.
Now, the bad news. Fusion 22H2 is still in beta. While my first run experience with the latest build of Fusion is running well, the setup and installation process is not for the casual user. This all stems from a licensing deal between Microsoft and Qualcomm. In short, Qualcomm is the exclusive manufacturer of ARM SoCs that are used by Microsoft, and a select few partners, for OEM devices the run the ARM edition of Windows. The exclusive nature of this deal, therefore, prevents Microsoft from selling ARM CPU editions of Windows directly to customers as they do with versions of Windows that run on Intel and AMD processors.
As end-users, the only way to get a Windows for ARM installer is to enroll in the Microsoft Windows Insider beta program. But the Microsoft provided installer comes in a Hyper-V .vhdx virtual disk image file. While Parallels Desktop 17 does a good job of automatically downloading, converting, and installing Windows 11 for you, there is no such option with Fusion. Honestly, that’s a bit of a letdown, in my opinion. To get the ARM version of Windows 11 to run on the Fusion 22H2 technical preview, you are left to download the .vhdx Microsoft installer file and then do the .iso file conversion on your own. Otherwise, you are left with the option of downloading an untrusted and pre-converted .iso file from the Internet. If VMware plans on making Windows 11 compatibility on Apple Silicon Mac’s a selling point, my expectation is that they will need to do a lot of work to give customers a smooth onboarding process like Parallels did.
And therein lies the crux of the problem. There are no companies mentioned here that officially support running Windows 11 on an M1 or M2 Mac. Not Microsoft and certainly not Apple. VMware and Parallels don’t either, but both vendors now ship software drivers that make running Windows 11 on Apple Silicon Macs possible.
It is possible to get the ARM edition of Windows 11 running on an Apple Silicon Mac and then activate Windows with a Microsoft license key. I was able to activate my Parallels Desktop 17 Windows 11 install with a Windows 11 Home license key that I purchased from NewEgg.com. While my install of Windows 11 Home is now legally licensed, my configuration is absolutely not supported or endorsed as a valid configuration. This hodgepodge approach is good for anyone who wants to tinker with Windows, like I do at home. However, as an IT professional, but is certainly not a production-ready solution. Without official support and legally purchased Windows ARM edition SKUs, this solution has no place in a commercial organization.
One day, I expect that Microsoft/Qualcomm exclusivity deal will come to an end. More CPU vendors will make ARM-based processors for PCs, and Microsoft will be able to sell Windows ARM licenses to OEMs and customers. Until then, virtualized ARM editions of Windows belong in the lab. Apple, Parallels, and VMware have proven that the foundation is there and that it works. Now, Microsoft just needs to end the Qualcomm contract.
Until then, I’ll be dreaming of the day when I can have a 14-inch MacBook Pro with a Windows 11 Pro VM running on my desk at work.
It has been a long time since I build a Microsoft Active Directory lab environment. Years ago, I put together a test lab with physical white box machines that I built. The popularity of virtual machine technology makes all of that space hogging, wires everywhere, make your wife annoyed mess a thing of the past.
This will be the first in a series of posts about how I setup a virtual test lab using VMware Fusion on my Mac.
I’m looking for a playground so my requirements are pretty low. To build my virtual lab environment I will be using my everyday use 2015 5K iMac with a 3.3Ghz Quad-Core Intel Core i5 CPU and 32GB of RAM. Faster CPUs and more RAM is always better, however, in 2015 my needs were different. I am also running VMware Fusion Pro 12 as the hypervisor on my iMac. Due to the physical constrains of my iMac, not all of these virtual machines will be running all the time. Likewise, they will not be optimized for speed.
As a side note, anyone purchasing a new M1 Apple Silicon powered Macintosh – the 2020 MacBook Air, the 2020 2-port USB-C 13-inch MacBook Pro, or the 2020 silver Mac mini – will not currently be able to run virtualization technology like VMware Fusion or Parallels Desktop because these apps haven’t yet been updated to work on M1 and Apple’s new virtualization technology layer.
For my initial lab setup, I plan on deploying the Insider editions of Windows Server Core, Windows 10 Pro, and then building an Active Directory domain to manage the environment. Then, I added a virtualized macOS 11 Big Sur VM. In the future, I plan to deploy an IIS web server on my domain controller and the developer edition of SQL Server on another AD member Core server. I will be using Microsoft’s RD Client for macOS to connect to the Windows machines. To network the virtual machines together, I will use the “Share with my Mac” VMware Fusion networking option. From my home network perspective, there will only be one DHCP1 IP network address being used (by my iMac) and each VM will get it’s own private IP address thanks to the magic of NAT2.
For my next article in this series, I will discuss the setup process for Windows Server Core.
During this year’s Worldwide Developer Conference, WWDC, Apple announced the long-rumored start of the transition from Macs that run on Intel CPUs to their own in-house designed CPUs, currently referred to as “Apple Silicon”.
All of This Has Happened Before
If you are a user who came to the Macintosh platform during or after 2006, don’t worry. This is actually the third time Apple has made a big architecture shift like this. Apple’s first Macintosh architecture transition was in 1994 from the Motorola 68000-series processors, the ones that were used in the original Macintosh line up, to the PowerPC 601 CPU first introduced in the Macintosh PowerPC 6100. Then, in 2005, Apple again transitioned the Mac. This time from the PowerPC architecture to the Intel Core Duo architecture. The move to Intel processors also had a side benefit in that Mac could directly boot into Windows; something that had previously required special hardware cards or slow virtualization software. Clearly, moving from one processor architecture to another is something that Apple has some experience with. The move from one CPU architecture to another is an extremely complicated effort. Apple spends years planning for and laying the groundwork components for such a transition years in advance. For example, discarding 32-bit app support from 2019’s macOS Mojave was, in retrospect, a major leading indicator for the start of the Apple Silicon transition in 2020. Tim Cook’s words at WWDC 2020 carry the same message as Steve Jobs’ during WWDC 2005 right down to the dad joke about secret labs and double lives.
Moving to Apple Silicon
Starting with the A4 processor, Apple has been designing and using their own special blend of CPUs. Apple’s custom purpose-built processes have been used in 2010’s iPhone 4 and the original iPad. Apple has continued to press their custom processor advantage by building an in-house team of chip designers that has powered iOS and iPadOS devices to greater levels of performance year-over-year. Johny Srouji’s silicon team has been very, very busy.
One of the big advantages to Apple’s CPUs is that they aren’t just CPUs. Apple refers to their processors as “systems on a chip”. In traditional Intel Macs, there are discrete CPUs, graphics processing chips, known as GPUs, and RAM. For example, a current iMac will have an Intel Core i7 Coffee Lake CPU and will have to send messages between the AMD Radeon Pro GPU and memory. Communicating between these components takes time. Apple’s A-Series SoCs, including the first Macs running Apple Silicon due out late this year, give these machines a performance boost over those that use off the shelf commodity parts.
Using their own SoCs gives Apple another strategic advantage – they are able to develop key customer facing features such as Touch ID and Face ID which required the use of the technology that is found in the iPhone’s T2 secure enclave. While Apple didn’t specifically talk about future Macintosh products during the online only developer conference back in June, I expect the first Apple Silicon iMac to have Face ID. While today’s Intel-powered MacBooks have Touch ID, the current design requires a heavy amount of engineering to fully integrate the T2 co-processor with the Intel CPU. I expect that the first Apple laptop with Apple Silicon will have a much cleaner, streamlined implementation.
Besides performance, I am particularly interested in seeing where Apple Silicon Macs go in terms of customer security and privacy, machine learning (i.e.: high quality ML search results in large Photo libraries), and quality of life features (i.e.: Apple Pay and Apple Watch unlock).
What About Virtualization and Thunderbolt Support?
The switch over to Apple Silicon won’t be without tradeoffs and compromises during the two-year transition period. Since the announcement at WWDC, two big questions have come up about key features of Intel Macs.
The first is what about virtualization? Virtualization allows customers to run Microsoft Windows and other operating systems. Apple has said that their first party solution, Boot Camp, will only work on Intel-based Macs. For Apple Silicon Macs, Apple will be introducing a new virtualization layer and re-introducing key technologies from the PowerPC to Intel transition: Universal 2 and Rosetta 2. With Universal 2, app developers will be able to compile and deploy apps for both Apple Silicon and Intel Macs. Rosetta 2 will help protect customer’s investment in software by enabling software written only for Intel Macs to run smoothly on Apple Silicon Macs running macOS 11 Big Sur. During the keynote, Docker and Parallels were both specifically mentioned as a way to run containers and Linux virtual machines on Apple Silicon Macs running Big Sur. Since Apple Silicon Macs are based on the same processor architecture as iPhone and iPad, iOS and iPadOS apps will now be able to be natively run on new Macs without modification. This will be a boon for customers and developers alike as the number of apps and customers will increase.
But what about Mac users who rely on the ability to run Microsoft Windows for things like Active Directory management tools and Windows-only business applications, including Microsoft Project and Microsoft Visio? Presumably, virtualization vendors VMware and Parallels will be working on solutions for Apple Silicon Mac. This, however, is not a forgone conclusion. Shortly after Apple’s announcement, Fusion developer VMware posted a question to Twitter asking how customers would use their software on Apple Silicon.
One possible solution would be Apple and Microsoft working together to bring Windows on ARM support to Apple Silicon and macOS Big Sur. Microsoft’s Surface X PC already runs a version of Windows 10 that has been optimized to run on a custom Qualcomm ARM chip known as the Microsoft SQ1 SoC. Such a deal could go a long way to virtualizing Windows on Macs similar to how Windows runs on Intel Macs today. At the very least, such a deal could be a leg up for VMware and Parallels products. Microsoft is working collaboratively to make sure that Microsoft Office (Word, Excel, and PowerPoint) are ready for Apple Silicon-powered Macs. Anything is possible from the sometimes partners and sometimes rivals. I like to think that there will be a solution for running Windows and Windows-only application on Apple Silicon Macs, but I won’t be counting on the ability to virtualize Windows on an Apple Silicon Mac into my buying decision at the end of the year.
At the tail end of 2019, Apple began shipping their new Mac Pro tower and Pro Display XDR. The Pro Display XDR, a several thousand-dollar professional workflow monitor, uses Thunderbolt 3 technology to connect it to compatible 2019 and 2020 Macs. The Thunderbolt 3 standard requires and Intel CPU and is one of the reasons why the 2018 and 2020 iPad Pro tablets have USB-C only ports. The good news is that Apple plans on protecting their customer’s investment in the 32-inch 6k display technology. Intel recently announced the USB-C 4 and Thunderbolt 4 standard, which is based on the same USB-C and Thunderbolt 3 connector port. Apple, in a statement to news outlets, said that, “We remain committed to the future of Thunderbolt and will support it in Macs with Apple silicon.” While Apple did not get into specifics of how they will bring USB-C 4 and Thunderbolt 4 to future Macs, we now know that existing and new peripherals based on the Intel standards will continue to be supported into the future.
Buying Advice and the Future
The announcement of Apple Silicon Macs and macOS 11 Big Sur make for an exciting time for Macintosh fans. Just as the transition to Intel CPUs unlocked better performance, Apple Silicon Macs will usher in the next decade of new features for customers.
With that said, the next two years are going to be in flux. If you are a tech enthusiast, then you are probably going to be like me and will want to get your hands on a new Apple Silicon Mac as soon as you can. As an early adopter you will not doubt run into some compatibility issues with existing software and peripherals. 2020 Apple Silicon Macs, after all, will be “1.0” devices. Apple Silicon hardware released in late 2021 and beyond will have the benefit of feedback from late 2020 and early 2021 Apple Silicon Macs. You should avoid buying a new Apple Silicon Mac with the hope that one day a feature you need or want will be supported.
If you are someone who just prefers the Mac, then buy the best Mac you can when the need comes up. Don’t worry about which chip is in your new Mac. You will receive years of support and trouble-free use for years to come.
If you are a professional who relies on the Mac to get your work done, you will have some decisions to make. If you find yourself working primarily in Adobe Creative Cloud products, Microsoft Office, and Autodesk Maya and Cinema 4D, you may be ready for the new platform. However, if you look down the list of software and features that just have to work flawlessly, then, your best bet is to stick with the Intel Mac you have today or purchase a new Intel Mac when you need one during the next 18 months.
The future of the Macintosh platform is brighter as it has ever been, and I am looking forward to the new features!
This weekend, I started a small project to install some old DOS and Windows 95-family games into virtual machines (VMs) that I have running in VMware Fusion (VMware Workstation on Windows PCs).
Trying to get old MS-DOS games, like Quake and Tie Fighter working have proven to be particularly difficult as I have long forgotten the art of configuring drivers in autoexec.bat and confg.sys.
To help, I have found two tools that have been useful in this weekend’s hacking effort to get the games loaded and relearn what was forgotten.
The first is Apple’s own Disk Utility. Disk Utility can be used for a number of things on macOS, but it can be used to bundle up the contents of a folder into a floppy disk .img file. Apple has a really good step-by-step KB support article on how to make disk images.
I wasn’t having much success in using Disk Utility to create CD and DVD .iso files. So, rather than waste many hours on troubleshooting, I chose to download InfraRecorder for Windows and load it into a Windows 10 Insider VM. The free software can be downloaded from Ninite.com – a site the provides safe utility software for Windows PCs without all of the malware, bloatware, adware…you get the idea.
Finally, if you are looking for some old boot disks or OS installers, WinWorld has a full library of software that should have what you are looking for. For me, I needed that Windows 98 Second Edition floppy to get the oakcdrom.sys file since my original floppy went missing over a decade ago.
To correct the problem this time, and your milage may vary here, I cleared the checkmark for the Use full resolution for Retina display option. I left the single window and full screen VM settings as they were.
Earlier this week, I was working from home while and taking some vacation time while my car was getting serviced. (But that is an entirely different post for a different time.)
While working, I wanted to use a copy of a corporate Windows 7 VMware guest machine on my 5K iMac. The only problem is that the Windows 7 text is microscopically small on the iMac, which is running at its maximum screen resolution of 3200 x 1800. On my home iMac, I am running VMware Fusion 8.5.8.
However, the steps for adjusting Retina display support in the KB article didn’t exactly work for my configuration of Windows 7 guest. In addition to the virtual machine settings provided by VMware, I wanted to share the configuration adjustments that worked for me, and hopefully, by extension, may also help you.
To get started, I copied the guest virtual machine to my virtual machine folder on my iMac’s hard drive. Then, I started up the virtual machine, logged in with an administrator level account, and uninstalled the VMware Tools package that was installed by VMware Workstation, and then reinstalled the version of VMware Tools from Fusion. This step might be unnecessary, but I wanted to keep the version of VMware Tools consistant with the version that I have on my iMac for Fusion 8.
After the shell game with VMware Tools has finished, I shutdown the Windows 7 guest. Next, I used the directions that VMware provided in their KB article.
Finally, to make the text in the Windows 7 guest virtual machine readable, I had to do two more things:
1. In Control Panel > Appearance and Personalization > Display, I set the text size to “Larger – 150%”.
2. In Control Panel > Appearance and Personalization > Display > Screen Resolution, I set the Windows 7 resolution to 2048 x 1536.
For the Windows screen resolution step above, you may want to go one resolution step up or down from there, depending on your preferences.
Since we are talking about a Windows machine, I rebooted the Windows 7 guest just to test everything out. Now I am able to comfortably run and read the text on my Windows 7 guest virtual machine on my 5K iMac running at full resolution.