VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE Manuale Utente Scaricare il pdf (Pagina 21)

VMware ThinApp

R E V I E W E R ’ S G U I D E / 2 1

Recapture

Recapture simply means going through the setup capture process again for the purpose of incorporating the

updates in between the Setup Capture pre-scan and post-scan snapshots. The result of this process is a new

package that has the new changes in conﬁguration or updates embedded. For example, your original package

was Microsoft OneNote. To create the updated package, simply install Microsoft OneNote and apply the most

recent Service Pack, then build a new application package.

Sandbox Merge

This method consolidates updates from a sandbox into an existing project directory. To use the Sandbox Merge

method, ﬁrst launch the virtualized application onto a clean workstation. Then run the update, which will place

the new ﬁles, registry, and conﬁguration changes into the sandbox of that workstation. Then use the sbmerge

utility provided by VMware to merge the changes from the sandbox of that capture machine into the existing

project directory, and then rebuild the package to incorporate the changes.

Post-Capture

The post-capture method of incorporating updates involves manually placing folders in the appropriate

directories of the capture, manually editing the registry ﬁles to include changes, and editing the package.ini ﬁle

to change conﬁguration settings. Use this method when you deﬁnitively know the ﬁles or registry changes that

you want to make. This method does not require the use of the Setup Capture process but you must re-build

the package using the build.bat ﬁle to incorporate the changes.

Deploying Updates

Once the applications updates have been incorporated into a package there are three methods for deployment.

Package Replacement

The package replacement method for updating application packages can be used for either streamed or

deployed execution mode. If you have created an updated package and have an administrative window where

no users will launch the applications then you can simply replace the original .exe based package with the

updated .exe. Make sure that the ﬁlename stays exactly the same: users depend on the shortcuts previously

created to launch the applications.

Side by Side Update

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, and

so on.

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

no change window required for the administrator. Users will execute the updated package as they launch the

applications and the original application packaged .exe directs them to the updated package.

AppSync

Application Sync provides updates to unmanaged machines that connect over networks with some degree

of latency. AppSync provides a mechanism for a dierential transfer over http to the endpoint, thus it is only

used for application packages in deployed execution mode. When an application starts, Application Sync can

query a Web server or ﬁleshare to see if an updated version of the package is available. If an update is available,

the dierences between the existing package and the new package are downloaded and used to construct an

updated version of the package. The end user must have the rights to modify the packages. If not, then the

1 2 ... 16 17 18 19 20 21 22 23

Commenti su questo manuale

Nessun commento

VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE Manuale Utente Pagina 21

Commenti su questo manuale

Prodotti e manuali riguardandi Networking VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE