User`s guide

Configuring Processes and Services 11
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
“AllowUnsupportedExternalChildProcesses,” on page 44
n
“AutoShutdownServices Parameter,” on page 44
n
“AutoStartServices Parameter,” on page 45
n
“ChildProcessEnvironmentDefault Parameter,” on page 45
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.
VMware, Inc.
43