7.0

n
Use floating assignment so that users log in to any available desktop. This setting reduces the number
of desktops required if everyone does not need to be logged in at the same time.
n
Create instant-clone or View Composer linked-clone desktops so that desktops share the same base
image and use less storage space in the datacenter than full virtual machines.
n
For View Composer desktop pools, determine what action, if any, to take when users log off. Disks
grow over time. You can conserve disk space by refreshing the desktop to its original state when users
log off. You can also set a schedule for periodically refreshing desktops. For example, you can schedule
desktops to refresh daily, weekly, or monthly.
n
For instant clone desktop pools, View automatically deletes the instant clone whenever a user logs out.
A new instant clone is created and ready for the next user to log in, thus effectively refreshing the
desktop on every log out.
n
If applicable, and if you use View Composer linked-clone pools, consider storing desktops on local ESXi
data stores. This strategy can offer advantages such as inexpensive hardware, fast virtual-machine
provisioning, high-performance power operations, and simple management. For a list of the limitations,
see “Storing View Composer Linked Clones on Local Datastores,” on page 248. Instant clone pools are
not supported on local data stores.
NOTE For information about other types of storage options, see Chapter 16, “Reducing and Managing
Storage Requirements,” on page 233.
n
Use the Persona Management feature so that users always have their preferred desktop appearance and
application settings, as with Windows user profiles. If you do not have the desktops set to be refreshed
or deleted at logoff, you can configure the persona to be removed at logoff.
IMPORTANT View Persona Management facilitates implementing a floating-assignment pool for those users
who want to retain settings between sessions. Previously, one of the limitations of floating-assignment
desktops was that when end users logged off, they lost all their configuration settings and any data stored in
the remote desktop.
Each time end users logged on, their desktop background was set to the default wallpaper, and they would
have to configure each application's preferences again. With View Persona Management, an end user of a
floating-assignment desktop cannot tell the difference between their session and a session on a dedicated-
assignment desktop.
Pools for Knowledge Workers and Power Users
Knowledge workers must be able to create complex documents and have them persist on the desktop.
Power users must be able to install their own applications and have them persist. Depending on the nature
and amount of personal data that must be retained, the desktop can be stateful or stateless.
For knowledge workers who do not need user-installed applications except for temporary use, you can
create stateless desktop images and save all their personal data outside of the virtual machine, on a file
server or in an application database. For other knowledge workers and for power users, you can create
stateful desktop images. Use the following pool settings:
n
Some power users and knowledge workers, such as accountants, sales managers, marketing research
analysts, might need to log into the same desktop every time. Create dedicated assignment pools for
them.
n
Use the Persona Management feature so that users always have their preferred desktop appearance and
application settings, as with Windows user profiles.
n
Use vStorage thin provisioning so that at first, each desktop uses only as much storage space as the disk
needs for its initial operation.
Setting Up Desktop and Application Pools in View
12 VMware, Inc.