5.1
Table Of Contents
- ThinApp User’s Guide
- Contents
- About This Book
- Installing ThinApp
- Capturing Applications
- Phases of the Capture Process
- Preparing to Capture Applications
- Capturing Applications with the Setup Capture Wizard
- Create a System Image Before the Application Installation
- Rescan the System with the Installed Application
- Defining Entry Points as Shortcuts into the Virtual Environment
- Set Entry Points
- Manage with VMware Horizon Application Manager
- Set User Groups
- Defining Isolation Modes for the Physical File System
- Set File System Isolation Modes
- Storing Application Changes in the Sandbox
- Customize the Sandbox Location
- Send Anonymous Statistics to VMware
- Customize ThinApp Project Settings
- Defining Package Settings
- Customize Package Settings
- Opening Project and Parameter Files
- Build Virtual Applications
- Advanced Package Configuration
- Capturing Internet Explorer 6 on Windows XP
- Capturing Multiple Application Installers with ThinApp Converter
- ThinApp Package Management
- Deploying Applications
- ThinApp Deployment Options
- Establishing File Type Associations with the thinreg.exe Utility
- Building an MSI Database
- Controlling Application Access with Active Directory
- Starting and Stopping Virtual Services
- Using ThinApp Packages Streamed from the Network
- Using Captured Applications with Other System Components
- Performing Paste Operations
- Accessing Printers
- Accessing Drivers
- Accessing the Local Disk, the Removable Disk, and Network Shares
- Accessing the System Registry
- Accessing Networking and Sockets
- Using Shared Memory and Named Pipes
- Using COM, DCOM, and Out-of-Process COM Components
- Starting Services
- Using File Type Associations
- Sample Isolation Mode Configuration Depending on Deployment Context
- Updating and Linking Applications
- Application Updates That the End User Triggers
- Application Sync Updates
- Using Application Sync in a Managed or Unmanaged Environment
- Update Firefox 2.0.0.3 to Firefox 3 with Application Sync
- Fix an Incorrect Update with Application Sync
- Application Sync Effect on Entry Point Executable Files
- Updating thinreg.exe Registrations with Application Sync
- Maintaining the Primary Data Container Name with Application Sync
- Completing the Application Sync Process When Applications Create Child Processes
- Application Link Updates
- View of the Application using Application Link
- Link a Base Application to the Microsoft .NET Framework
- Set Up Nested Links with Application Link
- Affecting Isolation Modes with Application Link
- PermittedGroups Effect on Linked Packages
- Sandbox Changes for Standalone and Linked Packages
- Import Order for Linked Packages
- File and Registry Collisions in Linked Packages
- VBScript Collisions in Linked Packages
- VBScript Function Order in Linked Packages
- Storing Multiple Versions of a Linked Application in the Same Directory
- Using Application Sync for a Base Application and Linked Packages
- Application Sync Updates
- Application Updates That the Administrator Triggers
- Automatic Application Updates
- Upgrading Running Applications on a Network Share
- Application Synchronization Using Group Policy Object
- Sandbox Considerations for Upgraded Applications
- Updating the ThinApp Version of Packages
- Application Updates That the End User Triggers
- Locating the ThinApp Sandbox
- Creating ThinApp Snapshots and Projects from the Command Line
- ThinApp File System Formats and Macros
- Creating ThinApp Scripts
- Callback Functions
- Implement Scripts in a ThinApp Environment
- API Functions
- Monitoring and Troubleshooting ThinApp
- Glossary
- Index
ThinApp User’s Guide
100 VMware, Inc.
The cmd.exe utility obtains the first location by calling GetCurrentDirectoryW and the second location
by calling GetFullPathNameW with "." as the path specifies. These calls return the path for the current
working directory. The log file shows that the cmd.exe utility creates the C:\test\cmd_test\bin>
prompt. The utility queries the PROMPT environment variable that returns $P$G and uses the
WriteConsoleW API function to print the prompt to the screen after internally expanding $P$G to
C:\test\cmd_test\bin>.
Troubleshooting Specific Applications
Troubleshooting tips are available for capturing Microsoft Outlook, Explorer.exe, and Java Runtime
Environment.
Troubleshoot Registry Setup for Microsoft Outlook
Microsoft Outlook stores account settings in registry keys and files. When you start Microsoft Outlook for the
first time, it checks that the keys exist. If Microsoft Outlook cannot find the keys, it prompts you to create an
account.
This process works properly in the virtual environment when Microsoft Outlook is not installed on the
physical system. If the user already has Microsoft Outlook installed on the physical system, the captured
version finds the registry keys in the system registry and uses those settings. You must use Full isolation mode
for the registry keys and files where Microsoft Outlook stores its settings.
Set up Full isolation mode for Microsoft Outlook registry keys
1 Add the following entries to the HKEY_CURRENT_USER.txt file:
isolation_full HKEY_CURRENT_USER\Identities
isolation_full HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Windows Messaging Subsystem\Profiles
2 Create a ##Attributes.ini file with the following entries:
[Isolation]
DirectoryIsolationMode=Full
3Place the ##Attributes.ini file in each of the following subdirectories.
%AppData%\Microsoft\AddIns
%AppData%\Microsoft\Office
%AppData%\Microsoft\Outlook
%Local AppData%\Microsoft\FORMS
%Local AppData%\Microsoft\Outlook
4 (Optional) If the subdirectories do not exist, create the directories.
Viewing Attachments in Microsoft Outlook
Microsoft Outlook creates a default directory to store attachments when you open an attachment for viewing.
The typical location is C:\Documents and Settings\<user_name>\Local Settings\Temp\Temporary
Internet Files\OLK<xxxx>. The last xxxx is replaced by a random entry.
You can view attachments when the viewing application runs in the same virtual sandbox as Microsoft
Outlook. External applications might not be able to find the file to display because Microsoft Outlook stores
the file in the sandbox. You must use the Merged isolation mode for the directory that stores the attachments.
Set up Merged isolation mode to view Microsoft Outlook attachments
1 Add a value to the HKEY_CURRENT_USER.txt file that sets the name of the attachment directory:
isolation_full
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security
Value=OutlookSecureTempFolder
REG_SZ~%Profile%\Local Settings\OutlookTempxxxx#2300
In this example, 11.0 in the key name is for Microsoft Outlook 2003.










