Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Five common App-V v5 implementation scenarios


View products that this article applies to.

Summary

This article describes five common App-V v5 scenarios. Referencing the scenario that describes your implementation can convey an enormous amount of information in just a few words. For example, the following scenarios are already widely used by the App-V community: "Full Infrastructure", "ConfigMgr Integration" and "Standalone Client". 

↑ Back to the top


More Information

1. App-V v5 Full Infrastructure (Large scale virtual application publishing)

- All systems are domain members
- App-V v5 Clients
- App-V v4.6 Clients (optional for coexistence)
- App-V v5 Management Server
- App-V v5 Publishing Server
- Content server for URL or UNC streaming
- Microsoft SQL Server
- App-V v5 Reporting Server (optional)
- Server components can be on one or on multiple systems

Note: App-V v4.6 clients managed by App-V v4.5 Server


2. App-V v5 & Configuration Manager 2012 SP1 Integration Feature (Large scale, deployment of virtual & installed applications together)

- All systems are domain members
- App-V v5 Clients
- App-V v4.6 Clients (optional for coexistence)
- Configuration Manager 2012 SP1 where content is streamed from a Distribution Point via HTTP or downloaded to a local drive
- App-V v5 Reporting Server (optional)


3. Other ESD that can deploy via Windows Installer (.MSI) or execute Windows Powershell

- App-V v5 Clients
- App-V v4.6 Clients (optional for coexistence)
- Any ESD that is capable of installing from a Windows Installer file (.MSI) or of executing the App-V v5 Powershell CmdLets or of executing App-V v4.6 Sftmime commands (optional)
- Content server for URL or UNC streaming
- App-V v5 Reporting Server (optional)
- Possible additional requirements for 3rd party ESD


4. App-V v5 Standalone Client Domain

- All systems are domain members
- App-V v5 clients
- App-V v4.6 Clients (optional for coexistence)
- Content server for URL or UNC streaming
- Package files can also be on a local drive
- Suitable where centralized management is not required


5. App-V v5 Standalone Client Workgroup

- Systems are not domain members
- App-V v5 clients
- App-V v4.6 Clients (optional for coexistence)
- Package files are local
- Suitable for testing

↑ Back to the top


Keywords: SCCM, kb

↑ Back to the top

Article Info
Article ID : 2780807
Revision : 3
Created on : 3/27/2020
Published on : 3/27/2020
Exists online : False
Views : 292