Windows Server 2016 Full Support for Windows Server 2016 has been introduced for these products: ESXi 5.5, ESXi 5.5 Update 1, ESXi 5.5 Update 2, ESXi 5.5 Update 3, ESXi 6.0, ESXi 6.0 Update 1 and ESXi 6.0 Update 2.
In today’s post, I’ll be showing you how to install Windows Server 2016 with Desktop Experience on an ESXi 6.5 U1 host managed by a U1 instance. This step-by-step how-to guide is aimed at readers who have yet to install a Windows OS on a VMware hypervisor. For something a little bit more advanced, you can take your pick from the complete of published posts to date.Windows Server Flavors and RequirementsWindows Server 2016 comes in 3 flavors; Server Core (no GUI), Server with Desktop Experience (with GUI) and Nano Server. The latter is Microsoft’s headless server, one that is completely managed remotely with no local logon capabilities making it a perfect solution cloud deployments.
Nano server has recently been to primarily support and run containers.Windows Server 2016 also comes in 3 editions; Essentials, Standard, and Datacenter. Have a look at this to learn how each edition differs from the rest.As far as hardware requirements go, Microsoft’s suggests the following. Processor: 1.4 GHz 64-bit. The CPU must support NX, DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW and second level address translation.
RAM: 512MB or 2GB for a Desktop Experience installation. 800 MB is the required minimum when installing Windows Server 2016 as a VM. Storage: 32GB absolute minimum. NIC: 1 GigabitAs often is the case, the minimum hardware requirements quoted by Microsoft rarely come close to mirror what’s actually needed to run production boxes. With that in mind, consider increasing the resources allocated in accordance with the role(s) assigned to the server and its anticipated workload.Some optional requirements are;.
UEFI firmware to support secure boot where applicable. Trusted Platform Module ( TPM) capabilities to enable encryption features such as BitLocker.Creating the base VMI’ll be using the new vSphere client (HTML5) to create the base VM. Here are the steps.Step 1 – Right-click on a cluster, or host, and select New Virtual Machine (1). Select Create a new virtual machine (2) from the wizard. Click Next.Step 2 – Type in a name for the VM (1) and select a location (2), such as a datacenter, where you want it installed. The Windows folder shown is something I created.Step 3 – Select the ESXi host where the VM will be deployed to.
In the example, I selected a DRS enabled cluster (1) so placement is done automatically.Step 4 – Select a datastore (2) where the VM will be created. If you’re using storage policies, make sure to select the correct one from the VM Storage Policy drop-down box (1).Step 5 – Select the correct compatibility mode according to the ESXi version installed. In my case, I’ve selected ESXi 6.5 or later.Step 6– Select Microsoft Windows Server 2016 (64bit) guest OS Family and Version types. If you’re running this on older versions of ESXi, select Microsoft Windows Server 2012 (64 bit) instead.Step 7 – For the hardware requirements, I’m sticking with the values suggested to me by the wizard.
The only hardware settings I changed are the ones for the SCSI controller, which I set to VMWare Paravirtual, and the vNIC driver which I set to vmxnet3. This should improve the overall performance of the virtual machine. I also set the VMDK type to thin since I’m a bit short on storage space.To use the Secure Boot feature, change the BIOS firmware setting to EFI by navigating to Boot Options - Firmware under the VM Options tab.Step 8 – Review the configuration and press Finish to create the VM.Installing Windows Server 2016Now that the VM has been created, it’s time to install the guest OS. For this task, I’ll be using the client as I find it easier to use when mounting ISOs on VMs and such.Step 1 – Highlight the VM just created and click on Launch Remote Console link.Step 2 – Power up the VM and select Connect to Disk Image File (iso) from the VMRC - Removable Devices - CD/DVD drive 1. Navigate to the folder containing the Windows Server 2016 ISO image and select it.Step 3 – Select Send Ctrl+Alt+Del from the VMRC drop-down menu. You should see the Windows installer booting up.Step 4 – Select the language and localization settings matching your time-zone and country and click Next.Step 5 – Click on Install now to kick off the installation.Step 6 – Type in the product key, if you have one, and press Next. If you don’t, just click on the I don’t have a product key link to install Windows Server in evaluation mode.Step 7– Select the Windows Server edition and deployment type.
For this example, I’ve selected Windows Server 2016 Standard (Desktop Experience). Press Next.Step 8 – Accept the license terms by ticking on the option at the bottom and press Next.Step 9 – Select Custom: Install Windows only (advanced)Step 10a – At this point, I must mount the vmtools ISO image since I selected VMware Pararvirtual as the SCSI controller. This step is not required if you stick by the default setting (LSI Logic SAS). To this, we simply select Install VMware Tools from VMRC - Manage. This will mount the corresponding ISO image on the VM.
Once you do, click on Load driver, select the CD drive labelled VMware Tools and drill down to the /Program Files/VMware/VMware Tools/Drivers/pvscsi/Win8/amd64 folder as shown next.Step 10b – The VMware PVSCSI Controller driver is automatically selected for you. Click Next to continue.Step 11 – If you see Drive 0 Unallocated Space listed, it means that the paravirtual driver has correctly detected the VMDK specified for the VM.Before pressing Next, disconnect the VMware Tools ISO image and reconnect the one for Windows Server 2016.
You won’t be able to proceed with the installation unless you do this.Once you reconnect the Windows Server ISO, press Refresh and make sure that the Windows can’t be installed at the bottom clears. Press Next to use the entire disk for the Windows Server installation.Step 12 – Wait for the installation procedure to finish.Step 13 – Set a password for the administrator account and press Finish.Step 14 – Log in and install the VMware Tools. Disconnect the Windows Server ISO image as described and mount the VMware Tools ISO image still using the VMware Remote Console client ( VMRC - Manage - Install VMware Tools).
Click on the mounted DVD Drive or taskbar notification to run the vmtools installer. Follow the instructions and reboot the VM when done.Congratulations!
You now have Windows Server 2016 with Desktop Experience running on VMware. For production environments, you should go for the Server Core version for better performance and improved security. Also note that the steps covered today apply to installing Windows Server 2016 on both physical ESXi hosts as well as nested ones. If you wish to learn how to set up a nested vSphere environment, have a look at this.
An IT veteran for over 23 years, I covered various roles throughout my career. Prior to joining Altaro as a blog writer and QA tester, I was employed as an infrastructure engineer at a cloud services provider working exclusively with VMware products. The Altaro VMware blog enables me to share the experience and knowledge gained and, much to my surprise, is what got me the vExpert 2017 award. Besides being a techie and a science buff, I like to travel and play guitars. I also do some photography and love having a go at playing the occasional XBOX game, Halo being my absolute favourite.
I am also a proud father of two and parent to a crazy Dachshund called Larry. 31 thoughts on 'How to Install Windows Server 2016 on VMware'.
Hi All,I am just starting our migration to Windows Server 2016 on ESXi. I just want to make sure that I don't configure something incorrectly that I will regret later as it has been a few years since I have configured a new ESXi host, and I just wanted to make sure nothing has changed as concerning best practices. The host that the VMs are on is a Dell R740 with a RAID 10 SSD array, 2x Intel 8 cores per proc, 128 GB of RAM. Here is what I am configuring for as a base template:Memory: 8GB with no limit on memory (I will get the limits defined later)Hard disk: 100 GB thin provision using the VMware Paravirtual controller (I plan on increasing the storage on per VM basis).
Disk mode= DependentNetwork Adapter: VMXNET 3Bios Firmware: BiosVMware installation option: Typical (as I understand it is not a good idea to choose complete unless there is use case for it)Thanks,Edited Dec 3, 2017 at 01:38 UTC. As far as I know VMWare does not have a comparable feature, definitely something I miss coming back to VMWare after working with Hyper-V for a short time.I'd also say 2GB memory is a good base to start at. I have a few 2016 servers running fine on 2GB (RDP GW/Licensing/Broker server for example). As long as you have the memory hot-plug enabled, you can always increase on the fly if the server needs it. Likewise, CPU and disk space can be increased on the fly so always best to start with bare minimum you think you can get away with.