mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
Created "deploy with electronic software distribution solutions" and "planning for server deployment" articles.
This commit is contained in:
Heidi Lohr
@ -0,0 +1,107 @@
|
||||
---
|
||||
title: Planning for the App-V Server Deployment (Windows 10)
|
||||
description: Planning for the App-V 5.1 Server 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 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.
|
||||
|
||||
## Planning for App-V Server Deployment
|
||||
|
||||
|
||||
The App-V server consists of the following features:
|
||||
|
||||
- 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.
|
||||
|
||||
The following list displays the recommended methods for installing the App-V server infrastructure:
|
||||
|
||||
- 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.
|
||||
|
||||
## <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>
|
||||
<colgroup>
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
<col width="20%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Server Type</th>
|
||||
<th align="left">Protocols</th>
|
||||
<th align="left">External Features Needed</th>
|
||||
<th align="left">Reporting</th>
|
||||
<th align="left"></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>IIS server</p></td>
|
||||
<td align="left"><p>HTTP</p>
|
||||
<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>Internal</p></td>
|
||||
<td align="left"></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>File</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>Internal</p></td>
|
||||
<td align="left"></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## 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).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
@ -69,9 +69,7 @@ Review the following to learn more about how to configure Microsoft SQL Server m
|
||||
The following steps can be used to validate the configuration:
|
||||
|
||||
1. Initiate a Microsoft SQL Server Mirroring session.
|
||||
|
||||
2. Select **Failover** to designate a new master Microsoft SQL Server instance.
|
||||
|
||||
3. Verify that the App-V management server continues to function as expected after the failover.
|
||||
|
||||
The connection string on the management server can be modified to include ```failover partner = <server2>```. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V client is doing a fresh connection (say after reboot).
|
||||
@ -79,36 +77,33 @@ The connection string on the management server can be modified to include ```fai
|
||||
Use the following steps to modify the connection string to include ```failover partner = <server2>```:
|
||||
|
||||
>[!IMPORTANT]
|
||||
>This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
|
||||
>This process involves changing the Windows registry with Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. Always make a backup copy of the registry files (**System.dat** and **User.dat**) before chagning the registry. Microsoft can't guarantee that problems caused by changing the registry can be resolved, so change the registry at your own risk.
|
||||
|
||||
|
||||
1. Login to the management server and open **regedit**.
|
||||
|
||||
2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**.
|
||||
|
||||
3. Modify the **MANAGEMENT\_SQL\_CONNECTION\_STRING** value with the **failover partner = <server2>**.
|
||||
|
||||
4. Restart management service using the IIS console.
|
||||
|
||||
**Note**
|
||||
Database Mirroring is on the list of Deprecated Database Engine Features for Microsoft SQL Server 2012 due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012.
|
||||
1. Log in to the management server and open **regedit**.
|
||||
2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**.
|
||||
3. Modify the **MANAGEMENT\_SQL\_CONNECTION\_STRING** value with the ```failover partner = <server2>``` value.
|
||||
4. Restart management service using the IIS console.
|
||||
>[!NOTE]
|
||||
>Database Mirroring is on the list of [deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>) due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012.
|
||||
|
||||
Click any of the following links for more information:
|
||||
|
||||
* [Prepare a Mirror Database for Mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx).
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://technet.microsoft.com/library/ms189053.aspx).
|
||||
|
||||
* [Establish a Database Mirroring Session Using Windows Authentication (SQL Server Management Studio)](https://technet.microsoft.com/library/ms188712(v=sql.130).aspx).
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://technet.microsoft.com/library/ms188712(v=sql.130).aspx).
|
||||
|
||||
* [Deprecated Database Engine Features in SQL Server 2012](https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx).
|
||||
* [Deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>).
|
||||
|
||||
## <a href="" id="bkmk-sqlalwayson"></a>Support for Microsoft SQL Server Always On configuration
|
||||
## Support for Microsoft SQL Server Always On configuration
|
||||
|
||||
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://technet.microsoft.com/library/hh510230.aspx).
|
||||
|
||||
## 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).
|
||||
|
||||
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
[Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Planning to Deploy App-V with an Electronic Software Distribution System (Windows 10)
|
||||
description: Planning to Deploy App-V with an Electronic Software Distribution System
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
ms.date: 04/19/2017
|
||||
---
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
>Applies to Windows 10, version 1607.
|
||||
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with System Center Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv).
|
||||
|
||||
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 collect data and generate reports.<br/>If you enable the App-V client to send report information without using the App-V Reporting server, the reporting data will be stored in associated .xml files. |
|
||||
|
||||
## 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).
|
||||
|
||||
## Related topics
|
||||
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
* [How to deploy App-V packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
* [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
|
||||
Reference in New Issue
Block a user