September 15, 2011 - Sven Huisman

VMware ThinApp Factory, Technical Preview

At VMworld 2011 in Las Vegas I attended the Hands-on lab “Solving Application Management Challenges with Application Virtualization” (HoL23). A big part of this HoL is about ThinApp, from basic to more advanced. If you are going to Copenhagen and take this lab AND you already know ThinApp, I advise you to skip chapter 1 to 3 and start with chapter 4, because you don’t have time to complete the entire HoL(lab manual is 238 pages). Chapter 4 is about a technical preview of ThinApp Factory. To be clear, this was not even Beta code but I was already impressed by the product and the features it will have. Here is my impression of ThinApp Factory (with screenshots!).

When you logon to the ThinApp Factory console through a webbrowser, the first thing you see is the ThinApp Factory Dashboard


The next thing you want to do is to add a File share or Feed to the application sources. In this location the source files are located that needs to be converted to a ThinApp application. Go to “Application Sources>File Shares>Add” and fill in the required fields.


You can select “OK to scan” so ThinApp Factory will scan the directory at a given interval to check if there are new applications to convert. If you select “OK to convert” applications will also automatically be converted.

If you not want applications automatically be converted, you will need to initiate this process. Go to “Applications>All Applications”.


You can now select the applications you want to convert. This can be done automatically (depending on the source file, for now it needs to be an unattended MSI build) or a manual capture can be started (which I will show later on).

You can also add Feeds as application sources:


A feed consists of one or more applications. Every application in a feed is defined by a combination of “name”, “version”, “locale” and “installerrevision”. When a new version of an application is made available via a feed, ThinApp Factory can automatically download the application and convert it into a ThinApp package without any user intervention.


Now back to the conversion. Here I select “Notepad++” to be converted and as you can see the source is from a feed.


Then click on “Build Selected…”


Here you can specify which Work pool (which virtual machine to use) when capturing the application. I can imagine you sometimes need to package on Windows XP and sometimes on Windows 7. You can also choose what default settings your project should have (for example: different package.ini settings).

After selecting “OK” you can see the converting progress under “Tasks”:


In the background a capture VM is started and the ThinApp capture is started with a command script. After the capture is completed, ThinApp Factory will remove the snapshot of the VM, so the capture virtual machine is at a clean state when the next conversion takes place.

When the conversion is ready, the ThinApp application is placed under “Staged Builds:


You can select the application and click on “Publish”.


The Application is now available in the ThinApp Store (which is part of the ThinApp Factory appliance).


Select the application and click on “Get Applications”


The application is now downloaded to the client.


What if I want to customize the automatically converted application? That’s also possible with ThinApp Factory. Go to Staged or published applications, select the application and click on “Edit”. You can edit all the settings of the ThinApp application, like the package.ini:


Or the registry through a GUI (finally!):


If you edit a package the application needs to be rebuilded. A rebuild does not require to start a virtual machine, this is done by the ThinApp Factory appliance.

As I mentioned, you can also manually capture an application. After you imported an application you can select it and click on “Manual capture…”. A nice interface pops up describing all the steps needed to be taken: Preparing, Customize VM, Pre-capturing, Install, Finishing.


The idea is that ThinApp Factory will be the management console for all your ThinApps. Both automatically converted and manually captured ThinApp applications centrally stored and publsihed.

So now you have seen the ThinApp Factory and the ThinApp Store. So what’s next? ThinApp Factory is going to be integrated with Horizon App Manager eventually. What potentially also is possible that users can upload applications (or a feed) to the ThinApp Factory so that the application will be converted to a ThinApp and published to the user through the ThinApp Store or Horizon App Manager. Then you will have user installed applications (think about stateless VDI).

By the way, the information published in this blogpost was not NDA information. I checked with VMware and it was OK to publish information that was presented or available in the labs.

Virtual Applications / VMworld 2011 Vegas Horizon App Manager / Thinapp / ThinApp Factory / VMworld 2011 /


  • Thanks for the great post and information, can’t wait to get my hands on this! The only thing I will comment on is the statement regarding “User Installed Applications” being a possibility. The way it is described above is not really User Installed Applications (UIA). Regular end users will not understand the concept of having to download the software they need/want; then have to go to a site to upload the software; and then go to another site to run it. On top of the learning curve is the likely hood of the Thin App process not working or users uploading apps they shouldn’t. User Installed Applications are mainly things like Active X controls, meeting software, and other things that are needed on demand. UniDesk and RingCube (now Citrix) have good examples of UIA where users can install the applications or plugins they need on demand to layer or personal virtual disk. I do not think VMware is nieve enough to believe this would be a viable answer to competitors UIA implementations…

  • […] captures d’écrans en Tech-Preview de ThinApp Factory sur le blog Virtual […]