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
44 VMware, Inc.
In the following entry, only users belonging to the App1users group can use the App1.exe file, and members
of the Everyone group can use the App2.exe file. The default message for denied users changes for App1.
[BuildOptions]
PermittedGroups=Everyone
[App1.exe]
PermittedGroups=App1Users
AccessDeniedMsg=Sorry, you can’t run this application
..
[App2.exe]
...
...
Starting and Stopping Virtual Services
When you capture and deploy a package that contains a Windows service, such as the SQL Server service, any
user can run the package and start and stop the service. Unlike native applications, virtual applications do not
require administrator rights for these operations.
Automatic Startup for Virtual Services
You can install a virtual service as a physical service, so that it starts when the physical machine is started. The
virtual service remains in its ThinApp project package, but is registered on the physical machine and
controlled using the natively installed service management tools.
After you package your service, for example Apache Server, you register it on the physical machine, using the
ThinReg.exe application. The service is created as a native service, using information from the virtual
registry. The service is available to all users using the virtual application. The service is not user specific.
The process is composed of the following tasks:
Capturing the service by using ThinApp
Registering the service on the physical machine by using ThinReg
Create a virtual service for automatic startup
1 On a clean local machine, use ThinApp to capture the service.
2 After the postscan process is complete, in the Setup Capture - Ready to Build dialog, click
Edit Package.ini.
The Package.ini file opens in a text editor.
3 Search for the services entry.
The entry is followed by the name of the service that you captured.
By default, the entry is commented out.
4 Remove the semicolon (;) from the start of the line.
5Save the Package.ini file.
6 Build the ThinApp project.
You can now register your virtual service so that it can be managed by using the native services management
tools.
Register the virtual service on a machine
1Run the ThinReg.exe application.
2 At the command line, type C:\Program Files\VMware\VMware ThinApp\ThinReg /a *.exe.
You must use /a to register services. If you run ThinApp without this option, the service is not registered.
You can change the path, if required for your system.