f4bb542824
In this patch, I replaced all occurrences of http://go.microsoft.com with https://go.microsoft.com
2.0 KiB
title, description, author, ms.assetid, ms.pagetype, ms.mktglfcycl, ms.sitesec, ms.prod
| title | description | author | ms.assetid | ms.pagetype | ms.mktglfcycl | ms.sitesec | ms.prod |
|---|---|---|---|---|---|---|---|
| Planning to Deploy App-V 5.0 with an Electronic Software Distribution System | Planning to Deploy App-V 5.0 with an Electronic Software Distribution System | jamiejdt | 8cd3f1fb-b84e-4260-9e72-a14d01e7cadf | mdop, appcompat, virtualization | deploy | library | w10 |
Planning to Deploy App-V 5.0 with an Electronic Software Distribution System
If you are using an electronic software distribution system to deploy App-V packages, review the following planning considerations. For information about using System Center Configuration Manager to deploy App-V, see Introduction to Application Management in Configuration Manager.
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
| Deployment requirement or option | Description |
|---|---|
The App-V Management server, Management database, and Publishing server are not required. |
These functions are handled by the implemented ESD solution. |
You can deploy the App-V Reporting server and Reporting database side by side with the ESD. |
The side-by-side deployment lets you to collect data and generate reports. If you enable the App-V client to send report information, and you are not using the App-V Reporting server, the reporting data is stored in associated .xml files. |
Got a suggestion for App-V?
Add or vote on suggestions here. For App-V issues, use the App-V TechNet Forum.