Академический Документы
Профессиональный Документы
Культура Документы
Table of Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
JMP – Next-Generation Application and Delivery Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Organization of This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
T E C H N I C A L W H I T E PA P E R | 2
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
T E C H N I C A L W H I T E PA P E R | 3
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Introduction
VMware Horizon® 7 provides virtual desktop solution as well as an enterprise-class, application-
publishing solution. For users who do not require personalized virtual desktops and who handle a
standard set of tasks, VMware Horizon Apps is the ideal solution. Horizon Apps offers published
applications and session-based desktops, without VDI.
Horizon Apps leverages Microsoft RDSH servers to deliver published applications or desktops. Data,
applications, and desktops are centrally managed and secured. Users access their published applications
and desktops from a single digital workspace, through single sign-on from any authenticated device or OS.
Critical Horizon 7 features and components, such as the Blast Extreme display protocol, instant-clone
provisioning, VMware App Volumes™ application delivery, and VMware User Environment Manager™,
are integrated with published applications and desktops to provide a seamless user experience and
an easy-to-manage, scalable solution.
Published applications and desktops provide the opportunity to reduce hardware, software, and
operating costs, and simplify installation, upgrades, and troubleshooting.
When deploying an RDSH-based Horizon Apps solution, administrators must take a number of
considerations and best practices into account. Areas to consider include VMware ESXi host sizing,
RDSH image configuration and optimization, Horizon 7 configuration and policies, antivirus solutions,
provisioning, and recurring maintenance.
Administrators will also want to consider integrating VMware JMP technologies, which include VMware
Instant Clone Technology, App Volumes, and User Environment Manager.
JMP allows components of a desktop or RDSH server to be decoupled and managed independently
in a centralized manner, yet reconstituted on demand to deliver a personalized user workspace when
needed. JMP is supported with both on-premises and cloud-based Horizon 7 deployments, providing
a unified and consistent management platform regardless of your deployment topology.
The JMP approach provides several key benefits, including simplified desktop and RDSH image
management, faster delivery and maintenance of applications, and elimination of the need to manage
“full persistent” desktops.
Purpose
This guide provides best practices for anyone deploying a published application or published desktop
solution based on Horizon 7.
Audience
This guide is for anyone installing or administering Horizon 7 or Horizon Apps. Readers should
be familiar with basic installation and administration procedures, such as those described in
Publishing Applications with VMware Horizon 7.
T E C H N I C A L W H I T E PA P E R | 4
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
T E C H N I C A L W H I T E PA P E R | 5
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
When using load balancing across multiple physical network adapters connected to one vSwitch, make
sure that all the NICs have the same line speed.
Figure 1 shows an example of the proper configuration. The two adapters vmnic0 and vmnic1 are
connected to vSwitch0 and both have a line speed of 1000 Mb. The adapters vmnic2 and vmnic3
are connected to DSwitch10GBe. Both have a line speed of 10000 Mb.
T E C H N I C A L W H I T E PA P E R | 6
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Configure the BIOS settings to allow ESXi the most flexibility for the power-management features
offered by your hardware and then make your power-management choices within ESXi. For example,
disable all hardware-controlled power management features, but enable all power-management
features that the operating system can control.
For the resource cluster, the recommended power option is High performance because it allows the
highest user density and provides consistent performance.
iSCSI Recommendations
Using jumbo frames with iSCSI can reduce packet-processing overhead, thus improving the
CPU efficiency of storage I/O. For the best iSCSI performance, enable jumbo frames when possible.
See the VMware knowledge base article iSCSI and Jumbo Frames configuration on VMware ESXi/ESX
(1007654).
T E C H N I C A L W H I T E PA P E R | 7
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Provisioning more LUNs with fewer VMs on each LUN can enable the ESXi servers to simultaneously
present more I/O requests to the array. This setup has the potential to improve performance by ensuring
full utilization of all array resources and giving the array more opportunities to optimize the I/O.
However, provisioning too many LUNs, especially when many ESXi servers are connected to a single
array, can allow the ESXi hosts to simultaneously send so many I/O requests that they fill the array
queue, and the array returns QFULL/BUSY errors. This situation can reduce performance due to the
need to retry the rejected I/O requests.
Networking Recommendations
To ensure optimal network performance, we recommend using the vSphere Network I/O Control feature
to control bandwidth. We also recommend using the VMXNET3 network adapter whenever possible.
Each resource pool is associated with a port group. When network resource pools are not split
across physical network adapters, we recommend using NetIOC. For more information, see
vSphere Network I/O Control in the vSphere Networking Guide.
T E C H N I C A L W H I T E PA P E R | 8
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
The VMXNET network adapters—especially VMXNET3—also offer performance features not found
in other virtual network adapters. For optimal performance, use VMXNET3. For more information,
see Network Adapter Types in the vSphere Virtual Machine Administration Guide.
Active Directory
To apply group policies to the RDS hosts that deliver remote desktop or application sessions,
without affecting other Windows computers in the same AD domain, create an organizational unit
(OU) specifically for your RDS hosts. This OU cannot have inheritance or linked GPOs applied to
nonvirtual machines.
T E C H N I C A L W H I T E PA P E R | 9
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Computer Configuration > Policies > Administrative Templates > Windows Components >
Remote Desktop Services > Remote Desktop Session Host > Licensing
• LicenseServers (REG_MULTI_SZ)
• LicensingMode (2 = per device, 4 = per user)
It is recommended that you delete the key containing timebomb in the following hive of the registry of
the RDSH image so that the grace period starts after deployment and not on creation of the image:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
T E C H N I C A L W H I T E PA P E R | 1 0
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Note: This information is applicable whether you are implementing a new RDSH environment or
migrating an existing RDSH or virtual desktop infrastructure (VDI) environment to a Horizon 7 published
applications environment.
Make sure that the ratios do not span CPUs because every RDSH needs to follow NUMA.
Which configuration works best depends on the thread use of the application workload. Always test
your configuration with a pilot.
For example, if the hosts used for an RDSH cluster have two Intel Xeon Processor E5-2699 v4
(22 cores), the hosts should run a maximum of:
2 (physical CPUs) * 1 (1:1 ratio) * 20 (physical cores) / 4 (virtual CPUs) = 10 RDSH VMs
This amount is equal for both ratios. The extra cores and hyper-threaded cores are not lost. They are
used for virtual networking, storage, and other host tasks.
From the baseline that you previously established, you can estimate the CPU resources required per
type of user. With this example, we can determine the number of hosts required for a company:
• Based on Perfmon, the average CPU usage of one type of user found is 260 MHz.
• The Intel Xeon Processor E5-2699 v4 has an all-core turbo. If Turbo Boost is disabled or high
temperatures are expected, use the base frequency, which is 2200 MHz.
• With a speed of 2800 MHz and with four physical cores available per RDSH, this processor allows
for 11200 MHz to be shared among users.
• When leaving a 40 percent margin for CPU spikes, such as during boot storms, you can have 30 users
per RDSH, or 300 per ESXi host.
T E C H N I C A L W H I T E PA P E R | 1 1
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Start with 4 GB of memory for the operating system, plus 975 MB (750 MB + 30 percent margin)
per user, unless the performance monitoring shows high memory usage. In our example, the amount
is 32 GB:
Besides validating your calculations, you can determine whether to use a 1:1 or 2:1 virtual-to-physical
CPU ratio, based on performance.
For example, if you have 900 users who need to continue working when an ESXi host is down,
you need four hosts:
(900 / 300) + 1
If you want to use vSAN 6.5 RAID-6 Erasure Code, you need six hosts, because the supported
configuration is 4 + 2. You can also choose smaller CPUs.
With four hosts and 2 GB required for ESXi, you need 384 GB of host memory, which is the closest
supported configuration to the required amount of 322 GB to allow enough headroom for vSAN:
With six hosts, the closest supported configuration to the required amount of host memory is 256 GB
to allow enough headroom for vSAN:
2 + (6 * 32) = 194 GB
T E C H N I C A L W H I T E PA P E R | 1 2
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
The steps:
1. Create the master RDS host VM.
2. Install common Microsoft runtimes and features.
3. Install Microsoft updates.
4. Tune Windows with the OS Optimization Tool.
5. Trim the image.
These items cannot be part of an App Volumes AppStack or VMware ThinApp®. But make sure to install
these runtimes on all provisioning VMs.
Install the Desktop Experience feature if scanner redirection or a richer user experience is required.
For more information, see Install Desktop Experience on Windows Server in Setting Up Published
Desktops and Applications in Horizon 7.
T E C H N I C A L W H I T E PA P E R | 1 3
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Publishing occurs only when you create a new farm or update an existing farm to incorporate changes.
Publishing the master image takes between 7 and 40 minutes, depending on the type of storage and
number of hosts that you are using.
After the publishing process is complete, provisioning the servers takes 1 or 2 seconds per server.
Provisioning does not require power operations, and the clones are forked from a running parent VM
to further expedite the process.
You can delay the provisioning process by not enabling it in the Add Farm wizard. When you scale up
the pool, all that needs to be done is provisioning.
T E C H N I C A L W H I T E PA P E R | 1 4
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
A load-balancing script returns a load value. The load value can be based on any host metric, such as
CPU utilization or memory utilization. Horizon Agent maps the load value to a load preference and
reports the load preference to the Connection Server. The Connection Server uses the load preference
to determine where to place new application sessions.
Important: Include margins for peak loads in the script, just as we did in the CPU and memory
calculations. Use the script in conjunction with a reasonable maximum number of connections per host,
which is set on the host or farm. Session load balancing addresses load balancing only at connection
time and cannot move users after they have been assigned.
You must enable the VMware Horizon View Script Host service on an RDS host before you configure
a load-balancing script. The service is disabled by default. Set it to automatic using services.msc.
You must configure the same load-balancing script on every RDS host in the farm. Configuring a
load-balancing script involves setting a registry key on the RDS host.
If you are using an automated farm, you perform this procedure on the master VM for the
automated farm.
For more information, see Configuring Load Balancing for RDS Hosts in View Administration.
Horizon Smart Policies are available for configuring USB redirection, client-drive redirection, bandwidth
profiles, and more.
T E C H N I C A L W H I T E PA P E R | 1 5
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Folder Redirection
To allow user data to persist between sessions, use folder redirection for the Documents folder, at
a minimum. We recommend using User Environment Manager to configure folder redirection.
For more information, see Configure Folder Redirection in the VMware User Environment Manager
Administration Guide.
User Profiles
Because users can get a different RDS host each time they log in, we do not recommend keeping profile
information on the RDS host. Doing so consumes an excessive amount of disk space. Instead, use folder
redirection, and use mandatory user profiles, as described in the VMware blog post VMware User
Environment Manager, Part 1: Easier, Faster Windows Logins with Mandatory Profiles.
A mandatory user profile is a special type of preconfigured roaming profile that you can use to specify
settings for users. A user can modify a desktop, but the changes are not saved when the user logs out.
The next time the user logs in, the mandatory user profile created by the administrator is downloaded.
If you choose not to use mandatory user profiles, remove the cached user profile at logout. See
Delete cached copies of roaming profiles.
T E C H N I C A L W H I T E PA P E R | 1 6
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Printer Configuration
When using locally attached personal printers or specialized printers, such as bar code printers and label
printers, users can use local printer redirection (also called the virtual printing feature), which is included
with Horizon 7. This feature does not require installing printer drivers in the RDS host because the printer
driver is installed on client endpoints.
Keep the following in mind when using local printer redirection with VMware Horizon 7.
• Printer redirection supports many common printer features, such as two-sided printing, but it might
not support some unique features of a specific printer.
• Client systems that do not have local printer drivers, such as PCoIP zero clients and mobile clients,
are not supported.
However, local printer redirection is not the right solution for corporate network printers. Network
printing is redirected over virtual channels, which can impact overall performance. When using network
print servers, we recommend using User Environment Manager to set up printer mappings and to deliver
a follow-me printing solution. Printers can be mapped during the user login process. The printer is ready
immediately after the login process completes.
For example, you map a particular printer, such as a barcode printer, when a user launches a specific
application. The mapping is deleted when the user closes the application. This setup streamlines the
login process because the printer is mapped only when the user needs it.
Figure 3: Printer Mapping Settings Tab Showing the Path to the Printer
For more information, see the VMware blog post Choosing Printing Options for VMware Horizon 7.
T E C H N I C A L W H I T E PA P E R | 1 7
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
For more information, see the VMware User Environment Manager Application Profiler
Administration Guide.
Internet Explorer
To turn off hardware graphics acceleration for Internet Explorer, navigate to Internet Options >
Advanced > Accelerated graphics and select Use software rendering instead of GPU rendering.
Microsoft Office
To turn off hardware graphics acceleration for Microsoft Office, navigate to File > Options > Advanced
and select Disable hardware graphics acceleration.
Adobe Reader
To turn off hardware graphics acceleration and disable other CPU-intensive display options for
Adobe Reader:
1. Navigate to Preferences > Page Display > Rendering and deselect the following options:
• Smooth imaging
• Smooth line art
• Use page cache
• Enhance thin lines
2. Navigate to Preferences > Page Display > Page Content and Information and select
Disable smooth zooming.
For more information, see the Adobe documentation about General Application Settings in the
Windows Registry.
Google Chrome
To turn off hardware graphics acceleration for Chrome, navigate to chrome://settings > System and
deselect Use hardware acceleration when available.
Create dedicated AppStacks for RDS hosts. Do not reuse an AppStack that was originally created
for a desktop OS.
Install the applications on the same operating system that is on the deployment RDS host.
Before installing applications on an AppStack, switch the RDSH server to the RD-Install mode. For
more information, see Publishing Applications with VMware Horizon 7.
Important: If you are assigning App Volumes AppStacks to OUs, contact Global Support Services for
the App Volumes 2.12.3 hot patch. This fix will also be included in general releases of App Volumes
later than 2.12.
T E C H N I C A L W H I T E PA P E R | 1 8
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
T E C H N I C A L W H I T E PA P E R | 1 9
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
We recommend scheduling weekly or daily maintenance outside of business hours to minimize the
impact on users. If you have multiple shifts per day of users, weekly maintenance is recommended.
Otherwise, daily maintenance is recommended.
You can choose whether to log out users or wait for them to log out before performing maintenance.
T E C H N I C A L W H I T E PA P E R | 2 0
BEST PRACTICES FOR PUBLISHED APPLICATIONS AND DESKTOPS
IN VMWARE HORIZON APPS AND VMWARE HORIZON 7
Conclusion
Setting up a Horizon 7 RDSH environment is similar to deploying a VDI desktop environment. The main
differences involve calculating VM density on vSphere hosts and installing software and features on the
RDS host VMs. Adhering to the best practices described in this guide ensures that you get the best
performance for your RDSH applications and desktops.
Additional Resources
Choosing Printing Options for VMware Horizon 7 (VMware blog post)
Collecting the Windows Perfmon log data to diagnose virtual machine performance issues
(VMware knowledge base article)
Horizon 7 Documentation
Storage vMotion to thin disk does not reclaim null blocks (VMware knowledge base article)
VMware User Environment Manager, Part 1: Easier, Faster Windows Logins with Mandatory Profiles
(VMware blog post)
vSphere 6 Documentation
T E C H N I C A L W H I T E PA P E R | 2 1
VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com
Copyright © 2017 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed
at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be
trademarks of their respective companies. Item No: 5084-VMW-WP-HORIZON7-BEST-PRACTICES-USLET-20170724
7/17