Over the last four years I’ve been working with customers and partners on articulating and demonstrating the value of VMware ThinApp. While ThinApp does offer one of the most flexible and streamlined solutions for virtualizing Windows applications there are still times when you need to put the product knowledge and the application expert together to get the results you want. That has now occurred in written (and ebook) form with the release of the definitive guide for VMware ThinApp. The title, VMware ThinApp Essentials, much like the author, is understated as you will find the relevance of this book greatly exceeds the ‘essentials’. Yes, the author is one of our own VMware employees, but see for yourself that Peter Bjork always speaks to the reality of the customer environment and the satisfaction of well-implemented technology. Leverage Peter’s dedication to the technology, wide spectrum of application experience, and commitment to help you extract the most value out of your investment in application virtualization.
Deploying ThinApps with the help of VMware Horizon Workspace Application Manager is a great method, but what about updating? Horizon supports updating ThinApp packages and this blog post will walk you through one method of doing that.
This blog post was initially created for Horizon Application Manager. The same principles apply for Horizon Workspace.
Launching a ThinApp from Horizon Shows a Prompt for the First Time:
Do you or your users get an error “Do you want to allow this website to open a program on your computer?” prompt the first time they go to launch a ThinApp package in Horizon?
Often times we hear how someone is trying to publish a ThinApp Package via Horizon and not getting an icon. Continue reading
Many times you have to find out what processes are actually running within the virtual environment. I’ve already posted one method found here: (http://blogs.vmware.com/thinapp/2011/04/whats-keeping-my-sandbox-locked.html) but now it’s time for yet one more method.
This method uses an Entry Point running regedit.exe within the virtual environment. When you navigate the virtual registry you can see a HKEY_LOCAL_MACHINE\Software\Thinstall\ProcessList key. Looking in this key you’ll see the list of processes correctly running.
By Joshua Spencer, End User Computing Specialist, VMware
Over the years there has been much debate about which display protocol provides the best performance while being the most efficient. I think the debate is finally over, and the blog post you can find here goes a long way toward ending it. Leveraging the PCoIP protocol and the PCoIP Secure Gateway Server, VMware is helping end users stay connected from anywhere, at any time, using any device they choose.
We can think of connecting to a VMware View desktop using PCoIP as a client/server application. The virtual machine, which resides in the datacenter, gets the VMware View Agent installed. Because PCoIP is completely host-side rendered, this agent acts as the PCoIP server. On the end point device, we install the VMware View Client, which serves as the PCoIP client. The PCoIP server (View Agent) encrypts and compresses display information and sends it down to the View Client where the display is rendered on the screen.
What this means is that the View Client has to be installed on every end point that will connect to a VMware View desktop. Installing the client is a simple process of connecting to a website and running the executable.
The client includes two drivers: one for Virtual Printing and another for Advanced USB Redirection. Because of this, the View Client requires local administrative privileges for installation. While local admin privileges are not usually an issue on personal or IT-managed devices, I have seen a number of customers encounter situations where they cannot install the VMware View Client. VMware View is a highly adopted technology in the healthcare industry. Healthcare professionals often roam to multiple clinical sites throughout their network, and View provides a means of accessing a standard desktop workspace from any location. But what happens if he or she cannot install the View Client due to lack of permissions on a given PC? Likewise, I have seen this come up on public kiosk-like computers. For example, you are at a public library and you want to connect to your View desktop to get some work done. Library and other public-facing machines are often locked down, preventing the installation of any software, including the View Client.
One solution to this problem is to leverage a simple, yet powerful, tool called VMware ThinApp. With ThinApp we can virtualize the VMware View Client software, allowing it to run on any Windows device regardless of privilege level. ThinApp will take all of the files and registry keys that make up the View Client and produce a single executable file.
Should you use ReadOnlyData or readonlydata? With ThinApp version 4.7.2 it doesn’t matter! Many package.ini parameters have been case sensitive in ThinApp version 4.7.1 and older. With version 4.7.2 all parameters in package.ini are case insensitive.
By Tina de Benedictis, Technical Marketing Manager, Enterprise Desktop, End User Computing, VMware
ThinApp 4.7 was the first release with the option to enable your ThinApp virtual applications for VMware Horizon Application Manager. A new window in ThinApp Setup Capture gave you an easy, GUI-based way of enabling packages for Horizon as you captured them.
In the ThinApp 4.7 timeframe, how could you enable previously captured packages for Horizon? There were two ways:
- Recapture with ThinApp Setup Capture
- Add the Horizon parameters to Package.ini and rebuild the ThinApp package
ThinApp 4.7.2 has introduced a third method of Horizon enablement for previously captured applications.
If you ever need to compare what a virtualized application is presented with inside the virtual bubble against a normal physical install, you might try using the following technique.
Listed in the ThinApp User Guide, you can find an explanation of the different macro folders available in ThinApp projects. However, the published locations provide typical locations for Windows XP based systems. Here are their equivalents in Windows Vista, Windows 7, and Windows 8.