Microsoft Application Virtualization also known as App-V ;  formerly Softricity SoftGrid  is an application virtualization and application streaming solution from Microsoft. It was originally developed by Softricity, a company based in Boston , Massachusetts , acquired by Microsoft on July 17, App-V allows applications to be deployed "streamed" in real-time to any client from a virtual application server. It removes the need for traditional local installation of the applications, although a standalone deployment method is also supported. With a streaming-based implementation, the App-V client needs to be installed on the client machines and application data that is stored on the virtual application server is installed streamed to the client cache on demand when it is first used, or pre-installed in a local cache. App-V applications are also sandboxed from each other, so that different versions of the same application can be run under App-V concurrently and so that mutually exclusive applications can co-exist on the same system. Nevertheless the separation is not a security boundary. App-V thus allows centralized installation and management of deployed applications. It supports policy based access control; administrators can define and restrict access to the applications by certain users, or on certain computers, by defining policies governing the usage. App-V also features a tracking interface to track the usage of the virtualized application.
A Better Way – Use SFTTRAY instead
There are instances in which you will need to troubleshoot applications running in the App-V bubble or the virtualised environment. Although applications delivered by App-V are running locally, they are separated from other applications and the operating system by the App-V client the feature known as the SystemGuard , although usually referred to as the bubble. To do this you will need to launch a Command Prompt into the bubble.
Scenario — We have a App-V package and we have requirements to run some executable from within App-V bubble that we cannot have shortcut of. We want to run some executable from within App-V virtual bubble with some external random input files. We may have batch file with logic to call executable with n number of input files. For implementing above scenario, we have to go inside virtual bubble through command prompt. You can go inside virtual bubble using the command —. The above command will take you to the command prompt inside the virtual bubble. Now you can navigate to different folders with bubble. Now in XenApp, we will need to publish above command for the users.
The first step was to package and deliver Sybase 32 bit as an App-V package to the developers machines. However this on its own would mean launching PowerDesigner locally would still only ever interact with Sybase 64 bit which was also locally installed. By provisioning the RunVirtual registry key on the machine as above we were able to dictate that the App-V client listens for PowerDesigner. This would give the local PowerDesigner application full sight of the Sybase 32 bit and enable the developers to work with it. However a side effect of this approach is that PowerDesigner would lose sight of locally installed Sybase 64 bit. As RunVirtual operates on a process level there would be no flexibility in launch, PowerDesigner. In these initial stages we provisioned these keys manually on the machine however we also wanted a better way to manage connectors, if we stuck with RunVirtual as a solution we may have chosen to use Group Policy Preferences to write this in, or even used a script within the Sybase 32 bit package to write this down.