Reference Guide

Boss card information
7 Dell EMC XC Series Appliances and XC Core Systems Best Practices for Running Windows Server 2016 with
Hyper-V | A01
Virtual Machines (VMs) run on the boot device are not highly available and potentially fill up the local boot
device, which results in crashing the host hypervisor. This adds additional wear on the boot device.
Note: The Nutanix Cluster Checker (NCC) v. 2.2.2 and later monitors for VMs running on the boot device.
Important: A common cause for VMs being run from the boot device is misconfiguration during any add-node
or redeployment operation.
When adding or redeploying a Hyper-V node to the cluster, ensure that the Virtual Hard Disks and Virtual
Machines locations are configured in Hyper-V Manager so that they are directed to the Nutanix Cluster
Container location. For example, the storage UNC path for cluster having a fully qualified domain name of
cluster.domain.com and container name of ntnx-ctnr1 would contain \\cluster.domain.com\ntnx-ctnr1.
Hyper-V Manager Virtual Hard Disk and Virtual Machine UNC path
Note: In a Nutanix cluster, the path to the virtual hard disk files and virtual machine configuration files should
never be a path containing a local drive letter.
1.4 Anti-malware software
Microsoft recommends against installation of anti-malware on the Windows Server 2016 with Hyper-V host
operating system. However, if there is a regulatory compliance or other reason requiring that anti-malware
software be run in the host operating system, Microsoft requires the following scan exclusion rules: