4.7.3
Table Of Contents
- ThinApp Package.ini Parameters Reference Guide
- Contents
- About This Guide
- Configuring Package Parameters
- Package.ini File Structure
- Package.ini or ##Attributes.ini Files That Override Package.ini Settings
- Configuring the ThinApp Runtime
- Configuring Isolation
- Configuring File and Protocol Associations
- Configuring Build Output
- Configuring Permissions
- Configuring Objects and DLL Files
- ExternalCOMObjects Parameter
- ExternalDLLs Parameter
- ForcedVirtualLoadPaths Parameter
- IsolatedMemoryObjects Parameter
- IsolatedSynchronizationObjects Parameter
- NotificationDLLs Parameter
- NotificationDLLSignature Parameter
- ObjectTypes Parameter
- SandboxCOMObjects Parameter
- VirtualizeExternalOutOfProcessCOM Parameter
- Configuring File Storage
- Configuring Processes and Services
- Configuring Sizes
- Configuring Logging
- Configuring Versions
- Configuring Locales
- Configuring Individual Applications
- Configuring Dependent Applications Using the Application Utility
- Configuring Application Updates with the Application Sync Utility
- Configuring MSI Files
- Configuring Sandbox Storage and Inventory Names
- Other Configuration Parameters
- Locating the ThinApp Sandbox
- Controlling the Sandbox Location
- Sandbox Structure
- Creating ThinApp Snapshots and Projects from the Command Line
- Index
AutoStartServices Parameter
The AutoStartServices parameter controls whether to start the virtual services when the first virtual
application starts.
ThinApp sets an initial value that starts the virtual services that are installed with the automatic startup type
option. The virtual services start when the user runs the first parent process.
Example: Preventing a Virtual Service From Starting
When applications install a service, but do not use it, you can modify the AutoStartServices parameter to
prevent the start of the virtual service and save time.
[BuildOptions]
AutoStartServices=0
ChildProcessEnvironmentDefault Parameter
The ChildProcessEnvironmentDefault parameter determines whether ThinApp runs all child processes in the
virtual environment.
ThinApp creates all child processes in the virtual environment. If the processes are slow, you might want to
move child processes to the physical environment. As a child process, Microsoft Outlook might affect
performance when it copies the whole mailbox to the virtual environment.
You can create specific exceptions with the ChildProcessEnvironmentExceptions parameter.
See “ChildProcessEnvironmentExceptions Parameter,” on page 45.
Example: Create Child Processes in the Physical Environment
If you do not want the child process to operate in or slow down the virtual environment, you can modify the
ChildProcessEnvironmentDefault parameter to create child processes in the physical environment.
[BuildOptions]
ChildProcessEnvironmentDefault=External
ChildProcessEnvironmentExceptions Parameter
The ChildProcessEnvironmentExceptions parameter notes exceptions to the
ChildProcessEnvironmentDefault parameter when you want to specify child processes.
When you set the ChildProcessEnvironmentDefault parameter to Virtual, the
ChildProcessEnvironmentExceptions parameter lists the applications that run outside of the virtual
environment. When you set the ChildProcessEnvironmentDefault parameter to External, the
ChildProcessEnvironmentExceptions parameter lists the applications that run in the virtual environment.
Example: Specifying Exceptions to Running Child Processes in the Virtual
Environment
You can specify exceptions to running child processes in the virtual environment. When the virtual application
starts a notepad.exe child process, the child process runs outside the virtual environment.
[BuildOptions]
ChildProcessEnvironmentExceptions=AcroRd.exe;notepad.exe
ChildProcessEnvironmentDefault=Virtual
Chapter 11 Configuring Processes and Services
VMware, Inc. 45










