Merge pull request #116 from Justinha/8442312-app-v

Revised all reference to 5.0 and 5.1
This commit is contained in:
Justin Hall 2016-08-12 12:51:39 -07:00 committed by GitHub
commit c2eefbe8b1
7 changed files with 22 additions and 22 deletions

View File

@ -52,7 +52,7 @@
##### [App-V Capacity Planning](appv-capacity-planning.md)
##### [Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
##### [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
##### [Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)
##### [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
##### [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
##### [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
##### [Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md)
@ -65,9 +65,9 @@
##### [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
##### [How to Install the Sequencer](appv-install-the-sequencer.md)
##### [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
#### [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
##### [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)
##### [How to Deploy the App-V 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
#### [Deploying the App-V Server](appv-deploying-the-appv-server.md)
##### [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
##### [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
##### [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md)
##### [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
##### [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)

View File

@ -925,7 +925,7 @@ For example, an average user can stream a 100 MB package in less than 2 minutes,
The number of clients a streaming server can support can be significantly increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
## Combining App-V 5.1 Server Roles
## Combining App-V Server Roles
Discounting scaling and fault-tolerance requirements, the minimum number of servers needed for a location with connectivity to Active Directory is one. This server will host the management server, management server service, and Microsoft SQL Server roles. Server roles, therefore, can be arranged in any desired combination since they do not conflict with one another.

View File

@ -48,7 +48,7 @@ This checklist can be used to help you plan for preparing your organization for
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>If you plan to use the App-V management server, plan for the required roles.</p></td>
<td align="left"><p>[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)</p></td>
<td align="left"><p>[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">

View File

@ -1,5 +1,5 @@
---
title: Planning for the App-V 5.1 Server Deployment (Windows 10)
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
@ -9,15 +9,15 @@ ms.prod: w10
---
# Planning for the App-V 5.1 Server Deployment
# Planning for the App-V Server Deployment
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 5.1 Server Deployment
## Planning for App-V Server Deployment
The App-V 5.1 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.
@ -29,9 +29,9 @@ The App-V 5.1 server consists of the following features:
- Reporting Database facilitates database predeployments for App-V reporting.
The following list displays the recommended methods for installing the App-V 5.1 server infrastructure:
The following list displays the recommended methods for installing the App-V server infrastructure:
- Install the App-V 5.1 server. For more information, see [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).
- 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).
@ -54,7 +54,7 @@ The Management Server does not perform any load balancing. The associated metada
## Server-Related Protocols and External Features
The following displays information about server-related protocols used by the App-V 5.1 servers. The table also includes the reporting mechanism for each server type.
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>
@ -96,10 +96,10 @@ The following displays information about server-related protocols used by the Ap
## Have a suggestion for App-V?
Add or vote on suggestions [here](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).
Add or vote on suggestions at [Microsoft Application Virtualization](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)
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
[Deploying the App-V Server](appv-deploying-the-appv-server.md)

View File

@ -29,7 +29,7 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa
**Understand the security risks.** The most serious risk to App-V is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V clients. The loss of App-V functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.1 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.1 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (<http://go.microsoft.com/fwlink/p/?LinkId=28819>).
@ -38,7 +38,7 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa
## Accounts and groups in App-V
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V 5.1 servers.
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V servers.
**Note**  
App-V client computer accounts that need to connect to the publishing server must be part of the publishing servers **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
@ -47,7 +47,7 @@ App-V client computer accounts that need to connect to the publishing server mus
### <a href="" id="-------------app-v-5-1-server-security"></a> App-V server security
No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V 5.1 server operations.
No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V server operations.
<table>
<colgroup>

View File

@ -148,7 +148,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
Click **Next**.
7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V 5.0 Management Console.
7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console.
Click **Next**.
@ -193,14 +193,14 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
> [!IMPORTANT]
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V 5.0 Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
4. On the **Type of Application** page, select **Middleware**, and then click **Next**.
5. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V 5.0 Management Console.
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
Click **Next**.

View File

@ -25,7 +25,7 @@ The App-V server does not support the following scenarios:
- Deployment to a computer that runs the Server Core installation option.
- Deployment to a computer that runs a previous version of the App-V 5.1 server components. You can install App-V side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the Application Virtualization Management Service (HWS) 4.x is not supported.
- Deployment to a computer that runs a previous version of the App-V server components. You can install App-V side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the Application Virtualization Management Service (HWS) 4.x is not supported.
- Deployment to a computer that runs Microsoft SQL Server Express edition.