Updating existing ThinApp packages

In the previous section, we looked at how to create a brand-new ThinApp package to deliver as an AppStack; however, what if you already have a number of ThinApp packages in use today and they are not .msi-based packages? What now?

In this section, we are going to cover two ways of tackling this scenario.

The first involves taking an existing .exe-based ThinApp package containing Audacity 2.1.1; updating its configuration to allow it to be provisioned as an AppStack, basically turning it into a .msi file; creating the AppStack; and then assigning the AppStack to one of our Example Lab end users.

The second option is to take the original .exe and .dat ThinApp packaged files and then, using the THINREG.EXE command, create a new AppStack, attach it to the provisioning virtual desktop machine, and then register the package rather than install it, before assigning the AppStack to one of our Example Lab end users.

Before we start looking at either of these options...