User`s guide

VMware ThinApp Reviewer’s Guide
REVIEWER’S GUIDE / 65
Package Replacement
The package replacement method for updating application packages can be used for either streaming or
deployed execution mode. If you have created an updated package and have a quiet window when no users
will launch the application, then you can simply replace the original .exe-based package with the updated .exe.
Make sure that the filename stays exactly the same: users depend on the shortcuts previously created to launch
applications.
Side-by-Side Update
The side-by-side method for updating application packages can be used for either streaming 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 changing the filename
extension from .exe to .1. Subsequent updates can be placed in the same directory and incremented 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 filenames with an integer extension in the same directory. If an updated package, such as Mozilla
Firefox.2, is found, the application launches using the file with the highest numeric extension. Always keep
the original .exe that is referenced by the shortcut in place because 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 launch the updated package as they restart
the application, and the original application packaged .exe directs them to the updated package.
AppSync
Application Sync provides updates to ThinApp packages on 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; therefore, it is only used for application packages in deployed execution mode. When an application
starts, Application Sync can query an update web server or update file share 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 local package. If not, then the appsync.exe utility can be run as a scheduled service
as a user with sucient rights to perform the update. The updated package is then used for future launches of
the application. Settings that configure the location for AppSync updates and detailed AppSync configurations
are contained in the Package.ini file.
Practice in Updating ThinApp Packages Using the Side-by-Side Method
The side-by-side method of updating is very ecient and provides a built-in fallback mechanism. The steps
below provide guidance on how to use the side-by-side method for packages on file shares; the same method
can also be used for local packages.
This video demonstrates the side-by-side update method:
3 – ThinApp SxS Updating.mp4

asaThinApppackagenamedMozilla FireFox.exe

builtasaThinApppackagenamedMozilla Firefox Update.exe
Copythetwopackagesintothesamedirectoryeitherlocallyoronafileshare

application
Mozilla FireFox Update.exetoMozilla
FireFox.1
