6.7

Table Of Contents
Avoid problems by following these best practices.
VBS Hardware
Use the following Intel hardware for VBS:
n
Haswell CPU or later. For best performance, use the Skylake-EP CPU or later.
n
The Ivybridge CPU is acceptable.
n
The Sandybridge CPU might cause some slow performance.
Not all VBS functionality is available on AMD CPUs. For more information, see the VMware KB article
https://kb.vmware.com/s/article/53003.
Windows Guest OS Compatibility
In vSphere 6.7, VBS is supported for Windows 10 and Server 2016 virtual machines, although versions
1607 and 1703 require patches. Check Microsoft documentation for ESXi host hardware compatibility.
VBS in Windows guest OSs RS1, RS2, and RS3 requires HyperV to be enabled in the guest OS. See
VMware vSphere Release Notes for more information.
Unsupported VMware Features on VBS
The following features are not supported in a virtual machine when VBS is enabled:
n
Fault tolerance
n
PCI passthrough
n
Hot add of CPU or memory
Installation and Upgrade Caveats with VBS
Before you configure VBS, understand the following installation and upgrade caveats:
n
New virtual machines configured for Windows 10 and Windows Server 2016 on hardware versions
less than version 14 are created using Legacy BIOS by default. You must reinstall the guest operating
system after changing the virtual machine's firmware type from Legacy BIOS to UEFI.
n
If you plan to migrate your virtual machines from previous vSphere releases to vSphere 6.7 or
greater, and enable VBS on your virtual machines, use UEFI to avoid having to reinstall the operating
system.
Enable Virtualization-based Security on a Virtual Machine
You can enable Microsoft virtualization-based security (VBS) for supported Windows guest operating
systems at the same time you create a virtual machine.
Enabling VBS is a process that involves first enabling VBS in the virtual machine then enabling VBS in
the Windows guest OS.
vSphere Security
VMware, Inc. 187