VMware THIN4-CL-C Deployment Guide - Page 28

Application Sync, SBMerge, Packaging Updates and Modifications, Deploying Updates

Page 28 highlights

update component pieces in separate ThinApp packages rather than using Setup Capture to package all needed components into a single executable. Application Sync The Application Sync feature is a setting that initiates the pull of a differential update package from a central http web service or UNC location. The interval for polling for updates and the location of the http service or fileshare is configurable along with other settings in the Package.ini file. SBMerge The SBMerge.exe utility allows the administrator to merge run-time changes from an existing sandbox into any project directory of a captured application. The virtualized application package can then be rebuilt and distributed to end users incorporating the changes from the SBMerge process. Procedural Discussion Packaging Updates and Modifications There are three methods for capturing and deploying updates. Choose the method most appropriate for the update you wish to deploy.  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 configuration 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, first launch the virtualized application onto a clean workstation. Then run the update, which will place the new files, registry, and configuration 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 files to include changes, and editing the package.ini file to change configuration settings. Use this method when you definitively know the files 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 file to incorporate the changes. Deploying Updates Once the applications updates have been incorporated into a package there are three methods for deployment. When choosing which method is best it is important to consider the following questions: 28

  • 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

update component pieces in separate ThinApp packages rather than using Setup Capture to
package all needed components into a single executable.
Application Sync
The Application Sync feature is a setting that initiates the pull of a differential update package
from a central http web service or UNC location.
The interval for polling for updates and the
location of the http service or fileshare is configurable along with other settings in the Package.ini
file.
SBMerge
The SBMerge.exe utility allows the administrator to merge run-time changes from an existing
sandbox into any project directory of a captured application.
The virtualized application
package
can then be rebuilt and distributed to end users incorporating the changes from the SBMerge
process.
Procedural Discussion
Packaging Updates and Modifications
There are three methods for capturing and deploying updates. Choose the method most
appropriate for the update you wish to deploy.
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 configuration 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, first launch the virtualized application onto a clean workstation.
Then run the update, which will place the new files, registry, and configuration 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 files to include changes,
and editing the package.ini file to change configuration settings. Use this method when you
definitively know the files 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 file to incorporate the changes.
Deploying Updates
Once the applications updates have been incorporated into a
package
there are three methods
for deployment. When choosing which method is best it is important to consider the following
questions:
28