ScriptRunner.exe
|
-The script launcher application that is installed as part of the App-V client installation.
+ | The script launcher application that is included in the App-V client.
Note
- Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.
+ Although ScriptRunner.exe is included in the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.
diff --git a/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
index bf8851078f..4712ea5236 100644
--- a/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
+++ b/windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Enable Only Administrators to Publish Packages by Using an ESD
+Applies to: Windows 10, version 1607
Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you could not prevent end users from performing these tasks.
@@ -18,7 +19,7 @@ Starting in App-V 5.0 SP3, you can configure the App-V client so that only admin
1. Navigate to the following Group Policy Object node:
- **Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
+ **Computer Configuration > Administrative Templates > System > App-V > Publishing**.
2. Enable the **Require publish as administrator** Group Policy setting.
diff --git a/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md b/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md
index 7451d59112..719260f7f2 100644
--- a/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md
+++ b/windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Enable Reporting on the App-V Client by Using PowerShell
+Applies to: Windows 10, version 1607
Use the following procedure to configure the App-V for reporting.
@@ -84,4 +85,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
-[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
+[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/manage/appv-enable-the-app-v-desktop-client.md b/windows/manage/appv-enable-the-app-v-desktop-client.md
index e10f3d842c..372d15f311 100644
--- a/windows/manage/appv-enable-the-app-v-desktop-client.md
+++ b/windows/manage/appv-enable-the-app-v-desktop-client.md
@@ -10,6 +10,8 @@ ms.prod: w10
# Enable the App-V in-box client
+Applies to: Windows 10, version 1607
+
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 client can also get virtual application content from the management server.
With Windows 10, version 1607, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
@@ -32,9 +34,18 @@ With Windows 10, version 1607, the App-V client is installed automatically. You
3. Restart the device.
-4. To verify that the App-V client is enabled on the device, type `Get-AppvStatus` and press ENTER.
+4. To verify that the App-V client is enabled on the device, type `Get-AppvStatus` and press ENTER.
-See [Using the client management console](appv-using-the-client-management-console.md) for information about configuring the App-V client.
+
+For information about configuring the App-V client, see:
+
+- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
+
+- [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
+
+- [Using the client management console](appv-using-the-client-management-console.md)
+
+- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
## Have a suggestion for App-V?
diff --git a/windows/manage/appv-evaluating-appv.md b/windows/manage/appv-evaluating-appv.md
index 6ce476b57b..752e208607 100644
--- a/windows/manage/appv-evaluating-appv.md
+++ b/windows/manage/appv-evaluating-appv.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Evaluating App-V
+Applies to: Windows 10, version 1607
+
Before you deploy App-V into a production environment, you should evaluate it in a lab environment. You can use the information in this topic to set up App-V in a lab environment for evaluation purposes only.
## Configure lab computers for App-V Evaluation
diff --git a/windows/manage/appv-for-windows.md b/windows/manage/appv-for-windows.md
index 17e12bb59e..b39dc03511 100644
--- a/windows/manage/appv-for-windows.md
+++ b/windows/manage/appv-for-windows.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Application Virtualization (App-V) for Windows 10 overview
+Applies to: Windows 10, version 1607
The topics in this section provide information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
@@ -31,7 +32,7 @@ The topics in this section provide information and step-by-step procedures to he
[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 Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
- [Deploying the App-V 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)
@@ -46,7 +47,7 @@ The topics in this section provide information and step-by-step procedures to he
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
- [Maintaining App-V](appv-maintaining-appv.md)
-- [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
+- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
[Troubleshooting App-V](appv-troubleshooting.md)
diff --git a/windows/manage/appv-getting-started.md b/windows/manage/appv-getting-started.md
index de7fadffcd..bd71d41e48 100644
--- a/windows/manage/appv-getting-started.md
+++ b/windows/manage/appv-getting-started.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Getting Started with App-V for Windows 10
+Applies to: Windows 10, version 1607
+
Microsoft Application Virtualization (App-V) for Windows 10 enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise). If you are new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. For information about what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
diff --git a/windows/manage/appv-high-level-architecture.md b/windows/manage/appv-high-level-architecture.md
index 396b92d811..6bd39c9a55 100644
--- a/windows/manage/appv-high-level-architecture.md
+++ b/windows/manage/appv-high-level-architecture.md
@@ -11,6 +11,7 @@ ms.prod: w10
# High Level Architecture for App-V
+Applies to: Windows 10, version 1607
Use the following information to help you simplify you Microsoft Application Virtualization (App-V) deployment.
diff --git a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md
index f02ef3fd54..77ee61220b 100644
--- a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md
+++ b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md
@@ -1,29 +1,4 @@
---
title: How to Install the App-V Client for Shared Content Store Mode (Windows 10)
-description: How to Install the App-V Client for Shared Content Store Mode
-author: MaggiePucciEvans
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
+redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client
---
-
-
-# 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.
-
-**Enable the App-V client for SCS mode**
-
-1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
-
-2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
-
-## Have a suggestion for App-V?
-
-Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related topics
-
-- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
diff --git a/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md b/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
index 7bb1ffa822..787a0bfe6c 100644
--- a/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
+++ b/windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts.
@@ -378,7 +379,7 @@ Before attempting this procedure, you should read and understand the information
## Related topics
-[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
+[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md
index 9f74a81f7a..c104d88d25 100644
--- a/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md
+++ b/windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.
diff --git a/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md
index 28cdb2f0b8..b964115f3b 100644
--- a/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md
+++ b/windows/manage/appv-install-the-management-server-on-a-standalone-computer.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to install the Management Server on a Standalone Computer and Connect it to the Database
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use the following procedure to install the management server on a standalone computer and connect it to the database.
diff --git a/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md b/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md
index 414c59f646..36bf1a453f 100644
--- a/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md
+++ b/windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Install the Publishing Server on a Remote Computer
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use the following procedure to install the publishing server on a separate computer. Before you perform the following procedure, ensure the database and management server are available.
diff --git a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md
index db35c6f9aa..324f9b5804 100644
--- a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md
+++ b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to install the Reporting Server on a Standalone Computer and Connect it to the Database
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use the following procedure to install the reporting server on a standalone computer and connect it to the database.
diff --git a/windows/manage/appv-install-the-sequencer.md b/windows/manage/appv-install-the-sequencer.md
index 19d09c9a09..3582d6adb7 100644
--- a/windows/manage/appv-install-the-sequencer.md
+++ b/windows/manage/appv-install-the-sequencer.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Install the App-V Sequencer
+Applies to: Windows 10, version 1607
+
Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Those devices must be running the App-V client to allow users to interact with virtual applications.
The App-V Sequencer is included in the Windows 10 Assessment and Deployment Kit (Windows ADK).
diff --git a/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
index dca76e75eb..d96ba47b0a 100644
--- a/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
+++ b/windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Load the PowerShell Cmdlets and Get Cmdlet Help
+Applies to: Windows 10, version 1607
What this topic covers:
diff --git a/windows/manage/appv-maintaining-appv.md b/windows/manage/appv-maintaining-appv.md
index 525a693300..c59a30d5c9 100644
--- a/windows/manage/appv-maintaining-appv.md
+++ b/windows/manage/appv-maintaining-appv.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Maintaining App-V
+Applies to: Windows 10, version 1607
After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure.
diff --git a/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
index 5447eb8b36..81e50c0cee 100644
--- a/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
+++ b/windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
@@ -11,6 +11,8 @@ ms.prod: w10
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
+Applies to: Windows 10, version 1607
+
The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell:
@@ -282,7 +284,7 @@ For more information about pending tasks, see [Upgrading an in-use App-V package
[Operations for App-V](appv-operations.md)
-[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
+[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
index b54a3e959a..140842081a 100644
--- a/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
+++ b/windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
@@ -11,10 +11,11 @@ ms.prod: w10
# How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
+Applies to: Windows 10, version 1607
An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group.
-A connection group XML file defines the connection group that runs on the computer where you’ve installed the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
+A connection group XML file defines the connection group for the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
This topic explains the following procedures:
@@ -134,7 +135,7 @@ This topic explains the following procedures:
[Operations for App-V](appv-operations.md)
-[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
+[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/manage/appv-managing-connection-groups.md b/windows/manage/appv-managing-connection-groups.md
index f702b6c319..1128ed8e21 100644
--- a/windows/manage/appv-managing-connection-groups.md
+++ b/windows/manage/appv-managing-connection-groups.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Managing Connection Groups
+Applies to: Windows 10, version 1607
Connection groups enable the applications within a package to interact with each other in the virtual environment, while remaining isolated from the rest of the system. By using connection groups, administrators can manage packages independently and can avoid having to add the same application multiple times to a client computer.
diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md
index 8baa974696..0c954a7bf8 100644
--- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md
+++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md
@@ -207,46 +207,9 @@ It is recommended that you use the App-V sequencer for converting critical appli
If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer.
-
-
[How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
-## Migrating Clients
-
-
-The following table displays the recommended method for upgrading clients.
-
-
-
-
-
-
-
-
-
-
-
-Upgrade your environment to the latest version of App-V 4.6 |
-[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy). |
-
-
-Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages. |
-[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md). |
-
-
-
-
-
-
-**Important**
-You must be running the latest version of App-V 4.6 to use coexistence mode. Additionally, when you sequence a package, you must configure the Managing Authority setting, which is in the **User Configuration** is located in the **User Configuration** section.
-
-
-
-## Migrating the App-V server Server Full Infrastructure
+## Migrating the App-V 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.
@@ -264,20 +227,20 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
-Upgrade your environment to the latest version of App-V 4.6. |
-[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy). |
+Review prerequisites. |
+[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software). |
-Deploy App-V version of the client. |
+Enable the App-V client. |
[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
-Install App-V server server. |
-[How to Deploy the App-V server Server](appv-deploy-the-appv-server.md). |
+Install App-V Server. |
+[How to Deploy the App-V Server](appv-deploy-the-appv-server.md). |
Migrate existing packages. |
-See Converting packages created using a prior version of App-V earlier in this topic. |
+See [Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this topic. |
diff --git a/windows/manage/appv-modify-an-existing-virtual-application-package.md b/windows/manage/appv-modify-an-existing-virtual-application-package.md
index b3b9a5bea2..de766bb0d5 100644
--- a/windows/manage/appv-modify-an-existing-virtual-application-package.md
+++ b/windows/manage/appv-modify-an-existing-virtual-application-package.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Modify an Existing Virtual Application Package
+Applies to: Windows 10, version 1607
This topic explains how to:
diff --git a/windows/manage/appv-modify-client-configuration-with-powershell.md b/windows/manage/appv-modify-client-configuration-with-powershell.md
index 0d76bd1169..3843e5468f 100644
--- a/windows/manage/appv-modify-client-configuration-with-powershell.md
+++ b/windows/manage/appv-modify-client-configuration-with-powershell.md
@@ -1,6 +1,6 @@
---
-title: How to Modify Client Configuration by Using PowerShell (Windows 10)
-description: How to Modify Client Configuration by Using PowerShell
+title: How to Modify Client Configuration by Using Windows PowerShell (Windows 10)
+description: How to Modify Client Configuration by Using Windows PowerShell
author: MaggiePucciEvans
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
@@ -9,16 +9,15 @@ ms.prod: w10
---
-# How to Modify Client Configuration by Using PowerShell
+# How to Modify Client Configuration by Using Windows PowerShell
+Applies to: Windows 10, version 1607
Use the following procedure to configure the App-V client configuration.
-**To modify App-V client configuration using PowerShell**
+1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
-1. To configure the client settings using PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing PowerShell, and a list of cmdlets see, [How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
-
-2. To modify the client configuration, open a PowerShell Command prompt and run the following cmdlet **Set-AppvClientConfiguration** with any required parameters. For example:
+2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppvClientConfiguration** with any required parameters. For example:
`$config = Get-AppvClientConfiguration`
@@ -26,18 +25,11 @@ Use the following procedure to configure the App-V client configuration.
`Set-AppcClientConfiguration –Name1 MyConfig –Name2 “xyz”`
- **Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
+
+## 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
-
[Operations for App-V](appv-operations.md)
-
-
-
-
-
-
-
-
-
diff --git a/windows/manage/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md b/windows/manage/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md
index a71950444f..5d1058e257 100644
--- a/windows/manage/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md
+++ b/windows/manage/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md
@@ -1,23 +1,4 @@
---
title: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy (Windows 10)
-description: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy
-author: MaggiePucciEvans
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
+redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client
---
-
-# How to Modify App-V client configuration using the ADMX template and Group Policy
-
-You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Policies** > **Administrative Templates** > **System** > **App-V**.
-
-## Have a suggestion for App-V?
-
-Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related topics
-
-- [Deploying App-V](appv-deploying-appv.md)
-
-- [About Client Configuration Settings](appv-client-configuration-settings.md)
diff --git a/windows/manage/appv-move-the-appv-server-to-another-computer.md b/windows/manage/appv-move-the-appv-server-to-another-computer.md
index 0a7e9d26c6..98840475e6 100644
--- a/windows/manage/appv-move-the-appv-server-to-another-computer.md
+++ b/windows/manage/appv-move-the-appv-server-to-another-computer.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to move the App-V server to another computer
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use the following information to create a new management server console in your environment.
diff --git a/windows/manage/appv-operations.md b/windows/manage/appv-operations.md
index 96cdf448fb..9ab975f65f 100644
--- a/windows/manage/appv-operations.md
+++ b/windows/manage/appv-operations.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Operations for App-V
+Applies to: Windows 10, version 1607
This section of the Microsoft Application Virtualization (App-V) Administrator’s Guide includes information about the various types of App-V administration and operating tasks that are typically performed by an administrator. This section also includes step-by-step procedures to help you successfully perform those tasks.
@@ -41,7 +42,7 @@ This section of the Microsoft Application Virtualization (App-V) Administrator
Provides instructions for migrating to App-V from a previous version.
-- [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
+- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
Describes the set of Windows PowerShell cmdlets available for administrators performing various App-V server tasks.
diff --git a/windows/manage/appv-performance-guidance.md b/windows/manage/appv-performance-guidance.md
index 0154fa543b..7d81539a07 100644
--- a/windows/manage/appv-performance-guidance.md
+++ b/windows/manage/appv-performance-guidance.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Performance Guidance for Application Virtualization
+Applies to: Windows 10, version 1607
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
@@ -171,9 +172,9 @@ The following table displays the required steps to prepare the base image and th
-Install the App-V client version of the client.
+Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
-Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
+Configure for Shared Content Store (SCS) mode. For more information see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
Configure Preserve User Integrations on Login Registry DWORD.
Pre-configure all user- and global-targeted packages for example, Add-AppvClientPackage.
Pre-configure all user- and global-targeted connection groups for example, Add-AppvClientConnectionGroup.
@@ -191,9 +192,9 @@ The following table displays the required steps to prepare the base image and th
|
-Install the App-V client version of the client.
+Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
-Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
+Configure for Shared Content Store (SCS) mode. For more information see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
Configure Preserve User Integrations on Login Registry DWORD.
Pre-configure all global-targeted packages for example, Add-AppvClientPackage.
Pre-configure all global-targeted connection groups for example, Add-AppvClientConnectionGroup.
@@ -225,8 +226,7 @@ The following table displays the required steps to prepare the base image and th
Shared Content Store (SCS) Mode
-Configurable in PowerShell using Set- AppvClientConfiguration –SharedContentStoreMode, or
-During installation of the App-V client.
+Configurable in Windows PowerShell with `Set-AppvClientConfiguration -SharedContentStoreMode 1` or configurable with Group Policy, as described in [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
|
When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).
This helps to conserve local storage and minimize disk I/O per second (IOPS). |
diff --git a/windows/manage/appv-planning-checklist.md b/windows/manage/appv-planning-checklist.md
index 91d7f0fe4e..98fab89487 100644
--- a/windows/manage/appv-planning-checklist.md
+++ b/windows/manage/appv-planning-checklist.md
@@ -11,6 +11,7 @@ ms.prod: w10
# App-V Planning Checklist
+Applies to: Windows 10, version 1607
This checklist can be used to help you plan for preparing your organization for an App-V deployment.
@@ -41,7 +42,7 @@ This checklist can be used to help you plan for preparing your organization for
 |
-Plan for App-V 1.0 Deployment Prerequisites and prepare your computing environment. |
+Plan for App-V deployment prerequisites and prepare your computing environment. |
[App-V Prerequisites](appv-prerequisites.md) |
|
@@ -60,13 +61,13 @@ This checklist can be used to help you plan for preparing your organization for
 |
If applicable, review the options and steps for migrating from a previous version of App-V. |
-[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md) |
+[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) |
|
 |
-Plan for running App-V clients using in shared content store mode. |
-[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md) |
+Decide whether to configure App-V clients in Shared Content Store mode. |
+[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md) |
|
diff --git a/windows/manage/appv-planning-folder-redirection-with-appv.md b/windows/manage/appv-planning-folder-redirection-with-appv.md
index ed2d892f9f..0fa4187590 100644
--- a/windows/manage/appv-planning-folder-redirection-with-appv.md
+++ b/windows/manage/appv-planning-folder-redirection-with-appv.md
@@ -10,6 +10,8 @@ ms.prod: w10
# Planning to Use Folder Redirection with App-V
+Applies to: Windows 10, version 1607
+
Microsoft Application Virtualization (App-V) supports the use of folder redirection, a feature that enables users and administrators to redirect the path of a folder to a new location.
This topic contains the following sections:
diff --git a/windows/manage/appv-planning-for-appv-server-deployment.md b/windows/manage/appv-planning-for-appv-server-deployment.md
index 26fb4f3269..5b529740ab 100644
--- a/windows/manage/appv-planning-for-appv-server-deployment.md
+++ b/windows/manage/appv-planning-for-appv-server-deployment.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Planning for the App-V Server Deployment
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
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.
diff --git a/windows/manage/appv-planning-for-appv.md b/windows/manage/appv-planning-for-appv.md
index 3ffee286de..f96314b3c9 100644
--- a/windows/manage/appv-planning-for-appv.md
+++ b/windows/manage/appv-planning-for-appv.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Planning for App-V
+Applies to: Windows 10, version 1607
+
Use this information to plan how to deploy App-V so that it does not disrupt your users or the network.
## Planning information
@@ -21,7 +23,7 @@ Use this information to plan how to deploy App-V so that it does not disrupt you
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
- This section describes the minimum hardware and software requirements necessary for App-V client, sequencer and server feature installations. Additionally, associated feature planning information is also displayed.
+ This section describes the minimum hardware and software requirements and other planning information for the App-V sequencer and App-V server components.
- [App-V Planning Checklist](appv-planning-checklist.md)
diff --git a/windows/manage/appv-planning-for-high-availability-with-appv.md b/windows/manage/appv-planning-for-high-availability-with-appv.md
index 73f8c5234a..45de84806a 100644
--- a/windows/manage/appv-planning-for-high-availability-with-appv.md
+++ b/windows/manage/appv-planning-for-high-availability-with-appv.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Planning for High Availability with App-V Server
+Applies to: Windows 10, version 1607
+
Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high level of available service.
Use the information in the following sections to help you understand the options to deploy App-V in a highly available configuration.
@@ -54,11 +56,11 @@ Review the following for more information about configuring IIS and Network Load
## Support for clustered file servers when running SCS mode
-Running App-V Server in Share Content Store (SCS) mode with clustered file servers is supported.
+Running App-V Server in Shared Content Store (SCS) mode with clustered file servers is supported.
The following steps can be used to enable this configuration:
-- Configure App-V to run in client SCS mode. For more information about configuring App-V SCS mode, see [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).
+- Configure the App-V client to run in Shared Content Store mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
- Configure the file server cluster, configured in either the scale out mode (which started with Windows Server 2012) or the earlier clustering mode, with a virtual SAN.
diff --git a/windows/manage/appv-planning-for-sequencer-and-client-deployment.md b/windows/manage/appv-planning-for-sequencer-and-client-deployment.md
index 9911146ef4..dc75756ac9 100644
--- a/windows/manage/appv-planning-for-sequencer-and-client-deployment.md
+++ b/windows/manage/appv-planning-for-sequencer-and-client-deployment.md
@@ -10,6 +10,7 @@ ms.prod: w10
# Planning for the App-V Sequencer and Client Deployment
+Applies to: Windows 10, version 1607
Before you can use App-V, you must install the App-V Sequencer, enable the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
@@ -66,4 +67,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
-- [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
+- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
diff --git a/windows/manage/appv-planning-for-using-appv-with-office.md b/windows/manage/appv-planning-for-using-appv-with-office.md
index c272ff6893..d2a6ac394f 100644
--- a/windows/manage/appv-planning-for-using-appv-with-office.md
+++ b/windows/manage/appv-planning-for-using-appv-with-office.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Planning for Using App-V with Office
+Applies to: Windows 10, version 1607
+
Use the following information to plan how to deploy Office by using Microsoft Application Virtualization (App-V). This article includes:
- [App-V support for Language Packs](#bkmk-lang-pack)
diff --git a/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md b/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
index e1cbb7a833..bd295e6783 100644
--- a/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
+++ b/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
@@ -10,6 +10,8 @@ ms.prod: w10
# Planning to Deploy App-V with an electronic software distribution system
+Applies to: Windows 10, version 1607
+
If you are using an electronic software distribution system to deploy App-V packages, review the following planning considerations. For information about using System Center Configuration Manager to deploy App-V, see [Introduction to Application Management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv).
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
diff --git a/windows/manage/appv-planning-to-deploy-appv.md b/windows/manage/appv-planning-to-deploy-appv.md
index 997ba3e4e0..292322be4f 100644
--- a/windows/manage/appv-planning-to-deploy-appv.md
+++ b/windows/manage/appv-planning-to-deploy-appv.md
@@ -9,7 +9,7 @@ ms.prod: w10
---
-# Planning to Deploy App-V for Windows 0
+# Planning to Deploy App-V for Windows 10
Applies to: Windows 10, version 1607
@@ -55,7 +55,7 @@ Describes the planning considerations for the App-V Client and for the Sequencer
Describes the recommended path for migrating from previous versions of App-V, while ensuring that existing server configurations, packages and clients continue to work in your new App-V environment.
-[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
+[Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
## Planning for using App-V with Office
diff --git a/windows/manage/appv-preparing-your-environment.md b/windows/manage/appv-preparing-your-environment.md
index 1af564cc9d..43f08c5ad6 100644
--- a/windows/manage/appv-preparing-your-environment.md
+++ b/windows/manage/appv-preparing-your-environment.md
@@ -10,6 +10,8 @@ ms.prod: w10
# Preparing Your Environment for App-V
+Applies to: Windows 10, version 1607
+
There are a number of different deployment configurations and prerequisites that you must consider before you create your deployment plan for Microsoft Application Virtualization (App-V). This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
## App-V prerequisites
diff --git a/windows/manage/appv-publish-a-connection-group.md b/windows/manage/appv-publish-a-connection-group.md
index 9f4e344c77..75a1fe2178 100644
--- a/windows/manage/appv-publish-a-connection-group.md
+++ b/windows/manage/appv-publish-a-connection-group.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Publish a Connection Group
+Applies to: Windows 10, version 1607
After you create a connection group, you must publish it to computers that run the App-V client.
diff --git a/windows/manage/appv-publish-a-packages-with-the-management-console.md b/windows/manage/appv-publish-a-packages-with-the-management-console.md
index d66b07c352..0bb07f76ce 100644
--- a/windows/manage/appv-publish-a-packages-with-the-management-console.md
+++ b/windows/manage/appv-publish-a-packages-with-the-management-console.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Publish a Package by Using the Management Console
+Applies to: Windows 10, version 1607
Use the following procedure to publish an App-V package. Once you publish a package, computers that are running the App-V client can access and run the applications in that package.
@@ -31,7 +32,7 @@ The ability to enable only administrators to publish or unpublish packages (desc
1. Navigate to the following Group Policy Object node:
- **Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
+ **Computer Configuration > Administrative Templates > System > App-V > Publishing**.
2. Enable the **Require publish as administrator** Group Policy setting.
diff --git a/windows/manage/appv-register-and-unregister-a-publishing-server-with-the-management-console.md b/windows/manage/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
index 9b3b9d8b15..70a7911816 100644
--- a/windows/manage/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
+++ b/windows/manage/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Register and Unregister a Publishing Server by Using the Management Console
+Applies to: Windows 10, version 1607
You can register and unregister publishing servers that will synchronize with the App-V management server. You can also see the last attempt that the publishing server made to synchronize the information with the management server.
diff --git a/windows/manage/appv-release-notes-for-appv-for-windows.md b/windows/manage/appv-release-notes-for-appv-for-windows.md
index ef3c356c57..dfad3fa3e9 100644
--- a/windows/manage/appv-release-notes-for-appv-for-windows.md
+++ b/windows/manage/appv-release-notes-for-appv-for-windows.md
@@ -13,10 +13,10 @@ ms.prod: w10
Applies to: Windows 10, version 1607
-The following is a known issue in Application Virtualization (App-V) for Windows 10, version 1607:
-
-**Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client**
+The following are known issues in Application Virtualization (App-V) for Windows 10, version 1607.
+## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client
+
MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
**Workaround**:
@@ -41,6 +41,123 @@ MSI packages that were generated using an App-V sequencer from previous versions
By default, the path to the Windows SDK installation will be: **C:\Program Files (x86)\Windows Kits\10**
+## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
+
+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**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
+
+## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
+
+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.
+
+**Workaround**: Do one of the following:
+
+- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration will be stored in each user’s profile and will be applied correctly.
+
+- 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.
+
+- Create a new package with the custom configuration using the App-V Sequencer.
+
+## Server files not deleted after new App-V Server 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.
+
+**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
+
+## 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?
diff --git a/windows/manage/appv-reporting.md b/windows/manage/appv-reporting.md
index 1da03fe86b..411a7617d6 100644
--- a/windows/manage/appv-reporting.md
+++ b/windows/manage/appv-reporting.md
@@ -11,6 +11,7 @@ ms.prod: w10
# About App-V Reporting
+Applies to: Windows 10, version 1607
Application Virtualization (App-V) includes a built-in reporting feature that helps you collect information about computers running the App-V client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
@@ -38,22 +39,26 @@ The following list displays the end–to-end high-level workflow for reporting i
-4. After importing the App-V Windows PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample Windows PowerShell cmdlet enables App-V reporting:
+4. After importing the App-V Windows PowerShell module using `Import-Module AppvClient` as administrator, enable App-V client reporting. This sample Windows PowerShell command enables App-V reporting:
``` syntax
- Set-AppvClientConfiguration –reportingserverurl : -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
+ Set-AppvClientConfiguration -ReportingServerURL : -ReportingEnabled 1 -ReportingStartTime <0-23> -ReportingRandomDelay <#min>
```
To immediately send App-V report data, run `Send-AppvClientReport` on the App-V client.
- For more information about installing the App-V client with reporting enabled see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
+ For more information about configuring reporting on the App-V client, see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
5. After the reporting server receives the data from the App-V client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server and then a notification is sent to the App-V client.
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
>**Note**
- By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache. If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
+ By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
+
+
+
+ If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
### App-V reporting server frequently asked questions
@@ -98,10 +103,10 @@ The following table displays answers to common questions about App-V reporting
|
Can reporting be scheduled? |
-Yes. Besides manually sending reporting using PowerShell Cmdlets (Send-AppvClientReport), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:
+ | Yes. Besides manually sending reporting using Windows PowerShell cmdlets (Send-AppvClientReport), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:
Using Windows PowerShell cmdlets - Set-AppvClientConfiguration. For example:
-Set-AppvClientConfiguration -ReportingEnabled 1 - ReportingServerURL http://any.com/appv-reporting
+Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL http://any.com/appv-reporting
For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: ReportingEnabled, ReportingServerURL, ReportingDataCacheLimit, ReportingDataBlockSize, ReportingStartTime, ReportingRandomDelay, ReportingInterval.
@@ -123,44 +128,36 @@ The following table displays answers to common questions about App-V reporting
## App-V Client Reporting
-To use App-V reporting you must enable and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** Windows PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using Windows PowerShell.
+To use App-V reporting you must enable and configure the App-V client. To configure reporting on the client, use the Windows PowerShell cmdlet **Set-AppVClientConfiguration**, or the Group Policy **ADMX Template**. For more information about the Windows PowerShell cmdlets, see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of Windows PowerShell commands for configuring App-V client reporting.
### Configuring App-V Client reporting using Windows PowerShell
The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
**Note**
-The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. For more information about using the ADMX template, see [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).
-
-
+The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**.
**To enable reporting and to initiate data collection on the computer running the App-V client**:
-```syntax
-Set-AppVClientConfiguration –ReportingEnabled 1
-```
+`Set-AppVClientConfiguration –ReportingEnabled 1`
**To configure the client to automatically send data to a specific reporting server**:
``` syntax
-Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30 -ReportingInterval 1 -ReportingRandomDelay 30
+Set-AppVClientConfiguration -ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
```
-This example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
+The preceding example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
**To limit the size of the data cache on the client**:
-```syntax
-Set-AppvClientConfiguration –ReportingDataCacheLimit 100
-```
+`Set-AppvClientConfiguration –ReportingDataCacheLimit 100`
Configures the maximum size of the reporting cache on the computer running the App-V client to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
**To configure the data block size transmitted across the network between the client and the server**:
-```syntax
-Set-AppvClientConfiguration –ReportingDataBlockSize 10240
-```
+`Set-AppvClientConfiguration –ReportingDataBlockSize 10240`
Specifies the maximum data block that the client sends to 10240 MB.
@@ -240,9 +237,7 @@ You can configure the computer that is running the App-V client to automatically
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following Windows PowerShell cmdlet:
-```syntax
-Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess
-```
+`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
diff --git a/windows/manage/appv-running-locally-installed-applications-inside-a-virtual-environment.md b/windows/manage/appv-running-locally-installed-applications-inside-a-virtual-environment.md
index cdd905e166..6ac3c28269 100644
--- a/windows/manage/appv-running-locally-installed-applications-inside-a-virtual-environment.md
+++ b/windows/manage/appv-running-locally-installed-applications-inside-a-virtual-environment.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
+Applies to: Windows 10, version 1607
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this if you:
diff --git a/windows/manage/appv-security-considerations.md b/windows/manage/appv-security-considerations.md
index 79d71d971a..9ed0a92e4a 100644
--- a/windows/manage/appv-security-considerations.md
+++ b/windows/manage/appv-security-considerations.md
@@ -11,6 +11,7 @@ ms.prod: w10
# App-V Security Considerations
+Applies to: Windows 10, version 1607
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
@@ -31,9 +32,9 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa
**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 ().
+**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, see the [Microsoft Security TechCenter](https://technet.microsoft.com/en-us/security/bb291012).
-**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet ().
+**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://technet.microsoft.com/library/hh994572.aspx).
## Accounts and groups in App-V
diff --git a/windows/manage/appv-sequence-a-new-application.md b/windows/manage/appv-sequence-a-new-application.md
index a860b731e8..872c82b881 100644
--- a/windows/manage/appv-sequence-a-new-application.md
+++ b/windows/manage/appv-sequence-a-new-application.md
@@ -11,6 +11,8 @@ ms.prod: w10
# How to Sequence a New Application with App-V
+Applies to: Windows 10, version 1607
+
In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
**To review or do before you start sequencing**
@@ -53,11 +55,9 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
> [!NOTE]
> If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
-
-
+
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **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 Management Console.
Click **Next**.
@@ -66,8 +66,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
> [!IMPORTANT]
> You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
-
-
+
Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
8. On the **Installation** page, wait while the sequencer configures the virtualized application package.
@@ -76,8 +75,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
> [!NOTE]
> To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
-
-
+
Click **Next**.
10. On the **Installation Report** page, you can review information about the virtualized application package you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**.
@@ -109,9 +107,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
> [!IMPORTANT]
> The system does not support non-printable characters in **Comments** and **Descriptions**.
-
-
-
+
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
15. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory where the package was created.
@@ -179,9 +175,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
> [!IMPORTANT]
> The system does not support non-printable characters in Comments and Descriptions.
-
-
-
+
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
**To sequence a middleware application**
@@ -218,8 +212,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
> [!IMPORTANT]
> The system does not support non-printable characters in Comments and Descriptions.
-
-
+
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
diff --git a/windows/manage/appv-sequence-a-package-with-powershell.md b/windows/manage/appv-sequence-a-package-with-powershell.md
index f35388deed..a4778e669b 100644
--- a/windows/manage/appv-sequence-a-package-with-powershell.md
+++ b/windows/manage/appv-sequence-a-package-with-powershell.md
@@ -11,6 +11,8 @@ ms.prod: w10
# How to Sequence a Package by using Windows PowerShell
+Applies to: Windows 10, version 1607
+
Use the following procedure to create a new App-V package using Windows PowerShell.
> [!NOTE]
diff --git a/windows/manage/appv-supported-configurations.md b/windows/manage/appv-supported-configurations.md
index b212b67b96..ffa45bea9e 100644
--- a/windows/manage/appv-supported-configurations.md
+++ b/windows/manage/appv-supported-configurations.md
@@ -11,7 +11,7 @@ ms.prod: w10
# App-V Supported Configurations
-Applies to: Windows 10, version 1607
+Applies to: Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; and Windows Server 2008 R2
This topic specifies the requirements to install and run App-V in your Windows 10 environment.
@@ -35,7 +35,7 @@ The App-V server does not support the following scenarios:
### Management server operating system requirements
-The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
+The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
> [!IMPORTANT]
> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.
@@ -90,7 +90,7 @@ The following table lists the SQL Server versions that are supported for the App
### Publishing server operating system requirements
-The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
+The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
### Publishing server hardware requirements
@@ -105,7 +105,7 @@ App-V adds no additional requirements beyond those of Windows Server.
### Reporting server operating system requirements
-The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
+The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
### Reporting server hardware requirements
diff --git a/windows/manage/appv-technical-reference.md b/windows/manage/appv-technical-reference.md
index 713d772993..20015f1626 100644
--- a/windows/manage/appv-technical-reference.md
+++ b/windows/manage/appv-technical-reference.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Technical Reference for App-V
+Applies to: Windows 10, version 1607
This section provides reference information related to managing App-V.
@@ -25,6 +26,14 @@ This section provides reference information related to managing App-V.
Describes how the following App-V client operations affect the local operating system: App-V files and data storage locations, package registry, package store behavior, roaming registry and data, client application lifecycle management, integration of App-V packages, dynamic configuration, side-by-side assemblies, and client logging.
+- [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
+
+ Tells how to view publishing metadata, which can help you resolve publishing-related issues.
+
+- [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
+
+ Describes reasons and methods for running a locally installed application in a virtual environment, alongside applications that have been virtualized by using Application Virtualization (App-V).
+
## Have a suggestion for App-V?
diff --git a/windows/manage/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md b/windows/manage/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
index a39449b055..5ff573ad8e 100644
--- a/windows/manage/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
+++ b/windows/manage/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
+Applies to: Windows 10, version 1607
Use the following procedure to transfer the access and default package configurations to another version of a package by using the management console.
diff --git a/windows/manage/appv-troubleshooting.md b/windows/manage/appv-troubleshooting.md
index 7a8e67b35c..bdfd75f528 100644
--- a/windows/manage/appv-troubleshooting.md
+++ b/windows/manage/appv-troubleshooting.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Troubleshooting App-V
+Applies to: Windows 10, version 1607
Troubleshooting content is not included in the Administrator’s Guide for this product. Instead, you can find troubleshooting information for this product on the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905).
diff --git a/windows/manage/appv-using-the-client-management-console.md b/windows/manage/appv-using-the-client-management-console.md
index 64affa5f4b..266069cfe2 100644
--- a/windows/manage/appv-using-the-client-management-console.md
+++ b/windows/manage/appv-using-the-client-management-console.md
@@ -11,18 +11,30 @@ ms.prod: w10
# Using the App-V Client Management Console
+Applies to: Windows 10, version 1607
-This topic provides information about how you can configure and manage the Microsoft Application Virtualization (App-V) client.
+This topic provides information about about using the Application Virtualization (App-V) client management console to manage packages on the computer running the App-V client.
-## Modify App-V client configuration
+## Obtain the client management console
+The client management console is separate from the App-V client itself. You can download the client management console from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41186).
-The App-V client has associated settings that can be configured to determine how the client will run in your environment. You can manage these settings on the computer that runs the client or by using PowerShell or Group Policy. For more information about how to modify the client using PowerShell or Group Policy configuration see, [How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md).
+> [!NOTE]
+To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
+
+## Options for managing the App-V client
+
+The App-V client has associated settings that can be configured to determine how the client will run in your environment. You can manage these settings on the computer that runs the client, or you can use Windows PowerShell or Group Policy. For more information about configuring the client by using Windows PowerShell or Group Policy, see:
+
+- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
+
+- [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
+
+- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
## The App-V client management console
-
-You can obtain information about the App-V client or perform specific tasks by using the App-V client management console. Many of the tasks that you can perform in the client management console you can also perform by using PowerShell. The associated PowerShell cmdlets for each action are also displayed in the following table. For more information about how to use PowerShell, see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
+You can obtain information about the App-V client or perform specific tasks by using the App-V client management console. Many of the tasks that you can perform in the client management console you can also perform by using Windows PowerShell. The associated Windows PowerShell cmdlets for each action are also displayed in the following table. For more information about how to use Windows PowerShell, see [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md).
The client management console contains the following described main tabs.
@@ -45,10 +57,10 @@ The client management console contains the following described main tabs.
Update – Use the Update tile to refresh a virtualized application or to receive a new virtualized package.
The Last Refresh displays the current version of the virtualized package.
Download all virtual applications – Use the Download tile to download all of the packages provisioned to the current user.
-(Associated PowerShell cmdlet: Mount-AppvClientPackage)
+(Associated Windows PowerShell cmdlet: Mount-AppvClientPackage)
Work Offline – Use this tile to disallow all automatic and manual virtual application updates.
-(Associated PowerShell cmdlet: Set-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled)
+(Associated Windows PowerShell cmdlet: Set-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled)
|
@@ -59,18 +71,12 @@ The client management console contains the following described main tabs.
App Connection Groups |
The APP CONNECTION GROUPS tab displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group.
-(Associated PowerShell cmdlets: Download - Mount-AppvClientConnectionGroup. Repair -AppvClientConnectionGroup.)
+(Associated Windows PowerShell cmdlets: Download - Mount-AppvClientConnectionGroup. Repair -AppvClientConnectionGroup.)
|
-
-
-[How to Access the Client Management Console](appv-accessing-the-client-management-console.md)
-
-[How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
-
## Have a suggestion for App-V?
@@ -78,14 +84,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
-
[Operations for App-V](appv-operations.md)
-
-
-
-
-
-
-
-
-
diff --git a/windows/manage/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md b/windows/manage/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
index 5a89f2304c..30be0a6fa7 100644
--- a/windows/manage/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
+++ b/windows/manage/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
@@ -11,6 +11,7 @@ ms.prod: w10
# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
+Applies to: Windows 10, version 1607
Use the following procedure to view and configure default package extensions.
diff --git a/windows/manage/appv-viewing-appv-server-publishing-metadata.md b/windows/manage/appv-viewing-appv-server-publishing-metadata.md
index abfc25f877..babe5ccc6a 100644
--- a/windows/manage/appv-viewing-appv-server-publishing-metadata.md
+++ b/windows/manage/appv-viewing-appv-server-publishing-metadata.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Viewing App-V Server Publishing Metadata
+Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
Use this procedure to view publishing metadata, which can help you resolve publishing-related issues. You must be using the App-V Management server to use this procedure.
diff --git a/windows/manage/index.md b/windows/manage/index.md
index e3a69f2e47..eba6dd0e9c 100644
--- a/windows/manage/index.md
+++ b/windows/manage/index.md
@@ -8,7 +8,6 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: security
author: jdeckerMS
-localizationpriority: high
---
# Manage and update Windows 10
diff --git a/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md b/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
index a2f9376e50..4c0fc7b9d4 100644
--- a/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
+++ b/windows/manage/manage-connections-from-windows-operating-system-components-to-microsoft-services.md
@@ -365,7 +365,7 @@ To turn off the Windows Mail app:
To prevent communication to the Microsoft Account cloud authentication service. Many apps and system components that depend on Microsoft Account authentication may lose functionality. Some of them could be in unexpected ways.
-- Change the **Start** REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentControlSet\\Services\\wlidsvc** to 4.
+- Change the **Start** REG\_DWORD registry setting in **HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Services\\wlidsvc** to 4.
### 11. Microsoft Edge
diff --git a/windows/manage/uev-accessibility.md b/windows/manage/uev-accessibility.md
index e54c168813..a217f7090c 100644
--- a/windows/manage/uev-accessibility.md
+++ b/windows/manage/uev-accessibility.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Accessibility for UE-V
+Applies to: Windows 10, version 1607
Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
diff --git a/windows/manage/uev-administering-uev-with-windows-powershell-and-wmi.md b/windows/manage/uev-administering-uev-with-windows-powershell-and-wmi.md
index 081924a8c9..d69be9fa38 100644
--- a/windows/manage/uev-administering-uev-with-windows-powershell-and-wmi.md
+++ b/windows/manage/uev-administering-uev-with-windows-powershell-and-wmi.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Administering UE-V with Windows PowerShell and WMI
+Applies to: Windows 10, version 1607
User Experience Virtualization (UE-V) provides Windows PowerShell cmdlets to help administrators perform various UE-V tasks. The following sections provide more information about using Windows PowerShell in UE-V.
diff --git a/windows/manage/uev-administering-uev.md b/windows/manage/uev-administering-uev.md
index 83f4e99a1b..90cea589aa 100644
--- a/windows/manage/uev-administering-uev.md
+++ b/windows/manage/uev-administering-uev.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Administering UE-V
+Applies to: Windows 10, version 1607
+
After you finish deploying User Experience Virtualization (UE-V), you'll perform ongoing administrative tasks, such as managing the configuration of the UE-V service and recovering lost settings. These tasks are explained in the following sections.
## Managing UE-V configurations
diff --git a/windows/manage/uev-application-template-schema-reference.md b/windows/manage/uev-application-template-schema-reference.md
index c5c7a98379..d46ce33a56 100644
--- a/windows/manage/uev-application-template-schema-reference.md
+++ b/windows/manage/uev-application-template-schema-reference.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Application Template Schema Reference for UE-V
+Applies to: Windows 10, version 1607
User Experience Virtualization (UE-V) uses XML settings location templates to define the desktop application settings and Windows settings that are captured and applied by UE-V. UE-V includes a set of default settings location templates. You can also create custom settings location templates with the UE-V template generator.
diff --git a/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md b/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md
index e05fa13e99..38b08127f0 100644
--- a/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md
+++ b/windows/manage/uev-changing-the-frequency-of-scheduled-tasks.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Changing the Frequency of UE-V Scheduled Tasks
+Applies to: Windows 10, version 1607
When the User Experience Virtualization (UE-V) service is enabled, it creates the following scheduled tasks:
diff --git a/windows/manage/uev-configuring-uev-with-group-policy-objects.md b/windows/manage/uev-configuring-uev-with-group-policy-objects.md
index 9bb13f98c6..43b3c09793 100644
--- a/windows/manage/uev-configuring-uev-with-group-policy-objects.md
+++ b/windows/manage/uev-configuring-uev-with-group-policy-objects.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Configuring UE-V with Group Policy Objects
+Applies to: Windows 10, version 1607
Some User Experience Virtualization (UE-V) Group Policy settings can be defined for computers, and other Group Policy settings can be defined for users. The Group Policy administrative templates for these settings are included in Windows 10, version 1607.
diff --git a/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md b/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md
index f6f6eb97fc..44aab5f355 100644
--- a/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md
+++ b/windows/manage/uev-configuring-uev-with-system-center-configuration-manager.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Configuring UE-V with System Center Configuration Manager
+Applies to: Windows 10, version 1607
After you deploy User Experience Virtualization (UE-V) and its required features, you can start to configure it to meet your organization's need. The UE-V Configuration Pack provides a way for administrators to use the Compliance Settings feature of System Center Configuration Manager (2012 SP1 or later) to apply consistent configurations across sites where UE-V and Configuration Manager are installed.
diff --git a/windows/manage/uev-deploy-required-features.md b/windows/manage/uev-deploy-required-features.md
index c3324cab35..5a97b8c141 100644
--- a/windows/manage/uev-deploy-required-features.md
+++ b/windows/manage/uev-deploy-required-features.md
@@ -10,6 +10,8 @@ ms.prod: w10
# Deploy required UE-V features
+Applies to: Windows 10, version 1607
+
To get up and running with User Experience Virtualization (UE-V), install and configure the following features.
- [Deploy a settings storage location](#deploy-a-ue-v-settings-storage-location) that is accessible to end users.
diff --git a/windows/manage/uev-deploy-uev-for-custom-applications.md b/windows/manage/uev-deploy-uev-for-custom-applications.md
index 120b0b4602..20d213dd27 100644
--- a/windows/manage/uev-deploy-uev-for-custom-applications.md
+++ b/windows/manage/uev-deploy-uev-for-custom-applications.md
@@ -10,6 +10,8 @@ ms.prod: w10
# Use UE-V with custom applications
+Applies to: Windows 10, version 1607
+
User Experience Virtualization (UE-V) uses XML files called ***settings location templates*** to monitor and synchronize application settings and Windows settings between user devices. By default, some settings location templates are included in UE-V. However, if you want to synchronize settings for desktop applications other than those included in the default templates, you can create your own custom settings location templates with the UE-V template generator.
After you’ve reviewed [Prepare a UE-V Deployment](uev-prepare-for-deployment.md) and decided that you want to synchronize settings for custom applications (third-party, line-of-business, e.g.), you’ll need to deploy the features of UE-V described in this topic.
diff --git a/windows/manage/uev-for-windows.md b/windows/manage/uev-for-windows.md
index 96293f71db..962d9be2ce 100644
--- a/windows/manage/uev-for-windows.md
+++ b/windows/manage/uev-for-windows.md
@@ -10,6 +10,8 @@ ms.prod: w10
# User Experience Virtualization (UE-V) for Windows 10 overview
+Applies to: Windows 10, version 1607
+
Many users customize their settings for Windows and for specific applications. Customizable Windows settings include Windows Store appearance, language, background picture, font size, and accent colors. Customizable application settings include language, appearance, behavior, and user interface options.
With User Experience Virtualization (UE-V), you can capture user-customized Windows and application settings and store them on a centrally managed network file share. When users log on, their personalized settings are applied to their work session, regardless of which device or virtual desktop infrastructure (VDI) sessions they log on to.
diff --git a/windows/manage/uev-manage-administrative-backup-and-restore.md b/windows/manage/uev-manage-administrative-backup-and-restore.md
index 61f024d919..1f704b6f74 100644
--- a/windows/manage/uev-manage-administrative-backup-and-restore.md
+++ b/windows/manage/uev-manage-administrative-backup-and-restore.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Manage Administrative Backup and Restore in UE-V
+Applies to: Windows 10, version 1607
+
As an administrator of User Experience Virtualization (UE-V), you can restore application and Windows settings to their original state. You can also restore additional settings when a user adopts a new device.
## Restore Settings in UE-V when a User Adopts a New Device
diff --git a/windows/manage/uev-manage-configurations.md b/windows/manage/uev-manage-configurations.md
index bfcb65c039..38ce78a9cb 100644
--- a/windows/manage/uev-manage-configurations.md
+++ b/windows/manage/uev-manage-configurations.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Manage Configurations for UE-V
+Applies to: Windows 10, version 1607
In the course of the User Experience Virtualization (UE-V) lifecycle, you have to manage the configuration of the UE-V service and also manage storage locations for resources such as settings package files. The following topics provide guidance for managing these UE-V resources.
diff --git a/windows/manage/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md b/windows/manage/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md
index e28ebdbf9e..465f29054b 100644
--- a/windows/manage/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md
+++ b/windows/manage/uev-managing-settings-location-templates-using-windows-powershell-and-wmi.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Managing UE-V Settings Location Templates Using Windows PowerShell and WMI
+Applies to: Windows 10, version 1607
User Experience Virtualization (UE-V) uses XML settings location templates to define the settings that User Experience Virtualization captures and applies. UE-V includes a set of standard settings location templates. It also includes the UE-V template generator tool that enables you to create custom settings location templates. After you create and deploy settings location templates, you can manage those templates by using Windows PowerShell and the Windows Management Instrumentation (WMI). For a complete list of UE-V PowerShell cmdlets, see [UE-V 2 Cmdlet Reference](https://technet.microsoft.com/library/dn520275.aspx).
diff --git a/windows/manage/uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi.md b/windows/manage/uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi.md
index fc1134e656..c10781cef0 100644
--- a/windows/manage/uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi.md
+++ b/windows/manage/uev-managing-uev-agent-and-packages-with-windows-powershell-and-wmi.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Managing the UE-V service and packages with Windows PowerShell and WMI
+Applies to: Windows 10, version 1607
+
You can use Windows Management Instrumentation (WMI) and Windows PowerShell to manage User Experience Virtualization (UE-V) service configuration and synchronization behavior. For a complete list of UE-V PowerShell cmdlets, see [UE-V Cmdlet Reference](https://technet.microsoft.com/library/dn520275.aspx).
diff --git a/windows/manage/uev-migrating-settings-packages.md b/windows/manage/uev-migrating-settings-packages.md
index 0bf674caeb..b0e1bbf5f0 100644
--- a/windows/manage/uev-migrating-settings-packages.md
+++ b/windows/manage/uev-migrating-settings-packages.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Migrating UE-V settings packages
+Applies to: Windows 10, version 1607
In the lifecycle of a User Experience Virtualization (UE-V) deployment, you might have to relocate the user settings packages either when you migrate to a new server or when you perform backups. Settings packages might have to be migrated in the following scenarios:
diff --git a/windows/manage/uev-privacy-statement.md b/windows/manage/uev-privacy-statement.md
index 30e1e65622..a5f18c5a9e 100644
--- a/windows/manage/uev-privacy-statement.md
+++ b/windows/manage/uev-privacy-statement.md
@@ -12,6 +12,7 @@ ms.prod: w8
# User Experience Virtualization Privacy Statement
+Applies to: Windows 10, version 1607
Microsoft is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you desire in your personal computing. This privacy statement explains many of the data collection and use practices of Microsoft User Experience Virtualization (“UE-V”). This is a preliminary disclosure that focuses on features that communicate with the Internet and is not intended to be an exhaustive list.
diff --git a/windows/manage/uev-security-considerations.md b/windows/manage/uev-security-considerations.md
index 2cfc34087e..65ad037e94 100644
--- a/windows/manage/uev-security-considerations.md
+++ b/windows/manage/uev-security-considerations.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Security Considerations for UE-V
+Applies to: Windows 10, version 1607
This topic contains a brief overview of accounts and groups, log files, and other security-related considerations for User Experience Virtualization (UE-V). For more information, follow the links that are provided here.
diff --git a/windows/manage/uev-sync-methods.md b/windows/manage/uev-sync-methods.md
index 7b78c035f0..d3c32cedc6 100644
--- a/windows/manage/uev-sync-methods.md
+++ b/windows/manage/uev-sync-methods.md
@@ -10,6 +10,7 @@ ms.prod: w10
# Sync Methods for UE-V
+Applies to: Windows 10, version 1607
The User Experience Virtualization (UE-V) service lets you synchronize users’ application and Windows settings with the settings storage location. The *Sync Method* configuration defines how the UE-V service uploads and downloads those settings to the settings storage location. UE-V includes a SyncMethod called the *SyncProvider*. For more information about trigger events that start the synchronization of application and Windows settings, see [Sync Trigger Events for UE-V](uev-sync-trigger-events.md).
diff --git a/windows/manage/uev-sync-trigger-events.md b/windows/manage/uev-sync-trigger-events.md
index 811a463e97..c17211c902 100644
--- a/windows/manage/uev-sync-trigger-events.md
+++ b/windows/manage/uev-sync-trigger-events.md
@@ -10,6 +10,7 @@ ms.prod: w10
# Sync Trigger Events for UE-V
+Applies to: Windows 10, version 1607
User Experience Virtualization (UE-V) lets you synchronize your application and Windows settings across all your domain-joined devices. *Sync trigger events* define when the UE-V service synchronizes those settings with the settings storage location. For more information about Sync Method configuration, see [Sync Methods for UE-V](uev-sync-methods.md).
diff --git a/windows/manage/uev-synchronizing-microsoft-office-with-uev.md b/windows/manage/uev-synchronizing-microsoft-office-with-uev.md
index 47aaa206af..849914ed61 100644
--- a/windows/manage/uev-synchronizing-microsoft-office-with-uev.md
+++ b/windows/manage/uev-synchronizing-microsoft-office-with-uev.md
@@ -11,6 +11,8 @@ ms.prod: w10
# Synchronizing Office with UE-V
+Applies to: Windows 10, version 1607
+
Microsoft User Experience Virtualization (UE-V) supports the synchronization of Microsoft Office application settings. The combination of UE-V and App-V support for Office enables the same experience on virtualized instances of Office from any UE-V-enabled device or virtualized desktop.
To synchronize Office applications settings, you can download Office templates from the [Microsoft User Experience Virtualization (UE-V) Template Gallery](http://go.microsoft.com/fwlink/p/?LinkId=246589). This resource provides Microsoft-authored UE-V settings location templates as well as community-developed settings location templates.
diff --git a/windows/manage/uev-technical-reference.md b/windows/manage/uev-technical-reference.md
index d8eec5847d..5ee914062b 100644
--- a/windows/manage/uev-technical-reference.md
+++ b/windows/manage/uev-technical-reference.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Technical Reference for UE-V
+Applies to: Windows 10, version 1607
This technical reference section includes additional technical documentation about the various features of User Experience Virtualization (UE-V). This information is provided to help the administrator better understand UE-V.
diff --git a/windows/manage/uev-troubleshooting.md b/windows/manage/uev-troubleshooting.md
index bc48051f72..29117acb21 100644
--- a/windows/manage/uev-troubleshooting.md
+++ b/windows/manage/uev-troubleshooting.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Troubleshooting UE-V
+Applies to: Windows 10, version 1607
Troubleshooting content is not included in the Administrator's Guide for this product. Instead, you can find troubleshooting information for this product on the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905).
diff --git a/windows/manage/uev-using-uev-with-application-virtualization-applications.md b/windows/manage/uev-using-uev-with-application-virtualization-applications.md
index 1f495c9b74..c26e3024bd 100644
--- a/windows/manage/uev-using-uev-with-application-virtualization-applications.md
+++ b/windows/manage/uev-using-uev-with-application-virtualization-applications.md
@@ -11,6 +11,7 @@ ms.prod: w10
# Using UE-V with Application Virtualization applications
+Applies to: Windows 10, version 1607
User Experience Virtualization (UE-V) supports Microsoft Application Virtualization (App-V) applications without any required modifications to either the App-V package or the UE-V template. However, an additional step is required because you cannot run the UE-V template generator directly on a virtualized App-V application. Instead, you must install the application locally, generate the template, and then apply the template to the virtualized application. UE-V supports App-V for Windows 10 packages and App-V 5.0 packages.
diff --git a/windows/whats-new/applocker.md b/windows/whats-new/applocker.md
index 3cfd7a6582..2e082cd98c 100644
--- a/windows/whats-new/applocker.md
+++ b/windows/whats-new/applocker.md
@@ -7,7 +7,7 @@ ms.prod: w10
ms.mktglfcycl: explore
ms.sitesec: library
author: brianlic-msft
-redirect_url: https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview
+redirect_url: https://technet.microsoft.com/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511
---
# What's new in AppLocker?
diff --git a/windows/whats-new/bitlocker.md b/windows/whats-new/bitlocker.md
index 6db25cd066..9f0df242bf 100644
--- a/windows/whats-new/bitlocker.md
+++ b/windows/whats-new/bitlocker.md
@@ -7,7 +7,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security, mobile
author: brianlic-msft
-redirect_url: https://technet.microsoft.com/itpro/windows/keep-secure/bitlocker-overview
+redirect_url: https://technet.microsoft.com/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511
---
# What's new in BitLocker?
diff --git a/windows/whats-new/security-auditing.md b/windows/whats-new/security-auditing.md
index 8890adb735..8b3428b2bd 100644
--- a/windows/whats-new/security-auditing.md
+++ b/windows/whats-new/security-auditing.md
@@ -7,7 +7,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
author: brianlic-msft
ms.pagetype: security, mobile
-redirect_url: https://technet.microsoft.com/itpro/windows/keep-secure/security-auditing-overview
+redirect_url: https://technet.microsoft.com/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511
---
# What's new in security auditing?
diff --git a/windows/whats-new/user-account-control.md b/windows/whats-new/user-account-control.md
index 3d41d3ca1d..4a670324d3 100644
--- a/windows/whats-new/user-account-control.md
+++ b/windows/whats-new/user-account-control.md
@@ -7,7 +7,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: brianlic-msft
-redirect_url: https://technet.microsoft.com/itpro/windows/keep-secure/user-account-control-overview
+redirect_url: https://technet.microsoft.com/itpro/windows/whats-new/whats-new-windows-10-version-1507-and-1511
---
# What's new in User Account Control?
|