In this blog post will explain how you can configure VMware UEM 9.x to provide integration with VMware ThinApp applications.

Using the integration, you can centrally manage default and mandatory application settings with VMware UEM for ThinApp packages as well.

ThinApp integration

In the VMware UEM Admin console, you might notice when you open an application, there is a little checkbox to Enable ThinApp Support on the DirectFlex tab.

TI-2

As you might suspect; this option will enable the ThinApp integration. The best part of selecting this checkbox, is you don’t have to capture or reconfigure the application with the Merged Isolation Mode anymore like you used to do before this option was available. It really doesn’t matter in which isolation mode the package is created, because VMware UEM will be able to manage the application inside the virtual “bubble”.

In order to make the ThinApp integration possible, the only requirements are:

  • VMware UEM 9.0 and higher
  • ThinApp 5.2 and higher. For Windows 10, it’s advisable to upgrade to version 5.2.2, as explained in my previous blog post
  • Just like any other application in VMware UEM, you need to know where the user settings will be stored. VMware supplies a very helpful tool to figure this out; the VMware UEM Application Profiler. Please note, only natively installed applications are supported with this tool.

Virtual Executable

When selecting the application executable, an important thing to note is you must select the virtual executable (i.e. the executable which runs inside the virtual “bubble”), and not the ThinApp package executable itself.

The virtual executable is retrieved when looking at the package.ini

Inside, there is a chapter with the ThinApp executable name. In below example 7-Zip File Manager.exe. In the source line, the virtual executable is listed, in this case 7zFM.exe.

TI-3

Next, we configure this virtual executable in VMware UEM. You only have to configure the executable name, not the entire virtual path as well.

TI-4

 Last step – conformation.

The last step is to check if everything is working correctly. Log on with a (test) user and launch the application. When the application is correctly “profiled” (see requirements above) You should notice two things:

  1. In the Profile Archive share, there will be a .zip file created for the application, meaning the user settings are saved.
  2. A FlexEngine-ThinApp.log will be created in the same folder containing the FlexEngine log files. This log will allow you to do some basic troubleshooting, if needed.