by Diana Tsao, Product Marketing, End-User Computing
Last week, VMware announced the Horizon Suite, a comprehensive platform for workforce mobility to connect users to their data, applications, and desktops. Along with delivering new features and functionality, we have streamlined the packages for the Horizon family of products.
Packaging changes include the End of Availability of VMware ThinApp and VMware View Enterprise. Don’t worry – End of Availability does not mean End of Life! EOA means the current packaging will be discontinued, but the functionality is still available. End of Life (EOL) means the product will no longer be offered nor be supported by VMware.
ThinApp is absolutely not going away as application virtualization is a core enabling technology for the Horizon Suite. To that end, we have included it in ALL of the Horizon family products.
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.
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.