
With its soulmate VMware by its side for support, the recently renamed ThinApp is now taking its first tentative steps into adulthood. With its chief competitors already paired off and dancing up a storm, Thinstall looked more and more like the lonesome loser, dateless and stag at the junior prom.įortunately, this awkward teenager eventually grew up. Also, watch instructional videos made by John at wallflower: That's how I used to describe Thinstall when discussing the movers and shakers of the application virtualization party scene. Can I link VMware ThinApp virtual applications so they can see one another?Ĭheck out hundreds more useful Q&As like this in John Savill's FAQ for Windows. Does VMware ThinApp use an agent on the client computer? Are there any limitations to the types of applications I can virtualize with VMware ThinApp? This option copies the ThinApp to the local PC as well as registering shortcuts and file type associations. This access is determined based on groups encoded in the application and the user's group memberships.Īnother option is to generate MSI files and deploy to computers using normal MSI deployment techniques. The logon script calls ThinReg to register all the applications from the network share containing the ThinApps, based on the applications to which the user has access. To create the shortcuts and associations, use ThinReg.exe, which is placed on a file share or logon folder. You need to place shortcuts on user desktops and create file extension associations (so that if someone clicks a DOCX file, ThinApp Word is launched). Instead, you typically place ThinApp applications on a network share, USB drive, or local hard drive.

Because there's no agent for ThinApp applications, there's no client side service to check for applications and pull them down.
