Application Updates That the Administrator Triggers
ThinApp provides the AppSync.exe and sbmerge.exe utilities for administrators.
The AppSync.exe utility forces an Application Sync update on a client machine.
The sbmerge.exe utility make incremental updates to applications. For example, an administrator might use the utility to incorporate a plug-in for Firefox or to change the home page of a Web site to point to a different default site.
Forcing an Application Sync Update on Client Machines
You can use the AppSync command to force an Application Sync update on a client machine. You might want to update a package stored in a location where standard users do not have write access. In this situation, you cannot use Application Sync parameters to check for updates when an application starts because users do not have the required rights to update the package. You can schedule a daily AppSync.exe run under an account with sufficient privileges. The Application Sync parameters, such as AppSyncUpdateFrequency, in the Package.ini file do not affect the AppSync command.
To force an Application Sync update, use the AppSync <Application_Sync_URL> <executable_file_path> command. The value of the URL is the same as the Application Sync URL in the Package.ini file and the executable file path is the path to the executable file that requires the update.
Updating Applications with Runtime Changes
The sbmerge.exe utility merges runtime changes recorded in the application sandbox back into a ThinApp project. A typical workflow for this utility involves the following tasks:
Running the sbmerge.exe utility to merge registry and file system changes from the sandbox into the ThinApp project.
Merge Sandbox Changes with Firefox
This procedure for the sbmerge.exe utility uses Firefox 2.0.0.3 as an example of a captured application.
Merge sandbox changes with Firefox 2.0.0.3
1
2
Double-click the build.bat file in the captured application folder to rebuild the application package.
For example, a Firefox 2.0.0.3 path to the build.bat file might be C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox 2.0.0.3\build.bat.
3
Create a Thinstall directory in the bin directory for the sandbox location.
4
For example, change the home page.
5
For example, navigate to C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox 2.0.0.3.
6
From the command line, type the "C:\Program Files\VMware\VMware ThinApp\sbmerge" Print command.
ThinApp prints the changes that affected the sandbox folder when using the captured application.
7
From the command line, type the "C:\Program Files\VMware\VMware ThinApp\sbmerge" Apply command.
ThinApp empties the Thinstall folder and merges the sandbox changes with the application.
sbmerge.exe Commands
The sbmerge.exe Print command displays sandbox changes and does not make modifications to the sandbox or original project.
The sbmerge.exe Apply command merges changes from the sandbox with the original project. This command updates the project registry and file system to reflect changes and deletes the sandbox directory.
Usage
"C:\Program Files\VMware\VMware ThinApp\sbmerge" Print [<optional_parameters>]
"C:\Program Files\VMware\VMware ThinApp\sbmerge" Apply [<optional_parameters>]
Optional Parameters
The optional sbmerge.exe parameters specify project and sandbox paths and block progress messages and merging of sandbox files.
If you start the sbmerge.exe command from a location other than the application project folder, use the absolute or relative path to the project directory using the -ProjectDir <project_path> parameter. A sample command is "C:\Program Files\VMware\VMware ThinApp\sbmerge" Print ProjectDir "C:\<project_folder_path>"".
If you use a custom location for the sandbox, use the SandboxDir <sandbox_path> parameter to specify the location.
You can specify a .ini file to determine the content for exclusion. This file contains separate sections to specify files, such as the FileSystemIgnoreList and the RegistryIgnoreList.
The sbmerge.exe utility uses the snapshot.ini file in the ThinApp installation folder by default to exclude certain content from the merge process. This option enables you to specify another .ini file to ensure the additional exclusion of content.