Archive for ThinApp

How To ThinApp Microsoft Office 2010

This video guide will demonstrate how to ThinApp Microsoft Office 2010 by following the steps detailed within a guide posted by

What I’m Using:

- VMware Workstation 8

- Base Windows XP Pro VM

- Base Windows 7 Pro VM

- VMware ThinApp v4.7

- Microsoft Office 2010 Standard with MAK key

Key Points To Follow:

- You must create the ThinApp on a Windows XP machine

- You must disconnect your network connection to the Internet before you install Microsoft Office

If you follow this guide exactly you will succeed in creating a working ThinApp of Microsoft Office 2010 that can be activated.

Rebuild Your ThinApps with ReLink

In this post we will be a addressing the issue of receiving the error message ‘your runtime license has expired’ as shown below.

This message occurs when the license used to create the ThinApp has expired most commonly found with trial licensing. I had this very problem after creating a number of ThinApps for a proof of concept when they unexpectedly returned the above message. Thankfully VMware have included the ReLink application to deal with such issues allowing you to rebuild your ThinApps under a valid license.

To relink your ThinApps with a working license key, follow the simple steps below:

Step1. Copy all of the application files for your ThinApp to a computer that has a a valid ThinApp license running the ThinApp application.

Step 2. Open a Command Prompt windows by typing ‘cmd’ into the Run  box and navigate to the ThinApp application folder:

cd C:\Program Files (x86)\VMware\VMware ThinApp

Following this, type ‘relink.exe followed by the path and full name of your ThinApp.

Example: relink.exe “C:\Users\User\Desktop\PINs 4\PINs 4.exe”

Step 3. Press enter to execute the command and wait for the ThinApp to be built. If you have a separate .dat file as part of your ThinApp, also run the same command for this. If you have an MSI package, this will not need rebuilding with relink.

A successful output should look as follows:

Step 4. Within your ThinApp folder, delete and files with the extension .bak as these are the original builds of the application and are no longer required.

Thanks for reading and look out for my other ThinApp posts.

How to ThinApp Firefox with Integrated Flash and Java

This video will demonstrate how to ThinApp capture the firefox browser along with integrating both flash and java plug-ins.

VMware ThinApp Custom Entry Point

This is a short post on how to create a custom entry point in VMware ThinApp. You may have run into the problem before where you create a shortcut with a number switches and hope to be able to use this as an entry point, but when you run the ThinApp postscan the shortcut you created doesn’t show up as a selectable entry point.

The solution is simple. When you have created the entry point you want, simply rename the shortcut and add the extension .exe as shown below. This won’t affect the shortcut but will allow ThinApp to pick it up as valid executable.

In my example, I have an application shortcut as well as a shortcut to a text configuration file. I simply added .exe onto the file name to make it visible as an entry in VMware ThinApp.

Thanks for reading and look out for my other articles on VMware ThinApp


Run 32 Bit Apps on 64 Bit Platforms

With application virtualisation legacy applications can be made available on newer operating system platforms, in particular 64 bit architectures. VMware ThinApp is designed to allow 32 bit application run on 64 bit operating system natively out of the box, however with some applications this doesn’t always work as expected.

Within the ThinApp packager there is an option you can enable that allows the emulation of a 32 bit platform for your virtualised application allowing its use on a 64 bit operating system. The following steps detail how to enable this feature.

Step 1. Before building your application, edit your package.ini file by uncommenting the wow64=0 entry as shown below.

Step 2. Save your package.ini file and built your application.

Set ThinApp Application Name

In this post I will be showing you a simple way to define the name of you ThinApp application as sometimes it doesn’t always show up as expected.

Step 1. Before building your application, edit your package.ini file with the following entry under the header of your chosen entry point.

StatusBarDisplayName=App name

Step 2. Save your package.ini file and built your application, the application launch name should appear something like this.

VMware ThinApp with .NET Framework

With a lot of Microsoft applications .NET Framework is commonly required during installation. When trying to ThinApp these applications .NET Framework can be required as part of the virtualised app. This post will detail a step you may fine yourself needing to take if you experience .NET related problems with your ThinApp applications.

Basically, when you install .NET Framework not all components are executed and compiled during the time of installation. Some of these components can remain uncompiled until the application calls for them. If this is the case with an application you are trying to virtualise you may run in to issues launching the ThinApped application.

To get around this, during the installation period (After prescan, Before postscan) run the following command in a command prompt window.

C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

This will compile any remaining components within your .NET installation ready to be captured as part of your new ThinApp.

If all components have been compiled, the below message should be returned.

An Idiot’s Guide To VMware ThinApp

This post details a straightforward simple approach to creating your first virtualised application with VMware ThinApp. In this guide VMware ThinApp v4.7 is being used to virtualise Firefox v9.0.

Step 1. Load the ThinApp application and click next.

Step 2. When ready, click prescan to create a capture of your systems current state.

During the capture you can monitor the directories being scanned.

Step 3. Once the prescan has completed, install the application you wish to virtualise. In my case, Firefox.

Step 4. Once the application is installed and configured click postscan.

Step 5. After the post scan has completed you will be presented with a number of possible entry points for loading the application. Use the default selection and click next.

Step 6. Use the default setting of everyone and click next.

Step 7. Use the default setting of full write access and click next.

Step 8. On this step you can choose to have the application USB portable, or for desktop use by selecting where the application user data is written to. For this guide we will be using the default selection of writing application data to the users local profile and clicking next.

Step 9. In this step you have the option to specify a name for you application.

Step 10. Here you can select to use a single file to access your application or split it out into a data file and entry point. Splitting out the application is used when the application is particularly large or consists of multiple entry points. For this example I will stick with the default option and click save.

Step 11. Once the project has been saved, click build to start the application build process.

Step 12. Once the application has been build it will be visible withing the capture directory.

Step 13. Run the application.

Thanks for reading and look out for my future posts on advanced ThinApp configuration.

Update Your ThinApps With AppSync

In this post i will detail how to use the AppSync feature within VMware ThinApp. This is one component of ThinApp that doesn’t appear to get much attention but is quite impressive all the same. AppSync basically allows you to update your ThinApps to a newer version by pre defining an AppSync location within the ThinApp ‘package.ini’ during the build sequence. When you run a ThinApp configured to check for updates, it will go off and query the defined AppSync target and download any updates in the background whilst the current version of the ThinApp is running. On completion, the new version will be available when the ThinApp is next launched. The below steps will detail how to use AppSync with any newly created ThinApps.

Step 1. Create a file repository on either a server or workstation and share this folder for all on your network. I created two shared folders called ‘Apps’ and ‘AppSync’. One for my live applications, and one for the updates.

Step 2. Once you repositories are setup and can be accessed over the network, processed to create a ThinApp capture of the application you want to use. In my case i used Firefox, I created two captures for version 9.0 and version 10. For help on this step see articles:


Step 3. Once you have captured and saved you application, edit the package.ini file before building you ThinApp. Within the package.ini file, uncomment the relevant AppSync parameters for both of your ThinApp applications as shown below:

The key parameter is the ‘AppSyncURL’ entry that’s defined where the ThinApp points to for AppSync updates. To defined a network shares you must enter the path with inverted slashes not commonly used for network paths, for example use file://thinappsrv/AppSync/Firefox.exe opposed to file:\\thinappsrv\AppSync\Firefox.exe. For reference on all of these parameters, see for further information.

Stepm 4. Once you have built your ThinApps, place the most recent version into the file location the ThinApps are pointing to for AppSync updates. In my case i will place Firefox version 10 in this folder, followed by placing Firefox version 9 in the Apps folder where users will access the app from. On running the older version of your application, you will be able to  witness the AppSync updates being pulled over the network to the application folder.

To see this process in action please view the below video as it illustrates in detail how to setup your AppSync environment after building your ThinApps.

Thanks for reading this post and lookout for future ThinApp articles.