ThinApp – Part 2: Capturing Applications

ThinApp – Part 2: Capturing Applications

  In this part, we will list basic steps for capturing Applications with Thinapp. There are three steps that need to be followed, and these are;

These are:

1. On clean machine, run ThinApp prescan and then install the application (it can be physical or virtual Windows machine with fresh installation). (Prescan takes a snapshot of the current state of the machine)
2. After the install, Thinapp does postscan to get another snapshot of the system and registry.
3. Thinapp project is then created using the differences between two snapshots.

Before capture, it is best practice to take VM level snapshot so that you can return back to base golden image for capturing other applications in clean state.

ThinApp supports 32 and 64 bit Windows platforms. For all supported platforms, please visit documentation center of ThinApp.

During capture process, the limitations of ThinApp is that it cannot virtualize:

• Ay component embedded in OS
• Apps requiring kernel mode device drivers
• Antivirus and Personal Firewalls
• Scanner Drivers and printer Drivers

First of all, thin app needs to be installed on a clean image that will be used for capturing: Run thinapp setup capture from the network share…Installation is very easy, just follow the steps on screen to install ThinApp Setup. The files installed can be seen in the following picture.

Capturing Apps:

Start the capture Wizard

Click prescan

Install Application and click postScan

You can put app data or files into package, like customizations, templates, extra documents before postscan. After postscan, snapshots are created under “Local Settings\Temp”. Select files you want to have available for users:

Some of the apps listed here is for troubleshooting and not for end user, such as: 

• cmd: Access to virtual systems
• regedit: access to virtual registry
• iexplore.exe: debug Internet related apps

If Horizon Workspace is installed, you can configure in the next screen:

Select authorized groups:

Sandbox location:

Isolation Mode:

Project location:

Primary data Container

Sometimes MSI can be chosen over EXE:

• App registers in add remove programs
• can be displayed in file association list and shortcuts in the computer
• When traditional desktop management is used to deploy to remote locations, msi might be needed to manage lifecycle.
• For deployment with Vmware View,
• If using AD GPO to push apps or deploy polices

Put in Captures Folder:

You can further edit ini file before build

For Updating the Thinapp, we have 4 options:

1. Versioning: Suffix files with version numbers, Thinapp  selects the Highest sequential number. Ex, app.1 app.2 (Sandbox is not deleted)
2. SMBMerge.Exe: Merges runtime changes back into ThinApp project
3. Application Sync: Updates over Http and https automatically (Admin puts updates to Web/Update Server)
4. Relink.exe: to update the existing package to the latest version of ThinApp.

Hope Helps!

• Author
• Recent Posts

Bulent Tolu

Systems Engineer at Veeam

Bulent is an IT professional with MSc in MIS and close to 20-years of experience in broad range of technologies. He has a passion to continually research, test and evaluate new technologies and follow industry best practices to secure and optimize IT systems and solve IT challenges for enteprises. Currently, he lives in Ankara and works as Systems Engineer at Veeam.

Latest posts by Bulent Tolu (see all)

• VMware Identity Manager – Workspace ONE – Provide Access to Horizon Desktops and Apps & Workspace ONE mode - 17 September 2017
• VMware Identity Manager 2.9.2 – Workspace ONE – Installation in DMZ with Outbound-Only Connection Mode - 17 September 2017
• Deploy Unified Access Gateway (UAG) 3.0 with Horizon - 17 September 2017