5.1

Table Of Contents
DisableCutPaste Parameter
You use the DisableCutPaste parameter to disable the cut and paste option in the ThinApp application.
LoadDotNetFromSystem Parameter
The LoadDotNetFromSystem parameter specifies that the ThinApp application must use the .NET installation
that is present in the user's system, not the .NET installation that is in the ThinApp application.
PermittedComputers Parameter
The PermittedComputers parameter allows you to increase security by specifying a limited set of Active
Directory Groups of computers that are permitted to use the virtual application .
Services Parameter
The Services parameter specifies how to register the ThinApp package as a system service.
StatusbarDisplayName Parameter
The StatusbarDisplayName parameter displays the application's title in the status bar of the ThinApp
application start dialog box. You can modify this value to display different application name in the status
bar.
DisableTransactionRegistry Parameter
You use the DisableTransactionRegistry parameter to prevent data corruption when an application fails
during a write operation, a power failure, or an incomplete disk flush on a removable disk present in the
ThinApp package.
DisableTransactionRegistry Parameter might help with performance in some rare circumstances if your
Sandbox is located on a network share.
PreventDLLInjection
You can use the PreventDlInjection parameter to prevent ThinApp runtime from loading a DLL, when
another external application calls the SetWindowHook to set a global hook.
This should be used only when the hook is in conflict with a virtualized application. For example, if
virtualized application is unable to start when the other application NxPowerLite calls SetWindowsHookto set a
global hook oehook.dll, modifying the package.ini with this entry allows the virtualized application to start.
ProcessExternalNameBehavior Parameter
You can use the ProcessExternalNameBehavior parameter to distinguish a child process from a parent
process.
By default, both child process and parent process names in Task Manager will be entry point names. But if
ProcessExternalNameBehavior is set to default the child process will get the name of native application while
parent process will still have the entry point name. This parameter allows users to distinguish between
parent and child processes in some scenarios.
ThinApp Package.ini Parameters Reference Guide
80 VMware, Inc.