5.1

ThinApp User’s Guide
54 VMware, Inc.
Prevent the startup of the ctfmon.exe process
1 If you did not activate the cmd.exe entry point during the capture process, set the Disabled parameter
for the cmd.exe entry in the Package.ini file to 0 and rebuild the package with the build.bat utility.
This generates an executable file for the cmd.exe entry point in the /bin directory.
2Copy the /bin directory in the captured application directory to a clean virtual machine or delete the
sandbox for the Microsoft Office package.
3 Double-click the cmd.exe entry point.
4 In the Windows command processor, run the INTL.CPL command.
5In the Languages tab of the Regional and Languages dialog box, click Details.
6In the Advanced tab of the Text Services and Input Languages dialog box, select the Turn off advanced
text services check box.
7Click OK in all the open dialog boxes and leave the Windows command processor open.
8 Unregister the MSIMTF.dll and MSCTF.dll files with the REGSVR32.EXE/U <DLL_file> command.
See knowledge base article 282599 in the Microsoft Web site.
9 Close the Windows command processor.
10 If the virtual machine does not reside on the same machine where ThinApp is installed, copy the sandbox
from the package to the packaging system.
The default sandbox location is %APPDATA%\Thinstall.
11 From the standard command prompt on the packaging system, use the sbmerge.exe utility to merge the
updated sandbox with the package.
A sample command is SBMERGE APPLY –ProjectDir "C:\Program Files\VMware
\VMware ThinApp\Captures\Microsoft Office Professional 2007" –SandboxDir
"%APPDATA%\Thinstall\Microsoft Office Pro 2007".
12 Rebuild the package and test the package on a clean virtual machine to confirm that the ctfmon.exe
process no longer exists.
Application Link Updates
The Application Link utility connects dependent applications at runtime. You can package, deploy, and update
component pieces separately rather than capture all components in the same package.
ThinApp can link up to 250 packages at a time. Each package can be any size.
The Application Link utility is useful for the following objects:
 Large shared libraries and frameworks – Link runtime components, such as .NET, JRE, or ODBC drivers,
with dependent applications.
For example, you can link .NET to an application even if the local machine for the application prevents
the installation of .NET or already has a different version of .NET.
If you have multiple applications that require .NET, you can save space and make a single .NET package
and point the multiple applications to the .NET package. When you update .NET with a security fix, you
can update a single package rather than multiple packages.
 Add-on components and plug-ins – Package and deploy application-specific components and plug-ins
separately from the base application.
For example, you might separate Adobe Flash Player or Adobe Reader from a base Firefox application
and link the components.
You can deploy a single Microsoft Office package to all users and deploy individual add-on components
for each user.