ThinApp Package.ini Parameters Reference Guide ThinApp 4.7.3 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
ThinApp Package.ini Parameters Reference Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents About This Guide 7 1 Configuring Package Parameters 9 2 Package.ini File Structure 11 3 Package.ini or ##Attributes.ini Files That Override Package.
ThinApp Package.
Contents Source Parameter 60 WorkingDirectory Parameter 60 17 Configuring Dependent Applications Using the Application Utility 61 Application Link Pathname Formats 61 RequiredAppLinks Parameter 62 OptionalAppLinks Parameter 63 18 Configuring Application Updates with the Application Sync Utility 65 AppSyncClearSandboxOnUpdate Parameter AppSyncExpireMessage Parameter 66 AppSyncExpirePeriod Parameter 66 AppSyncURL Parameter 66 AppSyncUpdateFrequency Parameter 67 AppSyncUpdatedMessage Parameter 67 AppSyncWa
ThinApp Package.
About This Guide The ThinApp Package.ini Parameters Reference Guide provides information on how to configure and customize the ThinApp Package.ini parameters. You can refer this guide to customize the parameters of the virtual application outside of the capture process. Intended Audience This book is intended for anyone who has to customize the Package.ini parameters of the captured applications.
ThinApp Package.ini Parameters Reference Guide 8 VMware, Inc.
Configuring Package Parameters 1 Advanced users can customize the parameters of a virtual application, outside of the capture process. Parameters can affect the configuration of build options that include MSI, update, and entry point settings. The Package.ini file is located in the project folder for your virtual application. The file contains parameters that configure a captured application during the build process. The Setup Capture wizard sets the initial values of some Package.ini parameters.
ThinApp Package.ini Parameters Reference Guide 10 VMware, Inc.
Package.ini File Structure 2 The structure of the Package.ini file includes sections that apply to all applications or individual applications. Most parameters must appear under a specific section heading. The Package.ini file contains the following headings: [BuildOptions] The [BuildOptions] section of the Package.ini file applies to all applications. Individual applications inherit these parameters unless application-specific entries override the settings. For example, the [Adobe Reader 8.
ThinApp Package.ini Parameters Reference Guide 12 VMware, Inc.
Package.ini or ##Attributes.ini Files That Override Package.ini Settings 3 You can apply certain parameters to the Package.ini or ##Attributes.ini files, depending on requirements, that override Package.ini settings at directory level. You can use the DirectoryIsolationMode, CompressionType, and ExcludePattern parameters in an ##Attributes.ini file to override directory-level Package.ini settings. The ##Attributes.ini file is located in the folder macros of the project folder.
ThinApp Package.ini Parameters Reference Guide 14 VMware, Inc.
Configuring the ThinApp Runtime 4 You can modify ThinApp parameters for runtime configuration tasks that affect application startup performance and virtual computer names. 1 NetRelaunch Parameter on page 15 The NetRelaunch parameter determines whether to restart an application from the local disk when you run the application from a network share or removable disk, to address the slow startup of applications.
ThinApp Package.ini Parameters Reference Guide Because a large number of desktop computers use Symantec AntiVirus, ThinApp enables applications to open from a network share without incurring lengthy scan times. When the application runs from a network share or removable disk, ThinApp creates a stub executable file in the directory that the CachePath parameter sets on the local disk and restarts the application from this stub executable file.
Chapter 4 Configuring the ThinApp Runtime If you run a GetComputerName or GetComputerNameEx command, the computer returns LOCALHOST. If the Windows system requires the GetComputerName and GetComputerNameEx commands to operate in a standard way and return the actual name of the computer where the application runs, do not rename the machine as LOCALHOST.
ThinApp Package.ini Parameters Reference Guide 18 VMware, Inc.
Configuring Isolation 5 ThinApp isolation parameters determine the read and write access to the file system and registry keys This chapter includes the following topics: n “DirectoryIsolationMode Parameter,” on page 19 n “RegistryIsolationMode Parameter,” on page 20 DirectoryIsolationMode Parameter The DirectoryIsolationMode parameter specifies the level of read and write access for directories to the physical file system.
ThinApp Package.ini Parameters Reference Guide You must place the parameter under an [Isolation] heading. For more information about modifying the ##Attributes.ini file settings, see the ThinApp User’s Guide. Example: Using WriteCopy Isolation In this example, you modify the DirectoryIsolationMode parameter with WriteCopy isolation to ensure that the virtual application can read resources on the local machine, but not write to the host computer. This is the default setting for the snapshot.exe utility.
Chapter 5 Configuring Isolation Example: Using Merge Isolation in the Registry This example shows how you can ensure that the application can write to any key on the computer, except where the package specifies otherwise. [Isolation] RegistryIsolationMode=Merged VMware, Inc.
ThinApp Package.ini Parameters Reference Guide 22 VMware, Inc.
Configuring File and Protocol Associations 6 You can modify ThinApp parameters to associate file extensions with applications and to specify protocols that are visible to the physical environment. This chapter includes the following topics: n “FileTypes Parameter,” on page 23 n “Protocols Parameter,” on page 24 FileTypes Parameter The FileTypes parameter lists file extensions that the thinreg.exe utility associates with an executable file.
ThinApp Package.ini Parameters Reference Guide Protocols Parameter The Protocols parameter specifies the protocols, such as HTTP, that are visible to applications in the physical environment. This parameter is similar to the FileTypes parameter, but deals with applications that handle protocols rather than file types. The capture process generates initial values that you cannot add to. You can remove entries for browsers or other applications.
Configuring Build Output 7 You can modify ThinApp parameters to specify the location of the build output and the files in the package. This chapter includes the following topics: n “ExcludePattern Parameter,” on page 25 n “Icon Parameter,” on page 26 n “OutDir Parameter,” on page 26 n “RetainAllIcons Parameter,” on page 27 ExcludePattern Parameter The ExcludePattern parameter excludes files or directories during the application build process.
ThinApp Package.ini Parameters Reference Guide Icon Parameter The Icon parameter specifies the icon file to associate with a generated executable file. This icon appears in the application, for example Microsoft Word, and in the files associated with the application, such as .doc files. Each application includes its own icon stored as a .ico file, within the .exe file of the application, or within a .dll file. The capture process attaches the icons to the executable files.
Chapter 7 Configuring Build Output RetainAllIcons Parameter The RetainAllIcons parameter keeps all of the original icons of the executable file listed in the Source parameter in the application. Icons that are not assigned to application executable files reside in the virtual file system of the package. The RetainAllIcons parameter determines whether to copy the unused icons from the virtual file system to the executable file.
ThinApp Package.ini Parameters Reference Guide 28 VMware, Inc.
Configuring Permissions 8 You can modify parameters for security tasks that define user access to packages and change Data Execution Prevention (DEP) protection. Permissions parameters are generally specified under the [build options] section.
ThinApp Package.ini Parameters Reference Guide The AddPageExecutePermission parameter instructs ThinApp to add execution permission to pages that an application allocates. The application can then run on machines that have DEP protection enabled, without modifying the opt-out list. ThinApp sets an initial value for the AddPageExecutePermission parameter that prevents any change to the DEP protections.
Chapter 8 Configuring Permissions Example: Inheriting the Global PermittedGroups Setting If you do not specify a PermittedGroups setting for an application, the application inherits the global PermittedGroups value in the [BuildOptions] section. [App2.exe] ... Example: Mixing Group Names and SID Strings You can mix group names and SID strings in the same entry for the PermittedGroups parameter.
ThinApp Package.ini Parameters Reference Guide 32 VMware, Inc.
Configuring Objects and DLL Files 9 You can modify ThinApp parameters to specify COM object access and DLL loading requirements.
ThinApp Package.ini Parameters Reference Guide You can list the CLSID keys. [BuildOptions] ExternalCOMObjects={8BC3F05E-D86B-11D0-A075-00C04FB68820};{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ExternalDLLs Parameter The ExternalDLLs parameter can force Windows to load specific DLL files from the virtual file system. ThinApp sets an initial value that loads DLL files from the virtual file system and passes the loading process to Windows for DLL files on the physical file system.
Chapter 9 Configuring Objects and DLL Files IsolatedMemoryObjects Parameter The IsolatedMemoryObjects parameter lists the shared memory objects to isolate from other applications or from system objects. Applications that use CreateFileMapping and OpenFileMapping Windows functions create shared memory objects. When you do not isolate memory objects, conflicts can occur between virtual applications and native applications sharing those objects.
ThinApp Package.ini Parameters Reference Guide The IsolatedSynchronizationObjects parameter does not appear in the Package.ini file, but you can add the parameter. ThinApp sets an initial value that makes synchronization objects accessible to other applications. Virtual applications with different sandboxes can detect the synchronization objects. The IsolatedSynchronizationObjects parameter accepts a list of entries that are separated by a semicolon (;).
Chapter 9 Configuring Objects and DLL Files ObjectTypes Parameter The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications in the physical environment. You can use scripts, such as VBScripts, to call objects that start captured applications. An object type is registered to only one native or virtual application at a time.
ThinApp Package.ini Parameters Reference Guide If a compatibility problem exists with an external COM object running in the virtual environment, you can create and run COM objects on the host system. To run only specific COM objects outside of the virtual environment, you can use the ExternalCOMObjects parameter to list the CLSID of each COM object. See “ExternalCOMObjects Parameter,” on page 33.
Configuring File Storage 10 You can modify ThinApp parameters to configure file storage and set up virtual drives. This chapter includes the following topics: n “CachePath Parameter,” on page 39 n “UpgradePath Parameter,” on page 40 n “VirtualDrives Parameter,” on page 40 CachePath Parameter The CachePath parameter sets the deployment system path to a cache directory for font files and stub executable files.
ThinApp Package.ini Parameters Reference Guide Example: Setting the Cache and Sandbox at the Same Directory Level When you use a USB device and move the sandbox to the USB device, you might move the cache to the USB device to avoid interfering with the local machine. In this situation, the cache and sandbox exist in the same directory level.
Chapter 10 Configuring File Storage n CD-ROM – Indicates a CD-ROM drive. n RAMDISK—Indicates a RAM disk. Virtual drives are useful when applications rely on hard-coded paths to drive letters that might not be available on the deployment systems. For example, legacy applications might expect that the D: drive is a CD-ROM and that the data files are available at D:\media. Virtual drive settings override the physical properties of the drive on the physical deployment system.
ThinApp Package.ini Parameters Reference Guide Example: Assigning a Drive Letter to a Virtual Drive You can specify the X, D, and Z virtual drive letters. n Drive X is a removable disk with the ff797828 serial number. n Drive D is a CD-ROM drive with an assigned serial number. n Drive Z is a FIXED disk with an assigned serial number. [BuildOptions] VirtualDrives=Drive=X, Serial=ff897828, Type=REMOVABLE; Drive=D, Type=CDROM; Drive=Z 42 VMware, Inc.
Configuring Processes and Services 11 You can modify ThinApp parameters to configure processes and services that might specify write access to a native process or the startup and shutdown of virtual services.
ThinApp Package.ini Parameters Reference Guide ThinApp blocks any attempt by a captured application to inject itself into a native application. The captured application can still inject itself into virtual applications running in the same sandbox. ThinApp does not display the default parameter in the Package.ini file. When ThinApp blocks a captured application from injecting itself into a native application, Log Monitor generates trace logs that refer to the AllowExternalProcessModifications parameter.
Chapter 11 Configuring Processes and Services AutoStartServices Parameter The AutoStartServices parameter controls whether to start the virtual services when the first virtual application starts. ThinApp sets an initial value that starts the virtual services that are installed with the automatic startup type option. The virtual services start when the user runs the first parent process.
ThinApp Package.ini Parameters Reference Guide 46 VMware, Inc.
Configuring Sizes 12 You can modify ThinApp parameters to compress file and block sizes for applications. This chapter includes the following topics: n “BlockSize Parameter,” on page 47 n “CompressionType Parameter,” on page 47 n “MSICompressionType Parameter,” on page 48 BlockSize Parameter The BlockSize parameter controls the size of compression blocks only when ThinApp compresses files for a build. A larger block size can achieve higher compression.
ThinApp Package.ini Parameters Reference Guide Table 12-1. Sample Compression Ratios and Startup Times for a Microsoft Office 2003 Package Running From a Local Hard Drive Compression Type None Fast Size 448,616KB 257,373KB Compression Ratio 100% 57% Startup Time (first run) 6 seconds 6 seconds Startup Time (second run) 0.1 seconds 1 second Build Time (first build) 3 minutes 19 minutes Build Time (second build) 2 minutes 1.
Chapter 12 Configuring Sizes If you create an MSI file during the capture process, ThinApp adds the MSICompressionType parameter to the Package.ini file and sets the initial value of Fast to compress the file. Decompression occurs at the time of installation. You do not have to set the MSICompressionType parameter to Fast when you set the CompressionType parameter to Fast. Setting both parameters does not increase the amount of compression.
ThinApp Package.ini Parameters Reference Guide 50 VMware, Inc.
Configuring Logging 13 You can modify ThinApp parameters to prevent logging activity or customize the location of the log files. This chapter includes the following topics: n “DisableTracing Parameter,” on page 51 n “LogPath Parameter,” on page 51 DisableTracing Parameter The DisableTracing parameter prevents .trace file generation when you run Log Monitor for security and resource purposes. You might block standard .trace file generation to hide the application history from a user.
ThinApp Package.ini Parameters Reference Guide 52 VMware, Inc.
Configuring Versions 14 ThinApp parameters provide information about the versions of application executable files and ThinApp packages. This chapter includes the following topics: n “CapturedUsingVersion Parameter,” on page 53 n “StripVersionInfo Parameter,” on page 53 n “Version.XXXX Parameter,” on page 54 CapturedUsingVersion Parameter The CapturedUsingVersion parameter displays the version of ThinApp for the capture process and determines the file system macros that ThinApp must expand.
ThinApp Package.ini Parameters Reference Guide Example: Generating an Application Without Version Information In rare cases, you might modify the StripVersionInfo parameter to generate an application without version information. For example, you might want to circumvent version detection scans that compare versions against a database of outdated software. [app.exe] Source=%ProgramFilesDir%\myapp\app.exe StripVersionInfo=1 Version.XXXX Parameter The Version.
Configuring Locales 15 You can use ThinApp parameters to verify locale information. This chapter includes the following topics: n “AnsiCodePage Parameter,” on page 55 n “LocaleIdentifier Parameter,” on page 55 n “LocaleName Parameter,” on page 56 AnsiCodePage Parameter The AnsiCodePage parameter displays a numerical value that represents the language of the operating system on which you capture the application. ThinApp uses the value to manage multibyte strings.
ThinApp Package.ini Parameters Reference Guide LocaleName Parameter The LocaleName parameter displays the name of the locale when you capture an application on Microsoft Vista. Displaying the LocaleName of a Captured Application The LocaleName parameter can display a Japanese locale name. [BuildOptions] LocaleName=ja-JP 56 VMware, Inc.
Configuring Individual Applications 16 You can modify ThinApp parameters to configure specific applications. Parameters specific to entry points are specified under the [.exe]sections of the Package.ini file. For example, the entries under Adobe Reader 8.exe for an Adobe Reader application might affect command-line arguments and application shortcuts.
ThinApp Package.ini Parameters Reference Guide CommandLine="C:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode Command-line arguments can use the /
Chapter 16 Configuring Individual Applications Example: Reserving space using ReserveExtraAddressSpace parameter You can instruct the Windows loader to reserve extra address space. Add K after the number to indicate kilobytes or M to indicate megabytes. [.exe] Source=%ProgramFilesDir%\\.exe ReserveExtraAddressSpace=512K Shortcut Parameter The Shortcutparameter points a shortcut executable file to the primary data container that contains the virtual file system and virtual registry.
ThinApp Package.ini Parameters Reference Guide Source Parameter The Source parameter specifies the executable file that ThinApp loads when you use a shortcut executable file. The parameter provides the path to the executable file in the virtual or physical file system. ThinApp specifies the source for each executable file. If an application suite has three user entry points, such as Winword.exe, Powerpnt.exe, and Excel.exe, the Package.ini file lists three application entries.
Configuring Dependent Applications Using the Application Utility 17 The Application Link utility keeps shared components or dependent applications in separate packages. In the Package.ini file, you can use the OptionalAppLinks and RequiredAppLinks entries to dynamically combine ThinApp packages at runtime on end-user computers. This process enables you to package, deploy, and update component pieces separately and keep the benefits of application virtualization.
ThinApp Package.ini Parameters Reference Guide n Path names can specify multiple links or dependencies with a semicolon that separates individual filenames. An example is RequiredAppLinks=Dependency1.exe; Dependency2.exe;. n Path names can contain asterisk and query wildcard characters (* and ?) in filenames and directory paths. For example, RequiredAppLinks=WildPath*\WildFilename*.dat.
Chapter 17 Configuring Dependent Applications Using the Application Utility RequiredAppLinks=Plugin.exe You can import a single package located in a subdirectory of the base executable file. RequiredAppLinks=plugins\Plugin.exe You can import all executable files located in the directory for plug-in files. If ThinApp cannot import any executable file because the file is not a valid Thinapp package or because a security problem exists, the base executable file fails to load. RequiredAppLinks=plugins\*.
ThinApp Package.ini Parameters Reference Guide 64 VMware, Inc.
Configuring Application Updates with the Application Sync Utility 18 The Application Sync utility keeps deployed virtual applications up to date. When an application starts, the Application Sync utility can query a Web server to determine if an updated version of the package is available. If an update is available, ThinApp downloads the differences between the existing package and the new package and constructs an updated version of the package.
ThinApp Package.ini Parameters Reference Guide AppSyncClearSandboxOnUpdate Parameter The AppSyncClearSandboxOnUpdate parameter determines whether to clear the sandbox after an update. ThinApp sets an initial value of the AppSyncClearSandboxOnUpdate parameter that keeps the contents of the sandbox. Example: Modifying AppSyncClearSandboxOnUpdate Parameter You can modify the AppSyncClearSandboxOnUpdate parameter to clear the sandbox after application updates.
Chapter 18 Configuring Application Updates with the Application Sync Utility AppSyncURL=https://// You can specify local and network drive paths. A primary data container can be either a .exe or .dat file. file:///C:// You can use a UNC path and access locations of network resources.
ThinApp Package.ini Parameters Reference Guide AppSyncWarningMessage Parameter The AppSyncWarningMessage parameter sets the message that appears when the warning period starts. The first time you start the application in the warning period, a warning message appears and ThinApp tries to access the update from the server. If ThinApp cannot update the package, ThinApp tries again every time the application starts. The warning message appears only after each AppSyncWarningFrequency period expires.
Configuring MSI Files 19 You can modify ThinApp parameters to configure MSI files for deployment through desktop management systems. Information about compression of MSI files appears with other parameters that control file sizes. See “MSICompressionType Parameter,” on page 48.
ThinApp Package.ini Parameters Reference Guide MSIDefaultInstallAllUsers Parameter The MSIDefaultInstallAllUsers parameter sets the installation mode of the MSI database. You can install a .msi file for all users on a computer and for individual users. The parameter is applied only when the MSIFilename parameter requests the generation of a Windows Installer database.
Chapter 19 Configuring MSI Files MSIInstallDirectory Parameter The MSIInstallDirectory parameter specifies the relative path of the MSI installation directory. The path is relative to %ProgramFilesDir% for installations on each machine and relative to %AppData% for installations for each user. When you install the MSI database for all users, ThinApp places applications in the C:\%ProgramFilesDir %\ (VMware ThinApp) directory during the installation on each machine.
ThinApp Package.ini Parameters Reference Guide Example: Creating an MSI file using MSIProductCode Parameter The capture process can create an MSI file with 590810CE-65E6-3E0B-08EF-9CCF8AE20D0E as the product code. [BuildOptions] MSIFilename=.msi MSIProductCode={590810CE-65E6-3E0B-08EF-9CCF8AE20D0E} MSIProductVersion Parameter The MSIProductVersion parameter specifies a product version number for the MSI database to facilitate version control.
Chapter 19 Configuring MSI Files MSIUpgradeCode Parameter The MSIUpgradeCode parameter specifies a code for the MSI database that facilitates updates. When two packages, such as the version 1.0 package and the version 2.0 package, have the same upgrade code, the MSI installer detects this link, uninstalls the earlier package, and installs the updated package. The capture process generates a random upgrade code based on the inventory name.
ThinApp Package.ini Parameters Reference Guide 74 VMware, Inc.
Configuring Sandbox Storage and Inventory Names 20 You can modify ThinApp parameters to configure the sandbox where all changes that the captured application makes are stored. The ThinApp inventory name might affect the need to change the sandbox name.
ThinApp Package.ini Parameters Reference Guide If you have a package that includes other applications, you might update the inventory name manually to reflect the true contents of the package. For example, if you capture the SuperApp application and the package includes Java Runtime, the InventoryName value might appear as Java Runtime Environment 1.5 instead of SuperApp. The Add or Remove Programs window displays the first application installed within the package.
Chapter 20 Configuring Sandbox Storage and Inventory Names SandboxNetworkDrives Parameter The SandboxNetworkDrives parameter determines whether ThinApp directs write operations to a network drive or to the sandbox, regardless of isolation mode settings. When you use this parameter to direct write operations to network drives, the result is the same as setting the isolation mode for the drive to Merged mode.
ThinApp Package.ini Parameters Reference Guide SandboxRemovableDisk Parameter The SandboxRemovableDisk parameter determines whether the application can write removable disk changes to the disks or to the sandbox. Removable disks include USB flash devices and removable hard drives. ThinApp sets an initial value that instructs the application to write removable disk file changes to the disk.
Other Configuration Parameters 21 You can use some ThinApp parameters to configure printers, disable the cut and paste option, specify settings for a computer. and group SIDs and modify the user name that appears in the status bar.
ThinApp Package.ini Parameters Reference Guide HidePrinters Parameter You use the HidePrinters parameter to hide the printers present in the ThinApp package. 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 .
Locating the ThinApp Sandbox 22 The sandbox is the directory where all changes that the captured application makes are stored. The next time you start the application, those changes are incorporated from the sandbox. When you delete the sandbox directory, the application reverts to its captured state. Search Order for the Sandbox During startup of the captured application, ThinApp searches for an existing sandbox in specific locations and in a specific order. ThinApp uses the first sandbox it detects.
ThinApp Package.ini Parameters Reference Guide For example, if the Mozilla Firefox 3.0_SANDBOX_DIR environment variable exists, its value determines the parent directory sandbox location. If the value is z:\FirefoxSandbox before you run the application, ThinApp stores the sandbox in z:\FirefoxSandbox.JOHNDOE-COMPUTER if the directory already exists. If the directory does not exist, ThinApp creates a sandbox in z:\FirefoxSandbox.
Controlling the Sandbox Location 23 The setup capture process adds the SandboxName parameter to the Package.ini file. If you capture Firefox and Mozilla Firefox 3.0 is the value of this parameter, the default location of the sandbox for the application is %AppData%\Thinstall\Mozilla Firefox 3.0. The typical %AppData% location is C:\Documents and Settings\\Application Data. %AppData% is often mapped to a shared network drive. You can store the sandbox on a network or on a portable drive.
ThinApp Package.ini Parameters Reference Guide Store the Sandbox on a Portable Device You can use the SandboxPath parameter to set a portable device location for the sandbox. You can use any portable device, such as a USB drive, that appears as a disk drive in the My Computer system folder. A portable device location is useful to keep the sandbox data on the device where the application resides. Procedure 1 Open the Package.ini file.
Sandbox Structure 24 ThinApp stores the sandbox using a file structure almost identical to the build project structure. ThinApp uses macro names for shell folder locations, such as %AppData%, instead of hard coded paths. This structure enables the sandbox to migrate to different computers dynamically when the application runs from new locations. The sandbox contains the following registry files: Registry.rw.tvr Contains all registry modifications that the application makes. Registry.rw.
ThinApp Package.ini Parameters Reference Guide Listing Virtual Registry Contents with vregtool Because the sandbox contains the modifications to the registry, you might need the vregtool utility to view modified virtual registry changes. You must have access to the vregtool utility in C:\Program Files\VMware\VMware ThinApp. A sample command to list the contents of a virtual registry file is vregtool registry.rw.tvr printkeys. 86 VMware, Inc.
Creating ThinApp Snapshots and Projects from the Command Line 25 You can use the snapshot.exe utility to create snapshot files of machine states, create the template file for the Package.ini file, create a ThinApp project, and display the contents of a snapshot file. Using the Command Line to Create Snapshots The snapshot.exe utility creates a snapshot of a computer file system and registry and creates a ThinApp project from two previously captured snapshots. You do not have to start the snapshot.
ThinApp Package.ini Parameters Reference Guide Usage snapshot.exe SnapshotFileName.snapshot [-Config ConfigFile.ini][BaseDir1][BaseDir2][BaseReg1 ] Example: Create Machine Snapshot Use the following example to create a machine snapshot. Snapshot My.snapshot Snapshot My.snapshot –Config MyExclusions.ini Snapshot My.snapshot C:\MyAppDirectory HKEY_LOCAL_MACHINE\Software\MyApp Options The options specify the directories or subkeys in the snapshot. Table 25-1.
Chapter 25 Creating ThinApp Snapshots and Projects from the Command Line Example: -Config ConfigFile.ini is optional. The configuration file specifies directories or registry subkeys for exclusion from the project. If you do not specify a configuration file, ThinApp uses the snapshot.ini file. Snapshot Template.ini –GenerateProject C:\MyProject Snapshot Template.ini –GenerateProject C:\MyProject –Config MyExclusions.ini Displaying the Contents of a Snapshot File The snapshot.
ThinApp Package.ini Parameters Reference Guide The snapshot process makes a copy of the all registry entries on the system and file system metadata. File system metadata includes path, filename, attribute, size, and time stamp information but excludes actual file data. Procedure 1 At the command line, runsnapshot.exe without adding any parameters. The help menu for the snapshot.exe utility appears. 90 2 Use the commands in the menu to create the ThinApp project. 3 (Optional) Delete the C:\Start.
Index Symbols ##Attributes.ini file, overrinding Package.
ThinApp Package.
Index ChildProcessEnvironmentExceptions 45 CommandLine parameter 57 CompressionType 47 DirectoryIsolationMode 19 DisableCutPaste parameter 80 Disabled parameter 58 DisableTracing 51 DisableTransactionRegistry parameter 80 ExcludePattern 25 ExternalCOMObjects 33, 34 FileType 23 ForcedVirtualLoadPaths 34 HidePrinters parameter 80 Icon 26 InventoryName parameter 75 IsolatedMemoryObjects 35 IsolatedSynchronizationObjects 35 LoadDotNetFromSystem parameter 80 LocaleIdentifier parameter 55 LocaleName parameter 56
ThinApp Package.
