There are several methods that you can use to deliver App-V packages in your environment – you could even combine the methods depending on your requirements. I will summarise the methods here and give you some links to existing Microsoft articles and white papers and some excellent blog posts that discuss these options in detail:
- Native infrastructure - App-V includes server infrastructure that be used to stream packages to clients. A central management server is used to authorise applications and streaming servers can be used for branch offices. Replication (such as that provided by DFS-R) is required for keeping package sources in sync. This is the most dynamic method for delivering App-V packages but it doesn’t scale as well as other methods - the App-V Management Server database does not support replication.
- System Centre Configuration Manager 2007 R2 - SCCM has native support for App-V 4.5 and 4.6. It supports importing App-V packages and deploying them to client computers and can stream packages or deliver them completely.
- Stand-alone using Windows Installer deployment - The App-V Sequencer can create a Windows Installer (MSI) file when saving a package. The MSI file can be used with your existing software deployment tool (ESD) such as Group Policy or Altiris Client Management Suite. If the 3rd party ESD is aware of the package manifest file (an XML file produced by the sequencer) it can deploy App-V packages with a finer level of control. Using the MSI file, App-V packages are deployed to the machine rather than being able to target users.
The Microsoft infrastructure deployment solutions are outlined in this diagram:
- Stand-alone using the SFTMIME command (or the roll-your-own deployment tool) - The final method is not widely used; however I have designed an App-V deployment for a client who use an in-house developed software deployment solution. The product has been extended to use SFTMIME commands to add packages to client machines and control user access to virtual applications. Tim Mangan makes this type of solution freely available from his site with App-V_DeployNPublishApp.
Use the following links to read more on the infrastructure solutions. Be sure to start with the Infrastructure Planning and Design guide from Microsoft.
- Infrastructure Planning and Design downloadable documents and more on TechNet
- Application Virtualization Server-based scenario
- Electronic Software Distribution-based scenario
- Stand-Alone Delivery scenario
- Centralized Management & Scalable Infrastructure
- Microsoft Assessment and Planning Toolkit
- Microsoft Application Virtualization and Configuration Manager 2007 R2
- Virtual Application Management with Microsoft Application Virtualization 4.5 and System Center Configuration Manager 2007 R2
- Virtual Application Management with Microsoft Application Virtualization 4.6 and System Center Configuration Manager 2007 R2
- App-V 4.5 Server Sizing Guide
- How Microsoft Is Architecting the Virtual Application Infrastructure
- Choosing the right App-V delivery model
- Choosing the right App-V Delivery Model (App-v integration: possibilities and impossibilities)
- App-V 4.6 and ConfigMgr 2007 SP2: even better together
- How to integrate App-V with SCCM without losing the features you care about