[BuildOptions]

AdminStudio 2021 | 21.0 | ThinApp Assistant

The [BuildOptions] section of the package.ini file specifies Global options which will be inherited by each child executable file. The following options are included:

[BuildOptions] Section of package.ini

Option

Description

SandboxName

When a ThinApp application is built, a Sandbox cache is created in the following location:

c:\Documents & Settings\USER_NAME\Application Data\ThinApp\SandboxName

The SandboxName entry in the package.ini file is used to name the directory where sandbox files are stored at runtime.

SandboxName=MyApplicationV3

By default, AdminStudio names the Sandbox by assigning it a unique GUID. However, if you want to override this default Sandbox name, you may (optionally) enter a new name in the package.ini file using the SandboxName option.

If no Sandbox Name is entered, a unique GUID is used, such as:

SandboxName={2BDBE10A-9E53-4B5E-811D-DF8019D0B13C}

Note:This option corresponds to the Sandbox Name field on the General Information page.

InventoryName

Used by desktop management systems to identify packages for usage reporting purposes. If you do not use a desktop management system or license-controlled system, this value has no effect

InventoryName=MainApp v1.0

SandboxNetworkDrives

Enable this option if you want changes to data on Network-mapped drives to go into the sandbox. By default, the ThinApp application can read and write to network mapped drives with no changes. The value for SandboxNetworkDrives is set to either 0 (off) or 1 (on).

SandboxNetworkDrives=0

Note:This option corresponds to the Mapped Network Drive Changes go to Sandbox option on the General Settings page.

SandboxRemovableDisk

Enable this option if you want changes to data on Removable disk (floppy/flash) to go into the sandbox. By default the application can read and write to removable disk with no changes. The value for SandboxRemovableDisk can be set to either 0 (off) or 1 (on).

SandboxRemovableDisk=0

Note:This option corresponds to the Removable Disk Changes go to Sandbox option on the General Settings page.

RemoveSandboxOnExit

Enable this option if you want to delete the sandbox when the ThinApp application exits. This resets the application to its original captured state If the application spawns child processes, the clean up will be postponed until all have quit. The value for RemoveSandboxOnExit can be set to either 0 (off) or 1 (on).

RemoveSandboxOnExit=0

Note:This option corresponds to the Reset Sandbox on Exit option on the General Settings page.

ExternalCOMObjects

This option allows you to specify that you want specific COM objects to be executed on the system instead of in the virtual environment. This option only applies to out-of-process COM objects (LocalServer32) and Services-based COM objects.

To specify multiple objects, put a semicolon after each entry. Objects should always be specified in CLSID format

The following class ID specifies the class ID for Microsoft Word:

ExternalCOMObjects={000209FF-0000-0000-C000-000000000046};{000209FF-0000-0000-C000-000000000047}

Caution:This option is for advanced users.

VirtualizeExternalOutOfProcessCOM

Enable this option if you want all out-of-process COM objects to be loaded outside of the virtual environment . By doing this, the application may indirectly modify the machine—for example, the MSI installer service COM object could be modified.

VirtualizeExternalOutOfProcessCOM=0

The value for this option can be set to either:

• 0—Inside virtual environment
• 1—Outside the virtual environment

The default is to create all out-of-process COM objects inside the virtual environment.

PermittedGroups

Using this option, you can specify the Active Directory groups which are allowed to use this ThinApp application.

PermittedGroups=Group1;Group2;Group3

Note:This option corresponds to the Allow application execution to the following user groups option on the General Settings page.

AccessDeniedMsg

Use this option to customize the message the user sees if they do not have permission to execute a ThinApp application.

AccessDeniedMsg=You do not have access to execute this application, please contact your Administrator

Note:This option corresponds to the Message shown when users not belonging to above groups run the ThinApp application field on the General Settings page.

ChildProcessEnvironmentDefault and ChildProcessEnvironmentExceptions

Executables located in the virtual file system are always executed within the virtual environment. Executables located in the physical file system can be executed inside or outside the virtual environment.

The default is determined by the ChildProcessEnvironmentDefault option, which can be set to Virtual or External. If this option is not present, the default is the Virtual environment.

It is possible to override the default for specific applications by specifying a list of applications, separated by semicolons, using the ChildProcessEnvironmentExceptions option. If a complete path is specified, the full name of the executable is used for the comparison; otherwise, only the file name is used.

For example:

ChildProcessEnvironmentDefault=Virtual

ChildProcessEnvironmentExceptions=exec.exe;c:\path\file.exe

In this example, c:\exec.exe, c:\Windows\exec.exe and c:\path\file.exe would be executed externally.

AutoShutdownServices

Use this option to specify if virtualized services keep on running when the last non-service process exits. Permitted values are:

• 0—Keep on running.
• 1—Stop virtualized services (Default).

AutoShutdownServices=1

NetRelaunch

Under some conditions, Norton AntiVirus will try to perform a complete scan of an executable. This scan can have a big impact on launch times for large executable files located on network shares. Norton AntiVirus decides to perform a complete scan under these conditions:

• If the executable is launched from a network share or removable disk. It skips the scan when the executable is located on the hard drive).
• When the executable makes its first network connection. It does not scan the executable if the executable does not make any network connections.

Because a large number of desktops have Norton AntiVirus installed, ThinApp automatically compensates for this by allowing applications to launch from a network share without incurring the lengthy scan times. It does so by creating a small stub executable in the user's sandbox which is then relaunched. Because the small executable can be scanned quickly, it will load the remainder of the application data from the original source location.

You can disable ThinApp default behavior by adding the NetRelaunch=1 option to disable full file scans.

NetRelaunch=1