Microsoft Application Virtualization: Wikis

Advertisements
  
  

Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.

Encyclopedia

From Wikipedia, the free encyclopedia

Microsoft Application Virtualization (also known as App-V;[1] formerly Microsoft SoftGrid)[2] is an application virtualization and application streaming solution from Microsoft. It was acquired by Microsoft during the acquisition of Boston, Massachusetts-based Softricity on July 17, 2006.[3] Softgrid represents Microsoft's entry to a new avenue of virtualization product, alongside their existing Hyper-V package, Microsoft Virtual Server, Microsoft Virtual PC, and other products newly announced in 2006, such as System Center Virtual Machine Manager, the latter of which is designed for "Datacenter Virtualization".[4]

Contents

Overview

Microsoft Application Virtualization (MS App-V) platform allows applications to be deployed in real-time to any client from a virtual application server. It removes the need for local installation of the applications. Instead, only the App-v client needs to be installed on the client machines. All application data is permanently stored on the virtual application server. Whichever software is needed is either streamed or locally cached from the application server on demand and run locally. The App-V stack sandboxes the execution environment so that the application does not make changes to the client itself (OS File System and/or Registry). App-V applications are also sandboxed from each other, so that different versions of the same application can be run under SoftGrid concurrently. This approach enables any application to be delivered without making any changes to its code.

MS 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 by defining policies governing the usage. App-V can require that applications not be run 'cached' from workstations, or require that 'cached' App-V applications routinely update license information from the App-V server, enforcing license compliance. These policies are centrally applied on the application repository. App-V also allows copy of the applications across multiple application servers for better scalability and fault tolerance, and also features a tracking interface to track the usage of the virtualized application.

The App-V client presents the user with a list of applications, to which the user has access. The user can then launch a virtualized instance of the application. Depending on the configuration, the systems administrator can be either notified of the action via email or it can require an explicit confirmation from the administrator for the application to start streaming and initialize or it can just simply check the Active Directory for the user's rights and stream the application to the user if it is authorized to run the application. The App-V client can also install local shortcuts that bootstrap the process of launching individual virtualized software instances.

Architecture

The App-V system architecture is composed of the following components:

  • Microsoft Systems Center Virtual Application Server, also called App-V Application Server, which hosts virtualized application packages and streams them to the client computers for local execution. It also authorizes requesting clients and logs their application usage. Applications are converted to virtualized packages using the App-V Sequencer.
  • Microsoft App-V Application Virtualization for Desktops, also called App-V client, is the client side runtime which requests the application server to stream some application, receives the streamed virtual application packages, sets up the runtime environment and executes the applications locally.
  • App-V Management Console, the management tool to set up, administer and manage App-V servers. It can be used to define policies that govern the usage of the applications. It can also be used to create, manage, update and replicate virtualized application packages.

App-V Architecture.png

Advertisements

Operation

App-V Application Virtualization is composed mainly of two components – SystemGuard and App-V Sequencer. SystemGuard tracks and analyses configuration repositories and resources used by the application and intercepts the use of these resources, redirecting them to the virtualized instances of the resources. Virtualized resources include virtualized data such as user profile information and data; virtualized system services, such as COM controls, windows services and copy/paste abilities; and virtualized configuration repositories like registry hives and INI files. Not all applications that run as a service can be virtualized, although these limitations may change in future product versions. The virtualized instances are created in the runtime sandbox which hosts the virtualized instance, representing the resources of the actual client system the application is being executed on. Thus the application is decoupled from the resources of the system the application is installed on. Each application, or multiple instances of the same application, is run in its own virtual sandbox, each with its own set of virtual resources. The SystemGuard runtime environments can include specific dependencies such as DLL files as well. Multiple SystemGuard runtime environments can be in execution simultaneously.

App-V sequencer is the component which packages an application for virtualization and streaming. It analyzes the application for the resources that it requires and creates the SystemGuard runtime environment that it will require. It also packages specific DLL files that it might require at the client side. It then packs all the application code and data into App-V's proprietary format that makes it more suitable for streaming. Individual libraries are packed separately so that each library can be streamed as required, rather than having the client to download the entire application at the beginning. When a streaming request is made, an entire sequencer package is transferred to the client, who unpacks and initializes the SystemGuard environment and hosts the application inside it. Each package is cached by the client for the duration of the application session. User settings are stored in the local system itself.

Virtualized application packages can also locally reside at the client computer, thus eliminating the need of application server and streaming. Microsoft Systems Management Server can be used to push these packages to the client computer in the absence of a virtual application server. In this scenario, the App-V SMS Connector can be used to locally manage the application packages.

Limitations

  • Microsoft Office plug-ins: Although one can sequence Microsoft Office plug-ins, but its not advised to sequence them due to many technical & usage issues. Say for example there are more than two plug-ins used by a user and if they are sequenced separately then user does not have a control which plug-in sequence to start when he double clicks any document file. The only work around to resolve the issue is by creating a single suite or dynamic suite of all the plug-ins.
  • Application Size: If the maximum client cache size is set for 4 GB (The max can be 64 GB), then the maximum size of application (sft file) which can be streamed on that machine is 4 GB. All applications that have an installed footprint greater than or equal to the max client size, set by the client, should not be sequenced. The maximum application size Softgrid can handle is 4GB.[citation needed]
  • Device Driver: App-V presently does not support sequencing of kernel-mode device drivers; thus any application that installs device driver cannot be usually sequenced. The only exception is when the device driver can be pre-installed locally; in this case, the application is sequenced without the device driver.
  • Shortcuts: Application should have minimum of one shortcut. If no shortcuts are present, then the application should be sequenced in a suite along with the application that needs it. Internet Explorer plugins require a special shortcut to start the browser process under the virtualization layer.
  • Middleware: Middleware applications may not be good candidates for sequencing as they may be runtime prerequisites for mutiple applications. With later versions of App-V, they can be sequenced into a separate package that other virtual applications are linked to.
  • Path hard coding: The application should not have folder/file path hard coded in the application itself. Some applications hard code the path of files in their executables rather than parameterising them. Configuration files such as ini, conf, txt etc and the Registry are good places to look for application-specific settings. Failing that, a shim can be used to remediate the application where source code or an update is not available.
  • Auto Update: Application with automatic updates should not be sequenced if their update mechanism cannot be disabled. Sequenced application most of the time fails to properly update itself. Also allowing auto update leads to non compliance of application version.
  • Services: For services, these can be started when application starts and shut down when application main executable terminate. Only user-mode services are suitable candidates for sequencing.
  • COM+: Some application which uses COM+ might not work properly in virtual environment.
  • COM DLL: A few applications that uses COM DLL surrogate virtualization, i.e. DLL’s that run in Dllhost.exe, do not work properly in Softgrid Environment.
  • Licensing Policies: Applications with licensing enforcement tied to machine, e.g. the license is tied to the system’s MAC address or harddisk serial number. This type of application should not be sequenced if the activation can not be done by the user at the first launch of sequenced application.
  • Internet Explorer & Service Packs: Microsoft does not support sequencing any version of Internet Explorer.

Similar Technologies

References

External links


Advertisements






Got something to say? Make a comment.
Your name
Your email address
Message