VMware THIN4-CL-C Deployment Guide - Page 7

Terminology, People and Process Considerations

Page 7 highlights

As virtualized applications are executed by end users, the dynamic application and user setting information is redirected into a storage location defined by the administrator, called the sandbox. Administrators can subsequently incorporate application updates and changes to configuration by a number of methods. These updates are rolled out to end users centrally as they launch the applications, deployed to end point systems via Active Directory group policy or alternative software deployment solutions, or provided via a centralized web service that will transfer a differential update. Applications run within VMware ThinApp containers cannot be tampered with because they are read-only and embedded into a compressed package. However, dynamic application configuration and user settings can easily be rolled back to the initial configuration for ease of support. Terminology ThinApp Streaming VMware ThinApp streaming has a unique meaning that describes the execution of an application rather than the delivery of the application. When a ThinApp packaged application is launched only the necessary blocks of data are streamed into memory for execution. This streamed execution occurs whether the package resides centrally on a file share, locally on the file system, or on a USB device. VMware ThinApp streaming does not require the local caching of files, instead it only streams into memory what is needed at that time to perform the application function. The amount streamed varies by application usage and depends on how many of the application functions are used and which dlls, registry, and files are needed for those functions. ThinApp streaming provides application files and registry settings to the end user based solely on the applications requests and regardless of the package size. For example, a very large application package that contains a suite of applications (but that is being used minimally) may stream the same amount of data as a small application that is subjected to heavy end user load. People and Process Considerations As with the implementation of any technology, it is critical to do the necessary planning, identify the appropriate skill sets, and integrate with existing processes. Practically speaking, implementation involves not only the initial deployment but also the ongoing maintenance and support structure for the entire lifecycle of the applications. In terms of planning, it is helpful to identify the major user communities and their application needs, then design your implementation accordingly. Different characteristics need to be considered for physical desktop, virtual desktop, and Terminal Services/Citrix based environments. One of the unique strengths of the VMware ThinApp solution is the portability of the technology and ease of integration into a wide array of environments. However, every organization is unique and has different objectives for implementing application virtualization. Equally important to process considerations is the commitment to leverage appropriate people to make a project successful. The following list identifies key skill sets recommended:  Application and Packaging Skills When packaging applications it is best to identify dependencies, update cycles, application errors, and custom files which are necessary for full functionality. Incorporating individuals familiar with custom applications will streamline the packaging process and help prevent unnecessary troubleshooting. Individuals who currently package applications can easily incorporate the VMware ThinApp setup capture into their existing processes and are often already aware of particular application requirements. 7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32

As virtualized applications are executed by end users, the dynamic application and user setting
information is redirected into a storage location defined by the administrator, called the
sandbox
.
Administrators can subsequently incorporate application updates and changes to configuration
by a number of methods.
These updates are rolled out to end users centrally as they launch the
applications, deployed to end point systems via Active Directory group policy or alternative
software deployment solutions, or provided via a centralized web service that will transfer a
differential update.
Applications run within VMware ThinApp containers cannot be tampered with
because they are read-only and embedded into a compressed
package
.
However, dynamic
application configuration and user settings can easily be rolled back to the initial configuration for
ease of support.
Terminology
ThinApp Streaming
VMware ThinApp streaming has a unique meaning that describes the execution of an application
rather than the delivery of the application.
When a ThinApp packaged application is launched
only the necessary blocks of data are streamed into memory for execution. This streamed
execution occurs whether the
package
resides centrally on a file share, locally on the file system, or
on a USB device. VMware ThinApp streaming does not require the local caching of files, instead it
only streams into memory what is needed at that time to perform the application function. The
amount streamed varies by application usage and depends on how many of the application
functions are used and which dlls, registry, and files are needed for those functions.
ThinApp
streaming provides application files and registry settings to the end user based solely on the
applications requests and regardless of the
package
size.
For example, a very large application
package
that contains a suite of applications (but that is being used minimally) may stream the
same amount of data as a small application that is subjected to heavy end user load.
People and Process Considerations
As with the implementation of any technology, it is critical to do the necessary planning, identify
the appropriate skill sets, and integrate with existing processes. Practically speaking,
implementation involves not only the initial deployment but also the ongoing maintenance and
support structure for the entire lifecycle of the applications. In terms of planning, it is helpful to
identify the major user communities and their application needs, then design your
implementation accordingly. Different characteristics need to be considered for physical desktop,
virtual desktop, and Terminal Services/Citrix based environments.
One of the unique strengths of the VMware ThinApp solution is the portability of the technology
and ease of integration into a wide array of environments. However, every organization is unique
and has different objectives for implementing application virtualization. Equally important to
process considerations is the commitment to leverage appropriate people to make a project
successful. The following list identifies key skill sets recommended:
Application and Packaging Skills
When packaging applications it is best to identify dependencies, update cycles, application
errors, and custom files which are necessary for full functionality. Incorporating individuals
familiar with custom applications will streamline the packaging process and help prevent
unnecessary troubleshooting. Individuals who currently package applications can easily
incorporate the VMware ThinApp setup capture into their existing processes and are often
already aware of particular application requirements.
7