mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Created "planning for sequencer and client deployment" article
This commit is contained in:
Heidi Lohr
@ -8,56 +8,41 @@ ms.sitesec: library
|
|||||||
ms.prod: w10
|
ms.prod: w10
|
||||||
ms.date: 04/19/2017
|
ms.date: 04/19/2017
|
||||||
---
|
---
|
||||||
|
# Planning for the App-V server deployment
|
||||||
|
|
||||||
|
>Applies to Windows Server 2016.
|
||||||
# Planning for the App-V Server Deployment
|
|
||||||
|
|
||||||
**Applies to**
|
|
||||||
- Windows Server 2016
|
|
||||||
|
|
||||||
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
|
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
|
||||||
|
|
||||||
## Planning for App-V Server Deployment
|
## About the App-V server
|
||||||
|
|
||||||
|
|
||||||
The App-V server consists of the following features:
|
The App-V server consists of the following features:
|
||||||
|
|
||||||
- Management Server – provides overall management functionality for the App-V infrastructure.
|
* Management Server—provides overall management functionality for the App-V infrastructure.
|
||||||
|
* Management Database—facilitates database predeployments for App-V management.
|
||||||
|
* Publishing Server—provides hosting and streaming functionality for virtual applications.
|
||||||
|
* Reporting Server—provides App-V reporting services.
|
||||||
|
* Reporting Database—facilitates database predeployments for App-V reporting.
|
||||||
|
|
||||||
- Management Database – facilitates database predeployments for App-V management.
|
The following list describes recommended App-V server infrastructure installation methods:
|
||||||
|
|
||||||
- Publishing Server – provides hosting and streaming functionality for virtual applications.
|
* Install the App-V server. For more information, see [How to deploy the App-V Server](appv-deploy-the-appv-server.md).
|
||||||
|
* Install the database, reporting, and management features on separate computers. For more information, see [How to install the Management and Reporting databases on separate computers from the Management and Reporting services](appv-install-the-management-and-reporting-databases-on-separate-computers.md).
|
||||||
|
* Use Electronic Software Distribution (ESD). For more information, see [How to deploy App-V packages using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
||||||
|
* Install all server features on a single computer.
|
||||||
|
|
||||||
- Reporting Server – provides App-V reporting services.
|
## App-V server interaction
|
||||||
|
|
||||||
- Reporting Database – facilitates database predeployments for App-V reporting.
|
This section describes how the various App-V server roles interact with each other.
|
||||||
|
|
||||||
The following list displays the recommended methods for installing the App-V server infrastructure:
|
The App-V Management Server contains the repository of packages and their assigned configurations. For Publishing Servers that are registered with the Management Server, the associated metadata is provided to the Publishing servers for use when publishing refresh requests are received from computers running the App-V Client. App-V publishing servers managed by a single management server can serve different clients with different website names and port bindings. Additionally, all Publishing Servers managed by the same Management Server are replicas of each other.
|
||||||
|
|
||||||
- Install the App-V server. For more information, see [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).
|
>[!NOTE]
|
||||||
|
>The Management Server does not perform load balancing. The associated metadata is passed to the publishing server for use when processing client requests.
|
||||||
|
|
||||||
- Install the database, reporting, and management features on separate computers. For more information, see [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md).
|
## Server-related protocols and external features
|
||||||
|
|
||||||
- Use Electronic Software Distribution (ESD). For more information, see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
|
The following table lists server-related protocols used by the App-V servers, and also describes the reporting mechanism for each server type.
|
||||||
|
|
||||||
- Install all server features on a single computer.
|
|
||||||
|
|
||||||
## <a href="" id="---------app-v-5-1-server-interaction"></a> App-V Server Interaction
|
|
||||||
|
|
||||||
|
|
||||||
This section contains information about how the various App-V server roles interact with each other.
|
|
||||||
|
|
||||||
The App-V Management Server contains the repository of packages and their assigned configurations. For Publishing Servers that are registered with the Management Server, the associated metadata is provided to the Publishing servers for use when publishing refresh requests are received from computers running the App-V Client. App-V publishing servers managed by a single management server can be serving different clients and can have different website names and port bindings. Additionally, all Publishing Servers managed by the same Management Server are replicas of each other.
|
|
||||||
|
|
||||||
**Note**
|
|
||||||
The Management Server does not perform any load balancing. The associated metadata is simply passed to the publishing server for use when processing client requests.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Server-Related Protocols and External Features
|
|
||||||
|
|
||||||
|
|
||||||
The following displays information about server-related protocols used by the App-V servers. The table also includes the reporting mechanism for each server type.
|
|
||||||
|
|
||||||
<table>
|
<table>
|
||||||
<colgroup>
|
<colgroup>
|
||||||
@ -69,9 +54,9 @@ The following displays information about server-related protocols used by the Ap
|
|||||||
</colgroup>
|
</colgroup>
|
||||||
<thead>
|
<thead>
|
||||||
<tr class="header">
|
<tr class="header">
|
||||||
<th align="left">Server Type</th>
|
<th align="left">Server type</th>
|
||||||
<th align="left">Protocols</th>
|
<th align="left">Protocols</th>
|
||||||
<th align="left">External Features Needed</th>
|
<th align="left">External features needed</th>
|
||||||
<th align="left">Reporting</th>
|
<th align="left">Reporting</th>
|
||||||
<th align="left"></th>
|
<th align="left"></th>
|
||||||
</tr>
|
</tr>
|
||||||
@ -81,27 +66,26 @@ The following displays information about server-related protocols used by the Ap
|
|||||||
<td align="left"><p>IIS server</p></td>
|
<td align="left"><p>IIS server</p></td>
|
||||||
<td align="left"><p>HTTP</p>
|
<td align="left"><p>HTTP</p>
|
||||||
<p>HTTPS</p></td>
|
<p>HTTPS</p></td>
|
||||||
<td align="left"><p>This server-protocol combination requires a mechanism to synchronize the content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server and a firewall to protect the server from exposure to the Internet.</p></td>
|
<td align="left"><p>This server-protocol combination requires a mechanism to synchronize content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server and a firewall to protect the server from exposure to the Internet.</p></td>
|
||||||
<td align="left"><p>Internal</p></td>
|
<td align="left"><p>Internal</p></td>
|
||||||
<td align="left"></td>
|
<td align="left"></td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr class="even">
|
<tr class="even">
|
||||||
<td align="left"><p>File</p></td>
|
<td align="left"><p>File</p></td>
|
||||||
<td align="left"><p>SMB</p></td>
|
<td align="left"><p>SMB</p></td>
|
||||||
<td align="left"><p>This server-protocol combination requires support to synchronize the content between the Management Server and the Streaming Server. Use a client computer with file sharing or streaming capability.</p></td>
|
<td align="left"><p>This server-protocol combination requires support to synchronize the content between the Management Server and the Streaming Server. Use a client computer that's capable of file sharing or streaming.</p></td>
|
||||||
<td align="left"><p>Internal</p></td>
|
<td align="left"><p>Internal</p></td>
|
||||||
<td align="left"></td>
|
<td align="left"></td>
|
||||||
</tr>
|
</tr>
|
||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
|
|
||||||
## Have a suggestion for App-V?
|
## Have a suggestion for App-V?
|
||||||
|
|
||||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||||
|
|
||||||
## Related topics
|
## Related topics
|
||||||
|
|
||||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
[Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||||
|
|
||||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
[Deploying the App-V server](appv-deploying-the-appv-server.md)
|
||||||
|
|||||||
@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
title: Planning for the App-V Sequencer and Client Deployment (Windows 10)
|
||||||
|
description: Planning for the App-V Sequencer and Client Deployment
|
||||||
|
author: MaggiePucciEvans
|
||||||
|
ms.pagetype: mdop, appcompat, virtualization
|
||||||
|
ms.mktglfcycl: deploy
|
||||||
|
ms.sitesec: library
|
||||||
|
ms.prod: w10
|
||||||
|
ms.date: 04/19/2017
|
||||||
|
---
|
||||||
|
# Planning for the App-V Sequencer and Client Deployment
|
||||||
|
|
||||||
|
>Applies to Windows 10, version 1607.
|
||||||
|
|
||||||
|
Before you can use App-V, you must install the App-V Sequencer and enable the App-V client. You can also the App-V shared content store, although it isn't required. The following sections will tell you how to set these up.
|
||||||
|
|
||||||
|
## Planning for App-V Sequencer deployment
|
||||||
|
|
||||||
|
App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V Sequencer.
|
||||||
|
|
||||||
|
> [!NOTE]
|
||||||
|
> For information about the new functionality of App-V sequencer, see [What's new in App-V](appv-about-appv.md).
|
||||||
|
|
||||||
|
The computer running the App-V sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V supported configurations](appv-supported-configurations.md).
|
||||||
|
|
||||||
|
Ideally, you should install the sequencer on a computer running as a virtual machine. This lets you revert the computer that's running the sequencer to a “clean” state before sequencing another application. When installing the sequencer using a virtual machine, you should do the following things:
|
||||||
|
|
||||||
|
1. Install all associated sequencer prerequisites.
|
||||||
|
2. Install the sequencer.
|
||||||
|
3. Take a “snapshot” of the environment.
|
||||||
|
|
||||||
|
>[!IMPORTANT]
|
||||||
|
>Your corporate security team should review and approve the sequencing process plan before implementing it. For security reasons, it's a good idea to keep sequencer operations in a lab separate from the production environment. The sequencing computers must be capapble of connecting to the corporate network to copy finished packages to the production servers. However, because the sequencing computers are typically operated without antivirus protection, they shouldn't remail on the corporate network unprotected. You can protect your sequencing computers by operating them on an isolated network, behind a firewall, or by using virtual machines on an isolated virtual network. Make sure your solution follows your company's corporate security policies.
|
||||||
|
|
||||||
|
## Planning for App-V client deployment
|
||||||
|
|
||||||
|
In Windows 10, version 1607, the App-V client is included with the operating system. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||||
|
|
||||||
|
## Planning for the App-V Shared Content Store (SCS)
|
||||||
|
|
||||||
|
The App-V Shared Content Store mode allows computers running the App-V client to run virtualized applications without saving any package contents to the App-V client computer. Virtual applications are streamed to target computers only when requested by the client.
|
||||||
|
|
||||||
|
The following list displays some of the benefits of using App-V SCS:
|
||||||
|
|
||||||
|
* Reduced app-to-app and multi-user application conflicts reduces the need for regression testing
|
||||||
|
* Reduced deployment risk accelerates application deployment
|
||||||
|
* Simplified profile management
|
||||||
|
|
||||||
|
## Have a suggestion for App-V?
|
||||||
|
|
||||||
|
Add or vote on suggestions on the [Application virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
|
||||||
|
|
||||||
|
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||||
|
|
||||||
|
## Other App-V deployment resources
|
||||||
|
|
||||||
|
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||||
|
|
||||||
|
## Related topics
|
||||||
|
|
||||||
|
* [How to install the sequencer](appv-install-the-sequencer.md)
|
||||||
|
* [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||||
|
* [Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||||
Reference in New Issue
Block a user