VMware ThinApp(무설치, 포터블) 설치 및 사용 메뉴얼

 

 

▣ VMware ThinApp 관하여 ...,

Register for your free 60-day evaluation of VMware ThinApp. VMware ThinApp makes it easy for application owners to eliminate application conflicts and to securely package virtualized applications for physical and virtual desktops throughout the enterprise. Learn more about VMware ThinApp

관련 홈페이지 : http://www.vmware.com/go/trythinapp 

 

 

▣ Install VMware ThinApp

 

 

Use the ThinApp.msi file to install ThinApp. For information about the directory that the installation creates, see ThinApp Directory Files.

 

To install ThinApp

 

1	Download ThinApp to a clean physical or virtual Windows machine.

2	Double-click the ThinApp.msi file.

3	Accept the license, enter the serial number, and enter the license display name that will appear when you launch applications captured by ThinApp.

4	Click Next to install ThinApp.

 

 

▣ Capture an Application with the Setup Capture Wizard

 

Use the Setup Capture wizard to package an application and set initial application parameters. If you use a virtual machine, consider taking a snapshot prior to running the wizard. A snapshot of the original clean state allows you to revert to the snapshot anytime you want to capture another application.

 

To capture an application with the Setup Capture wizard

 

1	Download the applications you want to capture.

For example, download Firefox Setup 2.0.0.3.exe and copy it to the clean machine you are working with.

 

2	Go to Start > Programs > VMware > ThinApp Setup Capture.

3	(Optional) In the dialog box that clarifies the definition and use of a clean computer, click the Advanced Settings button to select the drives and registry hives to scan.

You might want to scan a particular location other than the C:\ drive if you install applications to a different location. In rare cases, you might want to avoid scanning a registry hive if you know the application installer does not modify the registry.

 

4	Click Next to begin the first snapshot of the hard drive and registry files.

The scanning process takes about 10 seconds for Windows XP.

 

5	Minimize the Setup Capture wizard and install the applications you want to capture.

For example, double-click Firefox Setup 2.0.0.3.exe to install Firefox. If the application needs to reboot after the installation, reboot the system. The reboot launches the Setup Capture wizard again.

 

6	Make any necessary configuration changes to comply with your organization’s policies, such as using specific security settings or a particular home page.

If you do not make configuration changes, each user will have to make changes that might lead to inconsistent setup.

 

7	(Optional) Launch the application and address any prompts for information prior to continuing with the Setup Capture wizard.

If you do not address any prompts ahead of time, every user who uses the application will have to go through that process during the initial launch.

 

8	Close the application.

9	Maximize the Setup Capture wizard and click Next to proceed with another snapshot of the machine.

ThinApp stores the differences between the first snapshot and this snapshot in a virtual file system and virtual registry.

 

10	Specify the entry points, primary data container, and inventory name:

a	Select the check boxes for user-accessible entry points.

Entry points are the executable files that start the virtual application. The entry points you can choose from depend on the executables that your captured application creates during installation.

For example, if you install Microsoft Office, you can select entry points for Microsoft Word, Microsoft Excel, and other applications that are installed during a Microsoft Office installation. If you install Firefox, you might select Mozilla Firefox.exe and Mozilla Firefox (SafeMode).exe if users require safe mode access.

If you generate MSI files instead of executables and deploy the application on target machines, these entry points create desktop shortcuts.

For information about the cmd.exe, regedit.exe, and iexplore.exe entry point choices, see Entry Points for Troubleshooting.

b	Select the primary data container, the file that stores virtual files and registry information, from the list based on the selected entry pointed.

•	If the size of the container is smaller than 200MB, ThinApp creates a .exe file as the primary container. For a small application such as Firefox, any .exe file can serve as main data container.

•

If the size of the container is larger than 200MB, ThinApp creates a separate.dat file as the primary container because of problems associated with large .exe files, such as the inability of Microsoft Windows to show shortcut icons stored in large .exe files. ThinApp generates small .exe files along with the .dat file to store the icons for Windows to display.

•

If the size of the primary container is between 200MB and 1.5GB, ThinApp creates the default .dat file but you can override the default and select a .exe file. This choice generates a warning that you can dismiss. This selection allows all applications to work properly but might prevent the proper display of icons.

c	(Optional) Change the inventory name that ThinApp uses for internal tracking of the application in the Package.ini file.

ThinApp uses the inventory name during the update process with the Application Sync utility.

 

11	(Optional) Select the Active Directory groups that you want to authorize for access to the application and the sandbox location:

a	Click Add.

•	To specify objects, click Object Types.

•	To specify a location in the forest, click Locations.

•	To search of object names, enter the names according to the examples in the dialog box.

•	To locate user names in the Active Directory forest, click Advanced and use the Common Queries tab to search for groups according to names, descriptions, disabled accounts, passwords, and days since the last login.

For example, you might restrict access to an application to ensure users do not pass it to unauthorized users.

b	Select the ThinApp sandbox location depending on whether you want to deploy it to a local user machine, carry it on a mobile USB stick, or store it in a network location.

If you deploy the sandbox to a local machine, use the user’s profile. If you store the sandbox in a network drive, enter the relative path to the location where you want the sandbox created. A sample path is \\thinapp\sandbox\Firefox. You can select a network locations even if an application is installed on a local machine.

 

12	Select the isolation mode to determine which files and registry keys are visible and written by the virtual application you create:

•	To allow the application to read resources on and write to the local machine, keep the default Merged isolation mode.

This means that the application can modify elements outside of the virtual application package. Some applications rely on DLLs and registry information in the local system image. VMware recommends this mode for applications that do not write to system directories, such as Firefox. ThinApp directs write operations to the physical file system, with the exception of the following directories and their subdirectories that redirect write operations to the sandbox:

•

%AppData%

•	%Common AppData%

•	%Local AppData%

•	%Program Files Common%

•	%ProgramFilesDir%

•	%SystemRoot%

•	%SystemSystem%

The advantage of using Merged isolation mode is that documents saved by users end up on the physical system in the location expected by users, instead of in the sandbox. The disadvantage is that this mode might clutter the system image. An example of residue might be first-execution markers by shareware applications written to random computer locations as part of the licensing process.

•	To allow the application to read resources on the local machine and restrict most modifications to the sandbox, select the WriteCopy isolation mode.

ThinApp intercepts write operations to all directories and redirects them to the sandbox, with the exception of the following directories and their subdirectories that redirect write operations to the physical system:

•

%Desktop%

•	%Personal%

•	%SystemSystem%\Spool

Regardless of the choice for Merged or WriteCopy isolation mode, ThinApp treats write operations to network drives according to the SandboxNetworkDrives parameter in the Package.ini file. This parameter has a default value of 0 that directs write operations to the physical drive. ThinApp treats write operations to removable disks according to the SandboxRemovableDrives parameter in the Package.ini. This parameter has a default value of 0 that directs write operations to the physical drive.

VMware recommends this mode for legacy or untrusted applications. Although the WriteCopy mode might make it difficult to locate user data files that reside in the sandbox instead of the actual system, this mode is useful for locked down desktops where you want to prevent users from affecting the operating file system and registry files.

 

Note Any modification to any virtual element in the captured application package is stored in the sandbox, regardless of the isolation mode setting. If you capture Microsoft Office and use group policies, isolation modes do not affect the application because group policies can apply registry changes only to the physical environment. Virtual and physical registry elements appear as one to the captured application. If virtual entries exist for the registry, the Merged isolation mode cannot affect the application because Microsoft Office resorts to the virtual entries instead of physical entries. If necessary, remove such virtual entries to ensure the application affects the physical system, regardless of the isolation mode.

13	(Optional) Change the directory where you want to save the application package.

The package stores the captured software applications. If you keep the default directory and capture Firefox 2.0.0.3, the path might appear as C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox (2.0.0.3).

 

14	(Optional) Select the Build MSI package check box and change the MSI filename.

A typical Firefox application does not require an MSI installation. But other applications, such as Microsoft Office that integrate with application delivery tools, work well as an MSI package. MSI generation requires you to install the MSI on the target device before you can use the application package.

Unlike executable files that involve running the thinreg.exe utility on every machine to register file-type associations, register desktops shortcuts, display control panel extensions, and more to facilitate file launching, an MSI package automates this process when you deploy the application on target machines.

 

15	(Optional) If you want a lighter executable file for locations such as a USB stick, select the Fast compression radio button.

In typical circumstances, compression reduces the on-disk storage requirement by 50 percent but slows performance to uncompress the package on target machines.

 

16	Click Next to create the ThinApp project.

17	In the final dialog box, launch one of these options and click Finish.

•	Click Browse Project to look at the ThinApp project files in Windows Explorer.

For example, if you captured Firefox 2.0.0.3, the location of the project files might be C:\Program Files\VMware\VMware ThinApp\Captures\Mozilla Firefox 2.0.0.3. You might browse the project prior to building the application executable or MSI file to update a setting, such as an Active Directory specification, in the Package.ini file that contains the parameters set during the wizard.

The project includes folders, such as %AppData%, that represent file system paths that might change locations when running on different operating systems or computers. Most folders have Attributes.ini files that specify the isolation mode at the folder level. The isolation mode setting at the granular folder level overrides the overall isolation mode setting of the Package.ini file.

•	Click the Build Now button to build an executable or MSI file containing the files you installed during the Setup Capture process. The build output appears in the display box.

You can rebuild the project at any time after clicking Finish if you need to make changes.

Entry Points for Troubleshooting

If you want to troubleshoot or debug your environment, you can select these entry points during the setup capture process:

•	cmd.exe – Starts a command prompt in a virtual context that allows you to view the virtual filesystem.

•	regedit.exe – Starts the registry editor in a virtual context that allows you to view the virtual registry.

•	iexplore.exe – Starts iexplore.exe in a virtual context that allows you to test virtualized ActiveX controls.

Entry points start native executables in a virtual context. Entry points do not create virtual packages of cmd.exe, regedit.exe, or iexplore.exe.