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
46 VMware, Inc.
Figure 3-2. Application Streaming
Requirements and Recommendations for Streaming Packages
ThinApp does not require specific server software to provide streaming capability. Any Windows file share,
NAS device, or SMB share can provide this capability. The amount of data that needs to transfer before the
application can begin running varies for each application. Microsoft Office requires that only a fraction of the
package contents stream before an application can run.
VMware recommends that you use ThinApp streaming in a LAN-based environment with a minimum of
100MB networks. For WAN and Internet deployments that involve frequent or unexpected disconnections,
VMware recommends one of the following solutions:
Use a URL to deploy the applications.
Use a desktop deployment solution to push the package to the background. Allow the application to run
only after the entire package downloads.
These solutions reduce failures and eliminate situations in which the application requires unstreamed
portions during a network outage. A company with many branch offices typically designates one application
repository that mirrors a central shared folder at each branch office. This setup optimizes local performance
for client machines located at each branch office.
Security Recommendations for Streaming Packages
VMware recommends that you make a central shared directory for the package read-only. Users can read the
package contents but not change the executable file contents. When a package streams from a shared location,
ThinApp stores application changes in the user sandbox. The default sandbox location is
%AppData%\Thinstall\<application_name>. You can configure the sandbox location at runtime or at
package time.
A common configuration is to place the user sandbox on another central storage device. The user can use any
computer and keep individual application settings at a central share. When packages stream from a central
share, they remain locked until all users exit the application.
packaged executable
local PC
64KB (Block 1)
decompressed
(Block 1)
decompressed
(Block 2)
64KB (Block 2)
64KB (Block 3)
64KB (Block 4)
64KB (Block 5)
compressed file
128KB read request
VMware ThinApp VOS
virtual registry
Ethernet