VMware View ThinApp Integration

VMware
View

4
and
ThinApp
Integration Guide
I NT EGRAT I ON GUI DE
VMware View 4 and ThinApp
Integration Guide
I NT ERGRAT I ON GUI DE / 2
Table of Contents
Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction: The Composite Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Conceptual Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Packaging and Updating Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
VMware View Composer Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Scenario 1: Persistent Desktop with User Data Disk Conguration . . . . . . . . . . . . . . . 16
Scenario 2: Non-Persistent Desktop with Active Directory Conguration . . . . . . . . . 20
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
About the Authors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Integration Guide
I NT EGRAT I ON GUI DE / 3
Abstract
This guide describes the integration of VMware View and ThinApp and reviews the concepts of design, use case
development, and specic conguration scenarios.
Introduction: The Composite Desktop
The composite desktop describes the combination of a stateless operating system with user driven stateful
application settings, user identity, preferences, and data. By integrating VMware View 4 and ThinApp, IT
organizations can benet from an easily managed and scalable desktop, while providing end-users with
additional exibility and mobility and the same personalized experience they enjoyed with a physical desktop.
VMware View Premier Edition makes the stateless desktop an achievable and deliverable solution, which IT can
deliver and manage as a Service (DaaS).
Desktop and Application Virtualization working together
Desktop virtualization oers signicant benets of increased density and reduced scope of management for
IT, making it feasible to deliver hundreds and thousands of desktops based on a small number of images that
can be updated routinely without downtime or costly distribution mechanisms. Application virtualization
complements this larger desktop economy of scale by abstracting the application set and user customizations
from the highly standardized desktop instance. Applications become containers that are executed rather than
burdens to install, congure, and maintain. The desktop operating system becomes a stateless disposable
platform to execute virtualized applications and provide a personalized experience to the end user.
Benets Overview
Desktop Virtualization
VMware View 4 is the leading desktop virtualization solution built for delivering desktops as a managed
servicefrom the platform to the protocol. This solution lets enterprise IT manage operating systems,
applications, and user persona independently of each other. VMware View 4 simplies desktop management,
reduces desktop operational costs, and increases control for IT while providing end users with exible access,
creating a superior desktop experience for end usersover any network.
Benets:
S|no||edye:ca|ab|ede:|oonanaqenen
PedJcedoa|co:ode:|ooovner:||obyoercen
AJonaedde:|ooorov|:|on|nqand|naqenanaqenen
SJoer|orendJ:erexoer|enceand:a|:ac|on
|J:|ne::con|nJ|yandd|:a:errecoveryor|ede:|oo
PedJcedcarbonooor|nandenerqyco::
Integration Guide
Application Virtualization
VMware ThinApp is an agentless application virtualization solution that allows IT organizations to provide
applications to end users without managing the complexity of application conicts and prerequisites or
operating system dependencies. VMware ThinApp technology decouples the application from the operating
system, providing exibility, portability, and isolation. VMware ThinApp plugs directly into existing IT tools and
processes, enabling corporate IT organizations and ISVs to deliver encapsulated application containers across a
variety of operating systems without complex conguration and installation requirements.
Benets:
oercenaqen|e::aoo||ca|onv|rJa||.a|on|nyoJrde:|ooenv|ronnen
|||n|naeaoo||ca|oncon|c:andredJce:Jooorco::
PedJceeneror|:eaoo||ca|ondeo|oynenco::and|norovede||very|ne
Acce|eraeand:|no||yaoo||ca|ondeo|oynenJodae:andoac|e:v||oJd|:rJo|nqendJ:er:
|everaqeex|:|nq|nra:rJcJreandde:|oonanaqenenoo|:
|oc|dovnendoo|n|C:v||oJre:r|c|nq|eJ:eocr||ca|aoo||ca|on:
|eo|oyoorab|eaoo||ca|on:ov|rJa||yany|Co|y:|ca|andv|rJa|||nc||enorUS|:|c|
Conceptual Discussion
A conceptual discussion of deployment considerations is necessary at this point, before proceeding into the
specics of integration. The following topics address whether to stream or deploy virtualized applications and
the method of integrating those applications into the desktop operating system. The concept of persistence
is important because it has an eect on the ability of the Operating System and the applications to maintain
customizations made by the users which results in greater end user satisfaction. Packaging considerations for
VMware ThinApp are also discussed because some deployment related conguration will be embedded during
the packaging process prior to deployment.
Determining the Execution Mode
VMware ThinApp allows IT organizations to determine whether to use streaming or deployed execution mode
or to adopt a hybrid approach that lets them manage a standard set of applications centrally while distributing
others in deployed mode. The same virtualized application packages can be used for either execution mode.
The decision to either distribute the packages into the View desktops or stream them from a central network
share can be made on an application-by-application basis.
Deployment into the desktop instance provides more predictable performance because all execution is local,
but it requires application packages to be updated in the VMware View desktop and will have a storage
footprint in the virtual machine. Providing applications via streaming mode makes greater demands on the
network and can aect performance, but it allows applications to be updated with greater eciency due to the
one-to-many model of streaming mode, and there is no disk footprint within the View desktop.
Integration Guide
A cursory review of the benefits of both execution modes follows:
Streaming Execution mode allows the application to be stored centrally and accessed by multiple users.
This one-to-many model provides centralized deployment and update of an application package to multiple
end users for execution via a Windows desktop shortcut. The user launches the application from the central
network location where the application resides and streams data as needed while the application is in use.
The streaming method operates without storing the application in the local disk of the operating system, but
reoJ|re:a|ANba:edconnec|ono|e:rean|nq|oca|onoraoo||ca|on|aJnc|andexecJ|onSee|e
VMware ThinApp Streaming Information Guide for more detail.
Deployed Execution mode distributes the virtualized application packages to the VMware View desktops
local le system. In this distributed model, each client device receives and executes the package locally and
therefore can run the application regardless of network connectivity. Application performance is not subject
to network performance because execution is local. IT organizations can leverage an existing software
distribution system for deployed mode.
Desktop Persistence
Desktop persistence allows users to customize their VMware View desktop and maintain those settings for a
personalized desktop. Persistent desktops are assigned to individual users and remain so assigned until an
administrator makes a change. Administrators should use persistent desktops for users who want to customize
their desktops and maintain a one to one relationship between that instance of the operating system and that
endJ:erNonoer:|:ende:|oo:area||ocaedoJ:er:enoorar||yandJ:edon|yor|ecJrren:e::|on
Administrators can specify that users are routed either to the next available non-persistent desktop or that the
desktop is destroyed after the user logs o.
Nonoer:|:ende:|oo:a||ov:|eadn|n|:raoroJ|||.ea:ae|e::ooera|nq:y:en|naqeandd|:oo:e
of it after one user, thus maintaining the pristine operating system image and standardization for all users.
The combination of non-persistent desktops with application and prole virtualization provides the most
ecient administration model while providing consistent user personalization.
The User Persona
The user persona is the combination of application settings, the user prole, and user data. The ability to abstract
these components of the user experience from the operating system and re-apply them allows IT the benet of
managing a standardized desktop and the ability to deliver a personalized experience for the end user.
UserProfi|e
T|e\|ndov:U:er|ro||econa|n:nany:e|nq:|acJ:on|.e|ede:|oo|oo|andee|a:ve||a:J:er
:oec||caoo||ca|on:e|nq:T|eU:er|ro||ev|||bydeaJ||oJ:e|e:oec||caoo||ca|on:e|nq:ron
both virtualized and natively installed applications.
App|icationSettings
The Application Data location contains the sandbox, located in the users profile by default, to store
runtime changes to the virtualized applications registry, folders, and files. This location houses the
information that gives users a persistent application experience for toolbar settings and customized
options within virtualized applications.
HyDocumentsoranyuserdata|ocation
Ped|rec|ono||:|oca|ona||ov:orJ:erdaaobenanaqed:eoarae|yron|ede:|ooooera|nq
system. Virtualized and natively installed applications default to saving user data in My Documents.
Integration Guide
The collection of registry entries and les that represent the previously-described components are collectively
reerredoa:|eJ:er:oer:onaand|||J:raed|n||qJre
!"#$%&'(
)$"#(*'+'(
,--./0'+/%&(
1"++/&2$(
)$"#(!#%3/."(
Figure 1. User Persona
Methods for Providing Persistence
There are two primary methods to providing persistence of the user persona: Active Directorybased
conqJra|onandV|vareV|evConoo:erU:er|aa||:|:|o|nec|an|:n:orov|dea:a|c|oca|ono:ore
o prole and application settings between dierent instances of the VMware View desktop.
ActiveDirectorybasedconfiguration
Organizations with a well-managed group policy implementation may prefer to utilize those processes
and tools to provide persistence. The primary advantage of using Active Directory is that it is a dynamic
mechanism that can apply different settings based on different VMware View desktop pools or users.
The location for storage of this data is typically network based and easy to backup and manage.
Administrators can provide accessibility to the user data and user profile registry settings to additional
|oca|on::Jc|a:aPenoe|e:|oo:erv|ce:ba:edaoo||ca|onoro|y:|ca|de:|ooT|e:andardaooroac|
to Windows roaming profiles can be used in conjunction with group policy based folder redirection.
VHwareViewComposerUserDataDiskUDD
U:er|aa||:|:are:oec||cv|rJa|d|:|||e:|aareaac|edo|n:ance:o|eV|vareV|ev
desktop for storing user profiles and the My Documents user data location. The primary advantage
of this mechanism is that the redirection of persistent information is automatic. Administrators have
anaJonaednec|an|:nocreaeU||:v|enorov|:|on|nqV|evde:|oo:T|eU:er|aa||:||:
implemented as a separate virtual disk, which will store information for multiple users of that desktop.
T||:creae:are|a|on:||obeveen|eU||and|e|n:anceo|ede:|ooooera|nq:y:en
Integration Guide
Application Registration
The integration of virtualized applications into the desktop operating system occurs through the Application
Peq|:ra|onoroce::Aoo||ca|onreq|:ra|oncreae::|orcJ:on|ede:|oocreae:|eyoea::oc|a|on:
andenr|e:|n|eAddPenoveoroqran:aoo|eo|eConro||ane|byreq|:er|nqon|y|eT||nAoooac|aqe:
for which the user has been authorized. Figure 2 and Figure 3 show the state of the desktop and application
integration before and after application registration.
Figure 2. Before Application Registration
Figure 3. After Application Registration
Integration Guide
Utilizing ThinReg for Application Registration
The Thinreg utility automates the registration process and can be run from a login script, a local script, or a
command line. Since the registration process can enumerate which users have access to application packages,
the Thinreg process can be run against an entire directory of application packages; however, it only registers the
applications to which the user is entitled. Two common methods of implementation are described briey below.
LoginScriptbasedImp|ementation
The Thinreg executable can be incorporated into an existing login script with standard methods such as
.bat, WSH, KIX, or vbScript. See example below:
%logonserver%\netlogon\thinreg.exe /Q \\company.com\applications\*.exe
Loca|ScriptviaRegistryRunKeyorLogonScript
IT organizations can choose to implement the application registration process locally on the workstations
|n:eado|ncoroora|nq||no|e|oq|n:cr|oT|ePJn|eyo|ereq|:rycanca|||eT||nreqexe||eora
C|OcanbeJ:edorJnron|oqonooerorn|eaoo||ca|onreq|:ra|onJnc|on||ac|nq|eT||nreq
exe|n|e\|ndov:d|recory:|no|||e:|eT||nPeqexecJ|ono|e:cr|oandreoJ|re:no||nqnore
|an|eT||nPeqexecJab|eoJnc|on
Packaging and Updating Considerations
Role based Application Access
Administrators can use Active Directory groups to control access to virtualized applications. The setup capture
process allows administrators to enumerate and assign Active Directory groups. Those assignments are
embedded into the package during the build process. This process populates the PermittedGroups parameter
in the Package.ini and restricts usage of a package to a specic set of Active Directory users. Administrators
can optionally customize the error message to users if they are not allowed to launch the application. For a
desktop that is oine, the PermittedGroups function utilizes cached credentials to determine whether the user
has permission to launch the application.
AppLink
Aoo||ca|on||n||:aV|vareT||nAooeaJre|aa||ov:|eadn|n|:raorobJ||dre|a|on:||o:beveen
packages, creating modular packages that link together instead of larger packages that are more dicult to
d|:r|bJeandJodaeAdn|n|:raor:canJ:eAoo||ca|on||n|ocreaere|a|on:||o:beveen|oca|orrenoe
application packages containing components or dependencies. Administrator can congure the originating
application package to look rst in a local directory and then in a remote directory if the required or optional
component cannot be found. To provide a logical link to the remote directory you can use a domain-based DFS
nane:oaceor:andardUNCba:edoa|Aoo||ca|on||n|orov|de:|eo||ov|nqJnc|on:
||n|:rJn|neconoonen::Jc|a:N|T.P|orO||Cdr|ver:v||deoendenaoo||ca|on:|orexano|e
yoJcan||n|N|Toanaoo||ca|oneven||e|oca|nac||neor|eaoo||ca|ondoe:noa||ovor|e
|n:a||a|onoN|Tora|ready|a:ad|erenver:|onoN|T
A||ov:adn|n|:raor:odeo|oyaoo||ca|on:oec|cconoonen:ando|Jq|n::eoarae|yron|eba:e
aoo||ca|on|orexano|eyoJn|q|:eoaraeAdobe||a:|||ayerorAdobePeaderronaba:e||reox
application and link the components.
Integration Guide
Compression
VMware ThinApp provides the option of using compression to reduce the storage footprint of the application
packages. Applications launched in streaming mode request only the les and registry necessary to perform
the specic application function, which means that the package is never streamed in its entirety. With
compression enabled, the quantity of data transferred across the network is greatly reduced by an average
ooercenU|||.e||:Jnc|onby:oec|y|nq|econore::|ona:oo|on|n|eoac|aqe|n|beore|e
build process. Existing application packages can be rebuilt with compression anytime by utilizing the project
directories created during the setup capture process. For this reason, it is recommended to use compression for
packages that will be run in streamed execution mode.
SidebySideUpdate
The side by side method for updating application packages can be used for either streamed or deployed
execution mode. There is no requirement for application downtime. This method works by placing the new
application package in the same directory as the original application package and incrementing the lename
extension to an integer number. Subsequent updates can be placed in the directories with extensions .2, .3, etc.
The implementation of this update strategy follows a simple process. When a user launches an application
from a shortcut that references the original .exe, logic built into the package automatically checks for identical
package lenames with a numeric extension in the same directory. If an updated package, such as Mozilla
Firefox.2, is found, the application launches using the le with the highest numeric extension. Always keep
the original .exe that is referenced by the shortcut in place as it is a necessary pointer for the application to
launch with or without updated packages. There is no downtime for the users with this method of update and
noc|anqev|ndovreoJ|redor|eadn|n|:raorU:er:v|||execJe|eJodaedpackage as they launch the
applications and the original application packaged .exe directs them to the updated package.
AppSyncUpdate
The Application Sync feature is a setting that initiates the pull of a dierential update package from a central
|oveb:erv|ceorUNC|oca|onT|e|nerva|oroo|||nqorJodae:and|e|oca|ono|e|o:erv|ceor
leshare is congurable along with other settings in the Package.ini le. Refer to the Additional Resources
section for further detail on congurations.
VMware View Composer Integration
VHwareViewComposerConsiderations
V|vareV|evConoo:erorov|de:|ecaoab|||yocreaede:|oo|naqe:rao|d|yronaoarenor:andard
v|rJa|nac||ne|naqenadd||onV|vareV|evConoo:erredJce:|eoa|anoJno:oraqereoJ|red
to deploy virtual desktop images (see Figure 4). By leveraging linked clones, it introduces a streamlined
process for upgrading patches across multiple desktops by simply applying the patch to the parent image and
recomposing the linked clones.
V|vareV|evConoo:era|:oorov|de:|eab|||yo:eoaraeJ:erdaaandoro|e:e|nq:a||ov|nq:ovare
updates and patches to be applied to the parent image and inherited by the linked clones. After a linked clone
has been updated, the users personal settings from the user data disk are also applied to the updated image.
Integration Guide
I NT EGRAT I ON GUI DE / 1 0
IntegrationofVHwareViewComposerand1hinApp
T|ereare|reecon:|dera|on:or|neqra|onoV|vareV|evConoo:erandT||nAoo|e|oca|onoT||nAoo
packages, updates for the operating system and ThinApp packages, and the location for storage of the
application sandbox.
T|erearebene:odeo|oy|nqaoo||ca|on:oac|aqe:|no|eV|vareV|evConoo:erba:e|naqeV|vareV|ev
Conoo:erorov|de:a:rean||nednec|an|:norere:|andreconoo:e|eba:eooera|nq:y:env||c|can
also be used as an update vehicle for ThinApp application packages. This operation would allow for a mass update
of application packages along with a desktop recompose operation. The only caveat of this approach is that the
administrator will be combining operating system recompose events with application updates. Administrators
should compare the frequency of application updates with that of operating system updates and determine the
aooroor|ae|oca|onorT||nAoooac|aqe:T||nAoooac|aqe:cana|:obe|ocaedon|eU:er|aa||:|:bJ
will require a software distribution solution for initial delivery to each individual user data disk. Once the package
is distributed, AppSync can be used within the package as a pull mechanism to perform subsequent updates.
A compromise can be achieved by using streaming mode for frequently updated applications while deploying less
frequently updated applications into the operating system image or user data disk.
\|enJ:ed|nconJnc|onv||V|vareV|evConoo:eradn|n|:raor:|ave|eoo|onoJ|||.|nqU:er
Data Disks to logically separate application and user storage from the operating system. By default, VMware
ThinApp places the application sandbox in whatever location the %AppData% variable resolves to in the
ooera|nq:y:enU:er|aa||:|:aJona|ca||yrece|ve|edynan|cc|anqe:o|eaoo||ca|on:and
user-specic settings stored in the sandbox and maintain these through a refresh of the operating system.
Administrators can choose to redirect My Documents to a storage location or allow that user data to also
be|oJ:ed|n|eU:er|aa||:|A:d|:cJ::ed|n|eorev|oJ::ec|onMethods for Providing Persistence,
Torqan|.a|on:|ave|ec|o|ceoJ:|nq|eV|evConoo:erU:er|aa||:|:oranAc|ve||recoryba:ed
mechanism of folder redirection or roaming proles for the location of application settings.
Figure 4. VMware View Composer
Integration Guide
Integration Scenarios
This section reviews the components utilized to build two scenarios that illustrate the concepts of integration
between VMware View and ThinApp. After a review of the components and requirements, the tasks with
:creen:|o:areorov|dedova||yoJ|roJq||eoroce::o|neqra|onCon:J||eVMware View Evaluators
Guidea:ve||a:|edocJnen:||:ed|n|ePe:oJrce::ec|onor:oec|c:on|n:a||a|onandconqJra|on
of the base VMware View infrastructure and for details on packages and deployment of application with
VMware ThinApp.
VHwareViewand1hinAppComponentsCverview
VMware View and ThinApp integration utilizes the following infrastructure and components:
V|evConnec|onServer|n:a||ed|na\|ndov:Server:y:en|a|::eoaraeron|eV|rJa|Cener
V|evAqen|n:a||ed|nv|rJa|de:|ooX|\|ndov:orV|:ade:|oo:
V|evC||en|n:a||eda|eendoo|ndev|ceT||nc||en|oca||aoooorde:|oo:
V|evConoo:er|n:a||ed|nV|rJa|Ceneror||n|edc|oneorov|:|on|nqJ:e
T||nAooAoo||ca|onPeoo:|oryv||c||:aUNCba:ed|oca|on
T||nAooAoo||ca|on|ac|aqe:creaedv||SeJoCaoJreoo|
T||nAooT||nPeqoo|J|||.ed|n|oqon:cr|o
On the infrastructure side, the following components are utilized:
V|rJa|CenerV|varevCener
SO|Server
Ac|ve||recory
Integration Guide
1askbasedIntegrationScenarios
The remainder of this document will provide the necessary setup and conguration information to congure
the following common scenarios which illustrate the combination of operating system, application, and user
prole virtualization to deliver a user driven experience that is easily manageable for the IT organization.
A|er:|:enV|ev|e:|oo|oo|J|||.|nqV|evConoo:erU:er|aa||:|:
ANon|er:|:enV|ev|e:|oo|oo|J|||.|nqAc|ve||recoryba:edconqJra|on

I NI TI AL SETUP REQUI REMENTS
CreaeanAc|ve||recory
OUoreac|Scenar|o

CreaeanAc|ve||recory
Group for each Scenario and
test user accounts.

Integration Guide
Creaed|recor|e:andAc|ve
Directory shares with the
appropriate permissions for the
following locations.
T|eT||nAoo:rean|nq
share that will house
virtualized applications that
are streamed at run-time to
View desktops. This share
:|oJ|dbePeadOn|yor
users to minimize
administrative support.
Ie. \\FileServer\ThinApps
2. The Proles share which
will house roaming proles.
Ie. \\FileServer\Proles
3. The Home share which will
|oJ:e|eU:er:|one
directory.
Ie. \\FileServer\Home

Integration Guide
Creae|eba:e
View Desktop VM.
Creaeandoo|n|.ea
desktop OS instance, which
is joined to your domain.
Creaead|recory|n|eC
to hold deployed ThinApp
packages and populate with
the virtualized application
oac|aqe:eCT||nAoo:
||ace|eT||nPeq|xe
J|||y|nC\|ndov::o
that the application
registration process can r
un locally. *This le is
included with the VMware
ThinApp installation les.
7. From inside the virtual
machine, open a command
oronoandrJn|oconq
release, then shutdown
VM and take a snapshot.
Ie. Base
8. Power On the VM and
install some Windows
updates and optionally
place additional ThinApp
oac|aqe:|n|e|oca|C
ThinApps directory.
PJn|oconqre|ea:e
then shutdown VM and
take an additional snapshot.
eUodae

Integration Guide
U:eanAc|ve||recoryC|O
to allow for automated
application registration of
ThinApp packages.
CreaeaV|S:cr|ov||c|
registers packages from
the remote and local
ThinApp package
locations.
Creae|eA|C|Oor|e
|oqon:cr|obybrov:|nq
o:e|ecPeq|:ervb:

CreaeT||nAoo|ac|aqe:
CreaenJ||o|eT||nAoo
packages to place in local
and remote directories.
See VMware ThinApp
documentation for
specics of the Setup
CaoJreoroce::
Creae|ncrenena|Jodae
packages to perform a
Side-by-Side update.
Ie. Mozilla FireFox, Mozilla
||re|ox
AJ|or|.e|eoac|aqe:
using AD groups to
illustrate role based access
to applications.
Integration Guide
Scenario 1: Persistent Desktop with
User Data Disk Conguration
This scenario will utilize a persistent desktop pool to illustrate application registration, the hybrid approach of
using streamed and deployed ThinApp packages, and redirection of application settings and user data via an
Active Directory based conguration. For detailed information about similar conguration options consult the
VMware ThinApp Reference Architecture.
Setup1asks
Scenar|ovor|:v|||eAc|ve||recoryOUv||c|v|||J:eaV|ev|er:|:en|e:|oo|oo|v||U:er|aa
Disk based conguration to provide persistence.
Note: V|varev|||beJ:|nqU:er|aa||:|:oorov|deoer:|:enceoU:er|ro|e:||ea:erenoveanyroan|nq
oro|e:e|nq:ron|eU:er:|ro|eTabbeorecon|nJ|nq
SCENARI O 1 PERSI STENT DESKTOP
CreaeaV|evAJonaed
|er:|:en|oo|v||aU:er
Data Disk.
Creaeanev|er:|:en|oo|
Ped|recJ:erdaaoa
separate disk.
C|oo:ead|:|dr|ve|eer

Integration Guide
Verify that the test user does
not have Active Directory
Poan|nq|ro|econqJred
and|o|derPed|rec|on|:no
congured.
C|ec|U:er:|ro|eTab|n
Ac|ve||recoryU:er:
object
C|ec|C|Oover|y|o|der
Ped|rec|on|:no
congured.

Integration Guide
|aJnc|V|ev|e:|ooC|ec|
U:er|aa||:|crea|on
C|ec||dr|ve
|aJnc|a
ThinApp package.
8. Verify a hidden
Application Data
directory D:\Documents
and Settings\username\
Application Data
Verify that the Application
:e|nq:|eU:er|ro|eand
U:erdaaarena|na|ned
between View Desktop OS
refresh operations.
|aJnc|aV|ev|e:|oo
|aJnc|aT||nAoo
application. (ie. Microsoft
Word) and make a change
to the application. (ie.
CJ:on|.eOJ|c|Acce::
Toolbar.)
|a|eac|anqeoaU:er
Prole setting such as
desktop background.
Creaeand:avea
document noting that the
location should default to
the My Documents
location now redirected to
|eU:er:|oned|recory

Integration Guide
|d|naqePeconoo:ev|||
allow you to choose a dierent
virtual machine snapshot.
Pere:|v|||a||ovyoJo
discard all changes that users
have made to the OS disk to
restore it to its initial state.
|aJnc|V|vareV|ev
Administrator 4 and select
the correct pool.
Se|ec|d|naqeC|oo:e
e||erPere:|oreJrn
|e|naqeo|e|a:e
:naoorPeconoo:eo
update the image to the
Uodae:nao:|o
Se|ecV|rJa||ac||ne:
Se|ecaooroor|ae
schedule for task to start.
C|oo:eoorceJ:er:o
log o or wait for users to
log o.

Oo|ona|yoJ
authorized the ThinApp
packages for specic AD
groups, remove a user
from a group to reect
role based access to
applications.
Oncecono|eed|aJnc|
the View Desktop to verify
updated image and
persistence of the users
customizations to
application settings, user
prole, and user data.
Integration Guide
Scenario 2: Non-Persistent Desktop with Active
Directory Conguration
T||::cenar|ov|||J|||.eaNon|er:|:ende:|ooooo|o|||J:raeaoo||ca|onreq|:ra|on|e|ybr|daooroac|
of using streamed and deployed ThinApp packages, and redirection of application settings and user data via
Ac|ve||recoryba:edconqJra|onANon|er:|:ende:|ooooo|na|na|n:nore|a|on:||obeveenaq|ven
J:erandaV|evde:|ooU:er::|no|yared|recedo|enexava||ab|ede:|ooTorqan|.a|on:can|everaqe
Non|er:|:ende:|ooora:|ba:edJ:er:orconqJre|ede:|ooorone|neJ:eand|ende|e|ono
maintain standardization of the operating system. For detailed information about similar conguration options
con:J||eV|vareT||nAooPeerenceArc||ecJre
SetUp1asks
Scenar|ovor|:v|||eAc|ve||recoryOUv||c|v|||J:eaV|evNon|er:|:en|oo|v||Ac|ve||recory
based conguration to provide persistence.
SCENARI O 2 NON-PERSI STENT DESKTOP
CreaeaV|evAJonaed
Non|er:|:en|e:|oo|oo|
using View Manager.

ConqJrePoan|nq|ro|e:
and Home directories utilizing
leshares created in the Initial
SeJoPeoJ|renen:
Add|||S|PV|P|ro|e:
to user prole properties in
Active Directory
Add|||S|PV|P|one
to user prole properties in
Active Directory.
Integration Guide
Edit AD GPO for Folder
Ped|rec|ono|y|ocJnen:
Folder to the users home
directory.
Edit AD GPO for Folder
Ped|rec|onoAoo||ca|on
Data to the users home
directory.

Integration Guide
|aJnc|V|ev|e:|ooand|oq
|na:U:erPev|everover|y
the application registration
process has integrated the
ThinApp Packages.
Ie. Verify FileType
A::oc|a|on:andConro|
|ane|AddPenove
entries
Test Applications.
|aJnc|a|oca|and
remote ThinApp.

Noenerne|xo|orer
and 8 running together
with no conicts.

Integration Guide
UodaeaT||nAoo
Package. (See Initial
SeJoPeoJ|renen:
See additional
documentation for specics
of Side-by-Side updating.
2. Add the updated Mozilla
||reoxoac|aqeo
|||S|PV|PT||nAoo:
Pe|aJnc||o.|||a||reox
and verify updated package.
Verify that the Application
:e|nq:|eU:er|ro|eand
U:erdaaarena|na|ned
between View Desktop OS
refresh operations.
|aJnc|aV|ev|e:|oo
noting the name of the
desktop.
|aJnc|aT||nAoo
application. (ie. Microsoft
Word)and make a change
to the application. (ie.
CJ:on|.eOJ|c|Acce::
Toolbar.)
|a|eac|anqeoaU:er
Prole setting such as
desktop background.
Creaeand:avea
document noting that the
location should default
to the My Documents
location now redirected to
|eU:er:|oned|recory

Integration Guide
8. (Optional) If you
authorized the ThinApp
packages for specic AD
groups, remove a user
from a group to reect
role based access to
applications.
9. Edit the image or choose
ooveroandde|ee
after rst use.
\ac||nV|rJa|Cener
as the virtual machines
are updated or
re-created.
|oqbac||nand:eea||
your changes from the
previous section
regarding application
settings, userprole,
and user data.
Conc|J:|onScenar|o|neqraedV|vareV|evandT||nAoov||Ac|ve||recoryU:|nqanonoer:|:en
v|rJa|nac||neor|ede:|ooandAc|ve||recoryPoan|nq|ro|e:and|o|derPed|rec|onoroer:|:ence|:
a way to incorporate new technologies like Virtual Desktops into your existing environment with little changes.
U:|nq|eec|n|oJe:|n|e:e:cenar|o:ora|ybr|do|evov|||br|nq|eadn|n|:ra|ono|ede:|ooo
being Stateless where the OS, applications and user persistence are managed as separate containers. This
allows for extremely exible, agile but very end-user friendly desktop. Administrators will be able to seamlessly
make changes to operating systems and applications without disrupting the end user experience.
Integration Guide
Conclusion
The previous task based scenarios are simple to congure but provide guidance on how to deliver a
personalized user experience in the desktop while increasing the eciency of managing the operating
:y:en|naqeAdn|n|:raor:canJ|||.e|eV|evConoo:erJnc|ona||yoreconoo:eoJodaeno
just the operating system but also the ThinApp packages as this provides further eciency into the process
of managing desktops. While these scenarios provide a mock-up of an initial environment, the design and
testing process should be driven by the specic use cases of your organization and the workow of your
IT department.
About the Authors
Aaron Black is a Senior Technical Marketing Manager at VMware, focusing primarily on developing technical
content to aid in the evaluation and implementation of VMware ThinApp technology. Aarons background
includes roles as a systems engineer and solutions consultant in the Technical Services organization. Before
o|n|nqV|vare|evor|eda:a:y:en:enq|neerv||C|r|xSy:en:|eadaec|n|ca|corooraeTeana
Sor|nandde:|qned:o|J|on:orcJ:oner:oC|o|ceSo|J|on:ao|a|nJnre:e||eroV|vareorodJc:
Paul Weiss is a Senior Systems Engineer at VMware working with Enterprise customers in the South East.
He has worked with VMware products for many years. He has worked as a VMware Specialist at a Premier
VMware Partner, a Senior Systems Architect with a primary focus on large Sun environments, and as a Sun
Cer|edn:rJcor|aJ||a:overyear:o|neror|:eTexoer|enceand|:cer|edv||nany:o|J|on:|||e
So|ar|:Ped|a|J:|ne::con|nJ|yandV|vare|aJ|a|:o:erved|n|eUSArnyoryear:and|:aCJ|
War veteran.
Integration Guide
VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com
Copyright 2009 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: VMW_09Q4_IG_ViewThinApp_EN_P26_R1
Resources
VMware ThinApp Deployment Guide
http://www.vmware.com/resources/techresources/1098
VMware ThinApp Streaming Information Guide
http://www.vmware.com/resources/techresources/10027
V|vareT||nAooPeerenceArc||ecJre
www.vmware.com/resources/techresources/10053
VMware ThinApp Blog
VMware ThinApp employees regularly post and participate on the VMware ThinApp blog site
http://blogs.vmware.com/thinapp/
VMware ThinApp Product Documentation
http://www.vmware.com/support/pubs/thinapp_pubs.html
VMware View Manager Evaluators Guide
www.vmware.com/resources/techresources/10082
V|vareV|evPeerenceArc||ecJre
http://www.vmware.com/les/pdf/resources/vmware-view-reference-architecture.pdf

VMware View ThinApp Integration

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

VMware View ThinApp Integration

Caricato da

Copyright:

Formati disponibili

VMware

Potrebbero piacerti anche