Download VMware ThinApp User`s Manual
Transcript
Chapter 5 Deploying and Working with Virtual Applications Example Package.ini Files for Active Directory Access Control In the following example, App1 and App2 will both inherit PermittedGroups from BuildOptions. [BuildOptions] PermittedGroups=Administrators;OfficeUsers [App1.exe] ... .. [App2.exe] ... ... In the following example, App1 users can use App1.exe and members of the Everyone group can use App2.exe The default message for denied user is also changed for App1. [BuildOptions] PermittedGroups=Everyone [App1.exe] PermittedGroups=App1Users AccessDeniedMsg=Sorry, you can’t run this application .. [App2.exe] ... ... Application Updates If an application has built‐in auto updating capabilities, its update mechanism still functions when running under ThinApp. If the application downloads and runs an installer or patching program, this runs inside the virtual environment, and all of the changes made by the update software are written to the sandbox. When the application restarts, it uses the version of the executable in the sandbox, and not from the original package. For example, if you capture Firefox 1.5, your auto update mechanism might ask if you want to upgrade to Firefox 2.0. If you do, it downloads updates, writes them to the sandbox, and prompts you to restart. When you run the captured application again, you are running Firefox 2.0. If you delete the sandbox, Firefox reverts back to version 1.5. The VMware ThinApp Sandbox Merge utility can be used to merge changes made by an application’s update mechanism into the original package to build an executable to redeploy to end user machines. For more information on sbmerge, see “Using Sandbox Merge (sbmerge)” on page 127. VMware, Inc. 85