5.1
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
- DisableCutPaste Parameter
- LoadDotNetFromSystem Parameter
- PermittedComputers Parameter
- Services Parameter
- StatusbarDisplayName Parameter
- DisableTransactionRegistry Parameter
- PreventDLLInjection
- ProcessExternalNameBehavior Parameter
- PreventDllInjectionExceptions Parameter
- LargeAddressAware Parameter
- PermittedComputers Parameter
- PermittedComputersAccessDeniedMsg Parameter
- PermittedComputersOfflineAccess Parameter
- IgnoreDDEMessages Parameter
- Locating the ThinApp Sandbox
- Controlling the Sandbox Location
- Sandbox Structure
- Creating ThinApp Snapshots and Projects from the Command Line
- Index
Configuring Processes and Services 12
You can modify ThinApp parameters to configure processes and services that might specify write access to
a native process or the startup and shutdown of virtual services.
This chapter includes the following topics:
n
“AllowExternalKernelModeServices Parameter,” on page 43
n
“AllowExternalProcessModifications Parameter,” on page 43
n
“AutoShutdownServices Parameter,” on page 44
n
“AutoStartServices Parameter,” on page 44
n
“ChildProcessEnvironmentDefault Parameter,” on page 44
n
“ChildProcessEnvironmentExceptions Parameter,” on page 45
AllowExternalKernelModeServices Parameter
The AllowExternalKernelModeServices parameter controls whether applications can create and run native
kernel driver services. The service executable file must exist on the physical file system.
ThinApp does not display the default parameter in the Package.ini file but assigns an initial value that
prevents the application from starting a native Windows kernel driver service.
Example: Allowing an Application to Create or Open a Native Windows Kernel
Driver Service
You can add the AllowExternalKernelModeServices parameter to the Package.ini file and modify the
default value of 0 to 1 to allow the application to create or open a native Windows kernel driver service.
[BuildOptions]
AllowExternalKernelModeServices=1
AllowExternalProcessModifications Parameter
The AllowExternalProcessModifications parameter determines whether captured applications can write to
a native process. Some virtualized applications require a method to interact with native applications.
ThinApp blocks any attempt by a captured application to inject itself into a native application. The captured
application can still inject itself into virtual applications running in the same sandbox. ThinApp does not
display the default parameter in the Package.ini file.
When ThinApp blocks a captured application from injecting itself into a native application, Log Monitor
generates trace logs that refer to the AllowExternalProcessModifications parameter.
VMware, Inc.
43