VMware ThinApp 5.1 released

VMware released at September 9 ThinApp 5.1

VMware ThinApp 5.1 is the latest version of ThinApp. This release has the following enhancements.

Release notes are here 

ThinApp is part of the VMware Horizon Suite. Download here

ThinApp Package Management

In earlier versions of ThinApp, to change some specific Package.ini parameters, you had to first make those changes in the configuration file, save the file, and rebuild the package. Using the new ThinApp package management feature, you can dynamically reconfigure the attributes of deployed ThinApp packages at runtime. ThinApp Package management helps IT administrators manage ThinApp packages and define group policy for each package. Each package to be managed must have an associated group policy defined using its inventory name.

When you install ThinApp 5.1, a new folder named Policy is created in the installation directory. This folder contains tools and templates for managing ThinApp packages and contains the following files:

  • AppPolicy.exe
  • README.TXT
  • ThinAppBase.adml
  • ThinAppBase.admx
  • ThinAppGeneric.adml
  • ThinAppGeneric.admx

ThinApp selects the policy precedence when you rebuild a package and deploy it. If a package is managed by a group policy, ThinApp gives precedence to the policy over its Package.ini configuration.

Group Policy Administrative Templates

ThinApp 5.1, introduces the group policy administrative template (ADMX/ADML) files. With these template files you can reconfigure group policy settings for applications that were packaged by ThinApp. The GPO files work on domain controllers that run in the following environments:

  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012

Administrative Template files contain markup language that is used to describe a registry-based Group Policy. The administrative files are divided into language-neutral (.admx files) and language-specific resources (.adml files), available to all Group Policy administrators. These factors allow Group Policy tools to adjust the user interface according to the administrator’s configured language.

Reconfiguring Attributes of Deployed ThinApp Packages

In addition to ThinDirect, with ThinApp 5.1 you can now reconfigure or manage the following attributes of a deployed package:

  • AppSync
  • AppLink
  • Entry-Point Shortcuts

Note: To know how to reconfigure these package attributes, see the ThinApp 5.1 User’s Guide.

ThinDirect

In ThinApp 5.1, the following enhancements have been made to the ThinDirect plug-in:

    • Support for the update of ThinDirect settings at specified time intervals

In ThinApp 5.1, the ThinDirect functionality has been enhanced to periodically poll for the ThinDirect setting changes. Since, the ThinDirect settings are now detected dynamically, the user need not restart the browser to view the updated changes.

    • Support for dynamic changes to Thindirect via ADM

In ThinApp 5.1, you can use ThinDirect.ADM file to manage the thindirect enabled firefox.

    • Support for Overriding the Thindirect settings through GPO

In ThinApp installation directory, locate the Thindirect.admx andThinDirect.adml files. Use these files to manage the settings for ThinDirect feature by defining a group policy object. If the Thindirect feature is defined through the GPO, these settings would override the text file (thindirect.txt) based redirection.

    • Support for Redirection between two virtual browsers

ThinApp 5.1 supports redirection between two virtual browsers.

    • Support for Thindirect in Mozilla Firefox

In ThinApp 5.1, ThinDirect has been enhanced to work with Mozilla Firefox version 22 and later. In earlier versions of ThinApp, ThinDirect was limited to Internet Explorer.

New Package.ini Parameter Introduced

ThinApp 5.1 introduces the SandboxWindowClassName parameter. When you set theSandboxWindowClassName=1 you can sandbox or isolate the application defined window class names created and used within the ThinApp package.

Extracting an existing ThinApp project to a system

ThinApp 5.1 allows you to extract an existing ThinApp project to a capture and build operating system by using snapshot.exe and snapshot64.exe commands.

Pre-requisites
Before you extract an existing ThinApp project to a capture and build operating system, ensure that the following conditions are met:

  • Verify that the architecture and type of the captured operating system is the same as that of deployed operating system.
  • Perform the extraction of an existing ThinApp project on a clean capture and build machine.
  • Ensure that the user profile in the existing virtual project is the same as that of the capture and build machine.

ThinApp 5.1 has the following command line options to extract existing projects to capture and build operating systems.

  • snapshot.exe: Is used to extract an existing ThinApp project to a capture and build 32-bit operating system
  • snapshot64.exe: Is used to extract an existing ThinApp project to a capture and build 64-bit operating system

Note: To know more about the process for extracting existing ThinApp packages, see the ThinApp 5.1 User’s Guide.

MAPI Support

ThinApp 5.1 supports the Messaging Application Programming Interface (MAPI) on the following Microsoft Windows platforms:

  • Windows 7
  • Windows 8 32-bit
  • Windows 8 64-bit
  • Windows 8.1 32-bit
  • Windows 8.1 64-bit

ThinApp 5.1 provides the DefaultEmailProgram option in Package.ini to register a virtual email client as the host’s default email program. You have to enable this option to register the default email program. The Messaging Application Programming Interface (MAPI) is not supported on Windows XP x86 operating system. For more information, see KB artilce2087898.

Support for Internet Explorer 10 and Internet Explorer 11

ThinApp 5.1 supports Internet Explorer 10 and Internet Explorer 11 only on the Windows 7 operating system.

Support for Windows 8.1

ThinApp 5.1 works on the Windows 8.1 August update (Update 2).

For additional information about ThinApp 5.1, visit the following Web site:

Add a Comment

Your email address will not be published. Required fields are marked *

Current ye@r *