7.0

Table Of Contents
Virtual Machine Custom Configuration Parameters
You can use virtual machine custom configuration parameters as baseline settings when you create a virtual
machine for remote desktop deployment.
You can change certain settings when you use View Administrator to deploy desktop pools from the virtual
machine.
Table 31. Custom Configuration Parameters
Parameter Description and Recommendations
Name and Location
The name and location of the virtual machine.
If you plan to use the virtual machine as a template, assign a generic name. The
location can be any folder within your datacenter inventory.
Host/Cluster
The ESXi server or cluster of server resources that will run the virtual machine.
If you plan to use the virtual machine as a template, the location of the initial
virtual machine does not necessarily specify where future virtual machines
created from template will reside.
Resource Pool
If the physical ESXi server resources are divided into resource pools, you can
assign them to the virtual machine.
Datastore
The location of files associated with the virtual machine.
Hardware Machine Version
The hardware machine version that is available depends on the ESXi version you
are running. As a best practice, select the latest available hardware machine
version, which provides the greatest virtual machine functionality. Certain View
features require minimum hardware machine versions.
Guest Operating System
The type of operating system that you will install in the virtual machine.
CPUs
The number of virtual processors in the virtual machine.
For most guest operating systems, a single processor is sufficient.
Memory
The amount of memory to allocate to the virtual machine.
In most cases, 512MB is sufficient.
Network
The number of virtual network adapters (NICs) in the virtual machine.
One NIC is usually sufficient. The network name should be consistent across
virtual infrastructures. An incorrect network name in a template can cause
failures during the instance customization phases.
When you install Horizon Agent on a virtual machine that has more than one
NIC, you must configure the subnet that Horizon Agent uses. See “Configure a
Virtual Machine with Multiple NICs for Horizon Agent,” on page 36 for more
information.
IMPORTANT For Windows 7, Windows 8.*, Windows 10, Windows Server 2008 R2,
and Windows Server 2012 R2 operating systems, you must select the VMXNET 3
network adapter. Using the default E1000 adapter can cause customization
timeout errors on virtual machines. To use the VMXNET 3 adapter, you must
install a Microsoft hotfix:
n
For Windows 7 SP1: http://support.microsoft.com/kb/2550978
Install the hotfix before installing Horizon Agent. When installing the hotfix,
if you encounter Windows Update error 0x80070424, see
https://support.microsoft.com/en-us/kb/968002.
Chapter 3 Creating and Preparing a Parent Virtual Machine for Cloning
VMware, Inc. 21