
Page 18
o Individual Users: Some applications may be restricted to a small number of users
due to licensing or security restrictions. For example, access to a CAD application
may be restricted to a small number of employees within the Design Team.
Workload: Collecting application workload requirements will allow the virtualization
infrastructure to be sized and an appropriate application delivery model to be selected. For
example, resource intensive applications will not be delivered via a Hosted Shared Desktop
because there is limited control over how the resources are shared between users. There are
three classifications available for “Workload” in the User Assessment Worksheet:
If the application uses more than 1200MHz+ of available processor resources (50% of
a 2.4GHz CPU) or 1GB+ of RAM then it should be classified as “Resource Intensive”.
If the application is graphically intensive, certain delivery models may be more
appropriate than others. For example, XenApp supports HDX 3D which offers GPU
acceleration for DirectX only while XenDesktop supports HDX 3D Pro which offers
GPU acceleration for both DirectX and OpenGL. Therefore, Open GL based
applications, should be classified as “OpenGL”.
The application is not resource intensive and does not require OpenGL graphics.
Table 8: Application Workload Characteristics
Business: Do not complete. This section of the worksheet will be completed during the
Application Assessment, once the application list has been completed.
Compatibility: Do not complete. This section of the worksheet will be completed during the
Application Assessment, once the application list has been completed.
To save time and effort, the remaining items in the Application Assessment worksheet will be
completed during the Application Assessment once the rationalization process has been completed.
Capabilities Assessment
The information captured during the Capabilities Assessment will be used to achieve the following
objectives:
1. Identify Risks: Like traditional desktops, desktop virtualization is dependent on a wide range
of supporting technologies, including storage, networking, directory services and applications.
In many cases, issues reported with virtual desktops are a symptom rather than a cause. For
example, slow performance and disconnected sessions are more often caused by periods of
high-latency than a desktop specific issue. Therefore, a desktop virtualization project is an
excellent opportunity to review an organization’s existing infrastructure to ensure that it
provides a good solid foundation upon which the VDI environment can be built. Any risks
identified should be reported to the project manager so that they can be addressed
appropriately.
2. Create Roadmap: The Capabilities Assessment provides the project team with a detailed
understanding of the existing environment so that they can estimate implementation time for
each user group and prioritize the implementation order.
3. Virtual Desktop Design: Provide the project team with detailed information on the current
state of the environment so that they can successfully integrate the new virtual desktop
solution. The Capabilities Assessment should also determine whether existing infrastructure
components can be leveraged or whether new infrastructure needs to be purchased, for
example shared storage and virtualization technologies.