VMware THIN4-CL-C Deployment Guide - Page 21

Recommended Practices

Page 21 highlights

##Attributes.ini file overrides the overall Package.ini setting. The Package.ini setting determines the isolation mode only when ThinApp does not have ##Attributes.ini information. To compress only certain folders with large files rather than an entire application, compress files at the folder level with the CompressionType parameter in the ##Attributes.ini file. The ##Attributes.ini file appears in most folders for the captured application. For example, the Attributes.ini file might be located in C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox\%AppData%\##Attributes.ini. Edit the ##Attributes.ini File Use Notepad or another text editor to update the ##Attributes.ini file. 9. In the ##Attributes.ini file, uncomment, update, or delete the parameter. 10. Double-click the build.bat file in the captured application folder to rebuild the application package. Recommended Practices Creation of the Package Digest VMware recommends that customers create a standardized document that details the components of a package for IT organizational use. The packaging process is iterative by nature and so it is necessary to have a controlled document which communicates the primary contents and deployment configuration. A package digest serves this function and is highly beneficial over the lifecycle of the application. Critical elements of a package digest are outlined below. Customers should include information specific to their environment to make the digest as useful as possible.  Source Application Files & Versioning Information  Project Directory Location  Deployment Objectives  Package.Ini settings  Isolation Mode settings and explanation for non-default settings  VBScripts Scripts used, the originating authors, script documentation, and their dependencies  Platform Testing results  Build Notation and Naming Conventions Control Access to Project Directories VMware recommends that administrators control access to the project directories and have regular backup procedures in place. The project directories become the source files for generating updated application packages and allow the administrator to incorporate changes without re-running the Setup Capture process. The project directories are also helpful for troubleshooting efforts because the specifics of the capture machine's configuration and application modules are contained in the project directory. Access should be restricted to administrators because some of the settings in the Package.Ini file provide sensitive information for access control and update locations. Once the application is packaged, this information cannot be changed by end users. 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32

##
Attributes.ini
file overrides the overall
Package.ini
setting. The
Package.ini
setting determines
the isolation mode only when ThinApp does not have ##
Attributes.ini
information.
To compress only certain folders with large files rather than an entire application, compress files at
the folder level with the
CompressionType
parameter in the
##Attributes.ini
file.
The ##Attributes.ini file appears in most folders for the captured application. For example, the
Attributes.ini file might be located in C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla
Firefox\%AppData%\##Attributes.ini.
Edit the ##Attributes.ini File
Use Notepad or another text editor to update the
##Attributes.ini
file.
9.
In the
##Attributes.ini
file, uncomment, update, or delete the parameter.
10.
Double-click the build.bat file in the captured application folder to rebuild the application
package
.
Recommended Practices
Creation of the Package Digest
VMware recommends that customers create a standardized document that details the
components of a
package
for IT organizational use. The packaging process is iterative by nature
and so it is necessary to have a controlled document which communicates the primary contents
and deployment configuration. A package digest serves this function and is highly beneficial over
the lifecycle of the application. Critical elements of a package digest are outlined below.
Customers should include information specific to their environment to make the digest as useful
as possible.
Source Application Files & Versioning Information
Project Directory Location
Deployment Objectives
Package.Ini settings
Isolation Mode settings and explanation for non-default settings
VBScripts Scripts used, the originating authors, script documentation, and their dependencies
Platform Testing results
Build Notation and Naming Conventions
Control Access to Project Directories
VMware recommends that administrators control access to the project directories and have
regular backup procedures in place.
The project directories become the source files for
generating updated application packages and allow the administrator to incorporate changes
without re-running the Setup Capture process.
The project directories are also helpful for
troubleshooting efforts because the specifics of the capture machine’s configuration and
application modules are contained in the project directory.
Access should be restricted to
administrators because some of the settings in the Package.Ini file provide sensitive information
for access control and update locations.
Once the application is packaged, this information
cannot be changed by end users.
21