4.7.3

Because a large number of desktop computers use Symantec AntiVirus, ThinApp enables applications to open
from a network share without incurring lengthy scan times. When the application runs from a network share
or removable disk, ThinApp creates a stub executable file in the directory that the CachePath parameter sets
on the local disk and restarts the application from this stub executable file. The stub executable file can load
the runtime from the large package and read the remainder of the application from its original location on the
network. Some AntiVirus applications perceive that the application is local, so does not scan the larger
executable file on the network share or removable disk.
Example: Modifying the NetRelaunch Parameter
This example shows how you can modify the NetRelaunch parameter for stronger initial startup performance.
Modify the parameter if your application is small or you know that Symantec AntiVirus is not installed on the
desktops on which you are deploying the application.
[BuildOptions]
NetRelaunch=0
RuntimeEULA Parameter
The RuntimeEULA parameter controls the End-User License Agreement display for the package. This parameter
addresses legacy EULA requirements. VMware does not require a runtime EULA for ThinApp packages.
NOTE Do not modify the value of this parameter.
Example: Default RuntimeEULA Value
This example shows how the RuntimeEULA parameter prevents the display of the End-User License Agreement.
[BuildOptions]
;Default: do not show an Eula
RuntimeEULA=0
VirtualComputerName Parameter
The VirtualComputerName parameter determines whether to rename the computer name, to avoid naming
conflicts between the capture process and the deployment process.
Applications can use the name of the computer on which they are installed, or connect to a database and use
the name of the computer in the connection string. Because the capture process is different from the deployment
process, captured applications that require a computer name must add the computer name to the virtual
package to ensure that the application can run on any machine.
ThinApp comments out the initial setting of the VirtualComputerName parameter. This parameter uses a string
that the GetComputerName and GetComputerNameEx API functions return in a virtual application.
Example: Including a Virtual Computer Name
This example shows how the VirtualComputerName parameter creates a second name for a computer named
LOCALHOST, which will be captured in the virtual application. The application uses the second name to
connect to a virtual machine. If the capture system lacks the LOCALHOST name, ThinApp comments out the
VirtualComputerName parameter.
;VirtualComputerName=<original_machine_name>
If you rename a clean machine as LOCALHOST before performing the capture process, the Package.ini file
activates the name that the VirtualComputerName parameter created. The virtual application works with the
renamed LOCALHOST name because any computer that the application runs on receives this value as the
computer name.
ThinApp Package.ini Parameters Reference Guide
16 VMware, Inc.