Back in March VMware Labs released this Fling. We thought it was worth pointing to again. Jonathan Clark from VMware gives a demo of the VMware ThinApp version of the popular VMware vSphere Client. This VMware Labs Fling uses VMware ThinApp to package vSphere Client into a single portable EXE giving you instant access to your virtual infrastructure from any computer.
VMware Thinapp clients are easy to install and port. All it takes is copy/download the exe file and running on Windows machine, then connect to an existing vSphere server and you are all set to go. It is that easy! To learn more visit http://labs.vmware.com/flings/thinapp-vsphere.
ThinApp has been used by corporate administrators to deploy thousands of applications to millions of desktops. Use VMware ThinApp to create your own virtualized applications, for more information visit the VMware ThinApp page.
A recent KBTV video discusses Isolation Modes in VMware ThinApp. Isolation modes allow you to control the degree to which a virtualized application can read from and write to the local, physical PC where the virtual application resides.
ThinApp automatically configures isolation modes for directories in the file system and for registry subtrees in a ThinApp project. You can change the default isolation modes. Our video includes an overview the theory of isolation modes and how to implement them in practice.
Just to clarify.. ThinApp will not magically make an application run on Windows 7 if it is not supported on Windows 7. That said, we do offer some help with ThinApp. Great examples are Internet Explorer 6, Adobe Reader 5 and Lotus Notes 6.5.6. All not running natively on Win7 but does so with the help of ThinApp. It may be tricky to find the solution and there are no guaranties. The work around is often to include older Windows XP dlls into the package and that might make the application run on Win7.
Best practices packaging with ThinApp includes verifying nothing is being left running, locking the Sandbox, when the end-user shuts down the application. A simple method to verify nothing is running in the background is to try to delete the package’s Sandbox. If it is locked and you cannot delete it, something is still running.
To find out what it is I always use Sysinternals Process Explorer. This video will show you how to use Process Monitor to find out what is keeping the Sandbox opened.