VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE, Manual

Page: 35 / 146

VMware, Inc. 35
Chapter 2 Capturing Applications
5 If ThinApp Converter finds a single .mst file, it runs that file and adds the necessary silent installation
switches.
6 If ThinApp Converter finds a single .msi file, it runs that file and adds the necessary silent installation
switches.
If none of the steps enable ThinApp Converter to find a correct installation command, the subdirectory is
skipped. A warning is logged in the log file.
You must remove all network connections to the file server reference in the INI file from the host on which you
run ThinApp Converter, to prevent conflict between user credentials.
PackageIniOverrideFile
Specify the file path to the global Package.ini override file.
This optional parameter enables you to specify a global override file for Package.ini that is generated for
each ThinApp project. The values in the override file are merged into Package.ini in the ThinApp project
that is generated for each application.
Global overrides are useful when you have a global policy setting, for example, PermittedGroup in
Package.ini .
A Package.ini override file is formatted like a standard Windows INI file. You can add INI parameters and
values that are relevant to the Package.ini file.
The path is relative to the application installer’s network share. Using the example for specifying the network
shares for the application installers and ThinApp projects, if you specify
PackageIniOverrideFile=override.ini , ThinApp Converter will try to find the file under
\\AppInstallerServer\AppInstaller . You can provide a more explicit value by using predefined
variables. For more information, see “Predefined Environment Variables” on page 37.
You can specify a Package.ini file for each application. This process is described as part of the
[AppSettings: AppName ] section.
ExclusionList
Specify a comma ‐ or semicolon ‐ separated list of application directories that ThinApp will skip when searching
for application installers.
The list is case insensitive.
You can specify wildcards for DOS ‐ style file names. For example, Microsoft*. ? and * are supported.
Example
Following is an example of an exclusion specification using a wildcard.
[Settings]
ExclusionList=App?.old;FireFox1.0
ProjectPostProcessingCommand
Specify the file path to the project post processing command.
The file path is relative to the application installer’s network share. Using the example for specifying the
network shares for the application installers and ThinApp projects, if you specify
ProjectPostProcessingCommand=addscript.bat , ThinApp Converter will try to find the file under
\\AppInstallerServer\AppInstaller . You can provide a more explicit value by using predefined
variables. For more information, see “Predefined Environment Variables” on page 37.
StopOnError
Specify whether ThinApp Converter should stop converting an application if it encounters an error, or
continue with the other applications. The default value is false .