Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD)
Updated: November 1, 2012
Applies To: Application Virtualization 5.0
You can deploy App-V 5.0 packages using an Electronic Software Distribution (ESD) solution. When you use an ESD the following guidelines with regard to the App-V 5.0 management server should be considered:
Using an ESD eliminates the requirement for the App-V 5.0 management server, management database, and publishing server. These functions will be handled using the implemented ESD solution.
The App-V 5.0 reporting server and reporting database can be deployed side-by-side with the ESD. This allows you to collect data and generate reports. If the App-V 5.0 client is enabled to send report information and you are not using the App-V 5.0 reporting server, then the reporting data is stored in associated .xml files.
Deploying virtualized packages using an ESD
The following list displays three primary methods you can use to deploy App-V 5.0packages using an ESD.
You can use a third-party ESD solution to deploy a virtualized package.
You can us the associated Windows Installer (.msi) file that is created when you initially sequence an application to install the application on a target computer.
You can use PowerShell to deploy a virtualized application. For more information about PowerShell and App-V 5.0 see Administering App-V using PowerShell.
Deploying virtualized packages using Microsoft System Center 2012 Configuration Manager
Use the following link for more information about using App-V 5.0 and Microsoft System Center 2012 Configuration Manager.
Other resources for using an ESD and App-V 5.0
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.