Configuring Your Infrastructure For View Composer - VMware View Manager 4.5 Installation Manual

Hide thumbs Also See for View Manager 4.5:
Table of Contents

Advertisement

VMware View Installation Guide

Configuring Your Infrastructure for View Composer

You can take advantage of features in vSphere, vCenter Server, Active Directory, and other components of
your infrastructure to optimize the performance, availability, and reliability of View Composer.
Configuring the vSphere Environment for View Composer
To support View Composer, you should follow certain best practices when you install and configure vCenter
Server, ESX, and other vSphere components.
These best practices let View Composer work efficiently in the vSphere environment.
After you create the path and folder information for linked-clone virtual machines, do not change the
n
information in vCenter Server. Instead, use View Administrator to change the folder information.
If you change this information in vCenter Server, View Manager cannot successfully look up the virtual
machines in vCenter Server.
If you create more than 120 virtual machines as linked-clone desktops, edit the vSwitch settings on the
n
ESX host to increase the number of ports that are used for the virtual machines. By default, ESX is
configured for 120 ports.
When you deploy linked-clone desktops in a resource pool, make sure that your vSphere environment
n
has enough CPU and memory to host the number of desktops that you require. Use vSphere Client to
monitor CPU and memory usage in resource pools.
A cluster can contain at most eight ESX hosts. In a large View Composer environment, you might have to
n
configure many eight-host clusters.
Use vSphere DRS. DRS efficiently distributes linked-clone virtual machines among your hosts.
n
N
Storage vMotion is not supported for linked-clone desktops.
OTE
Additional Best Practices for View Composer
To make sure that View Composer works efficiently, check that your dynamic name service (DNS) operates
correctly, and run antivirus software scans at staggered times.
By making sure that DNS resolution operates correctly, you can overcome intermittent issues caused by DNS
errors. The View Composer service relies on dynamic name resolution to communicate with other computers.
To test DNS operation, ping the Active Directory and View Connection Server computers by name.
If you stagger the run times for your antivirus software, performance of the linked-clone desktops is not
affected. If the antivirus software runs in all linked clones at the same time, excessive I/O operations per second
(IOPS) occur in your storage subsystem. This excessive activity can affect performance of the linked-clone
desktops.
36
VMware, Inc.

Advertisement

Table of Contents
loading

This manual is also suitable for:

View composer 2.5

Table of Contents