Configuring Processes And Services; Allowexternalkernelmodeservices; Allowexternalprocessmodifications - VMware THINAPP 4.6 Manual

Examples
The VirtualDrives parameter is a single string that can hold information about multiple drive letters, and
optional parameters for those drive letters. The parameter uses semicolons to separate information assigned
to different drive letters and commas to separate parameters for individual drive letters. ThinApp assigns a
serial number and the FIXED type to the drive.
[BuildOptions]
VirtualDrives= Drive=A, Serial=12345678, Type=REMOVABLE; Drive=B, Serial=9ABCDEF0, Type=FIXED
You can specify the X, D, and Z virtual drive letters.
[BuildOptions]
VirtualDrives=Drive=X, Serial=ff897828, Type=REMOVABLE; Drive=D, Type=CDROM; Drive=Z
Drive X is a removable disk with the ff797828 serial number.
Drive D is a CD‐ROM drive with an assigned serial number.
Drive Z is a FIXED disk with an assigned serial number.

Configuring Processes and Services

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.

AllowExternalKernelModeServices

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.
Examples
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

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 the 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.
Examples
You can add the AllowExternalProcessModifications parameter to the Package.ini file to support write
operations from virtual processes to native processes. For example, a speech recognition application must
inject itself into native applications to voice the text.
[BuildOptions]
AllowExternalProcessModifications=1
VMware, Inc.
Chapter 5 Configuring Package Parameters
81