The choice of deployment method depends on which infrastructures already exist within your organization. It also depends on the scope of application usage. Some deployment methods are suitable for large-scale deployment, while others provide enhanced features. Ultimately, you might have to use a combination of the deployment methods available. The following list describes the different ways you can deploy virtual applications using App-V full infrastructure:

·     Deployment methods available with an App-V full infrastructure:

·     Streaming mode. Applications are streamed to the client, but management features that the App-V Management Server provides are not available. This is ideal in small deployment scenarios in which a complete App-V Management Server is not available. This method requires a custom application-publishing solution, such as a login script or a non-Microsoft electronic software distribution (ESD) system, to publish applications on the client (for example, configure program shortcuts, file type associations, and so on).

·     Full Infrastructure mode. Applications are streamed to the client, and a complete App-V Management Server provides features to track and manage application usage. These features include assigning applications to AD DS security groups, enforcing licenses, and reporting application usage.

·     Stand-alone mode. When using ESD systems or deploying applications to disconnected, unmanaged client computers, package applications as stand-alone MSI files.

For guidance on choosing deployment methods, see the Infrastructure Planning and Design document, Microsoft Application Virtualization 4.5, at This guide helps you evaluate the benefits and costs of each method and choose the right method for specific requirements. Additionally, when using App-V with Configuration Manager 2012 or Configuration Manager 2007 R3, you can stream applications or deliver them locally, downloading and executing them on the local computer. For more information about deploying virtualized applications with Configuration Manager 2007 R3, see the white paper, Virtual Application Management with Microsoft Application Virtualization 4.5 and System Center Configuration Manager 2007 R2.

Related Topics