mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 22:37:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into vs-8388390
This commit is contained in:
LizRoss
commit
acbf532f82
53
CONTRIBUTING.md
Normal file
53
CONTRIBUTING.md
Normal file
@ -0,0 +1,53 @@
|
||||
# Contributing to Windows IT professional documentation
|
||||
|
||||
Thank you for your interest in the Windows IT professional documentation! We appreciate your feedback, edits, and additions to our docs.
|
||||
This page covers the basic steps for contributing to our technical documentation.
|
||||
|
||||
## Sign a CLA
|
||||
|
||||
All contributors who are ***not*** a Microsoft employee must [sign a Microsoft Contribution Licensing Agreement (CLA)](https://cla.microsoft.com/) before contributing to any Microsoft repositories.
|
||||
If you've already contributed to Microsoft repositories in the past, congratulations!
|
||||
You've already completed this step.
|
||||
|
||||
## Editing topics
|
||||
|
||||
We've tried to make editing an existing file as simple as possible.
|
||||
|
||||
- If you're already in the repo, just navigate to the file you want to make the edits to and click the **Edit** button.
|
||||
- Alternatively, if you're viewing a TechNet page in your browser, click the **Contribute** button on the top right of the page. You will be redirected to the relevant source file in the repo, where you can click the **Edit** button.
|
||||
|
||||
When you're done, submit a pull request back to the master branch of the official repository.
|
||||
|
||||
After you create the pull request, a member of the writing team will review your changes.
|
||||
|
||||
If your request is accepted, updates are published to one of the following places:
|
||||
|
||||
- [Windows 10](https://technet.microsoft.com/itpro/windows)
|
||||
- [Internet Explorer 11](https://technet.microsoft.com/itpro/internet-explorer)
|
||||
- [Microsoft Edge](https://technet.microsoft.com/itpro/microsoft-edge)
|
||||
- [Surface](https://technet.microsoft.com/itpro/surface)
|
||||
- [Surface Hub](https://technet.microsoft.com/itpro/surface-hub)
|
||||
- [Windows 10 for Education](https://technet.microsoft.com/edu/windows)
|
||||
- [Microsoft Desktop Optimization Pack](https://technet.microsoft.com/itpro/mdop)
|
||||
|
||||
## Making more substantial changes
|
||||
|
||||
To make substantial changes to an existing article, add or change images, or contribute a new article, you will need to create a local clone of the content.
|
||||
For info about creating a fork or clone, see the GitHub help topic, [Fork a Repo](https://help.github.com/articles/fork-a-repo/).
|
||||
|
||||
Fork the official repo into your personal GitHub account, and then clone the fork down to your local device. Work locally, then push your changes back into your fork. Then open a pull request back to the master branch of the official repo.
|
||||
|
||||
## Using issues to provide feedback on documentation
|
||||
|
||||
If you just want to provide feedback rather than directly modifying actual documentation pages, you can create an issue in the repository.
|
||||
|
||||
At the top of a topic page you'll see an **Issues** tab. Click the tab and then click the **New issue** button.
|
||||
|
||||
Be sure to include the topic title and the URL for the page you're submitting the issue for, if that page is different from the page you launched the **New issue** dialog from.
|
||||
|
||||
## Resources
|
||||
|
||||
You can use your favorite text editor to edit Markdown. We recommend [Visual Studio Code](https://code.visualstudio.com/), a free lightweight open source editor from Microsoft.
|
||||
|
||||
You can learn the basics of Markdown in just a few minutes. To get started, check out [Mastering Markdown](https://guides.github.com/features/mastering-markdown/).
|
||||
|
||||
22
README.md
22
README.md
@ -1,6 +1,20 @@
|
||||
# win-cpub-itpro-docs
|
||||
This repo hosts the WDG ITPro content that is published to TechNet.
|
||||
# Windows IT professional documentation
|
||||
|
||||
Welcome! This repository houses the docs that are written for IT professionals for the following products:
|
||||
|
||||
- [Windows 10](https://technet.microsoft.com/itpro/windows)
|
||||
- [Internet Explorer 11](https://technet.microsoft.com/itpro/internet-explorer)
|
||||
- [Microsoft Edge](https://technet.microsoft.com/itpro/microsoft-edge)
|
||||
- [Surface](https://technet.microsoft.com/itpro/surface)
|
||||
- [Surface Hub](https://technet.microsoft.com/itpro/surface-hub)
|
||||
- [Windows 10 for Education](https://technet.microsoft.com/edu/windows)
|
||||
- [Microsoft Desktop Optimization Pack](https://technet.microsoft.com/itpro/mdop)
|
||||
|
||||
## Contributing
|
||||
|
||||
We actively merge contributions into this repository via [pull request](https://help.github.com/articles/using-pull-requests/) into the *master* branch.
|
||||
If not are not a Microsoft employee, before you submit a pull request you must [sign a Contribution License Agreement](https://cla.microsoft.com/) to ensure that the community is free to use your submissions.
|
||||
For more information on contributing, read our [contributions guide](CONTRIBUTING.md).
|
||||
|
||||
|
||||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
|
||||
|
||||
English Handoff Folder Structure Demo!
|
||||
|
||||
@ -1 +1,3 @@
|
||||
# Index test file for Open Publishing
|
||||
---
|
||||
redirect_url: https://technet.microsoft.com/edu/windows/
|
||||
---
|
||||
|
||||
7
license.md
Normal file
7
license.md
Normal file
@ -0,0 +1,7 @@
|
||||
Copyright (c) Microsoft Corporation. Distributed under the following terms:
|
||||
|
||||
1. Microsoft and any contributors to this project each grants you a license, under its respective copyrights, to the documentation under the [Creative Commons Attribution 3.0 United States License](http://creativecommons.org/licenses/by/3.0/us/legalcode). In addition, with respect to any sample code contained in the documentation, Microsoft and any such contributors grants you an additional license, under its respective intellectual property rights, to use the code to develop or design your software for Microsoft Windows.
|
||||
|
||||
2. Microsoft, Windows, and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. This license does not grant you rights to use any names, logos, or trademarks. For Microsoft’s general trademark guidelines, go to [http://go.microsoft.com/fwlink/?LinkID=254653](http://go.microsoft.com/fwlink/?LinkID=254653).
|
||||
|
||||
3. Microsoft and any contributors reserves all others rights, whether under copyrights, patents, or trademarks, or by implication, estoppel or otherwise.
|
||||
@ -149,6 +149,7 @@ To create a self-signed certificate, do the following:
|
||||
``` syntax
|
||||
[NewRequest]
|
||||
Subject="CN=BitLocker Network Unlock certificate"
|
||||
ProviderType=0
|
||||
Exportable=true
|
||||
RequestType=Cert
|
||||
KeyUsage="CERT_KEY_ENCIPHERMENT_KEY_USAGE"
|
||||
|
||||
@ -538,7 +538,7 @@ Historically, most malware has been unsigned. Simply by deploying code integrity
|
||||
|
||||
The core functionality and protection of Device Guard starts at the hardware level. Devices that have processors equipped with SLAT technologies and virtualization extensions, such as Intel VT x and AMD V, will be able to take advantage of a VBS environment that dramatically enhances Windows security by isolating critical Windows services from the operating system itself. This isolation is necessary, because you must assume that the operating system kernel will be compromised, and you need assurance that some processes will remain secure.
|
||||
|
||||
Device Guard leverages VBS to isolate its Hypervisor Code Integrity (HVCI) service, which enables Device Guard to protect all kernel mode processes and drivers from vulnerability exploits and zero days. HVCI uses the processor’s IOMMU functionality to force all software running in kernel mode to safely allocate memory. This means that after memory has been allocated, its state must be changed from writable to read only or execute only. By forcing memory into these states, it helps ensure that attacks are unable to inject malicious code into kernel mode processes and drivers through techniques such as buffer overruns or heap spraying. In the end, the VBS environment protects the Device Guard HVCI service from tampering even if the operating system’s kernel has been fully compromised, and HVCI protects kernel mode processes and drivers so that a compromise of this magnitude can’t happen in the first place.
|
||||
Device Guard leverages VBS to isolate its Hypervisor Code Integrity (HVCI) service, which enables Device Guard to help protect kernel mode processes and drivers from vulnerability exploits and zero days. HVCI uses the processor’s IOMMU functionality to force all software running in kernel mode to safely allocate memory. This means that after memory has been allocated, its state must be changed from writable to read only or execute only. By forcing memory into these states, it helps ensure that attacks are unable to inject malicious code into kernel mode processes and drivers through techniques such as buffer overruns or heap spraying. In the end, the VBS environment protects the Device Guard HVCI service from tampering even if the operating system’s kernel has been fully compromised, and HVCI protects kernel mode processes and drivers so that a compromise of this magnitude can’t happen in the first place.
|
||||
Another Windows 10 feature that employs VBS is Credential Guard. Credential Guard protects credentials by running the Windows authentication service known as LSA, and then storing the user’s derived credentials (for example, NTLM hashes; Kerberos tickets) within the same VBS environment that Device Guard uses to protect its HVCI service. By isolating the LSA service and the user’s derived credentials from both user mode and kernel mode, an attacker that has compromised the operating system core will still be unable to tamper with authentication or access derived credential data. Credential Guard prevents pass-the-hash and ticket types of attacks, which are central to the success of nearly every major network breach you’ve read about, which makes Credential Guard one of the most impactful and important features to deploy within your environment. For more information about how Credential Guard complements Device Guard, see the [Device Guard with Credential Guard](#dgwithcg) section.
|
||||
|
||||
**Device Guard with AppLocker**
|
||||
|
||||
@ -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 Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
##### [Planning for the App-V 5.1 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 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)
|
||||
#### [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)
|
||||
##### [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)
|
||||
|
||||
@ -173,7 +173,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
|
||||
</tbody>
|
||||
</table>
|
||||
<li><p>If you are upgrading to App-V for Windows server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 server](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/check-reg-key-svr).</p></li>
|
||||
<li><p>Follow the steps in [How to Deploy the App-V server components](appv-deploy-the-appv-server.md)</p></li>
|
||||
<li><p>Follow the steps in [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)</p></li>
|
||||
<p> </p></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
|
||||
@ -67,7 +67,7 @@ You can also manage your App-V environment using an Electronic Software Distribu
|
||||
|
||||
- When network bandwidth limitations inhibit electronic software distribution.
|
||||
|
||||
- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V Full Infrastructure Model consists of one or more App-V management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
|
||||
- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V Full Infrastructure Model consists of one or more App-V management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
|
||||
|
||||
**Important**
|
||||
The App-V full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
@ -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 Server Roles
|
||||
## Combining App-V 5.1 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.
|
||||
|
||||
@ -179,5 +179,5 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.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)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server Using a Script (Windows 10)
|
||||
description: How to Deploy the App-V Server Using a Script
|
||||
title: How to Deploy the App-V 5.1 Server Using a Script
|
||||
description: How to Deploy the App-V 5.1 Server Using a Script
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,14 +9,14 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Deploy the App-V Server Using a Script
|
||||
# How to Deploy the App-V 5.1 Server Using a Script
|
||||
|
||||
|
||||
In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters.
|
||||
|
||||
**To Install the App-V server using a script**
|
||||
**To Install the App-V 5.1 server using a script**
|
||||
|
||||
- Use the following tables for more information about installing the App-V server using the command line.
|
||||
- Use the following tables for more information about installing the App-V 5.1 server using the command line.
|
||||
|
||||
**Note**
|
||||
The information in the following tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**.
|
||||
@ -777,7 +777,7 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Deploy the App-V Server (Windows 10)
|
||||
description: How to Deploy the App-V Server
|
||||
title: How to Deploy the App-V 5.1 Server
|
||||
description: How to Deploy the App-V 5.1 Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -8,9 +8,9 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V server
|
||||
# How to Deploy the App-V 5.1 Server
|
||||
|
||||
Use the following procedure to install the App-V server..
|
||||
Use the following procedure to install the App-V 5.1 server.
|
||||
|
||||
**Before you start:**
|
||||
|
||||
@ -24,11 +24,11 @@ Use the following procedure to install the App-V server..
|
||||
|
||||
- If you use SQL scripts, instead of the Windows Installer, to set up the Management database or Reporting database, you must run the SQL scripts before installing the Management Server or Reporting Server. See [How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md).
|
||||
|
||||
**To install the App-V server**
|
||||
**To install the App-V 5.1 server**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it.
|
||||
|
||||
2. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
|
||||
2. Start the App-V 5.1 server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
|
||||
|
||||
3. Review and accept the license terms, and choose whether to enable Microsoft updates.
|
||||
|
||||
@ -74,7 +74,7 @@ Use the following procedure to install the App-V server..
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
| - | - |
|
||||
Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser<br/>After installation, you can add additional users or groups by using the Management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use <strong>Domain local</strong> or <strong>Universal</strong> groups are required to perform this action.|
|
||||
| Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser<br/>After installation, you can add additional users or groups by using the Management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use <strong>Domain local</strong> or <strong>Universal</strong> groups are required to perform this action.|
|
||||
| **Website name**: Specify the custom name that will be used to run the publishing service.<br/>If you do not have a custom name, do not make any changes.|
|
||||
|**Port binding**: Specify a unique port number that will be used by App-V. | Example: **12345**<br/>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
@ -113,4 +113,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.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 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
|
||||
@ -19,7 +19,7 @@ App-V supports a number of different deployment options. This section of the App
|
||||
|
||||
This section describes how to install the App-V sequencer which is used to virtualize applications, and the App-V client which runs on target computers to facilitate virtualized packages.
|
||||
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
This section provides information about installing the App-V management, publishing, database and reporting severs.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploying the App-V Server (Windows 10)
|
||||
description: Deploying the App-V Server
|
||||
title: Deploying the App-V 5.1 Server
|
||||
description: Deploying the App-V 5.1 Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -8,15 +8,15 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Deploying the App-V Server
|
||||
# Deploying the App-V 5.1 Server
|
||||
|
||||
You can install the App-V server features by using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V Security Considerations](appv-security-considerations.md).
|
||||
You can install the Application Virtualization (App-V) 5.1 server features by using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V Security Considerations](appv-security-considerations.md).
|
||||
|
||||
For information about deploying the App-V Server, see [About App-V](appv-about-appv.md).
|
||||
|
||||
>**Important**<br>Before you install and configure the App-V servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
|
||||
>**Important**<br>Before you install and configure the App-V 5.1 servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
|
||||
|
||||
## Download and install App-V server components
|
||||
## Download and install App-V 5.1 server components
|
||||
|
||||
App-V offers the following five server components, each of which serves a specific purpose in an App-V environment.
|
||||
|
||||
@ -24,15 +24,15 @@ App-V offers the following five server components, each of which serves a specif
|
||||
|
||||
>**Note**<br>If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you can still take advantage of the reporting and streaming capabilities in App-V.
|
||||
|
||||
- **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to deploy the App-V server components](appv-deploy-the-appv-server.md) for more information about the management database.
|
||||
- **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md) for more information about the management database.
|
||||
|
||||
- **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. See [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md) for more information about configuring the publishing server.
|
||||
|
||||
- **Reporting server.** Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. See [About App-V reporting](appv-reporting.md) for more information about the reporting capabilities in App-V.
|
||||
|
||||
- **Reporting database.** Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to deploy the App-V server](appv-deploy-the-appv-server.md) for more information about the reporting database.
|
||||
- **Reporting database.** Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md) for more information about the reporting database.
|
||||
|
||||
All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from:
|
||||
All five App-V 5.1 server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from:
|
||||
|
||||
- The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215) You must have a MSDN subscription to download the MDOP ISO package from the MSDN subscriptions site.
|
||||
|
||||
@ -51,18 +51,18 @@ In large organizations, you might want to install more than one instance of the
|
||||
## App-V standalone deployment
|
||||
The App-V standalone deployment provides a good topology for a small deployment or a test environment. When you use this type of implementation, all server components are deployed to a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. Therefore, you should not use this topology for larger deployments.
|
||||
|
||||
- [How to Deploy the App-V Server](appv-deploy-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 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
- [How to Deploy the App-V 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
|
||||
## App-V Server distributed deployment
|
||||
The distributed deployment topology can support a large App-V client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V Server components are deployed across multiple computers, based on the structure and requirements of the organization.
|
||||
## App-V 5.1 Server distributed deployment
|
||||
The distributed deployment topology can support a large App-V client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V 5.1 Server components are deployed across multiple computers, based on the structure and requirements of the organization.
|
||||
|
||||
- [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)
|
||||
|
||||
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.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 5.1 Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
|
||||
- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
|
||||
@ -75,8 +75,8 @@ You can also deploy the App-V clients and packages by using an ESD without havin
|
||||
|
||||
[Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
## App-V Server logs
|
||||
You can use App-V server log information to help troubleshoot the server installation and operational events while using App-V. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
|
||||
## App-V 5.1 Server logs
|
||||
You can use App-V 5.1 server log information to help troubleshoot the server installation and operational events while using App-V. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
|
||||
|
||||
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**
|
||||
|
||||
|
||||
@ -59,7 +59,7 @@ This checklist can be used to help you during an App-V deployment.
|
||||
<ul>
|
||||
<li><p>[How to Install the Sequencer](appv-install-the-sequencer.md)</p></li>
|
||||
<li><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)</p></li>
|
||||
<li><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
|
||||
<li><p>[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)</p></li>
|
||||
</ul></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
|
||||
@ -32,7 +32,7 @@ With Windows 10, the App-V client is installed automatically. You need to enable
|
||||
|
||||
3. Restart the device.
|
||||
|
||||
4. To verify that the App-V client is enabled on the device, enter **AppvClientEnabled** or **Get-AppvStatus** in Windows PowerShell.
|
||||
4. To verify that the App-V client is enabled on the device, enter **Get-AppvStatus** in Windows PowerShell.
|
||||
|
||||
See [Using the client management console](appv-using-the-client-management-console.md) for information about configuring the App-V client.
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ Use the following links for information about setting up the App-V sequencer and
|
||||
|
||||
Use the following links for information about setting up the App-V server in your lab environment.
|
||||
|
||||
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
- [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)
|
||||
|
||||
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ The topics in this section provides information and step-by-step procedures to h
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
- [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
- [App-V Deployment Checklist](appv-deployment-checklist.md)
|
||||
- [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
- [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
|
||||
@ -30,7 +30,7 @@ To start using App-V to deliver virtual applications to users, you’ll need to
|
||||
|
||||
| Component | What it does | Where to find it |
|
||||
|------------|--|------|
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](#_Deploying_the_App-V). | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). <br>You must have a MSDN subscription to download the MDOP ISO package.<br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components. |
|
||||
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md). | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). <br>You must have a MSDN subscription to download the MDOP ISO package.<br>See [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components. |
|
||||
| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10. <br>For information about enabling the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
|
||||
| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must be running the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit). |
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ms.prod: w10
|
||||
# How to Install the App-V Client for Shared Content Store Mode
|
||||
|
||||
|
||||
Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. You should ensure that all required prerequisites are installed on the computer you plan to install to. Use the following link to see [App-V Prerequisites](appv-prerequisites.md).
|
||||
Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode.
|
||||
|
||||
**Enable the App-V client for SCS mode**
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
|
||||
**To install the management database and the management server on separate computers**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
@ -50,7 +50,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
|
||||
**To install the reporting database and the reporting server on separate computers**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
@ -79,7 +79,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
|
||||
**To install the management and reporting databases using App-V database scripts**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on.
|
||||
|
||||
2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ Use the following procedure to install the management server on a standalone com
|
||||
|
||||
**To install the management server on a standalone computer and connect it to the database**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ Use the following procedure to install the publishing server on a separate compu
|
||||
|
||||
**To install the publishing server on a separate computer**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ Before performing the following procedure you should read and understand [About
|
||||
|
||||
**To install the reporting server on a standalone computer and connect it to the database**
|
||||
|
||||
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
|
||||
|
||||
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ Review the following requirements for using the App-V PowerShell cmdlets:
|
||||
<td align="left"><p>Users can run App-V Server cmdlets only if you grant them access by using one of the following methods:</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p><strong>When you are deploying and configuring the App-V Server</strong>:</p>
|
||||
<p>Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></li>
|
||||
<p>Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).</p></li>
|
||||
<li><p><strong>After you’ve deployed the App-V Server</strong>:</p>
|
||||
<p>Use the App-V Management console to add an additional Active Directory group or user. See [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md).</p></li>
|
||||
</ul></td>
|
||||
|
||||
@ -14,17 +14,17 @@ ms.prod: w10
|
||||
|
||||
After you have completed all the necessary planning, and then deployment of App-V, you can use the following information to maintain the App-V infrastructure.
|
||||
|
||||
## <a href="" id="move-the-app-v-5-1-server-"></a>Move the App-V Server
|
||||
## <a href="" id="move-the-app-v-5-1-server-"></a>Move the App-V 5.1 Server
|
||||
|
||||
|
||||
The App-V server connects to the App-V database. Therefore you can install the management component to any computer on the network and then connect it to the App-V database.
|
||||
The App-V 5.1 server connects to the App-V database. Therefore you can install the management component to any computer on the network and then connect it to the App-V database.
|
||||
|
||||
[How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md)
|
||||
|
||||
## <a href="" id="determine-if-an-app-v-5-1-application-is-running-virtualized-"></a>Determine if an App-V Application is Running Virtualized
|
||||
|
||||
|
||||
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V or above, should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
|
||||
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
|
||||
|
||||
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V and above, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
|
||||
|
||||
|
||||
@ -13,14 +13,13 @@ ms.prod: w10
|
||||
|
||||
|
||||
With Microsoft Application Virtualization (App-V), you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V infrastructure.
|
||||
However, you cannot migrate directly from App-V 4.x to App-V, you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
However, you cannot migrate directly from App-V 4.x to App-V for Windows 10—you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating to App-V 5.1 from a Previous Version](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version)
|
||||
|
||||
**Note**
|
||||
App-V packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V packages.
|
||||
Packages for App-V for Windows 10 are exactly the same as packages for App-V 5.0. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V for Window 10 packages.
|
||||
|
||||
For more information about the differences between App-V 4.6 and App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50).
|
||||
For information about the differences between earlier versions of App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50).
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
|
||||
|
||||
@ -252,7 +251,7 @@ You must be running the latest version of App-V 4.6 to use coexistence mode. Ad
|
||||
|
||||
|
||||
|
||||
## Migrating the App-V Server Full Infrastructure
|
||||
## Migrating the App-V 5.1 Server Full Infrastructure
|
||||
|
||||
|
||||
There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
|
||||
@ -278,8 +277,8 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
|
||||
<td align="left"><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Install App-V server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
<td align="left"><p>Install App-V 5.1 server.</p></td>
|
||||
<td align="left"><p>[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Migrate existing packages.</p></td>
|
||||
|
||||
@ -19,7 +19,7 @@ Use the following information to create a new management server console in your
|
||||
|
||||
The following list displays the steps necessary to create a new management server console:
|
||||
|
||||
1. Install the management server on a computer in your environment. For more information about installing the management server see [Deploying the App-V Server](appv-deploying-the-appv-server.md).
|
||||
1. Install the management server on a computer in your environment. For more information about installing the management server see [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md).
|
||||
|
||||
2. After you have completed the installation, use the following link to connect it to the App-V database - [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md).
|
||||
|
||||
|
||||
@ -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 Server Deployment](appv-planning-for-appv-server-deployment.md)</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></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Planning for the App-V Server Deployment (Windows 10)
|
||||
description: Planning for the App-V Server Deployment
|
||||
title: Planning for the App-V 5.1 Server Deployment (Windows 10)
|
||||
description: Planning for the App-V 5.1 Server Deployment
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,15 +9,15 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for the App-V Server Deployment
|
||||
# Planning for the App-V 5.1 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 Server Deployment
|
||||
## Planning for App-V 5.1 Server Deployment
|
||||
|
||||
|
||||
The App-V server consists of the following features:
|
||||
The App-V 5.1 server consists of the following features:
|
||||
|
||||
- Management Server – provides overall management functionality for the App-V infrastructure.
|
||||
|
||||
@ -29,9 +29,9 @@ The App-V 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 server infrastructure:
|
||||
The following list displays the recommended methods for installing the App-V 5.1 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 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 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 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 5.1 servers. The table also includes the reporting mechanism for each server type.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -96,21 +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).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[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 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Planning for High Availability with App-V Server (Windows 10)
|
||||
title: Planning for High Availability with App-V Server
|
||||
description: Planning for High Availability with App-V Server
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
|
||||
@ -38,10 +38,7 @@ Ideally, you should install the sequencer on a computer running as a virtual mac
|
||||
|
||||
## Planning for App-V client deployment
|
||||
|
||||
In Windows 10, version 1607, the App-V client is included with the operating system. For more info, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
For a list of the client minimum requirements see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
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)
|
||||
|
||||
|
||||
@ -37,11 +37,11 @@ Describes the options and requirements for deploying App-V with an electronic so
|
||||
|
||||
[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 Server deployment
|
||||
## Planning for the App-V 5.1 Server deployment
|
||||
|
||||
Describes the planning considerations for the App-V Server components and their functions.
|
||||
|
||||
[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
|
||||
## Planning for the App-V Sequencer and Client deployment
|
||||
|
||||
|
||||
@ -75,7 +75,7 @@ The following table indicates the software that is already installed for differe
|
||||
## App-V Server prerequisite software
|
||||
|
||||
|
||||
Install the required prerequisite software for the App-V Server components.
|
||||
Install the required prerequisite software for the App-V 5.1 Server components.
|
||||
|
||||
### What to know before you start
|
||||
|
||||
@ -517,50 +517,6 @@ The Reporting database is required only if you are using the App-V Reporting ser
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## App-V client prerequisite software
|
||||
|
||||
|
||||
Install the following prerequisite software for the App-V client.
|
||||
|
||||
> [!NOTE]
|
||||
> This is not required on Windows 10, version 1607.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Prerequisite</th>
|
||||
<th align="left">Details</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595)</p>
|
||||
<p></p></td>
|
||||
<td align="left"><p>Installing PowerShell 3.0 requires a restart.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[KB2533623](http://support.microsoft.com/kb/2533623)</p></td>
|
||||
<td align="left"><p>Applies to Windows 7 only: Download and install the KB.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784)</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Remote Desktop Services client prerequisite software
|
||||
|
||||
|
||||
|
||||
@ -13,150 +13,39 @@ ms.prod: w10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Review these known issues in Microsoft Application Virtualization (App-V) for Windows.
|
||||
The following is a known issue in Microsoft Application Virtualization (App-V) in Windows 10, version 1607:
|
||||
|
||||
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
|
||||
**MSI packages generated by App-V 5.1 and older sequencer fail to install on computers with built-in App-V client**
|
||||
|
||||
When MSI packages are generated by an older sequencer (5.1 and below), they include a check to ensure the App-V client is installed before allowing the MSI package to install. Since App-V client is now part of the operating system, the pre-requisite check fails and it leads to MSI installation failure.
|
||||
|
||||
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10 . This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier.
|
||||
**Workaround**:
|
||||
|
||||
**Workaround**: Upgrade the App-V 5.0 management server to the App-V management server for Windows 10 clients.
|
||||
1. Install the latest App-V sequencer, which is part of the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607. See [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). For more information, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
|
||||
2. Ensure that you have installed the **MSI Tools** included in the Windows 10 SDK, available as follows:
|
||||
|
||||
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration.
|
||||
- For the **Visual Studio Community 2015 with Update 3** client, which includes the latest Windows 10 SDK and developer tools, see [Downloads and tools for Windows 10](https://developer.microsoft.com/en-us/windows/downloads).
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
- For the standalone Windows 10 SDK without other tools, see [Standalone Windows 10 SDK](https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk).
|
||||
|
||||
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration is stored in each user’s profile and will be applied correctly.
|
||||
3. From an elevated Windows PowerShell prompt, navigate to the following folder:
|
||||
|
||||
- Create a custom deployment configuration file and apply it to the package on the client using the Add-AppvClientPackage cmdlet with the –DynamicDeploymentConfiguration parameter. See [About App-V Dynamic Configuration](appv-dynamic-configuration.md) for more information.
|
||||
<Windows Kits 10 installation folder>**\Microsoft Application Virtualization\Sequencer\**
|
||||
|
||||
- Create a new package with the custom configuration using the App-V sequencer.
|
||||
By default, this path will be:<br>**C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer**
|
||||
|
||||
## Server files not deleted after new App-V for Windows server installation
|
||||
4. Run the following command:
|
||||
|
||||
`Update-AppvPackageMsi -MsiPackage "<path to App-V Package .msi file>" -MsSdkPath "<path to Windows SDK installation>"`
|
||||
|
||||
If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files are not being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation.
|
||||
By default, the path to the Windows SDK installation will be:<br>**C:\Program Files (x86)\Windows Kits\10**
|
||||
|
||||
**Workaround**: Delete this registry key before you start installing App-V:
|
||||
|
||||
Under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall, locate and delete the installation GUID key that contains the DWORD value "DisplayName" with value data "Microsoft Application Virtualization (App-V) Server". This is the only key that should be deleted.
|
||||
|
||||
## File type associations added manually are not saved correctly
|
||||
|
||||
|
||||
File type associations added to an application package manually using the Shortcuts and FTAs tab at the end of the application upgrade wizard are not saved correctly. They will not be available to the App-V Client or to the Sequencer when updating the saved package again.
|
||||
|
||||
**Workaround**: To add a file type association, open the package for modification and run the update wizard. During the Installation step, add the new file type association through the operating system. The sequencer will detect the new association in the system registry and add it to the package’s virtual registry, where it will be available to the client.
|
||||
|
||||
## When streaming packages in Shared Content Store (SCS) mode to a client that is also managed with AppLocker, additional data is written to the local disk.
|
||||
|
||||
|
||||
To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V Client to stream the contents of a package on demand. However, if AppLocker manages an application within the package, some data might be written to the client’s local disk that would not otherwise be written.
|
||||
|
||||
**Workaround**: None
|
||||
|
||||
## In the Management Console Add Package dialog box, the Browse button is not available when using Chrome or Firefox
|
||||
|
||||
|
||||
On the Packages page of the Management Console, if you click **Add or Upgrade** in the lower-right corner, the **Add Package** dialog box appears. If you are accessing the Management Console using Chrome or Firefox as your browser, you will not be able to browse to the location of the package.
|
||||
|
||||
**Workaround**: Type or copy and paste the path to the package into the **Add Package** input field. If the Management Console has access to this path, you will be able to add the package. If the package is on a network share, you can browse to the location using File Explorer by doing these steps:
|
||||
|
||||
1. While pressing **Shift**, right-click on the package file
|
||||
|
||||
2. Select **Copy as path**
|
||||
|
||||
3. Paste the path into the **Add Package** dialog box input field
|
||||
|
||||
## <a href="" id="upgrading-app-v-management-server-to-5-1-sometimes-fails-with-the-message--a-database-error-occurred-"></a>Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
|
||||
|
||||
|
||||
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”
|
||||
|
||||
**Workaround**: Run this command on your SQL database:
|
||||
|
||||
`ALTER TABLE AppVManagement.dbo.PackageGroupMembers ADD PackageOptional bit NOT NULL DEFAULT 0, VersionOptional bit NOT NULL DEFAULT 0`
|
||||
|
||||
where “AppVManagement” is the name of the database.
|
||||
|
||||
## Users cannot open a package in a user-published connection group if you add or remove an optional package
|
||||
|
||||
|
||||
In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group.
|
||||
|
||||
**Workaround**: Have users log out and then log back in.
|
||||
|
||||
## Error message is erroneously displayed when the connection group is published only to the user
|
||||
|
||||
|
||||
When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.”
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
|
||||
- Publish all packages in a connection group.
|
||||
|
||||
The problem arises when the connection group being repaired has packages that are missing or not available to the user (that is, not published globally or to the user). However, the repair will work if all of the connection group’s packages are available, so ensure that all packages are published.
|
||||
|
||||
- Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-AppvClientConnectionGroup command.
|
||||
|
||||
Determine which packages are available to users and then run the Repair-AppvClientPackage command once for each package. Use PowerShell cmdlets to do the following:
|
||||
|
||||
1. Get all the packages in a connection group.
|
||||
|
||||
2. Check to see if each package is currently published.
|
||||
|
||||
3. If the package is currently published, run Repair-AppvClientPackage on that package.
|
||||
|
||||
## Icons not displayed properly in Sequencer
|
||||
|
||||
|
||||
Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32.
|
||||
|
||||
**Workaround**: Only use icons that are 16x16 or 32x32.
|
||||
|
||||
## InsertVersionInfo.sql script no longer required for the Management Database
|
||||
|
||||
|
||||
The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
|
||||
|
||||
The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340).
|
||||
|
||||
**Important**
|
||||
**Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
|
||||
|
||||
|
||||
|
||||
## Microsoft Visual Studio 2012 not supported
|
||||
|
||||
|
||||
App-V does not support Visual Studio 2012.
|
||||
|
||||
**Workaround**: None
|
||||
|
||||
## Application filename restrictions for App-V Sequencer
|
||||
|
||||
|
||||
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**Workaround**: Use a different filename
|
||||
|
||||
## 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).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[About App-V](appv-about-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -308,7 +308,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
|
||||
|
||||
[How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md)
|
||||
|
||||
|
||||
@ -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 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.
|
||||
**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.
|
||||
|
||||
**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 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 5.1 servers.
|
||||
|
||||
**Note**
|
||||
App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **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 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 5.1 server operations.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
|
||||
@ -18,13 +18,13 @@ This topic specifies the requirements to install and run App-V in your environme
|
||||
|
||||
This section lists the operating system and hardware requirements for all of the App-V Server components.
|
||||
|
||||
### Unsupported App-V Server scenarios
|
||||
### Unsupported App-V 5.1 Server scenarios
|
||||
|
||||
The App-V Server does not support the following scenarios:
|
||||
The App-V 5.1 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 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 App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
|
||||
- Deployment to a computer that runs a previous version of 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 App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
|
||||
|
||||
- Deployment to a computer that runs Microsoft SQL Server Express edition.
|
||||
|
||||
@ -271,129 +271,11 @@ The following table lists the SQL Server versions that are supported for the App
|
||||
|
||||
|
||||
|
||||
## App-V client system requirements
|
||||
## App-V client requirements and Remote Desktop Services client requirements
|
||||
|
||||
With Windows 10, version 1607 and later releases, the App-V client is included with Windows 10 Enterprise and Windows 10 Education. The App-V client is no longer part of the Microsoft Desktop Optimization Pack. Before you can use the App-V client, it must be enabled, as described in [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
The following table lists the operating systems that are supported for the App-V client installation.
|
||||
|
||||
> [!NOTE]
|
||||
> App-V is included with Windows 10, version 1607 and later.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Service pack</th>
|
||||
<th align="left">System architecture</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10, version 1511</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 10, version 1507</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows 8.1</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Windows 8</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Windows /p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>32-bit or 64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
The following App-V client installation scenarios are not supported, except as noted:
|
||||
|
||||
- Computers that run Windows Server
|
||||
|
||||
- Computers that run App-V 4.6 SP1 or earlier versions
|
||||
|
||||
- The App-V Remote Desktop services client is supported only for RDS-enabled servers
|
||||
|
||||
### App-V client hardware requirements
|
||||
|
||||
The following list displays the supported hardware configuration for the App-V client installation.
|
||||
|
||||
- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
|
||||
|
||||
- RAM— 1 GB (32-bit) or 2 GB (64-bit)
|
||||
|
||||
- Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
|
||||
|
||||
## Remote Desktop Services client system requirements
|
||||
|
||||
|
||||
The following table lists the operating systems that are supported for App-V Remote Desktop Services (RDS) client installation.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Operating system</th>
|
||||
<th align="left">Service Pack</th>
|
||||
<th align="left">System architecture</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2016</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Microsoft Windows Server 2012</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
|
||||
<td align="left"><p>SP1</p></td>
|
||||
<td align="left"><p>64-bit</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Remote Desktop Services client hardware requirements
|
||||
|
||||
App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
- Processor—1.4 GHz or faster, 64-bit (x64) processor
|
||||
|
||||
- RAM—2 GB RAM (64-bit)
|
||||
|
||||
- Disk space—200 MB available hard disk space
|
||||
Similarly, the App-V Remote Desktop Services (RDS) client is included with Windows Server 2016 Standard and Windows Server 2016 Datacenter.
|
||||
|
||||
## Sequencer system requirements
|
||||
|
||||
@ -452,7 +334,6 @@ The following table lists the operating systems that are supported for the App-V
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Sequencer hardware requirements
|
||||
|
||||
@ -460,191 +341,7 @@ See the Windows or Windows Server documentation for the hardware requirements. A
|
||||
|
||||
## <a href="" id="bkmk-supp-ver-sccm"></a>Supported versions of System Center Configuration Manager
|
||||
|
||||
|
||||
The App-V client supports the following versions of System Center Configuration Manager:
|
||||
|
||||
- Microsoft System Center 2012 Configuration Manager
|
||||
|
||||
- System Center 2012 R2 Configuration Manager
|
||||
|
||||
- System Center 2012 R2 Configuration Manager SP1
|
||||
|
||||
The following App-V and System Center Configuration Manager version matrix shows all officially supported combinations of App-V and Configuration Manager.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
<col width="12%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">App-V Version</th>
|
||||
<th align="left">System Center Configuration Manager 2007</th>
|
||||
<th align="left">System Center 2012 Configuration Manager</th>
|
||||
<th align="left">System Center 2012 Configuration Manager SP1</th>
|
||||
<th align="left">System Center 2012 R2 Configuration Manager</th>
|
||||
<th align="left">System Center 2012 R2 Configuration Manager SP1</th>
|
||||
<th align="left">System Center 2012 Configuration Manager SP2</th>
|
||||
<th align="left">System Center Configuration Manager Version 1511</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 CU1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.5 SP1</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.5 SP2</p></td>
|
||||
<td align="left"><p>R2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6</p></td>
|
||||
<td align="left"><p>R2, SP1</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP1</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 4.6 SP2</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 4.6 SP3</p></td>
|
||||
<td align="left"><p>R2, R3, SP2</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0</p></td>
|
||||
<td align="left"><p>MSI-Wrapper-Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP1</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP2</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
<td align="left"><p>With App-V 5.0 SP2 HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V 5.0 SP2 HF4</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p>
|
||||
<p>App-V 5.0 HF5 or later</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
<td align="left"><p>Requires HF5 or later</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V 5.0 SP3</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V</p></td>
|
||||
<td align="left"><p>MSI-Wrapper Only</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
<td align="left"><p>2012 SP1 CU4</p></td>
|
||||
<td align="left"><p>2012 R2 CU1</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
For more information about how Configuration Manager integrates with App-V, see [Planning for App-V Integration with Configuration Manager](http://technet.microsoft.com/library/jj822982.aspx).
|
||||
The App-V client works with System Center Configuration Manager versions starting with Technical Preview for System Center Configuration Manager, version 1606.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -18,6 +18,7 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
| [Configure Windows 10 taskbar](configure-windows-10-taskbar.md) | Updated sample XML for combined Start and taskbar layout; added note to explain the difference between applying taskbar configuration by Group Policy and by provisioning package |
|
||||
| [Set up a kiosk on Windows 10 Pro, Enterprise, or Education](set-up-a-kiosk-for-windows-10-for-desktop-editions.md) | Updated instructions for exiting assigned access mode. |
|
||||
|
||||
## RELEASE: Windows 10, version 1607
|
||||
|
||||
|
||||
@ -247,7 +247,7 @@ Edit the registry to have an account automatically logged on.
|
||||
|
||||
### Sign out of assigned access
|
||||
|
||||
To sign out of an assigned access account, press **Ctrl + Alt + Del**, and then sign in using another account. When you press **Ctrl + Alt + Del** to sign out of assigned access, the kiosk app will exit automatically. If you sign in again as the assigned access account or wait for the login screen timeout, the kiosk app will be re-launched.
|
||||
To exit the assigned access (kiosk) app, press **Ctrl + Alt + Del**, and then sign in using another account. When you press **Ctrl + Alt + Del** to sign out of assigned access, the kiosk app will exit automatically. If you sign in again as the assigned access account or wait for the login screen timeout, the kiosk app will be re-launched. The assigned access user will remain signed in until an admin account opens **Task Manager** > **Users** and signs out the user account.
|
||||
|
||||
If you press **Ctrl + Alt + Del** and do not sign in to another account, after a set time, assigned access will resume. The default time is 30 seconds, but you can change that in the following registry key:
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user