This blog post refers to Microsoft Application Virtualization (App-V), which decouples applications from the operating system and virtualizes applications per user, per application instance. As a result, application conflicts and the need for regression testing are dramatically reduced (See here for details).
App-V mitigates the application compatibility issues under Remote Desktop Services by reducing the conflicts between multiple application instances. However, the application must be pre-processed or ‘sequenced’ before deploying it on App-V.
App-V also allows an alternative method to run an application in the virtualized environment without sequencing (for debugging purposes). The “RDS Compatibility using App-V” script leverages this functionality of App-V to enable any application to run inside an App-V bubble without sequencing it.
This script is targeted at IT administrators who intend to address application compatibility issues with applications deployed on RDSH.
The main goal of the script is to run the applications that cannot run under Remote Desktop Service Host due to compatibility issues and are not targeted for sequencing. The script is used to run these applications quickly using App-V without sequencing them and is best suited for the following scenarios:
· Fixing run-time application compatibility issues on RDSH where sequencing is not possible
· Evaluating and verifying App-V application compatibility without sequencing the applications
The preferred way of running applications under App-V is to first sequence them and then run them with the App-V client. This enables the usage of the complete virtualization and other features of App-V.
The debugging method leveraged in this script does not enable file-system virtualization. Overall, this script is best suited for scenarios in which sequencing is not feasible.
The script and the instructions to use it are available at http://gallery.technet.microsoft.com/ScriptCenter/en-us/f632175d-42a5-41b5-be81-67de7b735a02
Microsoft App-V: http://www.microsoft.com/systemcenter/appv/default.mspx
Microsoft App-V for RDSH: http://www.microsoft.com/systemcenter/appv/terminalsvcs.mspx
Can you please explain the use case for this script with an example application? I understand RDSH and App-V.
For those apps which cannot be sequenced but have some AppCompat issues under RDSH.
Apps to be quickly evaluated with App-V for RDSH Compatibility where you don't want to spend lot of time in sequencing.
Would this be a good way to integrate Internet explorer with virtualized applications such as web plugins and full sharepoint functionality?
This doesn't help in integrating IE with virtualized apps. This is relevant for apps that doesn't run properly under RDSH Sessions. Please explain a bit more if this doesn't answer you.
I'm guessing from the "(for debugging purposes)" reference that this isn't supported by MS, but, what the heck, it's an important question worth asking: Is it supported?