deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Removd assetids, updated vsn of feature

Browse Source
This commit is contained in:
JanKeller1
2016-07-29 14:22:56 -07:00
parent e0a796e38f
commit 96b87194c9
95 changed files with 911 additions and 1004 deletions
Download Patch File Download Diff File Expand all files Collapse all files

87
windows/manage/appv-about-appv.md
View File

@ -1,8 +1,7 @@
---
title: About App-V 5.1
description: About App-V 5.1
title: About App-V (Windows 10)
description: About App-V
author: jamiejdt
ms.assetid: 35bc9908-d502-4a9c-873f-8ee17b6d9d74
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,16 +9,16 @@ ms.prod: w10
---
# About App-V 5.1
# About App-V
Use the following sections to review information about significant changes that apply to Application Virtualization (App-V) 5.1:
Use the following sections to review information about significant changes that apply to Application Virtualization (App-V):
[App-V 5.1 software prerequisites and supported configurations](#bkmk-51-prereq-configs)
[App-V software prerequisites and supported configurations](#bkmk-51-prereq-configs)
[Migrating to App-V 5.1](#bkmk-migrate-to-51)
[Migrating to App-V](#bkmk-migrate-to-51)
[What’s New in App-V 5.1](#bkmk-whatsnew)
[What’s New in App-V](#bkmk-whatsnew)
[App-V support for Windows 10](#bkmk-win10support)
@ -33,10 +32,10 @@ Use the following sections to review information about significant changes that
[Hardcoded path to installation folder is redirected to virtual file system root](#bkmk-hardcodepath)
## <a href="" id="bkmk-51-prereq-configs"></a>App-V 5.1 software prerequisites and supported configurations
## <a href="" id="bkmk-51-prereq-configs"></a>App-V software prerequisites and supported configurations
See the following links for the App-V 5.1 software prerequisites and supported configurations.
See the following links for the App-V software prerequisites and supported configurations.
<table>
<colgroup>
@ -51,11 +50,11 @@ See the following links for the App-V 5.1 software prerequisites and supported c
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>[App-V 5.1 Prerequisites](appv-prerequisites.md)</p></td>
<td align="left"><p>Prerequisite software that you must install before starting the App-V 5.1 installation</p></td>
<td align="left"><p>[App-V Prerequisites](appv-prerequisites.md)</p></td>
<td align="left"><p>Prerequisite software that you must install before starting the App-V installation</p></td>
</tr>
<tr class="even">
<td align="left"><p>[App-V 5.1 Supported Configurations](appv-supported-configurations.md)</p></td>
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.md)</p></td>
<td align="left"><p>Supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client components</p></td>
</tr>
</tbody>
@ -63,12 +62,12 @@ See the following links for the App-V 5.1 software prerequisites and supported c
 
**Support for using Configuration Manager with App-V:** App-V 5.1 supports System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager and Configuration Manager.
**Support for using Configuration Manager with App-V:** App-V supports System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager and Configuration Manager.
## <a href="" id="bkmk-migrate-to-51"></a>Migrating to App-V 5.1
## <a href="" id="bkmk-migrate-to-51"></a>Migrating to App-V
Use the following information to upgrade to App-V 5.1 from earlier versions. See [Migrating to App-V 5.1 from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) for more information.
Use the following information to upgrade to App-V from earlier versions. See [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) for more information.
### Before you start the upgrade
@ -103,7 +102,7 @@ Review the following information before you start the upgrade:
</tr>
<tr class="even">
<td align="left"><p>Upgrading from App-V 4.x</p></td>
<td align="left"><p>You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V 5.1. For more information, see:</p>
<td align="left"><p>You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V. For more information, see:</p>
<ul>
<li><p>“Differences between App-V 4.6 and App-V 5.0” in [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50.md)</p></li>
<li><p>[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)</p></li>
@ -112,15 +111,15 @@ Review the following information before you start the upgrade:
</tr>
<tr class="odd">
<td align="left"><p>Upgrading from App-V 5.0 or later</p></td>
<td align="left"><p>You can upgrade to App-V 5.1 directly from any of the following versions:</p>
<td align="left"><p>You can upgrade to App-V directly from any of the following versions:</p>
<ul>
<li><p>App-V 5.0</p></li>
<li><p>App-V 5.0 SP1</p></li>
<li><p>App-V 5.0 SP2</p></li>
<li><p>App-V 5.0 SP3</p></li>
</ul>
<p>To upgrade to App-V 5.1, follow the steps in the remaining sections of this topic.</p>
<p>Packages and connection groups will continue to work with App-V 5.1 as they currently do.</p></td>
<p>To upgrade to App-V, follow the steps in the remaining sections of this topic.</p>
<p>Packages and connection groups will continue to work with App-V as they currently do.</p></td>
</tr>
</tbody>
</table>
@ -129,7 +128,7 @@ Review the following information before you start the upgrade:
### <a href="" id="bkmk-steps-upgrd-infrastruc"></a>Steps to upgrade the App-V infrastructure
Complete the following steps to upgrade each component of the App-V infrastructure to App-V 5.1. The following order is only a suggestion; you may upgrade components in any order.
Complete the following steps to upgrade each component of the App-V infrastructure to App-V. The following order is only a suggestion; you may upgrade components in any order.
<table>
<colgroup>
@ -178,7 +177,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
</tbody>
</table>
<li><p>If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/check-reg-key-svr).</p></li>
<li><p>Follow the steps in [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)</p></li>
<li><p>Follow the steps in [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
<p> </p></li>
</ol></td>
</tr>
@ -200,18 +199,18 @@ Complete the following steps to upgrade each component of the App-V infrastructu
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.
**Note**  
App-V 5.1 packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and so there is no need to convert App-V 5.0 packages to App-V 5.1 packages.
App-V packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and so there is no need to convert App-V 5.0 packages to App-V packages.
 
## <a href="" id="bkmk-whatsnew"></a>What’s New in App-V 5.1
## <a href="" id="bkmk-whatsnew"></a>What’s New in App-V
These sections are for users who are already familiar with App-V and want to know what has changed in App-V 5.1. If you are not already familiar with App-V, you should start by reading [Planning for App-V 5.1](appv-planning-for-appv.md).
These sections are for users who are already familiar with App-V and want to know what has changed in App-V. If you are not already familiar with App-V, you should start by reading [Planning for App-V](appv-planning-for-appv.md).
### <a href="" id="bkmk-win10support"></a>App-V support for Windows 10
The following table lists the Windows 10 support for App-V. Windows 10 is not supported in versions of App-V prior to App-V 5.1.
The following table lists the Windows 10 support for App-V. Windows 10 is not supported in versions of App-V prior to App-V.
<table>
<colgroup>
@ -222,7 +221,7 @@ The following table lists the Windows 10 support for App-V. Windows 10 is not su
<thead>
<tr class="header">
<th align="left">Component</th>
<th align="left">App-V 5.1</th>
<th align="left">App-V</th>
<th align="left">App-V 5.0</th>
</tr>
</thead>
@ -264,8 +263,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V 5.1</th>
<th align="left">Prior to App-V 5.1</th>
<th align="left">New in App-V</th>
<th align="left">Prior to App-V</th>
</tr>
</thead>
<tbody>
@ -301,8 +300,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V 5.1</th>
<th align="left">Prior to App-V 5.1</th>
<th align="left">New in App-V</th>
<th align="left">Prior to App-V</th>
</tr>
</thead>
<tbody>
@ -325,8 +324,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V 5.1</th>
<th align="left">Prior to App-V 5.1</th>
<th align="left">New in App-V</th>
<th align="left">Prior to App-V</th>
</tr>
</thead>
<tbody>
@ -348,8 +347,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V 5.1</th>
<th align="left">Prior to App-V 5.1</th>
<th align="left">New in App-V</th>
<th align="left">Prior to App-V</th>
</tr>
</thead>
<tbody>
@ -405,7 +404,7 @@ In the left pane of the Management Console, the OVERVIEW menu option and its ass
### <a href="" id="bkmk-seqimprove"></a>Sequencer Improvements
The following improvements have been made to the package editor in the App-V 5.1 Sequencer.
The following improvements have been made to the package editor in the App-V Sequencer.
### Import and export the manifest file
@ -448,7 +447,7 @@ You can import and export virtual registry keys. To import a key, right-click th
### Import a directory into the virtual file system
You can import a directory into the VFS. To import a directory, click the **Package Files** tab, and then click **View** &gt; **Virtual File System** &gt; **Import Directory**. If you try to import a directory that contains files that are already in the VFS, the import fails, and an explanatory message is displayed. Prior to App-V 5.1, you could not import directories.
You can import a directory into the VFS. To import a directory, click the **Package Files** tab, and then click **View** &gt; **Virtual File System** &gt; **Import Directory**. If you try to import a directory that contains files that are already in the VFS, the import fails, and an explanatory message is displayed. Prior to App-V, you could not import directories.
### Import or export a VFS file without having to delete and then add it back to the package
@ -484,21 +483,21 @@ You can enable or disable Browser Helper Objects by selecting a new check box, E
You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
For more information including examples, see [Migrating to App-V 5.1 from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md).
For more information including examples, see [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md).
### <a href="" id="bkmk-supmultscripts"></a>Support for multiple scripts on a single event trigger
App-V 5.1 supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you are converting from App-V 4.6 to App-V 5.0 or later. To enable the use of multiple scripts, App-V 5.1 uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you are converting from App-V 4.6 to App-V 5.0 or later. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.
For more information, including a list of event triggers and the context under which scripts can be run, see the Scripts section in [About App-V 5.1 Dynamic Configuration](appv-dynamic-configuration.md).
For more information, including a list of event triggers and the context under which scripts can be run, see the Scripts section in [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
### <a href="" id="bkmk-hardcodepath"></a>Hardcoded path to installation folder is redirected to virtual file system root
When you convert packages from App-V 4.6 to 5.1, the App-V 5.1 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.)
When you convert packages from App-V 4.6 to 5.1, the App-V package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.)
Previously, the 4.6 root folder was not recognized and could not be accessed by App-V 5.0 packages. App-V 5.1 packages can access hardcoded files by their full path or can programmatically enumerate files under the App-V 4.6 installation root.
Previously, the 4.6 root folder was not recognized and could not be accessed by App-V 5.0 packages. App-V packages can access hardcoded files by their full path or can programmatically enumerate files under the App-V 4.6 installation root.
**Technical Details:** The App-V 5.1 package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V 5.1 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
**Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
## How to Get MDOP Technologies
@ -513,7 +512,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Release Notes for App-V 5.1](appv-release-notes-for-appv-for-windows.md)
[Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
 

21
windows/manage/appv-accessibility.md
View File

@ -1,8 +1,7 @@
---
title: Accessibility for App-V 5.1
description: Accessibility for App-V 5.1
title: Accessibility for App-V (Windows 10)
description: Accessibility for App-V
author: jamiejdt
ms.assetid: ef3f7742-f2e9-4748-ad60-74e0961b1bd9
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,15 +9,15 @@ ms.prod: w10
---
# Accessibility for App-V 5.1
# Accessibility for App-V
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.
## Keyboard Shortcuts for the App-V 5.1 Management Server
## Keyboard Shortcuts for the App-V Management Server
Following are the keyboard Shortcuts for the App-V 5.1 Management Server:
Following are the keyboard Shortcuts for the App-V Management Server:
<table>
<colgroup>
@ -41,7 +40,7 @@ Following are the keyboard Shortcuts for the App-V 5.1 Management Server:
<td align="left"><p>Enter</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Refresh the current page of the App-V 5.1 client console.</p></td>
<td align="left"><p>Refresh the current page of the App-V client console.</p></td>
<td align="left"><p>F5</p></td>
</tr>
</tbody>
@ -49,10 +48,10 @@ Following are the keyboard Shortcuts for the App-V 5.1 Management Server:
 
## Keyboard Shortcuts for the App-V 5.1 Sequencer
## Keyboard Shortcuts for the App-V Sequencer
Following are the keyboard shortcuts for the Virtual Registry tab in the package editor in the App-V 5.1 Sequencer:
Following are the keyboard shortcuts for the Virtual Registry tab in the package editor in the App-V Sequencer:
<table>
<colgroup>
@ -82,7 +81,7 @@ Following are the keyboard shortcuts for the Virtual Registry tab in the package
### Access Any Command with a Few Keystrokes
**Important**  
The information in this section only applies to the App-V 5.1 sequencer. For specific information about the App-V 5.1 server, see the Keyboard Shortcuts for the App-V 5.1 Management Server section of this document.
The information in this section only applies to the App-V sequencer. For specific information about the App-V server, see the Keyboard Shortcuts for the App-V Management Server section of this document.
 
@ -158,7 +157,7 @@ For more information about how accessible technology for computers helps to impr
## Related topics
[Getting Started with App-V 5.1](appv-getting-started.md)
[Getting Started with App-V](appv-getting-started.md)
 

15
windows/manage/appv-accessing-the-client-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Access the Client Management Console
title: How to Access the Client Management Console (Windows 10)
description: How to Access the Client Management Console
author: jamiejdt
ms.assetid: 22131251-acd5-44e7-a30b-7d389c518b6f
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,10 +12,10 @@ ms.prod: w10
# How to Access the Client Management Console
Use the App-V 5.1 client management console to manage packages on the computer running the App-V 5.1 client.
Use the App-V client management console to manage packages on the computer running the App-V client.
**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 5.1 client.
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.
 
@ -24,21 +23,21 @@ Use the following procedure to access the client management console.
**To access the client management console**
1. On the computer running the App-V 5.1 client, click **Start** and select **Microsoft Application Virtualization Client**.
1. On the computer running the App-V client, click **Start** and select **Microsoft Application Virtualization Client**.
**Note**  
For computers running the App-V 5.1 Remote Desktop Services client version, to access client management console follow step 1 of this procedure on the server running the client.
For computers running the App-V Remote Desktop Services client version, to access client management console follow step 1 of this procedure on the server running the client.
 
2. When the App-V 5.1 client management console is displayed, click the tab you want to review and perform any required tasks. For more information about the client management console tasks see, [Using the App-V 5.1 Client Management Console](appv-using-the-client-management-console.md).
2. When the App-V client management console is displayed, click the tab you want to review and perform any required tasks. For more information about the client management console tasks see, [Using the App-V Client Management Console](appv-using-the-client-management-console.md).
**Got 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/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

11
windows/manage/appv-add-or-remove-an-administrator-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Add or Remove an Administrator by Using the Management Console
title: How to Add or Remove an Administrator by Using the Management Console (Windows 10)
description: How to Add or Remove an Administrator by Using the Management Console
author: jamiejdt
ms.assetid: 7ff8c436-9d2e-446a-9ea2-bbab7e25bf21
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,11 +12,11 @@ ms.prod: w10
# How to Add or Remove an Administrator by Using the Management Console
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) 5.1 server.
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
**To add an administrator using the Management Console**
1. Open the Microsoft Application Virtualization (App-V) 5.1 Management Console and click **Administrators** in the navigation pane. The navigation pane displays a list of Access Directory (AD) users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) 5.1 server.
1. Open the Microsoft Application Virtualization (App-V) Management Console and click **Administrators** in the navigation pane. The navigation pane displays a list of Access Directory (AD) users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
2. To add a new administrator, click **Add Administrator** Type the name of the administrator that you want to add in the **Active Directory Name** field. Ensure you provide the associated user account domain name. For example, **Domain** \\ **UserName**.
@ -25,7 +24,7 @@ Use the following procedures to add or remove an administrator on the Microsoft
**To remove an administrator using the Management Console**
1. Open the Microsoft Application Virtualization (App-V) 5.1 Management Console and click **Administrators** in the navigation pane. The navigation pane displays a list of AD users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) 5.1 server.
1. Open the Microsoft Application Virtualization (App-V) Management Console and click **Administrators** in the navigation pane. The navigation pane displays a list of AD users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
2. Right-click the account to be removed from the list of administrators and select **Remove**.
@ -34,7 +33,7 @@ Use the following procedures to add or remove an administrator on the Microsoft
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

7
windows/manage/appv-add-or-upgrade-packages-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Add or Upgrade Packages by Using the Management Console
title: How to Add or Upgrade Packages by Using the Management Console (Windows 10)
description: How to Add or Upgrade Packages by Using the Management Console
author: jamiejdt
ms.assetid: 62417b63-06b2-437c-8584-523e1dea97c3
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# How to Add or Upgrade Packages by Using the Management Console
You can the following procedure to add or upgrade a package to the App-V 5.1 Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
You can the following procedure to add or upgrade a package to the App-V Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
**To add a package to the Management Console**
@ -43,7 +42,7 @@ You can the following procedure to add or upgrade a package to the App-V 5.1 Man
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

23
windows/manage/appv-administering-appv-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: Administering App-V 5.1 by Using PowerShell
description: Administering App-V 5.1 by Using PowerShell
title: Administering App-V by Using PowerShell (Windows 10)
description: Administering App-V by Using PowerShell
author: jamiejdt
ms.assetid: 9e10ff07-2cd9-4dc1-9e99-582f90c36081
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,15 +9,15 @@ ms.prod: w10
---
# Administering App-V 5.1 by Using PowerShell
# Administering App-V by Using PowerShell
Microsoft Application Virtualization (App-V) 5.1 provides Windows PowerShell cmdlets, which can help administrators perform various App-V 5.1 tasks. The following sections provide more information about using PowerShell with App-V 5.1.
Microsoft Application Virtualization (App-V) provides Windows PowerShell cmdlets, which can help administrators perform various App-V tasks. The following sections provide more information about using PowerShell with App-V.
## How to administer App-V 5.1 by using PowerShell
## How to administer App-V by using PowerShell
Use the following PowerShell procedures to perform various App-V 5.1 tasks.
Use the following PowerShell procedures to perform various App-V tasks.
<table>
<colgroup>
@ -37,7 +36,7 @@ Use the following PowerShell procedures to perform various App-V 5.1 tasks.
<td align="left"><p>Describes how to install the PowerShell cmdlets and find cmdlet help and examples.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></td>
<td align="left"><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></td>
<td align="left"><p>Describes how to manage the client package lifecycle on a stand-alone computer using PowerShell.</p></td>
</tr>
<tr class="odd">
@ -65,8 +64,8 @@ Use the following PowerShell procedures to perform various App-V 5.1 tasks.
<td align="left"><p>Describes how to create a package accelerator using PowerShell. You can use package accelerators automatically sequence large, complex applications.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[How to Enable Reporting on the App-V 5.1 Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)</p></td>
<td align="left"><p>Describes how to enable the computer running the App-V 5.1 to send reporting information.</p></td>
<td align="left"><p>[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)</p></td>
<td align="left"><p>Describes how to enable the computer running the App-V to send reporting information.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)</p></td>
@ -85,7 +84,7 @@ Make sure that any script you execute with your App-V packages matches the execu
## PowerShell Error Handling
Use the following table for information about App-V 5.1 PowerShell error handling.
Use the following table for information about App-V PowerShell error handling.
<table>
<colgroup>
@ -127,7 +126,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

25
windows/manage/appv-administering-virtual-applications-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: Administering App-V 5.1 Virtual Applications by Using the Management Console
description: Administering App-V 5.1 Virtual Applications by Using the Management Console
title: Administering App-V Virtual Applications by Using the Management Console (Windows 10)
description: Administering App-V Virtual Applications by Using the Management Console
author: jamiejdt
ms.assetid: a4d078aa-ec54-4fa4-9463-bfb3b971d724
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,10 +9,10 @@ ms.prod: w10
---
# Administering App-V 5.1 Virtual Applications by Using the Management Console
# Administering App-V Virtual Applications by Using the Management Console
Use the Microsoft Application Virtualization (App-V) 5.1 management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V 5.1 client. One or more management servers typically share a common data store for configuration and package information.
Use the Microsoft Application Virtualization (App-V) management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V client. One or more management servers typically share a common data store for configuration and package information.
The management server uses Active Directory Domain Services (AD DS) groups to manage user authorization and has SQL Server installed to manage the database and data store.
@ -21,14 +20,14 @@ Because the management servers stream applications to end users on demand, these
- Management Server – Use the management server to manage packages and connection groups.
- Publishing Server – Use the publishing server to deploy packages to computers that run the App-V 5.1 client.
- Publishing Server – Use the publishing server to deploy packages to computers that run the App-V client.
- Management Database - Use the management database to manage the package access and to publish the server’s synchronization with the management server.
## Management Console tasks
The most common tasks that you can perform with the App-V 5.1 Management console are:
The most common tasks that you can perform with the App-V Management console are:
- [How to Connect to the Management Console](appv-connect-to-the-management-console.md)
@ -44,7 +43,7 @@ The most common tasks that you can perform with the App-V 5.1 Management console
- [How to Register and Unregister a Publishing Server by Using the Management Console](appv-register-and-unregister-a-publishing-server-with-the-management-console.md)
- [How to Create a Custom Configuration File by Using the App-V 5.1 Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md)
- [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md)
- [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console](appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md)
@ -52,7 +51,7 @@ The most common tasks that you can perform with the App-V 5.1 Management console
- [How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console](appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md)
The main elements of the App-V 5.1 Management Console are:
The main elements of the App-V Management Console are:
<table>
<colgroup>
@ -80,7 +79,7 @@ The main elements of the App-V 5.1 Management Console are:
</tr>
<tr class="even">
<td align="left"><p>Administrators tab</p></td>
<td align="left"><p>Use the <strong>ADMINISTRATORS</strong> tab to register, add, or remove administrators in your App-V 5.1 environment.</p></td>
<td align="left"><p>Use the <strong>ADMINISTRATORS</strong> tab to register, add, or remove administrators in your App-V environment.</p></td>
</tr>
</tbody>
</table>
@ -97,12 +96,12 @@ JavaScript must be enabled on the browser that opens the Web Management Console.
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/home?forum=mdopappv).
## <a href="" id="other-resources-for-this-app-v-5-1-deployment-"></a>Other resources for this App-V 5.1 deployment
## <a href="" id="other-resources-for-this-app-v-5-1-deployment-"></a>Other resources for this App-V deployment
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Operations for App-V 5.1](appv-operations.md)
- [Operations for App-V](appv-operations.md)
 

3
windows/manage/appv-allow-administrators-to-enable-connection-groups.md
View File

@ -1,8 +1,7 @@
---
title: How to Allow Only Administrators to Enable Connection Groups
title: How to Allow Only Administrators to Enable Connection Groups (Windows 10)
description: How to Allow Only Administrators to Enable Connection Groups
author: jamiejdt
ms.assetid: 42ca3157-5d85-467b-a148-09404f8f737a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library

5
windows/manage/appv-application-publishing-and-client-interaction.md
View File

@ -1,8 +1,7 @@
---
title: Application Publishing and Client Interaction
title: Application Publishing and Client Interaction (Windows 10)
description: Application Publishing and Client Interaction
author: jamiejdt
ms.assetid: 36a4bf6f-a917-41a6-9856-6248686df352
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -666,7 +665,7 @@ App-V registry roaming falls into two scenarios, as shown in the following table
### App-V and folder redirection
App-V 5.1 supports folder redirection of the roaming AppData folder (%AppData%). When the virtual environment is started, the roaming AppData state from the user’s roaming AppData directory is copied to the local cache. Conversely, when the virtual environment is shut down, the local cache that is associated with a specific user’s roaming AppData is transferred to the actual location of that user’s roaming AppData directory.
App-V supports folder redirection of the roaming AppData folder (%AppData%). When the virtual environment is started, the roaming AppData state from the user’s roaming AppData directory is copied to the local cache. Conversely, when the virtual environment is shut down, the local cache that is associated with a specific user’s roaming AppData is transferred to the actual location of that user’s roaming AppData directory.
A typical package has several locations mapped in the user’s backing store for settings in both AppData\\Local and AppData\\Roaming. These locations are the Copy on Write locations that are stored per user in the user’s profile, and that are used to store changes made to the package VFS directories and to protect the default package VFS.

7
windows/manage/appv-apply-the-deployment-configuration-file-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Apply the Deployment Configuration File by Using PowerShell
title: How to Apply the Deployment Configuration File by Using PowerShell (Windows 10)
description: How to Apply the Deployment Configuration File by Using PowerShell
author: jamiejdt
ms.assetid: 78fe0f15-4a36-41e3-96d6-7d5aa77c1e06
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# How to Apply the Deployment Configuration File by Using PowerShell
The dynamic deployment configuration file is applied when a package is added or set to a computer running the App-V 5.1 client before the package has been published. The file configures the default settings for package for all users on the computer running the App-V 5.1 client. This section describes the steps used to use a deployment configuration file. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
The dynamic deployment configuration file is applied when a package is added or set to a computer running the App-V client before the package has been published. The file configures the default settings for package for all users on the computer running the App-V client. This section describes the steps used to use a deployment configuration file. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
**c:\\Packages\\Contoso\\MyApp.appv**
@ -37,7 +36,7 @@ The dynamic deployment configuration file is applied when a package is added or
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

5
windows/manage/appv-apply-the-user-configuration-file-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Apply the User Configuration File by Using PowerShell
title: How to Apply the User Configuration File by Using PowerShell (Windows 10)
description: How to Apply the User Configuration File by Using PowerShell
author: jamiejdt
ms.assetid: 986e638c-4a0c-4a7e-be73-f4615e8b8000
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -34,7 +33,7 @@ Use the following procedure to specify a user-specific configuration file. The f
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

103
windows/manage/appv-capacity-planning.md
View File

@ -1,8 +1,7 @@
---
title: App-V 5.1 Capacity Planning
description: App-V 5.1 Capacity Planning
title: App-V Capacity Planning (Windows 10)
description: App-V Capacity Planning
author: jamiejdt
ms.assetid: 7a98062f-5a60-49d6-ab40-dc6057e1dd5a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,20 +9,20 @@ ms.prod: w10
---
# App-V 5.1 Capacity Planning
# App-V Capacity Planning
The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V 5.1 infrastructure.
The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
**Important**  
Use the information in this section only as a general guide for planning your App-V 5.1 deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
Use the information in this section only as a general guide for planning your App-V deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
 
## Determine the Project Scope
Before you design the App-V 5.1 infrastructure, you must determine the project’s scope. The scope consists of determining which applications will be available virtually and to also identify the target users, and their locations. This information will help determine what type of App-V 5.1 infrastructure should be implemented. Decisions about the scope of the project must be based on the specific needs of your organization.
Before you design the App-V infrastructure, you must determine the project’s scope. The scope consists of determining which applications will be available virtually and to also identify the target users, and their locations. This information will help determine what type of App-V infrastructure should be implemented. Decisions about the scope of the project must be based on the specific needs of your organization.
<table>
<colgroup>
@ -39,7 +38,7 @@ Before you design the App-V 5.1 infrastructure, you must determine the project
<tbody>
<tr class="odd">
<td align="left"><p>Determine Application Scope</p></td>
<td align="left"><p>Depending on the applications to be virtualized, the App-V 5.1 infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.</p></td>
<td align="left"><p>Depending on the applications to be virtualized, the App-V infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Determine Location Scope</p></td>
@ -50,28 +49,28 @@ Before you design the App-V 5.1 infrastructure, you must determine the project
 
## Determine Which App-V 5.1 Infrastructure is Required
## Determine Which App-V Infrastructure is Required
**Important**  
Both of the following models require the App-V 5.1 client to be installed on the computer where you plan to run virtual applications.
Both of the following models require the App-V client to be installed on the computer where you plan to run virtual applications.
You can also manage your App-V 5.1 environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V 5.1 Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
You can also manage your App-V environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
 
- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V 5.1 in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
- With disconnected remote users who cannot connect to the App-V 5.1 infrastructure.
- With disconnected remote users who cannot connect to the App-V infrastructure.
- When you are running a software management system, such as Configuration Manager 2012.
- When network bandwidth limitations inhibit electronic software distribution.
- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V 5.1 Full Infrastructure Model consists of one or more App-V 5.1 management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V Full Infrastructure Model consists of one or more App-V management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
**Important**  
The App-V 5.1 full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
The App-V full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V Supported Configurations](appv-supported-configurations.md).
 
@ -79,15 +78,15 @@ You can also manage your App-V 5.1 environment using an Electronic Software Dist
- For rapid provisioning of applications to target computers.
- When you want to use App-V 5.1 reporting.
- When you want to use App-V reporting.
## End-to-end Server Sizing Guidance
The following section provides information about end-to-end App-V 5.1 sizing and planning. For more specific information, refer to the subsequent sections.
The following section provides information about end-to-end App-V sizing and planning. For more specific information, refer to the subsequent sections.
**Note**  
Round trip response time on the client is the time taken by the computer running the App-V 5.1 client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
 
@ -95,13 +94,13 @@ Round trip response time on the client is the time taken by the computer running
- A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time. (&lt;5 seconds)
## <a href="" id="---------app-v-5-1-management-server-capacity-planning-recommendations"></a> App-V 5.1 Management Server Capacity Planning Recommendations
## <a href="" id="---------app-v-5-1-management-server-capacity-planning-recommendations"></a> App-V Management Server Capacity Planning Recommendations
The App-V 5.1 publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V 5.1 management server supported configurations see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
The App-V publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V management server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md).
**Note**  
The default refresh time on the App-V 5.1 publishing server is ten minutes.
The default refresh time on the App-V publishing server is ten minutes.
 
@ -116,7 +115,7 @@ When multiple simultaneous publishing servers contact a single management server
The following table displays more information about each factor that impacts round trip time.
**Note**  
Round trip response time is the time taken by the computer running the App-V 5.1 publishing server to receive a successful package metadata update from the management server.
Round trip response time is the time taken by the computer running the App-V publishing server to receive a successful package metadata update from the management server.
 
@ -164,7 +163,7 @@ Round trip response time is the time taken by the computer running the App-V 5.1
 
The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V 5.1management server.
The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-Vmanagement server.
<table>
<colgroup>
@ -460,13 +459,13 @@ Using a geographically distributed deployment, where the management server & pub
Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
## <a href="" id="---------app-v-5-1-reporting-server-capacity-planning-recommendations"></a> App-V 5.1 Reporting Server Capacity Planning Recommendations
## <a href="" id="---------app-v-5-1-reporting-server-capacity-planning-recommendations"></a> App-V Reporting Server Capacity Planning Recommendations
App-V 5.1 clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V 5.1 client. For more information about App-V 5.1 Reporting Server supported configurations see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
App-V clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V client. For more information about App-V Reporting Server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md).
**Note**  
Round trip response time is the time taken by the computer running the App-V 5.1 client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
Round trip response time is the time taken by the computer running the App-V client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
 
@ -483,7 +482,7 @@ Round trip response time is the time taken by the computer running the App-V 5.1
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Multiple App-V 5.1 clients send reporting information to the reporting server simultaneously.</p></td>
<td align="left"><p>Multiple App-V clients send reporting information to the reporting server simultaneously.</p></td>
<td align="left"><p></p>
<ul>
<li><p>Round trip response time from the reporting server is 2.6 seconds for 500 clients.</p></li>
@ -524,19 +523,19 @@ Random delay = 4 \* number of clients / average requests per second.
Example: For 500 clients, with 120 requests per second, the Random delay is, 4 \* 500 / 120 = ~17 minutes.
## <a href="" id="---------app-v-5-1-publishing-server-capacity-planning-recommendations"></a> App-V 5.1 Publishing Server Capacity Planning Recommendations
## <a href="" id="---------app-v-5-1-publishing-server-capacity-planning-recommendations"></a> App-V Publishing Server Capacity Planning Recommendations
Computers running the App-V 5.1 client connect to the App-V 5.1 publishing server to send a publishing refresh request and to receive a response. Round trip response time is measured on the computer running the App-V 5.1 client. Processor time is measured on the publishing server. For more information about App-V 5.1 Publishing Server supported configurations see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
Computers running the App-V client connect to the App-V publishing server to send a publishing refresh request and to receive a response. Round trip response time is measured on the computer running the App-V client. Processor time is measured on the publishing server. For more information about App-V Publishing Server supported configurations see [App-V Supported Configurations](appv-supported-configurations.md).
**Important**  
The following list displays the main factors to consider when setting up the App-V 5.1 publishing server:
The following list displays the main factors to consider when setting up the App-V publishing server:
- The number of clients connecting simultaneously to a single publishing server.
- The number of packages in each refresh.
- The available network bandwidth in your environment between the client and the App-V 5.1 publishing server.
- The available network bandwidth in your environment between the client and the App-V publishing server.
 
@ -553,7 +552,7 @@ The following list displays the main factors to consider when setting up the App
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Multiple App-V 5.1 clients connect to a single publishing server simultaneously.</p></td>
<td align="left"><p>Multiple App-V clients connect to a single publishing server simultaneously.</p></td>
<td align="left"><p></p>
<ul>
<li><p>A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously.</p></li>
@ -571,7 +570,7 @@ The following list displays the main factors to consider when setting up the App
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Network between the App-V 5.1 client and the publishing server.</p>
<td align="left"><p>Network between the App-V client and the publishing server.</p>
<p></p></td>
<td align="left"><p></p>
<ul>
@ -603,17 +602,17 @@ The publishing server CPU usage is always high during the time interval when it
<tr class="header">
<th align="left">Scenario</th>
<th align="left">Variation</th>
<th align="left">Number of App-V 5.1 clients</th>
<th align="left">Number of App-V clients</th>
<th align="left">Number of packages</th>
<th align="left">Processor configuration on the publishing server</th>
<th align="left">Network connection type publishing server / App-V 5.1 client</th>
<th align="left">Round trip time on the App-V 5.1 client (in seconds)</th>
<th align="left">Network connection type publishing server / App-V client</th>
<th align="left">Round trip time on the App-V client (in seconds)</th>
<th align="left">CPU utilization on publishing server (in %)</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V 5.1 client sends publishing refresh request &amp; receives response, each request containing 120 packages</p></td>
<td align="left"><p>App-V client sends publishing refresh request &amp; receives response, each request containing 120 packages</p></td>
<td align="left"><p>Number of clients</p></td>
<td align="left"><p></p>
<ul>
@ -730,13 +729,13 @@ The publishing server CPU usage is always high during the time interval when it
 
## <a href="" id="---------app-v-5-1-streaming-capacity-planning-recommendations"></a> App-V 5.1 Streaming Capacity Planning Recommendations
## <a href="" id="---------app-v-5-1-streaming-capacity-planning-recommendations"></a> App-V Streaming Capacity Planning Recommendations
Computers running the App-V 5.1 client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V 5.1 client, and is the time taken to stream the entire package.
Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package.
**Important**  
The following list identifies the main factors to consider when setting up the App-V 5.1 streaming server:
The following list identifies the main factors to consider when setting up the App-V streaming server:
- The number of clients streaming application packages simultaneously from a single streaming server.
@ -759,7 +758,7 @@ The following list identifies the main factors to consider when setting up the A
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Multiple App-V 5.1 clients stream applications from a single streaming server simultaneously.</p></td>
<td align="left"><p>Multiple App-V clients stream applications from a single streaming server simultaneously.</p></td>
<td align="left"><p></p>
<ul>
<li><p>If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.</p></li>
@ -774,7 +773,7 @@ The following list identifies the main factors to consider when setting up the A
</ul></td>
</tr>
<tr class="odd">
<td align="left"><p>Network between the App-V 5.1 client and the streaming server.</p>
<td align="left"><p>Network between the App-V client and the streaming server.</p>
<p></p></td>
<td align="left"><p></p>
<ul>
@ -801,15 +800,15 @@ The following table displays sample values for each of the factors in the previo
<tr class="header">
<th align="left">Scenario</th>
<th align="left">Variation</th>
<th align="left">Number of App-V 5.1 clients</th>
<th align="left">Number of App-V clients</th>
<th align="left">Size of each package</th>
<th align="left">Network connection type streaming server / App-V 5.1 client</th>
<th align="left">Round trip time on the App-V 5.1 client (in seconds)</th>
<th align="left">Network connection type streaming server / App-V client</th>
<th align="left">Round trip time on the App-V client (in seconds)</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Multiple App-V 5.1 clients streaming virtual application packages from a streaming server.</p></td>
<td align="left"><p>Multiple App-V clients streaming virtual application packages from a streaming server.</p></td>
<td align="left"><p>Number of clients.</p></td>
<td align="left"><p></p>
<ul>
@ -887,7 +886,7 @@ The following table displays sample values for each of the factors in the previo
<p>160</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Network connection between client and App-V 5.1 streaming server.</p></td>
<td align="left"><p>Network connection between client and App-V streaming server.</p></td>
<td align="left"><p>1.5 Mbps Slow link network.</p></td>
<td align="left"><p></p>
<ul>
@ -915,7 +914,7 @@ The following table displays sample values for each of the factors in the previo
 
Each App-V 5.1 streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
**Note**  
The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions.
@ -926,14 +925,14 @@ For example, an average user can stream a 100 MB package in less than 2 minutes,
The number of clients a streaming server can support can be significantly increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
## Combining App-V 5.1 Server Roles
## Combining App-V Server Roles
Discounting scaling and fault-tolerance requirements, the minimum number of servers needed for a location with connectivity to Active Directory is one. This server will host the management server, management server service, and Microsoft SQL Server roles. Server roles, therefore, can be arranged in any desired combination since they do not conflict with one another.
Ignoring scaling requirements, the minimum number of servers necessary to provide a fault-tolerant implementation is four. The management server, and Microsoft SQL Server roles support being placed in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
Although there are a number of fault-tolerance strategies and technologies available, not all are applicable to a given service. Additionally, if App-V 5.1 roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities.
Although there are a number of fault-tolerance strategies and technologies available, not all are applicable to a given service. Additionally, if App-V roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities.
## Got a suggestion for App-V?
@ -943,9 +942,9 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[App-V 5.1 Supported Configurations](appv-supported-configurations.md)
[App-V Supported Configurations](appv-supported-configurations.md)
[Planning for High Availability with App-V 5.1](appv-planning-for-high-availability-with-appv.md)
[Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)

15
windows/manage/appv-configure-access-to-packages-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Configure Access to Packages by Using the Management Console
title: How to Configure Access to Packages by Using the Management Console (Windows 10)
description: How to Configure Access to Packages by Using the Management Console
author: jamiejdt
ms.assetid: 4fd39bc2-d814-46de-a108-1c21fa404e8a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,15 +12,15 @@ ms.prod: w10
# How to Configure Access to Packages by Using the Management Console
Before you deploy an App-V 5.1 virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
Use the following procedure to configure access to virtualized packages.
**To grant access to an App-V 5.1 package**
**To grant access to an App-V package**
1. Find the package you want to configure:
1. Open the App-V 5.1 Management console.
1. Open the App-V Management console.
2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
@ -44,11 +43,11 @@ Use the following procedure to configure access to virtualized packages.
To customize configurations for a specific group, click the **ASSIGNED CONFIGURATIONS** drop-down and select **Custom**. To configure the custom configurations, click **EDIT**. After you grant access, click **Close**.
**To remove access to an App-V 5.1 package**
**To remove access to an App-V package**
1. Find the package you want to configure:
1. Open the App-V 5.1 Management console.
1. Open the App-V Management console.
2. To display the **AD ACCESS** page, right-click the package to be configured, and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
@ -61,7 +60,7 @@ Use the following procedure to configure access to virtualized packages.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

11
windows/manage/appv-configure-connection-groups-to-ignore-the-package-version.md
View File

@ -1,8 +1,7 @@
---
title: How to Make a Connection Group Ignore the Package Version
title: How to Make a Connection Group Ignore the Package Version (Windows 10)
description: How to Make a Connection Group Ignore the Package Version
author: jamiejdt
ms.assetid: db16b095-dbe2-42c7-863d-b0d5d91b2f4c
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# How to Make a Connection Group Ignore the Package Version
Microsoft Application Virtualization (App-V) 5.1 lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
Microsoft Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
To upgrade a package in some earlier versions of App-V, you had to perform several steps, including disabling the connection group and modifying the connection group’s XML definition file.
@ -24,8 +23,8 @@ To upgrade a package in some earlier versions of App-V, you had to perform sever
</colgroup>
<thead>
<tr class="header">
<th align="left">Task description with App-V 5.1</th>
<th align="left">How to perform the task with App-V 5.1</th>
<th align="left">Task description with App-V</th>
<th align="left">How to perform the task with App-V</th>
</tr>
</thead>
<tbody>
@ -76,7 +75,7 @@ To upgrade a package in some earlier versions of App-V, you had to perform sever
<p>For more information, see:</p>
<ul>
<li><p>The example XML file, <strong>Connection group XML file with optional packages</strong>, in this section: [How to Use Optional Packages in Connection Groups](appv-use-optional-packages-in-connection-groups.md#bkmk-apps-plugs-optional)</p></li>
<li><p>[How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></li>
<li><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></li>
</ul></td>
</tr>
</tbody>

17
windows/manage/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
View File

@ -1,8 +1,7 @@
---
title: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
title: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server (Windows 10)
description: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
author: jamiejdt
ms.assetid: 23b2d03a-20ce-4973-99ee-748f3b682207
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,22 +12,22 @@ ms.prod: w10
# How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
Deploying packages and connection groups using the App-V 5.1 publishing server is helpful because it offers single-point management and high scalability.
Deploying packages and connection groups using the App-V publishing server is helpful because it offers single-point management and high scalability.
Use the following steps to configure the App-V 5.1 client to receive updates from the publishing server.
Use the following steps to configure the App-V client to receive updates from the publishing server.
**Note**  
For the following procedures the management server was installed on a computer named **MyMgmtSrv**, and the publishing server was installed on a computer named **MyPubSrv**.
 
**To configure the App-V 5.1 client to receive updates from the publishing server**
**To configure the App-V client to receive updates from the publishing server**
1. Deploy the App-V 5.1 management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to Create a Connection Group](appv-create-a-connection-group.md).
1. Deploy the App-V management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, see [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to Create a Connection Group](appv-create-a-connection-group.md).
2. To open the management console click the following link, open a browser and type the following: http://MyMgmtSrv/AppvManagement/Console.html in a web browser, and import, publish, and entitle all the packages and connection groups which will be necessary for a particular set of users.
3. On the computer running the App-V 5.1 client, open an elevated PowerShell command prompt, run the following command:
3. On the computer running the App-V client, open an elevated PowerShell command prompt, run the following command:
**Add-AppvPublishingServer  -Name  ABC  -URL  http:// MyPubSrv/AppvPublishing**
@ -60,7 +59,7 @@ For the following procedures the management server was installed on a computer n
The returned Id – in this case 1
4. On the computer running the App-V 5.1 client, open a PowerShell command prompt, and type the following command:
4. On the computer running the App-V client, open a PowerShell command prompt, and type the following command:
**Sync-AppvPublishingServer  -ServerId  1**
@ -71,7 +70,7 @@ For the following procedures the management server was installed on a computer n
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

11
windows/manage/appv-connect-to-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Connect to the Management Console
title: How to Connect to the Management Console (Windows 10)
description: How to Connect to the Management Console
author: jamiejdt
ms.assetid: 5a15ed86-7db7-4df3-80ca-bde26f3285e1
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,11 +12,11 @@ ms.prod: w10
# How to Connect to the Management Console
Use the following procedure to connect to the App-V 5.1 Management Console.
Use the following procedure to connect to the App-V Management Console.
**To connect to the App-V 5.1 Management Console**
**To connect to the App-V Management Console**
1. Open Internet Explorer browser and type the address for the App-V 5.1. For example, **http://&lt;Management server name&gt;:&lt;Management service port number&gt;/Console.html**.
1. Open Internet Explorer browser and type the address for the App-V. For example, **http://&lt;Management server name&gt;:&lt;Management service port number&gt;/Console.html**.
2. To view different sections of the console, click the desired section in the navigation pane.
@ -26,7 +25,7 @@ Use the following procedure to connect to the App-V 5.1 Management Console.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

3
windows/manage/appv-connection-group-virtual-environment.md
View File

@ -1,8 +1,7 @@
---
title: About the Connection Group Virtual Environment
title: About the Connection Group Virtual Environment (Windows 10)
description: About the Connection Group Virtual Environment
author: jamiejdt
ms.assetid: b7bb0e3d-8cd5-45a9-b84e-c9ab4196a18c
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library

5
windows/manage/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md
View File

@ -1,8 +1,7 @@
---
title: How to Create a Connection Group with User-Published and Globally Published Packages
title: How to Create a Connection Group with User-Published and Globally Published Packages (Windows 10)
description: How to Create a Connection Group with User-Published and Globally Published Packages
author: jamiejdt
ms.assetid: 851b8742-0283-4aa6-b3a3-f7f6289824c3
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -69,7 +68,7 @@ You can create user-entitled connection groups that contain both user-published
**How to use the App-V Server to create user-entitled connection groups**
1. Open the App-V 5.1 Management Console.
1. Open the App-V Management Console.
2. Follow the instructions in [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md) to publish packages globally and to the user.

7
windows/manage/appv-create-a-connection-group.md
View File

@ -1,8 +1,7 @@
---
title: How to Create a Connection Group
title: How to Create a Connection Group (Windows 10)
description: How to Create a Connection Group
author: jamiejdt
ms.assetid: 221e2eed-7ebb-42e3-b3d6-11c37c0578e6
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -19,7 +18,7 @@ When you place packages in a connection group, their package root paths are merg
**To create a connection group**
1. In the App-V 5.1 Management Console, select **CONNECTION GROUPS** to display the Connection Groups library.
1. In the App-V Management Console, select **CONNECTION GROUPS** to display the Connection Groups library.
2. Select **ADD CONNECTION GROUP** to create a new connection group.
@ -45,7 +44,7 @@ When you place packages in a connection group, their package root paths are merg
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[Managing Connection Groups](appv-managing-connection-groups.md)

13
windows/manage/appv-create-a-custom-configuration-file-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Create a Custom Configuration File by Using the App-V 5.1 Management Console
description: How to Create a Custom Configuration File by Using the App-V 5.1 Management Console
title: How to Create a Custom Configuration File by Using the App-V Management Console (Windows 10)
description: How to Create a Custom Configuration File by Using the App-V Management Console
author: jamiejdt
ms.assetid: f5ab426a-f49a-47b3-93f3-b9d60aada8f4
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,12 +9,12 @@ ms.prod: w10
---
# How to Create a Custom Configuration File by Using the App-V 5.1 Management Console
# How to Create a Custom Configuration File by Using the App-V Management Console
You can use a dynamic configuration to customize an App-V 5.1 package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V 5.1 Dynamic Configuration](appv-dynamic-configuration.md).
You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
Use the following procedure to create a Dynamic User Configuration file by using the App-V 5.1 Management console.
Use the following procedure to create a Dynamic User Configuration file by using the App-V Management console.
**To create a Dynamic User Configuration file**
@ -37,7 +36,7 @@ Use the following procedure to create a Dynamic User Configuration file by using
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

9
windows/manage/appv-create-a-package-accelerator-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Create a Package Accelerator by Using PowerShell
title: How to Create a Package Accelerator by Using PowerShell (Windows 10)
description: How to Create a Package Accelerator by Using PowerShell
author: jamiejdt
ms.assetid: 0cb98394-4477-4193-8c5f-1c1773c7263a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,11 +12,11 @@ ms.prod: w10
# How to Create a Package Accelerator by Using PowerShell
App-V 5.1 package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V 5.1 package accelerator, you are not always required to manually install an application to create the virtualized package.
App-V package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V package accelerator, you are not always required to manually install an application to create the virtualized package.
**To create a package accelerator**
1. Install the App-V 5.1 sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. Use the **New-AppvPackageAccelerator** cmdlet.
@ -44,7 +43,7 @@ App-V 5.1 package accelerators automatically sequence large, complex application
## Related topics
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 

15
windows/manage/appv-create-a-package-accelerator.md
View File

@ -1,8 +1,7 @@
---
title: How to Create a Package Accelerator
title: How to Create a Package Accelerator (Windows 10)
description: How to Create a Package Accelerator
author: jamiejdt
ms.assetid: b61f3581-7933-443e-b872-a96bed9ff8d7
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# How to Create a Package Accelerator
App-V 5.1 package accelerators automatically generate new virtual application packages.
App-V package accelerators automatically generate new virtual application packages.
**Note**  
You can use PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md).
@ -23,7 +22,7 @@ You can use PowerShell to create a package accelerator. For more information see
Use the following procedure to create a package accelerator.
**Important**  
Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V 5.1 Package Accelerator is applied.
Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
 
@ -39,13 +38,13 @@ Before you begin the following procedure, you should perform the following:
**To create a package accelerator**
1. **Important**  
The App-V 5.1 Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V 5.1 Sequencer.
The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V Sequencer.
 
To start the App-V 5.1 sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
2. To start the App-V 5.1 **Create Package Accelerator** wizard, in the App-V 5.1 sequencer console, click **Tools** / **Create Accelerator**.
2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, click **Tools** / **Create Accelerator**.
3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, click **Browse**, and locate the existing virtual application package (.appv file).
@ -94,7 +93,7 @@ Before you begin the following procedure, you should perform the following:
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md)

15
windows/manage/appv-create-a-virtual-application-package-package-accelerator.md
View File

@ -1,8 +1,7 @@
---
title: How to Create a Virtual Application Package Using an App-V Package Accelerator
title: How to Create a Virtual Application Package Using an App-V Package Accelerator (Windows 10)
description: How to Create a Virtual Application Package Using an App-V Package Accelerator
author: jamiejdt
ms.assetid: eae1e4f8-f14f-4bc8-9867-052561c37297
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -14,20 +13,20 @@ ms.prod: w10
**Important**  
The App-V 5.1 Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V 5.1 Sequencer.
The App-V Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V Sequencer.
 
Use the following procedure to create a virtual application package with the App-V 5.1 Package Accelerator.
Use the following procedure to create a virtual application package with the App-V Package Accelerator.
**Note**  
Before you start this procedure, copy the required Package Accelerator locally to the computer that runs the App-V 5.1 Sequencer. You should also copy all required installation files for the package to a local directory on the computer that runs the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
Before you start this procedure, copy the required Package Accelerator locally to the computer that runs the App-V Sequencer. You should also copy all required installation files for the package to a local directory on the computer that runs the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
 
**To create a virtual application package with an App-V 5.1 Package Accelerator**
**To create a virtual application package with an App-V Package Accelerator**
1. To start the App-V Sequencer, on the computer that runs the App-V 5.1 Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
1. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, and then click **Next**.
@ -90,7 +89,7 @@ Before you start this procedure, copy the required Package Accelerator locally t
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

25
windows/manage/appv-create-and-use-a-project-template.md
View File

@ -1,8 +1,7 @@
---
title: How to Create and Use a Project Template
title: How to Create and Use a Project Template (Windows 10)
description: How to Create and Use a Project Template
author: jamiejdt
ms.assetid: e5ac1dc8-a88f-4b16-8e3c-df07ef5e4c3b
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,31 +12,31 @@ ms.prod: w10
# How to Create and Use a Project Template
You can use an App-V 5.1 project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages.
You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages.
**Note**  
You can, and often should apply an App-V 5.1 project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application.
You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application.
 
App-V 5.1 project templates differ from App-V 5.1 Application Accelerators because App-V 5.1 Application Accelerators are application-specific, and App-V 5.1 project templates can be applied to multiple applications.
App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications.
Use the following procedures to create and apply a new template.
**To create a project template**
1. To start the App-V 5.1 sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
2. **Note**  
If the virtual application package is currently open in the App-V 5.1 Sequencer console, skip to step 3 of this procedure.
If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure.
 
To open the existing virtual application package that contains the settings you want to save with the App-V 5.1 project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
3. In the App-V 5.1 Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V 5.1 project template. Click Save.
3. In the App-V Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click Save.
The new App-V 5.1 project template is saved in the directory specified in step 3 of this procedure.
The new App-V project template is saved in the directory specified in step 3 of this procedure.
**To apply a project template**
@ -46,9 +45,9 @@ Use the following procedures to create and apply a new template.
 
To start the App-V 5.1 sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
2. To create or upgrade a new virtual application package by using an App-V 5.1 project template, click **File** / **New From Template**.
2. To create or upgrade a new virtual application package by using an App-V project template, click **File** / **New From Template**.
3. To select the project template that you want to use, browse to the directory where the project template is saved, select the project template, and then click **Open**.
@ -59,7 +58,7 @@ Use the following procedures to create and apply a new template.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

49
windows/manage/appv-creating-and-managing-virtualized-applications.md
View File

@ -1,8 +1,7 @@
---
title: Creating and Managing App-V 5.1 Virtualized Applications
description: Creating and Managing App-V 5.1 Virtualized Applications
title: Creating and Managing App-V Virtualized Applications (Windows 10)
description: Creating and Managing App-V Virtualized Applications
author: jamiejdt
ms.assetid: 26be4331-88eb-4cfb-9d82-e63d7ee54576
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,36 +9,36 @@ ms.prod: w10
---
# Creating and Managing App-V 5.1 Virtualized Applications
# Creating and Managing App-V Virtualized Applications
After you have properly deployed the Microsoft Application Virtualization (App-V) 5.1 sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
After you have properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
**Note**  
For more information about configuring the App-V 5.1 sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V 5.0 Sequencing Guide.docx).
For more information about configuring the App-V sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V 5.0 Sequencing Guide.docx).
**Note**
The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
The App-V Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
## Sequencing an application
You can use the App-V 5.1 Sequencer to perform the following tasks:
You can use the App-V Sequencer to perform the following tasks:
- Create virtual packages that can be deployed to computers running the App-V 5.1 client.
- Create virtual packages that can be deployed to computers running the App-V client.
- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
**Note**  
You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V 5.1 client.
You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client.
 
- Convert existing virtual packages.
The sequencer uses the **%TMP% \\ Scratch** or **%TEMP% \\ Scratch** directory and the **Temp** directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V 5.1 package.
When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V package.
- .msi file. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
@ -59,20 +58,20 @@ The **Options** dialog box in the sequencer console contains the following tabs:
- **General**. Use this tab to enable Microsoft Updates to run during sequencing. Select **Append Package Version to Filename** to configure the sequence to add a version number to the virtualized package that is being sequenced. Select **Always trust the source of Package Accelerators** to create virtualized packages using a package accelerator without being prompted for authorization.
**Important**  
Package Accelerators created using App-V 4.6 are not supported by App-V 5.1.  
Package Accelerators created using App-V 4.6 are not supported by App-V.  
- **Parse Items**. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the **Package Files** tab in **Advanced Editing**.
- **Exclusion Items**. Use this tab to specify which folders and directories should not be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click **New** and specify the location and the associated **Mapping Type**. This option is required for some packages.
App-V 5.1 supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
[How to Sequence a New Application with App-V 5.1](appv-sequence-a-new-application.md)
[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
## <a href="" id="---------app-v-5-1-shell-extension-support"></a> App-V 5.1 shell extension support
## <a href="" id="---------app-v-5-1-shell-extension-support"></a> App-V shell extension support
App-V 5.1 supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
App-V supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
Shell extensions are embedded in the package automatically during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
@ -139,9 +138,9 @@ The following table lists the supported shell extensions:
## Copy on Write (CoW) file extension support
Copy on write (CoW) file extensions allow App-V 5.1 to dynamically write to specific locations contained in the virtual package while it is being used.
Copy on write (CoW) file extensions allow App-V to dynamically write to specific locations contained in the virtual package while it is being used.
The following table displays the file types that can exist in a virtual package under the VFS directory, but cannot be updated on the computer running the App-V 5.1 client. All other files and directories can be modified.
The following table displays the file types that can exist in a virtual package under the VFS directory, but cannot be updated on the computer running the App-V client. All other files and directories can be modified.
| File Type | | | | | |
|------------ |------------- |------------- |------------ |------------ |------------ |
@ -169,7 +168,7 @@ You can use the sequencer to modify an existing package. The computer on which y
A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings.
App-V 5.1 project templates differ from App-V 5.1 Application Accelerators because App-V 5.1 Application Accelerators are application-specific, and App-V 5.1 project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V 5.1 project template:
App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
A template can specify and store multiple settings as follows:
@ -185,13 +184,13 @@ A template can specify and store multiple settings as follows:
**Note**  
Package accelerators created using a previous version of App-V must be recreated using App-V 5.1.
Package accelerators created using a previous version of App-V must be recreated using App-V.
You can use App-V 5.1 package accelerators to automatically generate a new virtual application packages. After you have successfully created a package accelerator, you can reuse and share the package accelerator.
You can use App-V package accelerators to automatically generate a new virtual application packages. After you have successfully created a package accelerator, you can reuse and share the package accelerator.
In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
After you have successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V 5.1 Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V 5.1 Package Accelerator is applied.
After you have successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
[How to Create a Package Accelerator](appv-create-a-package-accelerator.md)
@ -200,13 +199,13 @@ After you have successfully created a Package Accelerator, you can reuse and sha
## Sequencer error reporting
The App-V 5.1 Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
The App-V Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
You can also find additional information about sequencing errors using the Windows Event Viewer.
## <a href="" id="other-resources-for-the-app-v-5-1-sequencer-"></a>Other resources for the App-V 5.1 sequencer
## <a href="" id="other-resources-for-the-app-v-5-1-sequencer-"></a>Other resources for the App-V sequencer
- [Operations for App-V 5.1](appv-operations.md)
- [Operations for App-V](appv-operations.md)

7
windows/manage/appv-customize-virtual-application-extensions-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
title: How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console (Windows 10)
description: How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
author: jamiejdt
ms.assetid: dd71df05-512f-4eb4-a55f-e5b93601323d
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -17,7 +16,7 @@ Use the following procedure to customize the virtual application extensions for
**To customize virtual applications extensions for an AD group**
1. To view the package that you want to configure, open the App-V 5.1 Management Console. To view the configuration that is assigned to a given user group, select the package, and right-click the package name and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
1. To view the package that you want to configure, open the App-V Management Console. To view the configuration that is assigned to a given user group, select the package, and right-click the package name and select **Edit active directory access**. Alternatively, select the package and click **EDIT** in the **AD ACCESS** pane.
2. To customize an AD group, you can find the group from the list of **AD Entities with Access**. Then, using the drop-down box in the **Assigned Configuration** pane, select **Custom**, and then click **EDIT**.
@ -34,7 +33,7 @@ Use the following procedure to customize the virtual application extensions for
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

5
windows/manage/appv-delete-a-connection-group.md
View File

@ -1,8 +1,7 @@
---
title: How to Delete a Connection Group
title: How to Delete a Connection Group (Windows 10)
description: How to Delete a Connection Group
author: jamiejdt
ms.assetid: dfdfb507-8891-4f17-9125-5759c9b74483
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -26,7 +25,7 @@ Use the following procedure to delete an existing App-V connection group.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[Managing Connection Groups](appv-managing-connection-groups.md)

9
windows/manage/appv-delete-a-package-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Delete a Package in the Management Console
title: How to Delete a Package in the Management Console (Windows 10)
description: How to Delete a Package in the Management Console
author: jamiejdt
ms.assetid: 4a2be40b-bbb8-4fab-992d-7466df432858
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,11 +12,11 @@ ms.prod: w10
# How to Delete a Package in the Management Console
Use the following procedure to delete an App-V 5.1 package.
Use the following procedure to delete an App-V package.
**To delete a package in the Management Console**
1. To view the package you want to delete, open the App-V 5.1 Management Console and select **Packages**. Select the package to be removed.
1. To view the package you want to delete, open the App-V Management Console and select **Packages**. Select the package to be removed.
2. Click or right-click the package. Select **Delete** to remove the package.
@ -26,7 +25,7 @@ Use the following procedure to delete an App-V 5.1 package.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

6
windows/manage/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -14,12 +14,12 @@ ms.prod: w10
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
- Install the App-V 5.1 databases
- Install the App-V databases
- Upgrade the App-V databases to a later version
**Note**  
If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not required to upgrade to App-V 5.1.
If you have already deployed the App-V 5.0 SP3 database, the SQL scripts are not required to upgrade to App-V.
## How to install the App-V databases by using SQL scripts
@ -207,8 +207,6 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
<!-- Should 5.1 be put back into the titles and-or filenames of the following related topics? -->
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)

25
windows/manage/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md
View File

@ -1,8 +1,7 @@
---
title: How to deploy App-V 5.1 Packages Using Electronic Software Distribution
description: How to deploy App-V 5.1 Packages Using Electronic Software Distribution
title: How to deploy App-V Packages Using Electronic Software Distribution (Windows 10)
description: How to deploy App-V Packages Using Electronic Software Distribution
author: jamiejdt
ms.assetid: e1957a5a-1f18-42da-b2c1-a5ae5a4cca7a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,12 +9,12 @@ ms.prod: w10
---
# How to deploy App-V 5.1 Packages Using Electronic Software Distribution
# How to deploy App-V Packages Using Electronic Software Distribution
You can use an electronic software distribution (ESD) system to deploy App-V 5.1 virtual applications to App-V clients. For details, see the documentation available with the ESD you are using.
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients. For details, see the documentation available with the ESD you are using.
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V 5.1 with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
Use one of the following methods to publish packages to App-V client computers with an ESD:
@ -37,33 +36,33 @@ Use one of the following methods to publish packages to App-V client computers w
</tr>
<tr class="even">
<td align="left"><p>Stand-alone Windows Installer</p></td>
<td align="left"><p>Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V 5.1 package file information used to configure a package and copies the required package files to the client.</p></td>
<td align="left"><p>Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>PowerShell</p></td>
<td align="left"><p>Use PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V 5.1, see [Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md).</p></td>
<td align="left"><p>Use PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V, see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).</p></td>
</tr>
</tbody>
</table>
 
**To deploy App-V 5.1 packages by using an ESD**
**To deploy App-V packages by using an ESD**
1. Install the App-V 5.1 Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
1. Install the App-V Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
2. Use the App-V 5.1 Sequencer to create virtual application. For information about creating a virtual application, see [Creating and Managing App-V 5.1 Virtualized Applications](appv-creating-and-managing-virtualized-applications.md).
2. Use the App-V Sequencer to create virtual application. For information about creating a virtual application, see [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md).
3. After you create the virtual application, deploy the package by using your ESD solution.
If you are using System Center Configuration Manager, start by reviewing [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816) for information about using App-V 5.1 and System Center 2012 Configuration Manager.
If you are using System Center Configuration Manager, start by reviewing [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816) for information about using App-V and System Center 2012 Configuration Manager.
**Got 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/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

23
windows/manage/appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
description: How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
title: How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer (Windows 10)
description: How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer
author: jamiejdt
ms.assetid: 498d50c7-f13d-4fbb-8ea1-b959ade26fdf
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,12 +9,12 @@ ms.prod: w10
---
# How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer
# How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer
Use the following information to install the Microsoft Application Virtualization (App-V) 5.1 client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md).
Use the following information to install the Microsoft Application Virtualization (App-V) client (preferably, with the latest Service Packs and hotfixes) and the App-V 4.6 SP2 client or the App-V 4.6 S3 client on the same computer. For supported versions, requirements, and other planning information, see [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md).
**To deploy the App-V 5.1 client and App-V 4.6.x client on the same computer**
**To deploy the App-V client and App-V 4.6.x client on the same computer**
1. Install one of the following versions of the App-V client on the computer that is running App-V 4.6.
@ -23,11 +22,11 @@ Use the following information to install the Microsoft Application Virtualizatio
- [Microsoft Application Virtualization 4.6 Service Pack 3](http://www.microsoft.com/download/details.aspx?id=41187)
2. Install the App-V 5.1 client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V 5.1 client.
2. Install the App-V client on the computer that is running the App-V 4.6 SP2 or 4.6 SP3 version of the client. For best results, we recommend that you install all available updates to the App-V client.
3. Convert or re-sequence the packages gradually.
- To convert the packages, use the App-V 5.1 package converter and convert the required packages to the App-V 5.1 (**.appv**) file format.
- To convert the packages, use the App-V package converter and convert the required packages to the App-V (**.appv**) file format.
- To re-sequence the packages, consider using the latest version of the Sequencer for best results.
@ -37,13 +36,13 @@ Use the following information to install the Microsoft Application Virtualizatio
5. Convert extension points, as needed. For more information, see the following resources:
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md)
- [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md)
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md)
- [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md)
- [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)
6. Test that your App-V 5.1 packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
6. Test that your App-V packages are successful, and then remove the 4.6 packages. To check the user state of your client computers, we recommend that you use [User Experience Virtualization](http://technet.microsoft.com/library/dn458947.aspx) or another user environment management tool.
**Got 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/home?forum=mdopappv).
@ -52,7 +51,7 @@ Use the following information to install the Microsoft Application Virtualizatio
[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
[Deploying the App-V 5.1 Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
 

13
windows/manage/appv-deploy-the-appv-server-with-a-script.md
View File

@ -1,8 +1,7 @@
---
title: How to Deploy the App-V 5.1 Server Using a Script
description: How to Deploy the App-V 5.1 Server Using a Script
title: How to Deploy the App-V Server Using a Script (Windows 10)
description: How to Deploy the App-V Server Using a Script
author: jamiejdt
ms.assetid: 15c33d7b-9b61-4dbc-8674-399bb33e5f7e
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,14 +9,14 @@ ms.prod: w10
---
# How to Deploy the App-V 5.1 Server Using a Script
# How to Deploy the App-V Server Using a Script
In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters.
**To Install the App-V 5.1 server using a script**
**To Install the App-V server using a script**
- Use the following tables for more information about installing the App-V 5.1 server using the command line.
- Use the following tables for more information about installing the App-V server using the command line.
**Note**  
The information in the following tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**.
@ -778,7 +777,7 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
## Related topics
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
 

37
windows/manage/appv-deploying-appv.md
View File

@ -1,8 +1,7 @@
---
title: Deploying App-V 5.1
description: Deploying App-V 5.1
title: Deploying App-V (Windows 10)
description: Deploying App-V
author: jamiejdt
ms.assetid: af8742bf-e24b-402a-bcf4-0f2297f26bc4
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,40 +9,40 @@ ms.prod: w10
---
# Deploying App-V 5.1
# Deploying App-V
Microsoft Application Virtualization (App-V) 5.1 supports a number of different deployment options. This section of the App-V 5.1 Administrator’s Guide includes information you should consider about the deployment of App-V 5.1 and step-by-step procedures to help you successfully perform the tasks that you must complete at different stages of your deployment.
Microsoft Application Virtualization (App-V) supports a number of different deployment options. This section of the App-V Administrator’s Guide includes information you should consider about the deployment of App-V and step-by-step procedures to help you successfully perform the tasks that you must complete at different stages of your deployment.
## <a href="" id="---------app-v-5-1-deployment-information"></a> App-V 5.1 Deployment Information
## <a href="" id="---------app-v-5-1-deployment-information"></a> App-V Deployment Information
- [Deploying the App-V 5.1 Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
This section describes how to install the App-V 5.1 sequencer which is used to virtualize applications, and the App-V 5.1 client which runs on target computers to facilitate virtualized packages.
This section describes how to install the App-V sequencer which is used to virtualize applications, and the App-V client which runs on target computers to facilitate virtualized packages.
- [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
This section provides information about installing the App-V 5.1 management, publishing, database and reporting severs.
This section provides information about installing the App-V management, publishing, database and reporting severs.
- [App-V 5.1 Deployment Checklist](appv-deployment-checklist.md)
- [App-V Deployment Checklist](appv-deployment-checklist.md)
This section provides a deployment checklist that can be used to assist with installing App-V 5.1.
This section provides a deployment checklist that can be used to assist with installing App-V.
## Other Resources for Deploying App-V 5.1
## Other Resources for Deploying App-V
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Getting Started with App-V 5.1](appv-getting-started.md)
- [Getting Started with App-V](appv-getting-started.md)
- [Planning for App-V 5.1](appv-planning-for-appv.md)
- [Planning for App-V](appv-planning-for-appv.md)
- [Operations for App-V 5.1](appv-operations.md)
- [Operations for App-V](appv-operations.md)
- [Troubleshooting App-V 5.1](appv-troubleshooting.md)
- [Troubleshooting App-V](appv-troubleshooting.md)
- [Technical Reference for App-V 5.1](appv-technical-reference.md)
- [Technical Reference for App-V](appv-technical-reference.md)
## Got a suggestion for App-V?

21
windows/manage/appv-deploying-microsoft-office-2013-with-appv.md
View File

@ -1,8 +1,7 @@
---
title: Deploying Microsoft Office 2013 by Using App-V
title: Deploying Microsoft Office 2013 by Using App-V (Windows 10)
description: Deploying Microsoft Office 2013 by Using App-V
author: jamiejdt
ms.assetid: 9a7be05e-2a7a-4874-af25-09c0f5037876
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# Deploying Microsoft Office 2013 by Using App-V
Use the information in this article to use Microsoft Application Virtualization (App-V) 5.1, or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
Use the information in this article to use Microsoft Application Virtualization (App-V), or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
This topic contains the following sections:
@ -21,7 +20,7 @@ This topic contains the following sections:
- [Creating an Office 2013 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
- [Publishing the Office package for App-V 5.1](#bkmk-pub-pkg-office)
- [Publishing the Office package for App-V](#bkmk-pub-pkg-office)
- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
@ -83,7 +82,7 @@ Before you deploy Office by using App-V, review the following requirements.
<td align="left"><p>Packaging</p></td>
<td align="left"><ul>
<li><p>All of the Office applications that you want to deploy to users must be in a single package.</p></li>
<li><p>In App-V 5.1 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.</p></li>
<li><p>In App-V and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.</p></li>
<li><p>If you are deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project).</p></li>
</ul></td>
</tr>
@ -152,10 +151,10 @@ The following table describes the recommended methods for excluding specific Off
## <a href="" id="bkmk-create-office-pkg"></a>Creating an Office 2013 package for App-V with the Office Deployment Tool
Complete the following steps to create an Office 2013 package for App-V 5.1 or later.
Complete the following steps to create an Office 2013 package for App-V or later.
**Important**  
In App-V 5.1 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
In App-V and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
 
@ -564,7 +563,7 @@ After you download the Office 2013 applications through the Office Deployment To
2. Start a few Office 2013 applications, such as Excel or Word, to ensure that your package is working as expected.
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V 5.1
## <a href="" id="bkmk-pub-pkg-office"></a>Publishing the Office package for App-V
Use the following information to publish an Office package.
@ -642,9 +641,9 @@ Use the steps in this section to enable Office plug-ins with your Office package
1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
2. Sequence your plug-ins using the App-V 5.1 Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Office 365 ProPlus(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
3. Create an App-V 5.1 package that includes the desired plug-ins.
3. Create an App-V package that includes the desired plug-ins.
4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
@ -879,7 +878,7 @@ The following table describes the requirements and options for deploying Visio 2
**Dynamic Configuration**
[About App-V 5.1 Dynamic Configuration](appv-dynamic-configuration.md)
[About App-V Dynamic Configuration](appv-dynamic-configuration.md)
## Got a suggestion for App-V?

15
windows/manage/appv-deploying-packages-with-electronic-software-distribution-solutions.md
View File

@ -1,8 +1,7 @@
---
title: Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)
description: Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)
title: Deploying App-V Packages by Using Electronic Software Distribution (ESD)
description: Deploying App-V Packages by Using Electronic Software Distribution (ESD)
author: jamiejdt
ms.assetid: c2e4d176-460d-44ca-9a1d-69d2a733aa42
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,10 +9,10 @@ ms.prod: w10
---
# Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)
# Deploying App-V Packages by Using Electronic Software Distribution (ESD)
You can deploy App-V 5.1 packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V 5.1 with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
You can deploy App-V packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
To deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816)
@ -22,7 +21,7 @@ To deploy App-V packages with Microsoft System Center 2012 Configuration Manage
Describes the methods you can use to deploy App-V packages by using an ESD
[How to deploy App-V 5.1 Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
[How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
## How to Enable Only Administrators to Publish Packages by Using an ESD
@ -36,12 +35,12 @@ Explains how to configure the App-V client to enable only administrators to publ
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/home?forum=mdopappv).
## Other resources for using an ESD and App-V 5.1
## Other resources for using an ESD and App-V
Use the following link for more information about [App-V and Citrix Integration](http://go.microsoft.com/fwlink/?LinkId=330294 ) (http://go.microsoft.com/fwlink/?LinkId=330294).
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

51
windows/manage/appv-deploying-the-appv-sequencer-and-client.md
View File

@ -1,8 +1,7 @@
---
title: Deploying the App-V 5.1 Sequencer and Client
description: Deploying the App-V 5.1 Sequencer and Client
title: Deploying the App-V Sequencer and Client (Windows 10)
description: Deploying the App-V Sequencer and Client
author: jamiejdt
ms.assetid: 74f32794-4c76-436f-a542-f9e95d89063d
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,36 +9,36 @@ ms.prod: w10
---
# Deploying the App-V 5.1 Sequencer and Client
# Deploying the App-V Sequencer and Client
The Microsoft Application Virtualization (App-V) 5.1 Sequencer and client enable administrators to virtualize and run virtualized applications.
The Microsoft Application Virtualization (App-V) Sequencer and client enable administrators to virtualize and run virtualized applications.
## Deploy the client
The App-V 5.1 client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
[How to Deploy the App-V Client](appv-deploy-the-appv-client.md)
[How to Uninstall the App-V 5.1 Client](appv-uninstall-the-appv-client.md)
[How to Uninstall the App-V Client](appv-uninstall-the-appv-client.md)
[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
[How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
## Client Configuration Settings
The App-V 5.1 client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
[About Client Configuration Settings](appv-client-configuration-settings.md)
## Configure the client by using the ADMX template and Group Policy
You can use the Microsoft ADMX template to configure the client settings for the App-V 5.1 client and the Remote Desktop Services client. The ADMX template manages common client configurations by using an existing Group Policy infrastructure and it includes settings for the App-V 5.1 client configuration.
You can use the Microsoft ADMX template to configure the client settings for the App-V client and the Remote Desktop Services client. The ADMX template manages common client configurations by using an existing Group Policy infrastructure and it includes settings for the App-V client configuration.
**Important**  
You can obtain the App-V 5.1 ADMX template from the Microsoft Download Center.
You can obtain the App-V ADMX template from the Microsoft Download Center.
 
@ -49,23 +48,23 @@ After you download and install the ADMX template, perform the following steps on
2. Save the **.adml** file to the following directory: **Windows \\ PolicyDefinitions \\ &lt;Language Directory&gt;**
After you have completed the preceding steps, you can manage the App-V 5.1 client configuration settings with the **Group Policy Management** console.
After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console.
The App-V 5.1 client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries.
The App-V client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries.
[How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
## Deploy the client by using the Shared Content Store mode
The App-V 5.1 Shared Content Store (SCS) mode enables the SCS App-V 5.1 clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V 5.1 client are supported with SCS mode.
The App-V Shared Content Store (SCS) mode enables the SCS App-V clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V client are supported with SCS mode.
**Important**  
If the App-V 5.1 client is configured to run in the SCS mode, the location where the App-V 5.1 packages are streamed from must be available, otherwise, the virtualized package will fail. Additionally, we do not recommend deployment of virtualized applications to computers that run the App-V 5.1 client in the SCS mode across the internet.
If the App-V client is configured to run in the SCS mode, the location where the App-V packages are streamed from must be available, otherwise, the virtualized package will fail. Additionally, we do not recommend deployment of virtualized applications to computers that run the App-V client in the SCS mode across the internet.
 
Additionally, the SCS is not a physical location that contains virtualized packages. It is a mode that allows the App-V 5.1 client to stream the required virtualized package data across the network.
Additionally, the SCS is not a physical location that contains virtualized packages. It is a mode that allows the App-V client to stream the required virtualized package data across the network.
The SCS mode is helpful in the following scenarios:
@ -73,36 +72,36 @@ The SCS mode is helpful in the following scenarios:
- Remote desktop services (RDS) deployments
To use SCS in your environment, you must enable the App-V 5.1 client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V 5.1 client to run in SCS mode by entering the following PowerShell command on the computer that runs the App-V 5.1 client:
To use SCS in your environment, you must enable the App-V client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V client to run in SCS mode by entering the following PowerShell command on the computer that runs the App-V client:
**set-AppvClientConfiguration -SharedContentStoreMode 1**
There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V 5.1 client in SCS mode. This can be accomplished with PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using PowerShell commands. The package would not stream across the network because it would be locally stored.
There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V client in SCS mode. This can be accomplished with PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using PowerShell commands. The package would not stream across the network because it would be locally stored.
[How to Install the App-V 5.1 Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
## Deploy the Sequencer
The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V 5.1 client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.
The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.
For a list of changes in the App-V 5.1 Sequencer, see [About App-V 5.1](appv-about-appv.md).
For a list of changes in the App-V Sequencer, see [About App-V](appv-about-appv.md).
[How to Install the Sequencer](appv-install-the-sequencer.md)
## <a href="" id="---------app-v-5-1-client-and-sequencer-logs"></a> App-V 5.1 Client and Sequencer logs
## <a href="" id="---------app-v-5-1-client-and-sequencer-logs"></a> App-V Client and Sequencer logs
You can use the App-V 5.1 Sequencer log information to help troubleshoot the Sequencer installation and operational events while using App-V 5.1. The Sequencer-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Sequencer-related events:
You can use the App-V Sequencer log information to help troubleshoot the Sequencer installation and operational events while using App-V. The Sequencer-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Sequencer-related events:
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**. Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**.
## Other resources for deploying the Sequencer and client
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
[Planning for App-V 5.1](appv-planning-for-appv.md)
[Planning for App-V](appv-planning-for-appv.md)
## Got a suggestion for App-V?

25
windows/manage/appv-deployment-checklist.md
View File

@ -1,8 +1,7 @@
---
title: App-V 5.1 Deployment Checklist
description: App-V 5.1 Deployment Checklist
title: App-V Deployment Checklist (Windows 10)
description: App-V Deployment Checklist
author: jamiejdt
ms.assetid: 44bed85a-e4f5-49d7-a308-a2b681f76372
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,13 +9,13 @@ ms.prod: w10
---
# App-V 5.1 Deployment Checklist
# App-V Deployment Checklist
This checklist can be used to help you during Microsoft Application Virtualization (App-V) 5.1 deployment.
This checklist can be used to help you during Microsoft Application Virtualization (App-V) deployment.
**Note**  
This checklist outlines the recommended steps and a high-level list of items to consider when deploying App-V 5.1 features. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
This checklist outlines the recommended steps and a high-level list of items to consider when deploying App-V features. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
 
@ -38,19 +37,19 @@ This checklist outlines the recommended steps and a high-level list of items to
<tbody>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Complete the planning phase to prepare the computing environment for App-V 5.1 deployment.</p></td>
<td align="left"><p>[App-V 5.1 Planning Checklist](appv-planning-checklist.md)</p></td>
<td align="left"><p>Complete the planning phase to prepare the computing environment for App-V deployment.</p></td>
<td align="left"><p>[App-V Planning Checklist](appv-planning-checklist.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Review the App-V 5.1 supported configurations information to make sure selected client and server computers are supported for App-V 5.1 feature installation.</p></td>
<td align="left"><p>[App-V 5.1 Supported Configurations](appv-supported-configurations.md)</p></td>
<td align="left"><p>Review the App-V supported configurations information to make sure selected client and server computers are supported for App-V feature installation.</p></td>
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Run App-V 5.1 Setup to deploy the required App-V 5.1 features for your environment.</p>
<td align="left"><p>Run App-V Setup to deploy the required App-V features for your environment.</p>
<div class="alert">
<strong>Note</strong>  
<p>Keep track of the names of the servers and associated URL’s created during installation. This information will be used throughout the installation process.</p>
@ -62,7 +61,7 @@ This checklist outlines the recommended steps and a high-level list of items to
<ul>
<li><p>[How to Install the Sequencer](appv-install-the-sequencer.md)</p></li>
<li><p>[How to Deploy the App-V Client](appv-deploy-the-appv-client.md)</p></li>
<li><p>[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)</p></li>
<li><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
</ul></td>
<td align="left"><p></p></td>
</tr>
@ -79,7 +78,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
 

5
windows/manage/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
View File

@ -1,8 +1,7 @@
---
title: How to Enable Only Administrators to Publish Packages by Using an ESD
title: How to Enable Only Administrators to Publish Packages by Using an ESD (Windows 10)
description: How to Enable Only Administrators to Publish Packages by Using an ESD
author: jamiejdt
ms.assetid: bbc9fda2-fc09-4d72-8d9a-e83d2fcfe234
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -23,7 +22,7 @@ Starting in App-V 5.0 SP3, you can configure the App-V client so that only admin
2. Enable the **Require publish as administrator** Group Policy setting.
To alternatively use PowerShell to set this item, see [How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
**Got 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/home?forum=mdopappv).

19
windows/manage/appv-enable-reporting-on-the-appv-client-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Enable Reporting on the App-V 5.1 Client by Using PowerShell
description: How to Enable Reporting on the App-V 5.1 Client by Using PowerShell
title: How to Enable Reporting on the App-V Client by Using PowerShell (Windows 10)
description: How to Enable Reporting on the App-V Client by Using PowerShell
author: jamiejdt
ms.assetid: c4c58be6-cc50-44f6-bf4f-8346fc5d0c0e
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,16 +9,16 @@ ms.prod: w10
---
# How to Enable Reporting on the App-V 5.1 Client by Using PowerShell
# How to Enable Reporting on the App-V Client by Using PowerShell
Use the following procedure to configure the App-V 5.1 for reporting.
Use the following procedure to configure the App-V for reporting.
**To configure the computer running the App-V 5.1 client for reporting**
**To configure the computer running the App-V client for reporting**
1. Install the App-V 5.1 client. For more information about installing the client see [How to Deploy the App-V Client](appv-deploy-the-appv-client.md).
1. Install the App-V client. For more information about installing the client see [How to Deploy the App-V Client](appv-deploy-the-appv-client.md).
2. After you have installed the App-V 5.1 client, use the **Set-AppvClientConfiguration** PowerShell to configure appropriate Reporting Configuration settings:
2. After you have installed the App-V client, use the **Set-AppvClientConfiguration** PowerShell to configure appropriate Reporting Configuration settings:
<table>
<colgroup>
@ -73,7 +72,7 @@ Use the following procedure to configure the App-V 5.1 for reporting.
 
3. After the appropriate settings have been configured, the computer running the App-V 5.1 client will automatically collect data and will send the data back to the reporting server.
3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server.
Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** PowerShell cmdlet.
@ -82,7 +81,7 @@ Use the following procedure to configure the App-V 5.1 for reporting.
## Related topics
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 

31
windows/manage/appv-evaluating-appv.md
View File

@ -1,8 +1,7 @@
---
title: Evaluating App-V 5.1
description: Evaluating App-V 5.1
title: Evaluating App-V (Windows 10)
description: Evaluating App-V
author: jamiejdt
ms.assetid: 92d80b23-3eca-4be3-a771-e700ad1470db
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,33 +9,33 @@ ms.prod: w10
---
# Evaluating App-V 5.1
# Evaluating App-V
Before you deploy Microsoft Application Virtualization (App-V) 5.1 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 5.1 in a lab environment for evaluation purposes only.
Before you deploy Microsoft Application Virtualization (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 5.1 Evaluation
## Configure lab computers for App-V Evaluation
Use the following link for information about setting up the App-V 5.1 sequencer on a computer in your lab environment.
Use the following link for information about setting up the App-V sequencer on a computer in your lab environment.
### Installing the App-V 5.1 Sequencer and Creating Packages
### Installing the App-V Sequencer and Creating Packages
Use the following links for information about setting up the App-V 5.1 sequencer and creating packages in your lab environment.
Use the following links for information about setting up the App-V sequencer and creating packages in your lab environment.
- [How to Install the Sequencer](appv-install-the-sequencer.md)
- [Creating and Managing App-V 5.1 Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
### <a href="" id="configuring-the-app-v-5-1-server-"></a>Configuring the App-V 5.1 Server
### <a href="" id="configuring-the-app-v-5-1-server-"></a>Configuring the App-V Server
Use the following links for information about setting up the App-V 5.1 server in your lab environment.
Use the following links for information about setting up the App-V server in your lab environment.
- [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md)
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
- [Administering App-V 5.1 Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
### Installing the App-V 5.1 Client
### Installing the App-V Client
Use the following link for more information about creating and managing virtualized packages in your lab environment.
@ -52,7 +51,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Getting Started with App-V 5.1](appv-getting-started.md)
[Getting Started with App-V](appv-getting-started.md)
 

2
windows/manage/appv-getting-started.md
View File

@ -16,7 +16,7 @@ Microsoft Application Virtualization (App-V) enables organizations to deliver Wi
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise) and is available with Software Assurance. 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 [App-V Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md).
If you’re already using App-V 5.1, performing an in-place upgrade to Windows 10 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-from-an-existing-installation.md).
If you’re already using App-V, performing an in-place upgrade to Windows 10 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-from-an-existing-installation.md).
Important: You can migrate your existing App-V installation to Windows 10 from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10.

21
windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md
View File

@ -1,8 +1,7 @@
---
title: How to Install the App-V 5.1 Client for Shared Content Store Mode
description: How to Install the App-V 5.1 Client for Shared Content Store Mode
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: jamiejdt
ms.assetid: 6f3ecb1b-b5b5-4ae0-8de9-b4ffdfd2c216
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,25 +9,25 @@ ms.prod: w10
---
# How to Install the App-V 5.1 Client for Shared Content Store Mode
# How to Install the App-V Client for Shared Content Store Mode
Use the following procedure to install the Microsoft Application Virtualization (App-V) 5.1 client so that it uses the App-V 5.1 Shared Content Store (SCS) mode. You should ensure that all required prerequisites are installed on the computer you plan to install to. Use the following link to see [App-V 5.1 Prerequisites](appv-prerequisites.md).
Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. You should ensure that all required prerequisites are installed on the computer you plan to install to. Use the following link to see [App-V Prerequisites](appv-prerequisites.md).
**Note**  
Before performing this procedure if necessary uninstall any existing version of the App-V 5.1 client.
Before performing this procedure if necessary uninstall any existing version of the App-V client.
 
For more information about SCS mode, see [Shared Content Store in Microsoft App-V 5.0 – Behind the Scenes](http://go.microsoft.com/fwlink/?LinkId=316879) (http://go.microsoft.com/fwlink/?LinkId=316879).
**Install and configure the App-V 5.1 client for SCS mode**
**Install and configure the App-V client for SCS mode**
1. Copy the App-V 5.1 client installation files to the computer on which it will be installed. Open a command line and from the directory where the installation files are saved type one of the following options depending on the version of the client you are installing:
1. Copy the App-V client installation files to the computer on which it will be installed. Open a command line and from the directory where the installation files are saved type one of the following options depending on the version of the client you are installing:
- To install the RDS version of the App-V 5.1 client type: **appv\_client\_setup\_rds.exe /SHAREDCONTENTSTOREMODE=1 /q**
- To install the RDS version of the App-V client type: **appv\_client\_setup\_rds.exe /SHAREDCONTENTSTOREMODE=1 /q**
- To install the standard version of the App-V 5.1 client type: **appv\_client\_setup.exe /SHAREDCONTENTSTOREMODE=1 /q**
- To install the standard version of the App-V client type: **appv\_client\_setup.exe /SHAREDCONTENTSTOREMODE=1 /q**
**Important**  
You must perform a silent installation or the installation will fail.
@ -42,7 +41,7 @@ For more information about SCS mode, see [Shared Content Store in Microsoft App-
## Related topics
[Deploying the App-V 5.1 Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
 

5
windows/manage/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell (Windows 10)
description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
author: jamiejdt
ms.assetid: 2be6fb72-f3a6-4550-bba1-6defa78ca08a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -379,7 +378,7 @@ Before attempting this procedure, you should read and understand the information
## Related topics
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 

21
windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md
View File

@ -1,8 +1,7 @@
---
title: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
title: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services (Windows 10)
description: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
author: jamiejdt
ms.assetid: 2a67402e-3119-40ea-a247-24d166af1ced
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -22,7 +21,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
**To install the management database and the management server on separate computers**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
@ -51,7 +50,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
**To install the reporting database and the reporting server on separate computers**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
@ -78,19 +77,19 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
8. To start the installation, click **Install**.
**To install the management and reporting databases using App-V 5.1 database scripts**
**To install the management and reporting databases using App-V database scripts**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on.
1. Copy the App-V server installation files to the computer on which you want to install it on.
2. To extract the App-V 5.1 database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**.
3. After the extraction has been completed, to access the App-V 5.1 database scripts and instructions readme file:
3. After the extraction has been completed, to access the App-V database scripts and instructions readme file:
- The App-V 5.1 Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
- The App-V Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
- The App-V 5.1 Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
- The App-V Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
@ -106,7 +105,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
 

7
windows/manage/appv-install-the-management-server-on-a-standalone-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to install the Management Server on a Standalone Computer and Connect it to the Database
title: How to install the Management Server on a Standalone Computer and Connect it to the Database (Windows 10)
description: How to install the Management Server on a Standalone Computer and Connect it to the Database
author: jamiejdt
ms.assetid: 3f83c335-d976-4abd-b8f8-d7f5e50b4318
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -17,7 +16,7 @@ Use the following procedure to install the management server on a standalone com
**To install the management server on a standalone computer and connect it to the database**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
@ -51,7 +50,7 @@ Use the following procedure to install the management server on a standalone com
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
 

13
windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to Install the Publishing Server on a Remote Computer
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
description: How to Install the Publishing Server on a Remote Computer
author: jamiejdt
ms.assetid: 1c903f78-0558-458d-a149-d5f6fb55aefb
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -17,7 +16,7 @@ Use the following procedure to install the publishing server on a separate compu
**To install the publishing server on a separate computer**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
@ -33,13 +32,13 @@ Use the following procedure to install the publishing server on a separate compu
- Specify the website name that you want to use for the publishing service. Accept the default if you do not have a custom name.
- For the **Port Binding**, specify a unique port number that will be used by App-V 5.1, for example **54321**.
- For the **Port Binding**, specify a unique port number that will be used by App-V, for example **54321**.
7. On the **Ready to Install** page, click **Install**.
8. After the installation is complete, the publishing server must be registered with the management server. In the App-V 5.1 management console, use the following steps to register the server:
8. After the installation is complete, the publishing server must be registered with the management server. In the App-V management console, use the following steps to register the server:
1. Open the App-V 5.1 management server console.
1. Open the App-V management server console.
2. In the left pane, select **Servers**, and then select **Register New Server**.
@ -68,7 +67,7 @@ Use the following procedure to install the publishing server on a separate compu
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
 

15
windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to install the Reporting Server on a Standalone Computer and Connect it to the Database
title: How to install the Reporting Server on a Standalone Computer and Connect it to the Database (Windows 10)
description: How to install the Reporting Server on a Standalone Computer and Connect it to the Database
author: jamiejdt
ms.assetid: 11f07750-4045-4c8d-a583-7d70c9e9aa7b
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -16,13 +15,13 @@ ms.prod: w10
Use the following procedure to install the reporting server on a standalone computer and connect it to the database.
**Important**  
Before performing the following procedure you should read and understand [About App-V 5.1 Reporting](appv-reporting.md).
Before performing the following procedure you should read and understand [About App-V Reporting](appv-reporting.md).
 
**To install the reporting server on a standalone computer and connect it to the database**
1. Copy the App-V 5.1 server installation files to the computer on which you want to install it on. To start the App-V 5.1 server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
2. On the **Getting Started** page, review and accept the license terms, and click **Next**.
@ -47,7 +46,7 @@ Before performing the following procedure you should read and understand [About
- Specify the Website Name that you want to use for the Reporting Service. Leave the default unchanged if you do not have a custom name.
- For the **Port binding**, specify a unique port number that will be used by App-V 5.1, for example **55555**. You should also ensure that the port specified is not being used by another website.
- For the **Port binding**, specify a unique port number that will be used by App-V, for example **55555**. You should also ensure that the port specified is not being used by another website.
8. Click **Install**.
@ -56,11 +55,11 @@ Before performing the following procedure you should read and understand [About
## Related topics
[About App-V 5.1 Reporting](appv-reporting.md)
[About App-V Reporting](appv-reporting.md)
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
[How to Enable Reporting on the App-V 5.1 Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
 

7
windows/manage/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
View File

@ -1,8 +1,7 @@
---
title: How to Load the PowerShell Cmdlets and Get Cmdlet Help
title: How to Load the PowerShell Cmdlets and Get Cmdlet Help (Windows 10)
description: How to Load the PowerShell Cmdlets and Get Cmdlet Help
author: jamiejdt
ms.assetid: b6ae5460-2c3a-4030-b132-394d9d5a541e
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -44,7 +43,7 @@ Review the following requirements for using the App-V PowerShell cmdlets:
<td align="left"><p>Users can run App-V Server cmdlets only if you grant them access by using one of the following methods:</p></td>
<td align="left"><ul>
<li><p><strong>When you are deploying and configuring the App-V Server</strong>:</p>
<p>Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).</p></li>
<p>Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></li>
<li><p><strong>After you’ve deployed the App-V Server</strong>:</p>
<p>Use the App-V Management console to add an additional Active Directory group or user. See [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md).</p></li>
</ul></td>
@ -88,7 +87,7 @@ Review the following requirements for using the App-V PowerShell cmdlets:
<td align="left"><p>Run the <strong>Set-AppvClientConfiguration</strong> cmdlet with the <strong>-RequirePublishAsAdmin</strong> parameter.</p></td>
<td align="left"><ul>
<li><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md#bkmk-admin-only-posh-topic-cg)</p></li>
<li><p>[How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs)</p></li>
<li><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs)</p></li>
</ul></td>
</tr>
<tr class="even">

23
windows/manage/appv-maintaining-appv.md
View File

@ -1,8 +1,7 @@
---
title: Maintaining App-V 5.1
description: Maintaining App-V 5.1
title: Maintaining App-V (Windows 10)
description: Maintaining App-V
author: jamiejdt
ms.assetid: 5abd17d3-e8af-4261-b914-741ae116b0e7
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,34 +9,34 @@ ms.prod: w10
---
# Maintaining App-V 5.1
# Maintaining App-V
After you have completed all the necessary planning, and then deployment of App-V 5.1, you can use the following information to maintain the App-V 5.1 infrastructure.
After you have completed all the necessary planning, and then deployment of App-V, you can use the following information to maintain the App-V infrastructure.
## <a href="" id="move-the-app-v-5-1-server-"></a>Move the App-V 5.1 Server
## <a href="" id="move-the-app-v-5-1-server-"></a>Move the App-V Server
The App-V 5.1 server connects to the App-V 5.1 database. Therefore you can install the management component to any computer on the network and then connect it to the App-V 5.1 database.
The App-V server connects to the App-V database. Therefore you can install the management component to any computer on the network and then connect it to the App-V database.
[How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md)
## <a href="" id="determine-if-an-app-v-5-1-application-is-running-virtualized-"></a>Determine if an App-V 5.1 Application is Running Virtualized
## <a href="" id="determine-if-an-app-v-5-1-application-is-running-virtualized-"></a>Determine if an App-V Application is Running Virtualized
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V 5.1 or above, should open a named object called **AppVVirtual-&lt;PID&gt;** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V or above, should open a named object called **AppVVirtual-&lt;PID&gt;** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V 5.1 and above, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V and above, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
## Got 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/home?forum=mdopappv).
## Other resources for maintaining App-V 5.1
## Other resources for maintaining App-V
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

11
windows/manage/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell
description: How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell
title: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell (Windows 10)
description: How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
author: jamiejdt
ms.assetid: c3fd06f6-102f-43d1-a577-d5ced6ac537d
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,7 +9,7 @@ ms.prod: w10
---
# How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell:
@ -281,9 +280,9 @@ For more information about pending tasks, see [About App-V 5.0 SP2](https://tech
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 

9
windows/manage/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
title: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell (Windows 10)
description: How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
author: jamiejdt
ms.assetid: e1589eff-d306-40fb-a0ae-727190dafe26
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -29,7 +28,7 @@ This topic explains the following procedures:
**To add and publish the App-V packages in the connection group**
1. To add and publish the App-V 5.1 packages to the computer running the App-V client, type the following command:
1. To add and publish the App-V packages to the computer running the App-V client, type the following command:
Add-AppvClientPackage –path c:\\tmpstore\\quartfin.appv | Publish-AppvClientPackage
@ -133,9 +132,9 @@ This topic explains the following procedures:
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 

7
windows/manage/appv-managing-connection-groups.md
View File

@ -1,8 +1,7 @@
---
title: Managing Connection Groups
title: Managing Connection Groups (Windows 10)
description: Managing Connection Groups
author: jamiejdt
ms.assetid: 22c9d3cb-7246-4173-9742-4ba1c24b0a6a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -62,10 +61,10 @@ In some previous versions of App-V, connection groups were referred to as Dynami
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/home?forum=mdopappv).
## Other resources for App-V 5.1 connection groups
## Other resources for App-V connection groups
- [Operations for App-V 5.1](appv-operations.md)
- [Operations for App-V](appv-operations.md)
 

31
windows/manage/appv-microsoft-application-virtualization-administrators-guide.md
View File

@ -1,8 +1,7 @@
---
title: Microsoft Application Virtualization 5.1 Administrator's Guide
description: Microsoft Application Virtualization 5.1 Administrator's Guide
title: Microsoft Application Virtualization Administrator's Guide (Windows 10)
description: Microsoft Application Virtualization Administrator's Guide
author: jamiejdt
ms.assetid: 3049996a-7253-4599-a29a-1b58f9ab14a4
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,32 +9,32 @@ ms.prod: w10
---
# Microsoft Application Virtualization 5.1 Administrator's Guide
# Microsoft Application Virtualization Administrator's Guide
The Microsoft Application Virtualization (App-V) 5.1 Administrator’s Guide provides information and step-by-step procedures to help you administer the App-V 5.1 system 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.
The Microsoft Application Virtualization (App-V) Administrator’s Guide provides information and step-by-step procedures to help you administer the App-V system 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.
<a href="" id="getting-started-with-app-v-5-1"></a>[Getting Started with App-V 5.1](appv-getting-started.md)
<a href="" id="getting-started-with-app-v-5-1"></a>[Getting Started with App-V](appv-getting-started.md)
[About App-V 5.1](appv-about-appv.md)**|**[Evaluating App-V 5.1](appv-evaluating-appv.md)**|**[High Level Architecture for App-V 5.1](appv-high-level-architecture.md)**|**[Accessibility for App-V 5.1](appv-accessibility.md)
[About App-V](appv-about-appv.md)**|**[Evaluating App-V](appv-evaluating-appv.md)**|**[High Level Architecture for App-V](appv-high-level-architecture.md)**|**[Accessibility for App-V](appv-accessibility.md)
<a href="" id="planning-for-app-v-5-1"></a>[Planning for App-V 5.1](appv-planning-for-appv.md)
<a href="" id="planning-for-app-v-5-1"></a>[Planning for App-V](appv-planning-for-appv.md)
[Preparing Your Environment for App-V 5.1](appv-preparing-your-environment.md)**|**[App-V 5.1 Prerequisites](appv-prerequisites.md)**|**[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)**|**[App-V 5.1 Supported Configurations](appv-supported-configurations.md)**|**[App-V 5.1 Planning Checklist](appv-planning-checklist.md)
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)**|**[App-V Prerequisites](appv-prerequisites.md)**|**[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)**|**[App-V Supported Configurations](appv-supported-configurations.md)**|**[App-V Planning Checklist](appv-planning-checklist.md)
<a href="" id="deploying-app-v-5-1"></a>[Deploying App-V 5.1](appv-deploying-appv.md)
<a href="" id="deploying-app-v-5-1"></a>[Deploying App-V](appv-deploying-appv.md)
[Deploying the App-V 5.1 Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)**|**[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)**|**[App-V 5.1 Deployment Checklist](appv-deployment-checklist.md)**|**[Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)**|**[Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)**|**[Deploying the App-V Server](appv-deploying-the-appv-server.md)**|**[App-V Deployment Checklist](appv-deployment-checklist.md)**|**[Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md)**|**[Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
<a href="" id="operations-for-app-v-5-1"></a>[Operations for App-V 5.1](appv-operations.md)
<a href="" id="operations-for-app-v-5-1"></a>[Operations for App-V](appv-operations.md)
[Creating and Managing App-V 5.1 Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)**|**[Administering App-V 5.1 Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)**|**[Managing Connection Groups](appv-managing-connection-groups.md)**|**[Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)**|**[Using the App-V 5.1 Client Management Console](appv-using-the-client-management-console.md)**|**[Migrating to App-V 5.1 from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)**|**[Maintaining App-V 5.1](appv-maintaining-appv.md)**|**[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)**|**[Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)**|**[Managing Connection Groups](appv-managing-connection-groups.md)**|**[Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)**|**[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)
<a href="" id="troubleshooting-app-v-5-1"></a>[Troubleshooting App-V 5.1](appv-troubleshooting.md)
<a href="" id="troubleshooting-app-v-5-1"></a>[Troubleshooting App-V](appv-troubleshooting.md)
<a href="" id="technical-reference-for-app-v-5-1"></a>[Technical Reference for App-V 5.1](appv-technical-reference.md)
<a href="" id="technical-reference-for-app-v-5-1"></a>[Technical Reference for App-V](appv-technical-reference.md)
[Performance Guidance for Application Virtualization 5.1](appv-performance-guidance.md)**|**[Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)**|**[Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)**|**[Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
[Performance Guidance for Application Virtualization](appv-performance-guidance.md)**|**[Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)**|**[Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)**|**[Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
### Got a suggestion for App-V?

21
windows/manage/appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer
description: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer
title: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer (Windows 10)
description: How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer
author: jamiejdt
ms.assetid: 4ef823a5-3106-44c5-aecc-29edf69c2fbb
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,18 +9,18 @@ ms.prod: w10
---
# How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer
# How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer
Use the following procedure to migrate extension points from an App-V 4.6 package to a App-V 5.1 package using the deployment configuration file.
Use the following procedure to migrate extension points from an App-V 4.6 package to a App-V package using the deployment configuration file.
**Note**  
This procedure assumes that you are running the latest version of App-V 4.6.
The following procedure does not require an App-V 5.1 management server.
The following procedure does not require an App-V management server.
 
**To migrate extension points from a package from an App-V 4.6 package to a converted App-V 5.1 package using the deployment configuration file**
**To migrate extension points from a package from an App-V 4.6 package to a converted App-V package using the deployment configuration file**
1. Locate the directory that contains the deployment configuration file for the package you want to migrate. To set the policy, make the following update to the **userConfiguration** section:
@ -47,22 +46,22 @@ The following procedure does not require an App-V 5.1 management server.
&lt;/DeploymentConfiguration&gt;
2. To add the App-V 5.1 package, in an elevated PowerShell command prompt type:
2. To add the App-V package, in an elevated PowerShell command prompt type:
PS&gt;**$pkg= Add-AppvClientPackage** **–Path** &lt;Path to package location&gt; -**DynamicDeploymentConfiguration** &lt;Path to the deployment configuration file&gt;
PS&gt;**Publish-AppVClientPackage $pkg**
3. To test the migration, open the virtual application using associated FTAs or shortcuts. The application opens with App-V 5.1. Both, the App-V 4.6 package and the converted App-V 5.1 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.1 package.
3. To test the migration, open the virtual application using associated FTAs or shortcuts. The application opens with App-V. Both, the App-V 4.6 package and the converted App-V package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V package.
**Got 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/home?forum=mdopappv).
## Related topics
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md)
[How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md)
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

17
windows/manage/appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md
View File

@ -1,8 +1,7 @@
---
title: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User
description: How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User
title: How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User (Windows 10)
description: How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User
author: jamiejdt
ms.assetid: 19da3776-5ebe-41e1-9890-12b84ef3c1c7
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,7 +9,7 @@ ms.prod: w10
---
# How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User
# How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User
Use the following procedure to migrate packages created with App-V using the user configuration file.
@ -34,24 +33,24 @@ This procedure assumes that you are running the latest version of App-V 4.6.
&lt;/UserConfiguration&gt;
2. To add the App-V 5.1 package, type the following in an elevated PowerShell command prompt window:
2. To add the App-V package, type the following in an elevated PowerShell command prompt window:
PS&gt;**$pkg= Add-AppvClientPackage –Path** &lt;Path to package location&gt;
PS&gt;**Publish-AppVClientPackage $pkg -DynamicUserConfiguration** &lt;Path to the user configuration file&gt;
3. Open the application using FTAs or shortcuts now. The application should open using App-V 5.1.
3. Open the application using FTAs or shortcuts now. The application should open using App-V.
The App-V 4.6 package and the converted App-V 5.1 package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V 5.1 package.
The App-V 4.6 package and the converted App-V package are published to the user, but the FTAs and shortcuts for the applications have been assumed by the App-V package.
**Got 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/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md)
[How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md)
 

61
windows/manage/appv-migrating-to-appv-from-a-previous-version.md
View File

@ -1,8 +1,7 @@
---
title: Migrating to App-V 5.1 from a Previous Version
description: Migrating to App-V 5.1 from a Previous Version
title: Migrating to App-V from a Previous Version (Windows 10)
description: Migrating to App-V from a Previous Version
author: jamiejdt
ms.assetid: e7ee0edc-7544-4c0a-aaca-d922a33bc1bb
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,20 +9,20 @@ ms.prod: w10
---
# Migrating to App-V 5.1 from a Previous Version
# Migrating to App-V from a Previous Version
With Microsoft Application Virtualization (App-V) 5.1, you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V 5.1 infrastructure.
However, you cannot migrate directly from App-V 4.x to App-V 5.1, you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
With Microsoft Application Virtualization (App-V), you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V infrastructure.
However, you cannot migrate directly from App-V 4.x to App-V, you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
**Note**  
App-V 5.1 packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V 5.1 packages.
App-V packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V packages.
For more information about the differences between App-V 4.6 and App-V 5.1, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50).
For more information about the differences between App-V 4.6 and App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50).
 
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V 5.1 Package Converter
## <a href="" id="bkmk-pkgconvimprove"></a>Improvements to the App-V Package Converter
You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
@ -37,8 +36,8 @@ You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom
</colgroup>
<thead>
<tr class="header">
<th align="left">New in App-V 5.1</th>
<th align="left">Prior to App-V 5.1</th>
<th align="left">New in App-V</th>
<th align="left">Prior to App-V</th>
</tr>
</thead>
<tbody>
@ -140,7 +139,7 @@ ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
<li><p>Registry information</p></li>
<li><p>Scripts</p></li>
</ul></td>
<td align="left"><p>Each .osd file is converted to a separate, corresponding .xml file that contains the items listed here in App-V 5.1 deployment configuration format. These items can then be copied from these .xml files and placed in the deployment configuration or user configuration files as desired.</p>
<td align="left"><p>Each .osd file is converted to a separate, corresponding .xml file that contains the items listed here in App-V deployment configuration format. These items can then be copied from these .xml files and placed in the deployment configuration or user configuration files as desired.</p>
<p>In this example, there are three .xml files, corresponding with the three .osd files in the source directory. Each .xml file contains the environment variables, shortcuts, file type associations, registry information, and scripts in its corresponding .osd file.</p></td>
</tr>
<tr class="even">
@ -210,9 +209,9 @@ After you convert an existing package you should test the package prior to deplo
When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
**Note**  
It is recommended that you use the App-V 5.1 sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V 5.1](appv-sequence-a-new-application.md).
It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
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 5.1 sequencer.
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.
 
@ -240,12 +239,12 @@ The following table displays the recommended method for upgrading clients.
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
</tr>
<tr class="even">
<td align="left"><p>Install the App-V 5.1 client with co-existence enabled.</p></td>
<td align="left"><p>[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md).</p></td>
<td align="left"><p>Install the App-V client with co-existence enabled.</p></td>
<td align="left"><p>[How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Sequence and roll out App-V 5.1 packages. As needed, unpublish App-V 4.6 packages.</p></td>
<td align="left"><p>[How to Sequence a New Application with App-V 5.1](appv-sequence-a-new-application.md).</p></td>
<td align="left"><p>Sequence and roll out App-V packages. As needed, unpublish App-V 4.6 packages.</p></td>
<td align="left"><p>[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).</p></td>
</tr>
</tbody>
</table>
@ -257,10 +256,10 @@ You must be running the latest version of App-V 4.6 to use coexistence mode. Ad
 
## Migrating the App-V 5.1 Server Full Infrastructure
## Migrating the App-V Server Full Infrastructure
There is no direct method to upgrade to a full App-V 5.1 infrastructure. Use the information in the following section for information about upgrading the App-V server.
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.
<table>
<colgroup>
@ -279,12 +278,12 @@ There is no direct method to upgrade to a full App-V 5.1 infrastructure. Use the
<td align="left"><p>[Application Virtualization Deployment and Upgrade Considerations](https://technet.microsoft.com/en-us/itpro/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy).</p></td>
</tr>
<tr class="even">
<td align="left"><p>Deploy App-V 5.1 version of the client.</p></td>
<td align="left"><p>Deploy App-V version of the client.</p></td>
<td align="left"><p>[How to Deploy the App-V Client](appv-deploy-the-appv-client.md).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Install App-V 5.1 server.</p></td>
<td align="left"><p>[How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).</p></td>
<td align="left"><p>Install App-V server.</p></td>
<td align="left"><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>Migrate existing packages.</p></td>
@ -298,17 +297,17 @@ There is no direct method to upgrade to a full App-V 5.1 infrastructure. Use the
## Additional Migration tasks
You can also perform additional migration tasks such as reconfiguring end points as well as opening a package created using a prior version on a computer running the App-V 5.1 client. The following links provide more information about performing these tasks.
You can also perform additional migration tasks such as reconfiguring end points as well as opening a package created using a prior version on a computer running the App-V client. The following links provide more information about performing these tasks.
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md)
[How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md)
[How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md)
[How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md)
[How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md)
[How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md)
[How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md)
[How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User](appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md)
[How to Use an App-V 4.6 Application From an App-V 5.1 Application](appv-use-an-appv-46-sp1-application-from-an-appv-51-application.md)
[How to Use an App-V 4.6 Application From an App-V Application](appv-use-an-appv-46-sp1-application-from-an-appv-51-application.md)
## Got a suggestion for App-V?
@ -318,9 +317,9 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Other resources for performing App-V migration tasks
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[A simplified Microsoft App-V 5.1 Management Server upgrade procedure](http://go.microsoft.com/fwlink/p/?LinkId=786330)
[A simplified Microsoft App-V Management Server upgrade procedure](http://go.microsoft.com/fwlink/p/?LinkId=786330)
 

5
windows/manage/appv-modify-an-existing-virtual-application-package.md
View File

@ -1,8 +1,7 @@
---
title: How to Modify an Existing Virtual Application Package
title: How to Modify an Existing Virtual Application Package (Windows 10)
description: How to Modify an Existing Virtual Application Package
author: jamiejdt
ms.assetid: 6cdeec00-e4fe-4210-b4c7-6ca1ac643ddd
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -167,7 +166,7 @@ This topic explains how to:
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

9
windows/manage/appv-modify-client-configuration-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Modify Client Configuration by Using PowerShell
title: How to Modify Client Configuration by Using PowerShell (Windows 10)
description: How to Modify Client Configuration by Using PowerShell
author: jamiejdt
ms.assetid: c3a59592-bb0d-43b6-8f4e-44f3a2d5b7ea
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,9 +12,9 @@ ms.prod: w10
# How to Modify Client Configuration by Using PowerShell
Use the following procedure to configure the App-V 5.1 client configuration.
Use the following procedure to configure the App-V client configuration.
**To modify App-V 5.1 client configuration using PowerShell**
**To modify App-V client configuration using PowerShell**
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).
@ -32,7 +31,7 @@ Use the following procedure to configure the App-V 5.1 client configuration.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

19
windows/manage/appv-modify-client-configuration-with-the-admx-template-and-group-policy.md
View File

@ -1,8 +1,7 @@
---
title: How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy
description: How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy
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: jamiejdt
ms.assetid: 0d9cf13a-b29c-4c87-a776-15fea34027dd
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,17 +9,17 @@ ms.prod: w10
---
# How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy
# How to Modify App-V Client Configuration Using the ADMX Template and Group Policy
Use the Microsoft Application Virtualization (App-V) 5.1 ADMX template to configure App-V 5.1 client settings using the ADMX Template and Group Policy.
Use the Microsoft Application Virtualization (App-V) ADMX template to configure App-V client settings using the ADMX Template and Group Policy.
**To modify App-V 5.1 client configuration using Group Policy**
**To modify App-V client configuration using Group Policy**
1. To modify the App-V 5.1 client configuration, locate the **ADMXTemplate** files that are available with App-V 5.1.
1. To modify the App-V client configuration, locate the **ADMXTemplate** files that are available with App-V.
**Note**  
Use the following link to download the App-V 5.1 **ADMX Templates**: <http://go.microsoft.com/fwlink/p/?LinkId=393941>.
Use the following link to download the App-V **ADMX Templates**: <http://go.microsoft.com/fwlink/p/?LinkId=393941>.
 
@ -28,14 +27,14 @@ Use the Microsoft Application Virtualization (App-V) 5.1 ADMX template to config
Next, on the same computer, copy the **.adml** file to the following directory: **&lt;InstallationDrive&gt; \\ Windows \\ PolicyDefinitions \\ en-US**.
3. After you have copied the files open the Group Policy Management Console, to modify the policies associated with your App-V 5.1 clients browse to **Computer Configuration** / **Policies** / **Administrative Templates** / **System** / **App-V**.
3. After you have copied the files open the Group Policy Management Console, to modify the policies associated with your App-V clients browse to **Computer Configuration** / **Policies** / **Administrative Templates** / **System** / **App-V**.
**Got 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/home?forum=mdopappv).
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
[About Client Configuration Settings](appv-client-configuration-settings.md)

9
windows/manage/appv-move-the-appv-server-to-another-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to Move the App-V Server to Another Computer
title: How to Move the App-V Server to Another Computer (Windows 10)
description: How to Move the App-V Server to Another Computer
author: jamiejdt
ms.assetid: 853af9eb-db5b-421d-a0fe-79ded8752cef
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -20,16 +19,16 @@ Use the following information to create a new management server console in your
The following list displays the steps necessary to create a new management server console:
1. Install the management server on a computer in your environment. For more information about installing the management server see [Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md).
1. Install the management server on a computer in your environment. For more information about installing the management server see [Deploying the App-V Server](appv-deploying-the-appv-server.md).
2. After you have completed the installation, use the following link to connect it to the App-V 5.1 database - [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md).
2. After you have completed the installation, use the following link to connect it to the App-V database - [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md).
**Got 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/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

37
windows/manage/appv-operations.md
View File

@ -1,8 +1,7 @@
---
title: Operations for App-V 5.1
description: Operations for App-V 5.1
title: Operations for App-V (Windows 10)
description: Operations for App-V
author: jamiejdt
ms.assetid: dd13b5c9-2d1e-442f-91e4-43dec7f17ea2
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,19 +9,19 @@ ms.prod: w10
---
# Operations for App-V 5.1
# Operations for App-V
This section of the Microsoft Application Virtualization (App-V) 5.1 Administrator’s Guide includes information about the various types of App-V 5.1 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.
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.
## Operations Information
- [Creating and Managing App-V 5.1 Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
Describes how to create, modify, and convert virtualized packages.
- [Administering App-V 5.1 Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
Describes how to use the App-V Management console to perform tasks such as sequencing an application, changing a package, using a project template, and using a package accelerator.
@ -30,21 +29,21 @@ This section of the Microsoft Application Virtualization (App-V) 5.1 Administrat
Describes how connection groups enable virtualized applications to communicate with each other in the virtual environment; explains how to create, publish, and delete them; and describes how connection groups can help you better manage your virtualized applications.
- [Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
- [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
Describes how to deploy App-V packages by using an ESD.
- [Using the App-V 5.1 Client Management Console](appv-using-the-client-management-console.md)
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
Describes how perform client configuration tasks using the client management console.
- [Migrating to App-V 5.1 from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
Provides instructions for migrating to App-V 5.1 from a previous version.
Provides instructions for migrating to App-V from a previous version.
- [Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
- [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
Describes the set of Windows PowerShell cmdlets available for administrators performing various App-V 5.1 server tasks.
Describes the set of Windows PowerShell cmdlets available for administrators performing various App-V server tasks.
## Got a suggestion for App-V?
@ -54,17 +53,17 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Other Resources for App-V Operations
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Getting Started with App-V 5.1](appv-getting-started.md)
- [Getting Started with App-V](appv-getting-started.md)
- [Planning for App-V 5.1](appv-planning-for-appv.md)
- [Planning for App-V](appv-planning-for-appv.md)
- [Deploying App-V 5.1](appv-deploying-appv.md)
- [Deploying App-V](appv-deploying-appv.md)
- [Troubleshooting App-V 5.1](appv-troubleshooting.md)
- [Troubleshooting App-V](appv-troubleshooting.md)
- [Technical Reference for App-V 5.1](appv-technical-reference.md)
- [Technical Reference for App-V](appv-technical-reference.md)
 

43
windows/manage/appv-performance-guidance.md
View File

@ -1,8 +1,7 @@
---
title: Performance Guidance for Application Virtualization 5.1
description: Performance Guidance for Application Virtualization 5.1
title: Performance Guidance for Application Virtualization (Windows 10)
description: Performance Guidance for Application Virtualization
author: jamiejdt
ms.assetid: 5f2643c7-5cf7-4a29-adb7-45bf9f5b0364
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,16 +9,16 @@ ms.prod: w10
---
# Performance Guidance for Application Virtualization 5.1
# Performance Guidance for Application Virtualization
Learn how to configure App-V 5.1 for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
Implementing multiple methods can help you improve the end-user experience. However, your environment may not support all methods.
You should read and understand the following information before reading this document.
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [App-V 5 SP2 Application Publishing and Client Interaction](http://go.microsoft.com/fwlink/?LinkId=395206)
@ -30,14 +29,14 @@ Some terms used in this document may have different meanings depending on extern
 
Finally, this document will provide you with the information to configure the computer running App-V 5.1 client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V 5.1 in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
To help determine what information is relevant to your environment you should review each section’s brief overview and applicability checklist.
## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V 5.1 in stateful\* non-persistent deployments
## <a href="" id="---------app-v-5-1-in-stateful--non-persistent-deployments"></a> App-V in stateful\* non-persistent deployments
This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V 5.1 publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. A number of conditions must be met and steps followed to provide the optimal user experience.
This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This is achieved by uniquely addressing the often long-running App-V publishing refresh. As you will discover the basis of the approach, the fastest publishing refresh, is one that doesn’t have to actually do anything. A number of conditions must be met and steps followed to provide the optimal user experience.
Use the information in the following section for more information:
@ -172,9 +171,9 @@ The following table displays the required steps to prepare the base image and th
<tr class="odd">
<td align="left"><p></p>
<ul>
<li><p>Install the App-V 5.1 client version of the client.</p></li>
<li><p>Install the App-V client version of the client.</p></li>
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V 5.1 Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
<li><p>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).</p></li>
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
<li><p>Pre-configure all user- and global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
<li><p>Pre-configure all user- and global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
@ -192,9 +191,9 @@ The following table displays the required steps to prepare the base image and th
</ul></td>
<td align="left"><p></p>
<ul>
<li><p>Install the App-V 5.1 client version of the client.</p></li>
<li><p>Install the App-V client version of the client.</p></li>
<li><p>Install UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.</p></li>
<li><p>Configure for Shared Content Store (SCS) mode. For more information see [How to Install the App-V 5.1 Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md).</p></li>
<li><p>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).</p></li>
<li><p>Configure Preserve User Integrations on Login Registry DWORD.</p></li>
<li><p>Pre-configure all global-targeted packages for example, <strong>Add-AppvClientPackage</strong>.</p></li>
<li><p>Pre-configure all global-targeted connection groups for example, <strong>Add-AppvClientConnectionGroup</strong>.</p></li>
@ -292,7 +291,7 @@ The expectation in a stateful environment is that a UPM solution is implemented
The requirements for the UPM solution are as follows.
To enable an optimized login experience, for example the App-V 5.1 approach for the user, the solution must be capable of:
To enable an optimized login experience, for example the App-V approach for the user, the solution must be capable of:
- Persisting the below user integrations as part of the user profile/persona.
@ -309,9 +308,9 @@ To enable an optimized login experience, for example the App-V 5.1 approach for
- Capturing changes to the locations, which constitute the user integrations, prior to session logoff.
With App-V 5.1 when you add a publishing server (**Add-AppvPublishingServer**) you can configure synchronization, for example refresh during log on and/or after a specified refresh interval. In both cases a scheduled task is created.
With App-V when you add a publishing server (**Add-AppvPublishingServer**) you can configure synchronization, for example refresh during log on and/or after a specified refresh interval. In both cases a scheduled task is created.
In previous versions of App-V 5.1, both scheduled tasks were configured using a VBScript that would initiate the user and global refresh. With Hotfix Package 4 for Application Virtualization 5.0 SP2 the user refresh on log on was initiated by **SyncAppvPublishingServer.exe**. This change was introduced to provide UPM solutions a trigger process. This process delays the publish /refresh to allow the UPM solution to apply the user integrations. It will exit once the publishing/refresh is complete.
In previous versions of App-V, both scheduled tasks were configured using a VBScript that would initiate the user and global refresh. With Hotfix Package 4 for Application Virtualization 5.0 SP2 the user refresh on log on was initiated by **SyncAppvPublishingServer.exe**. This change was introduced to provide UPM solutions a trigger process. This process delays the publish /refresh to allow the UPM solution to apply the user integrations. It will exit once the publishing/refresh is complete.
**User Integrations**
@ -613,7 +612,7 @@ When publishing a virtual application package, the App-V Client will detect if a
<tbody>
<tr class="odd">
<td align="left"><p>Selectively Employ Dynamic Configuration files</p></td>
<td align="left"><p>The App-V 5.1 client must parse and process these Dynamic Configuration files.</p>
<td align="left"><p>The App-V client must parse and process these Dynamic Configuration files.</p>
<p>Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.</p>
<p>Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.</p></td>
<td align="left"><p>Publishing times will improve if these files are used selectively or not at all.</p></td>
@ -709,10 +708,10 @@ Fonts
&lt;!--
## <a href="" id="bkmk-terms1"></a> App-V 5.1 Performance Guidance Terminology
## <a href="" id="bkmk-terms1"></a> App-V Performance Guidance Terminology
The following terms are used when describing concepts and actions related to App-V 5.1 performance optimization.
The following terms are used when describing concepts and actions related to App-V performance optimization.
- **Complexity** – Refers to the one or more package characteristics that may impact performance during pre-configure (**Add-AppvClientPackage**) or integration (**Publish-AppvClientPackage**). Some example characteristics are: manifest size, number of virtual fonts, number of files.
@ -730,11 +729,11 @@ The following terms are used when describing concepts and actions related to App
- **Trigger** – (or Native Action Triggers). UPM uses these types of triggers to initiate monitoring or synchronization operations.
- **User Experience** - In the context of App-V 5.1, the user experience, quantitatively, is the sum of the following parts:
- **User Experience** - In the context of App-V, the user experience, quantitatively, is the sum of the following parts:
- From the point that users initiate a log-in to when they are able to manipulate the desktop.
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in PowerShell terms, sync) when using the App-V 5.1 full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage Powershell** commands are initiated.
- From the point where the desktop can be interacted with to the point a publishing refresh begins (in PowerShell terms, sync) when using the App-V full server infrastructure. In standalone instances, it is when the **Add-AppVClientPackage** and **Publish-AppVClientPackage Powershell** commands are initiated.
- From start to completion of the publishing refresh. In standalone instances, this is the first to last virtual application published.
@ -750,7 +749,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
[Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
 

33
windows/manage/appv-planning-checklist.md
View File

@ -1,8 +1,7 @@
---
title: App-V 5.1 Planning Checklist
description: App-V 5.1 Planning Checklist
title: App-V Planning Checklist (Windows 10)
description: App-V Planning Checklist
author: jamiejdt
ms.assetid: 1e26a861-0612-43a6-972f-375a40a8dcbc
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,13 +9,13 @@ ms.prod: w10
---
# App-V 5.1 Planning Checklist
# App-V Planning Checklist
This checklist can be used to help you plan for preparing your computing environment for Microsoft Application Virtualization (App-V) 5.1 deployment.
This checklist can be used to help you plan for preparing your computing environment for Microsoft Application Virtualization (App-V) deployment.
**Note**  
This checklist outlines the recommended steps and a high-level list of items to consider when planning for an App-V 5.1 deployment. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
This checklist outlines the recommended steps and a high-level list of items to consider when planning for an App-V deployment. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
 
@ -38,26 +37,26 @@ This checklist outlines the recommended steps and a high-level list of items to
<tbody>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Review the getting started information about App-V 5.1 to gain a basic understanding of the product before beginning deployment planning.</p></td>
<td align="left"><p>[Getting Started with App-V 5.1](appv-getting-started.md)</p></td>
<td align="left"><p>Review the getting started information about App-V to gain a basic understanding of the product before beginning deployment planning.</p></td>
<td align="left"><p>[Getting Started with App-V](appv-getting-started.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Plan for App-V 5.1 1.0 Deployment Prerequisites and prepare your computing environment.</p></td>
<td align="left"><p>[App-V 5.1 Prerequisites](appv-prerequisites.md)</p></td>
<td align="left"><p>Plan for App-V 1.0 Deployment Prerequisites and prepare your computing environment.</p></td>
<td align="left"><p>[App-V Prerequisites](appv-prerequisites.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>If you plan to use the App-V 5.1 management server, plan for the required roles.</p></td>
<td align="left"><p>[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)</p></td>
<td align="left"><p>If you plan to use the App-V management server, plan for the required roles.</p></td>
<td align="left"><p>[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Plan for the App-V 5.1 sequencer and client so you to create and run virtualized applications.</p></td>
<td align="left"><p>[Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)</p></td>
<td align="left"><p>Plan for the App-V sequencer and client so you to create and run virtualized applications.</p></td>
<td align="left"><p>[Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
@ -68,8 +67,8 @@ This checklist outlines the recommended steps and a high-level list of items to
</tr>
<tr class="even">
<td align="left"><img src="images/checklistbox.gif" alt="Checklist box" /></td>
<td align="left"><p>Plan for running App-V 5.1 clients using in shared content store mode.</p></td>
<td align="left"><p>[How to Install the App-V 5.1 Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)</p></td>
<td align="left"><p>Plan for running App-V clients using in shared content store mode.</p></td>
<td align="left"><p>[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)</p></td>
<td align="left"><p></p></td>
</tr>
</tbody>
@ -85,7 +84,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Planning for App-V 5.1](appv-planning-for-appv.md)
[Planning for App-V](appv-planning-for-appv.md)
 

37
windows/manage/appv-planning-for-appv-server-deployment.md
View File

@ -1,8 +1,7 @@
---
title: Planning for the App-V 5.1 Server Deployment
description: Planning for the App-V 5.1 Server Deployment
title: Planning for the App-V Server Deployment (Windows 10)
description: Planning for the App-V Server Deployment
author: jamiejdt
ms.assetid: eedd97c9-bee0-4749-9d1e-ab9528fba398
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,42 +9,42 @@ ms.prod: w10
---
# Planning for the App-V 5.1 Server Deployment
# Planning for the App-V Server Deployment
The Microsoft Application Virtualization (App-V) 5.1 server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
## Planning for App-V 5.1 Server Deployment
## Planning for App-V Server Deployment
The App-V 5.1 server consists of the following features:
The App-V server consists of the following features:
- Management Server – provides overall management functionality for the App-V 5.1 infrastructure.
- Management Server – provides overall management functionality for the App-V infrastructure.
- Management Database – facilitates database predeployments for App-V 5.1 management.
- Management Database – facilitates database predeployments for App-V management.
- Publishing Server – provides hosting and streaming functionality for virtual applications.
- Reporting Server – provides App-V 5.1 reporting services.
- Reporting Server – provides App-V reporting services.
- Reporting Database – facilitates database predeployments for App-V 5.1 reporting.
- Reporting Database – facilitates database predeployments for App-V reporting.
The following list displays the recommended methods for installing the App-V 5.1 server infrastructure:
The following list displays the recommended methods for installing the App-V server infrastructure:
- Install the App-V 5.1 server. For more information, see [How to Deploy the App-V 5.1 Server](appv-deploy-the-appv-server.md).
- Install the App-V server. For more information, see [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).
- Install the database, reporting, and management features on separate computers. For more information, see [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md).
- Use Electronic Software Distribution (ESD). For more information, see [How to deploy App-V 5.1 Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
- Use Electronic Software Distribution (ESD). For more information, see [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
- Install all server features on a single computer.
## <a href="" id="---------app-v-5-1-server-interaction"></a> App-V 5.1 Server Interaction
## <a href="" id="---------app-v-5-1-server-interaction"></a> App-V Server Interaction
This section contains information about how the various App-V 5.1 server roles interact with each other.
This section contains information about how the various App-V server roles interact with each other.
The App-V 5.1 Management Server contains the repository of packages and their assigned configurations. For Publishing Servers that are registered with the Management Server, the associated metadata is provided to the Publishing servers for use when publishing refresh requests are received from computers running the App-V 5.1 Client. App-V 5.1 publishing servers managed by a single management server can be serving different clients and can have different website names and port bindings. Additionally, all Publishing Servers managed by the same Management Server are replicas of each other.
The App-V Management Server contains the repository of packages and their assigned configurations. For Publishing Servers that are registered with the Management Server, the associated metadata is provided to the Publishing servers for use when publishing refresh requests are received from computers running the App-V Client. App-V publishing servers managed by a single management server can be serving different clients and can have different website names and port bindings. Additionally, all Publishing Servers managed by the same Management Server are replicas of each other.
**Note**  
The Management Server does not perform any load balancing. The associated metadata is simply passed to the publishing server for use when processing client requests.
@ -55,7 +54,7 @@ The Management Server does not perform any load balancing. The associated metada
## Server-Related Protocols and External Features
The following displays information about server-related protocols used by the App-V 5.1 servers. The table also includes the reporting mechanism for each server type.
The following displays information about server-related protocols used by the App-V servers. The table also includes the reporting mechanism for each server type.
<table>
<colgroup>
@ -105,7 +104,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
 

33
windows/manage/appv-planning-for-appv.md
View File

@ -1,8 +1,7 @@
---
title: Planning for App-V 5.1
description: Planning for App-V 5.1
title: Planning for App-V (Windows 10)
description: Planning for App-V
author: jamiejdt
ms.assetid: 8d84e679-0bd3-4864-976b-a3cbe6eafba6
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,45 +9,45 @@ ms.prod: w10
---
# Planning for App-V 5.1
# Planning for App-V
Use this information to plan how to deploy Microsoft Application Virtualization (App-V) 5.1 so that it does not disrupt your users or the network.
Use this information to plan how to deploy Microsoft Application Virtualization (App-V) so that it does not disrupt your users or the network.
## Planning information
- [Preparing Your Environment for App-V 5.1](appv-preparing-your-environment.md)
- [Preparing Your Environment for App-V](appv-preparing-your-environment.md)
This section describes the computing environment requirements and installation prerequisites that should be planned for before beginning App-V 5.1 setup.
This section describes the computing environment requirements and installation prerequisites that should be planned for before beginning App-V setup.
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
This section describes the minimum hardware and software requirements necessary for App-V 5.1 client, sequencer and server feature installations. Additionally, associated feature planning information is also displayed.
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.
- [App-V 5.1 Planning Checklist](appv-planning-checklist.md)
- [App-V Planning Checklist](appv-planning-checklist.md)
Planning checklist that can be used to assist in App-V 5.1 deployment planning.
Planning checklist that can be used to assist in App-V deployment planning.
## Got 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/home?forum=mdopappv).
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other resources for App-V 5.1 Planning
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other resources for App-V Planning
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Getting Started with App-V 5.1](appv-getting-started.md)
- [Getting Started with App-V](appv-getting-started.md)
- [Deploying App-V 5.1](appv-deploying-appv.md)
- [Deploying App-V](appv-deploying-appv.md)
- [Operations for App-V 5.1](appv-operations.md)
- [Operations for App-V](appv-operations.md)
- [Troubleshooting App-V 5.1](appv-troubleshooting.md)
- [Troubleshooting App-V](appv-troubleshooting.md)
- [Technical Reference for App-V 5.1](appv-technical-reference.md)
- [Technical Reference for App-V](appv-technical-reference.md)
 

20
windows/manage/appv-planning-for-high-availability-with-appv.md
View File

@ -1,6 +1,6 @@
---
title: Planning for High Availability with App-V 5.1 Server
description: Planning for High Availability with App-V 5.1 Server
title: Planning for High Availability with App-V Server (Windows 10)
description: Planning for High Availability with App-V Server
author: jamiejdt
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
@ -9,11 +9,11 @@ ms.prod: w10
---
# Planning for High Availability with App-V 5.1 Server
# Planning for High Availability with App-V Server
Microsoft Application Virtualization (App-V) 5.1 system configurations can take advantage of options that maintain a high level of available service.
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 5.1 in a highly available configuration.
Use the information in the following sections to help you understand the options to deploy App-V in a highly available configuration.
- [Support for Microsoft SQL Server clustering](#bkmk-sqlcluster)
@ -35,7 +35,7 @@ For instructions, see [How to Deploy the App-V Databases by Using SQL Scripts](a
## <a href="" id="bkmk-iisloadbal"></a>Support for IIS Network Load Balancing
You can use Internet Information Services (IIS) Network Load Balancing to configure a highly available environment for computers running the App-V 5.x Management, Publishing, and Reporting services which are deployed through IIS.
You can use Internet Information Services (IIS) Network Load Balancing to configure a highly available environment for computers running the App-V Management, Publishing, and Reporting services which are deployed through IIS.
Review the following for more information about configuring IIS and Network Load Balancing for computers running Windows Server operating systems:
@ -54,7 +54,7 @@ Review the following for more information about configuring IIS and Network Load
## <a href="" id="bkmk-clusterscsmode"></a>Support for clustered file servers when running SCS mode
Running App-V 5.1 Server in Share Content Store (SCS) mode with clustered file servers is supported.
Running App-V Server in Share Content Store (SCS) mode with clustered file servers is supported.
The following steps can be used to enable this configuration:
@ -78,7 +78,7 @@ Review the following for more information about configuring Windows Server Failo
## <a href="" id="bkmk-sqlmirroring"></a>Support for Microsoft SQL Server Mirroring
Using Microsoft SQL Server mirroring, where the App-V 5.1 management server database is mirrored utilizing two SQL Server instances, for App-V 5.1 management server databases is supported.
Using Microsoft SQL Server mirroring, where the App-V management server database is mirrored utilizing two SQL Server instances, for App-V management server databases is supported.
Review the following for more information about configuring Microsoft SQL Server Mirroring:
@ -92,7 +92,7 @@ The following steps can be used to validate the configuration:
2. Select **Failover** to designate a new master Microsoft SQL Server instance.
3. Verify that the App-V 5.1 management server continues to function as expected after the failover.
3. Verify that the App-V management server continues to function as expected after the failover.
The connection string on the management server can be modified to include **failover partner = &lt;server2&gt;**. This will only help when the primary on the mirror has failed over to the secondary and the computer running the App-V client is doing a fresh connection (say after reboot).
@ -123,7 +123,7 @@ Click any of the following links for more information:
## <a href="" id="bkmk-sqlalwayson"></a>Support for Microsoft SQL Server Always On configuration
The App-V 5.1 management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://technet.microsoft.com/library/hh510230.aspx).
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://technet.microsoft.com/library/hh510230.aspx).
## Have a suggestion for App-V?

41
windows/manage/appv-planning-for-migrating-from-a-previous-version-of-appv.md
View File

@ -1,8 +1,7 @@
---
title: Planning for Migrating from a Previous Version of App-V
title: Planning for Migrating from a Previous Version of App-V (Windows 10)
description: Planning for Migrating from a Previous Version of App-V
author: jamiejdt
ms.assetid: 4a058047-9674-41bc-8050-c58c97a80a9b
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,29 +12,29 @@ ms.prod: w10
# Planning for Migrating from a Previous Version of App-V
Use the following information to plan how to migrate to Microsoft Application Virtualization (App-V) 5.1 from previous versions of App-V.
Use the following information to plan how to migrate to Microsoft Application Virtualization (App-V) from previous versions of App-V.
## Migration requirements
Before you start any upgrades, review the following requirements:
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V 5.1 or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
- If you are upgrading from a version earlier than 4.6 SP2, upgrade to version 4.6 SP2 or version 4.6 SP3 first before upgrading to App-V or later. In this scenario, upgrade the App-V clients first, and then upgrade the server components.
- App-V 5.1 supports only packages that are created using App-V 5.0 or App-V 5.1, or packages that have been converted to the **.appv** format.
- App-V supports only packages that are created using App-V 5.0 or App-V, or packages that have been converted to the **.appv** format.
- If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V 5.1](appv-about-appv.md#bkmk-migrate-to-51) for instructions.
- If you are upgrading the App-V Server from App-V 5.0 SP1, see [About App-V](appv-about-appv.md#bkmk-migrate-to-51) for instructions.
## Running the App-V 5.1 client concurrently with App-V 4.6 SP2 or later
## Running the App-V client concurrently with App-V 4.6 SP2 or later
You can run the App-V 5.1 client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
You can run the App-V client concurrently on the same computer with the App-V 4.6 SP2 client or App-V 4.6 SP3 client.
When you run coexisting App-V clients, you can:
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V 5.1 format and publish both packages, when you have both clients running.
- Convert an App-V 4.6 SP2 or 4.6 SP3 package to the App-V format and publish both packages, when you have both clients running.
- Define the migration policy for the converted package, which allows the converted App-V 5.1 package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
- Define the migration policy for the converted package, which allows the converted App-V package to assume the file type associations and shortcuts from the App-V 4.6 SP2 package.
### Supported coexistence scenarios
@ -49,25 +48,25 @@ The following table shows the supported App-V coexistence scenarios. We recommen
<thead>
<tr class="header">
<th align="left">App-V 4.6.x client type</th>
<th align="left">App-V 5.1 client type</th>
<th align="left">App-V client type</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V 4.6 SP2</p></td>
<td align="left"><p>App-V 5.1</p></td>
<td align="left"><p>App-V</p></td>
</tr>
<tr class="even">
<td align="left"><p>App-V 4.6 SP2 RDS</p></td>
<td align="left"><p>App-V 5.1 RDS</p></td>
<td align="left"><p>App-V RDS</p></td>
</tr>
<tr class="odd">
<td align="left"><p>App-V 4.6 SP3</p></td>
<td align="left"><p>App-V 5.1</p></td>
<td align="left"><p>App-V</p></td>
</tr>
<tr class="even">
<td align="left"><p>App-V 4.6 SP3 RDS</p></td>
<td align="left"><p>App-V 5.1 RDS</p></td>
<td align="left"><p>App-V RDS</p></td>
</tr>
</tbody>
</table>
@ -78,12 +77,12 @@ The following table shows the supported App-V coexistence scenarios. We recommen
To run coexisting clients, you must:
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V 5.1 client.
- Install the App-V 4.6 SP2 or App-V 4.6 SP3 client before you install the App-V client.
- Enable the **Enable Migration Mode** Group Policy setting, which is in the **App-V** &gt; **Client Coexistence** node. To deploy the .admx template, see [How to Download and Deploy MDOP Group Policy (.admx) Templates](http://technet.microsoft.com/library/dn659707.aspx).
**Note**  
App-V 5.1 packages can run side by side with App-V 4.X packages if you have coexisting installations of App-V 5.1 and 4.X. However, App-V 5.1 packages cannot interact with App-V 4.X packages in the same virtual environment.
App-V packages can run side by side with App-V 4.X packages if you have coexisting installations of App-V and 4.X. However, App-V packages cannot interact with App-V 4.X packages in the same virtual environment.
 
@ -120,22 +119,22 @@ The following table provides links to the App-V 4.6.x client downloads and to th
 
For more information about how to configure App-V 5.1 client coexistence, see:
For more information about how to configure App-V client coexistence, see:
- [How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
- [How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
- [App-V 5.0 Coexistence and Migration](http://technet.microsoft.com/windows/jj835811.aspx)
## <a href="" id="converting--previous-version--packages-using-the-package-converter-"></a>Converting “previous-version” packages using the package converter
Before migrating a package, created using App- 4.6 SP2 or earlier, to App-V 5.1, review the following requirements:
Before migrating a package, created using App- 4.6 SP2 or earlier, to App-V, review the following requirements:
- You must convert the package to the **.appv** file format.
- The Package Converter supports only the direct conversion of packages that were created by using App-V 4.5 and later. To use the package converter on a package that was created using a previous version, you must use an App-V 4.5 or later version of the sequencer to upgrade the package, and then you can perform the package conversion.
For more information about using the package converter to convert a package, see [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). After you convert the file, you can deploy it to target computers that run the App-V 5.1 client.
For more information about using the package converter to convert a package, see [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). After you convert the file, you can deploy it to target computers that run the App-V client.
## Got a suggestion for App-V?

45
windows/manage/appv-planning-for-sequencer-and-client-deployment.md
View File

@ -1,8 +1,7 @@
---
title: Planning for the App-V 5.1 Sequencer and Client Deployment
description: Planning for the App-V 5.1 Sequencer and Client Deployment
title: Planning for the App-V Sequencer and Client Deployment (Windows 10)
description: Planning for the App-V Sequencer and Client Deployment
author: jamiejdt
ms.assetid: d92f8773-fa7d-4926-978a-433978f91202
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,22 +9,22 @@ ms.prod: w10
---
# Planning for the App-V 5.1 Sequencer and Client Deployment
# Planning for the App-V Sequencer and Client Deployment
Before you can start to use Microsoft Application Virtualization (App-V) 5.1, you must install the App-V 5.1 sequencer, the App-V 5.1 client, and optionally the App-V 5.1 shared content store. The following sections address planning for these installations.
Before you can start to use Microsoft Application Virtualization (App-V), you must install the App-V sequencer, the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
## Planning for App-V 5.1 sequencer deployment
## Planning for App-V sequencer deployment
App-V 5.1 uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V 5.1 sequencer.
App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V sequencer.
**Note**  
For information about the new functionality of App-V 5.1 sequencer, see the **Sequencer Improvements** section of [About App-V 5.1](appv-about-appv.md).
For information about the new functionality of App-V sequencer, see the **Sequencer Improvements** section of [About App-V](appv-about-appv.md).
 
The computer that runs the App-V 5.1 sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
The computer that runs the App-V sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V Supported Configurations](appv-supported-configurations.md).
Ideally, you should install the sequencer on a computer running as a virtual machine. This enables you to more easily revert the computer running the sequencer to a “clean” state before sequencing another application. When you install the sequencer using a virtual machine, you should perform the following steps:
@ -40,34 +39,34 @@ You should have your corporate security team review and approve the sequencing p
 
## Planning for App-V 5.1 client deployment
## Planning for App-V client deployment
To run virtualized packages on target computers, you must install the App-V 5.1 client on the target computers. The App-V 5.1 client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and specific file types to start virtualized applications. The client also helps obtain application content from the management server and caches the content before the client starts the application. There are two different client types: the client for Remote Desktop Services, which is used on Remote Desktop Session Host (RD Session Host) server systems and the App-V 5.1 client, which is used for all other computers.
To run virtualized packages on target computers, you must install the App-V client on the target computers. The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and specific file types to start virtualized applications. The client also helps obtain application content from the management server and caches the content before the client starts the application. There are two different client types: the client for Remote Desktop Services, which is used on Remote Desktop Session Host (RD Session Host) server systems and the App-V client, which is used for all other computers.
The App-V 5.1 client should be configured by using either the installer command line or by using a PowerShell script after the installation has been completed.
The App-V client should be configured by using either the installer command line or by using a PowerShell script after the installation has been completed.
The settings must be defined carefully in advance in order to expedite the deployment of the App-V 5.1 client software. This is especially important when you have computers in different offices where the clients must be configured to use different source locations.
The settings must be defined carefully in advance in order to expedite the deployment of the App-V client software. This is especially important when you have computers in different offices where the clients must be configured to use different source locations.
You must also determine how you will deploy the client software. Although it is possible to deploy the client manually on each computer, most organizations prefer to deploy the client through an automated process. A larger organization might have an operational Electronic Software Distribution (ESD) system, which is an ideal client deployment system. If no ESD system exists, you can use your organization’s standard method of installing software. Possible methods include Group Policy or various scripting techniques. Depending on the quantity and disparate locations of your client computers, this deployment process can be complex. You must use a structured approach to ensure that all computers get the client installed with the correct configuration.
For a list of the client minimum requirements see [App-V 5.1 Prerequisites](appv-prerequisites.md).
For a list of the client minimum requirements see [App-V Prerequisites](appv-prerequisites.md).
## <a href="" id="bkmk-client-coexist"></a>Planning for App-V client coexistence
You can deploy the App-V 5.1 client side by side with the App-V 4.6 client. Client coexistence requires that you add or publish virtualized applications by using either a deployment configuration file or a user configuration file, because there are certain settings in these configuration files that must be configured in order for App-V 5.1 to function with App-V 4.6 clients. When a package is upgraded by using either the client or the server, the package must resubmit the configuration file. This is true for any package that has a corresponding configuration file, so it is not specific to client coexistence. However, if you do not submit the configuration file during the package upgrade, then the package state will not function as expected in coexistence scenarios.
You can deploy the App-V client side by side with the App-V 4.6 client. Client coexistence requires that you add or publish virtualized applications by using either a deployment configuration file or a user configuration file, because there are certain settings in these configuration files that must be configured in order for App-V to function with App-V 4.6 clients. When a package is upgraded by using either the client or the server, the package must resubmit the configuration file. This is true for any package that has a corresponding configuration file, so it is not specific to client coexistence. However, if you do not submit the configuration file during the package upgrade, then the package state will not function as expected in coexistence scenarios.
App-V 5.1 dynamic configuration files customize a package for a specific user. You must create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use them. To create the file it requires an advanced manual operation.
App-V dynamic configuration files customize a package for a specific user. You must create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use them. To create the file it requires an advanced manual operation.
When a dynamic user configuration file is used, none of the App-V 5.1 information for the extension in the manifest file is used. This means that the dynamic user configuration file must include everything for the extension that is specific to App-V 5.1 in the manifest file, as well as the changes that you want to make, such as, deletions and updates. For more information about how to create a custom configuration file, see [How to Create a Custom Configuration File by Using the App-V 5.1 Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md).
When a dynamic user configuration file is used, none of the App-V information for the extension in the manifest file is used. This means that the dynamic user configuration file must include everything for the extension that is specific to App-V in the manifest file, as well as the changes that you want to make, such as, deletions and updates. For more information about how to create a custom configuration file, see [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md).
## <a href="" id="bkmk-plan-for-scs"></a>Planning for the App-V 5.1 Shared Content Store (SCS)
## <a href="" id="bkmk-plan-for-scs"></a>Planning for the App-V Shared Content Store (SCS)
The App-V 5.1 shared content store mode allows the computer running the App-V 5.1 client to run virtualized applications and none of the package contents is saved on the computer running the App-V 5.1 client. Virtual applications are streamed to target computers only when requested by the client.
The App-V shared content store mode allows the computer running the App-V client to run virtualized applications and none of the package contents is saved on the computer running the App-V client. Virtual applications are streamed to target computers only when requested by the client.
The following list displays some of the benefits of using the App-V 5.1 shared content store:
The following list displays some of the benefits of using the App-V shared content store:
- Reduced app-to-app and multi-user application conflicts and hence a reduced need for regression testing
@ -80,7 +79,7 @@ The following list displays some of the benefits of using the App-V 5.1 shared c
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/home?forum=mdopappv).
## <a href="" id="other-resources-for-the-app-v-5-1-deployment-"></a>Other resources for the App-V 5.1 deployment
## <a href="" id="other-resources-for-the-app-v-5-1-deployment-"></a>Other resources for the App-V deployment
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
@ -92,9 +91,9 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
[How to Deploy the App-V Client](appv-deploy-the-appv-client.md)
[How to Deploy the App-V 4.6.x and the App-V 5.1 Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
[How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
[How to Install the App-V 5.1 Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
 

7
windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
View File

@ -1,8 +1,7 @@
---
title: Planning to Deploy App-V 5.1 with an Electronic Software Distribution System
description: Planning to Deploy App-V 5.1 with an Electronic Software Distribution System
title: Planning to Deploy App-V with an Electronic Software Distribution System (Windows 10)
description: Planning to Deploy App-V with an Electronic Software Distribution System
author: jamiejdt
ms.assetid: c26602c2-5e8d-44e6-90df-adacc593607e
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,7 +9,7 @@ ms.prod: w10
---
# Planning to Deploy App-V 5.1 with an Electronic Software Distribution System
# Planning to Deploy App-V with an Electronic Software Distribution System
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](http://go.microsoft.com/fwlink/?LinkId=281816).

41
windows/manage/appv-planning-to-deploy-appv.md
View File

@ -1,8 +1,7 @@
---
title: Planning to Deploy App-V
title: Planning to Deploy App-V (Windows 10)
description: Planning to Deploy App-V
author: jamiejdt
ms.assetid: 39cbf981-d9c6-457f-b047-f9046e1a6442
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,49 +12,49 @@ ms.prod: w10
# Planning to Deploy App-V
You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for Microsoft Application Virtualization (App-V) 5.1. 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.
You should consider a number of different deployment configurations and prerequisites 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.
## <a href="" id="---------app-v-5-1-supported-configurations"></a> App-V 5.1 supported configurations
## <a href="" id="---------app-v-5-1-supported-configurations"></a> App-V supported configurations
Describes the minimum hardware and operating system requirements for each App-V components. For information about software prerequisites that you must install before you install App-V, see [App-V 5.1 Prerequisites](appv-prerequisites.md).
Describes the minimum hardware and operating system requirements for each App-V components. For information about software prerequisites that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
[App-V 5.1 Supported Configurations](appv-supported-configurations.md)
[App-V Supported Configurations](appv-supported-configurations.md)
## App-V 5.1 capacity planning
## App-V capacity planning
Describes the available options for scaling your App-V 5.1 deployment.
Describes the available options for scaling your App-V deployment.
[App-V 5.1 Capacity Planning](appv-capacity-planning.md)
[App-V Capacity Planning](appv-capacity-planning.md)
## Planning for high availability with App-V 5.1
## Planning for high availability with App-V
Describes the available options for ensuring high availability of App-V 5.1 databases and services.
Describes the available options for ensuring high availability of App-V databases and services.
[Planning for High Availability with App-V 5.1](appv-planning-for-high-availability-with-appv.md)
[Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
## Planning to Deploy App-V 5.1 with an Electronic Software Distribution System
## Planning to Deploy App-V with an Electronic Software Distribution System
Describes the options and requirements for deploying App-V with an electronic software distribution system.
[Planning to Deploy App-V 5.1 with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
[Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
## Planning for the App-V 5.1 Server deployment
## Planning for the App-V Server deployment
Describes the planning considerations for the App-V Server components and their functions.
[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)
[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
## Planning for the App-V 5.1 Sequencer and Client deployment
## Planning for the App-V Sequencer and Client deployment
Describes the planning considerations for the App-V Client and for the Sequencer software, which you use to create virtual applications and application packages.
[Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
[Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
## Planning for migrating from a previous version of App-V
@ -78,12 +77,12 @@ Explains how folder redirection works with App-V.
[Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md)
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other Resources for App-V 5.1 Planning
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other Resources for App-V Planning
- [Planning for App-V 5.1](appv-planning-for-appv.md)
- [Planning for App-V](appv-planning-for-appv.md)
- [Performance Guidance for Application Virtualization 5.1](appv-performance-guidance.md)
- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
 

23
windows/manage/appv-preparing-your-environment.md
View File

@ -1,8 +1,7 @@
---
title: Preparing Your Environment for App-V 5.1
description: Preparing Your Environment for App-V 5.1
title: Preparing Your Environment for App-V (Windows 10)
description: Preparing Your Environment for App-V
author: jamiejdt
ms.assetid: 64b2e1ac-1561-4c99-9815-b4688a0ff48a
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,22 +9,22 @@ ms.prod: w10
---
# Preparing Your Environment for App-V 5.1
# Preparing Your Environment for App-V
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) 5.1. 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.
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 5.1 prerequisites
## App-V prerequisites
- [App-V 5.1 Prerequisites](appv-prerequisites.md)
- [App-V Prerequisites](appv-prerequisites.md)
Lists the prerequisite software that you must install before installing App-V 5.1.
Lists the prerequisite software that you must install before installing App-V.
## App-V 5.1 security considerations
## App-V security considerations
- [App-V 5.1 Security Considerations](appv-security-considerations.md)
- [App-V Security Considerations](appv-security-considerations.md)
Describes accounts, groups, log files, and other considerations for securing your App-V environment.
@ -34,10 +33,10 @@ There are a number of different deployment configurations and prerequisites that
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/home?forum=mdopappv).
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other resources for App-V 5.1 Planning
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other resources for App-V Planning
- [Planning for App-V 5.1](appv-planning-for-appv.md)
- [Planning for App-V](appv-planning-for-appv.md)
 

29
windows/manage/appv-prerequisites.md
View File

@ -1,8 +1,7 @@
---
title: App-V 5.1 Prerequisites
description: App-V 5.1 Prerequisites
title: App-V Prerequisites (Windows 10)
description: App-V Prerequisites
author: jamiejdt
ms.assetid: 1bfa03c1-a4ae-45ec-8a2b-b10c2b94bfb0
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,12 +9,12 @@ ms.prod: w10
---
# App-V 5.1 Prerequisites
# App-V Prerequisites
Before installing Microsoft Application Virtualization (App-V) 5.1, ensure that you have installed all of the following required prerequisite software.
Before installing Microsoft Application Virtualization (App-V), ensure that you have installed all of the following required prerequisite software.
For a list of supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
For a list of supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client, see [App-V Supported Configurations](appv-supported-configurations.md).
## Summary of software preinstalled on each operating system
@ -43,7 +42,7 @@ The following table indicates the software that is already installed for differe
<td align="left"><p>All of the prerequisite software is already installed.</p>
<div class="alert">
<strong>Note</strong>  
<p>If you are running Windows 8, upgrade to Windows 8.1 before using App-V 5.1.</p>
<p>If you are running Windows 8, upgrade to Windows 8.1 before using App-V.</p>
</div>
<div>
 
@ -76,7 +75,7 @@ The following table indicates the software that is already installed for differe
## App-V Server prerequisite software
Install the required prerequisite software for the App-V 5.1 Server components.
Install the required prerequisite software for the App-V Server components.
### What to know before you start
@ -141,7 +140,7 @@ Install the required prerequisite software for the App-V 5.1 Server components.
<tbody>
<tr class="odd">
<td align="left"><p>Supported version of SQL Server</p></td>
<td align="left"><p>For supported versions, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).</p></td>
<td align="left"><p>For supported versions, see [App-V Supported Configurations](appv-supported-configurations.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
@ -227,7 +226,7 @@ JavaScript must be enabled on the browser that opens the Web Management Console.
### Management server database prerequisite software
The Management database is required only if you are using the App-V 5.1 Management server.
The Management database is required only if you are using the App-V Management server.
<table>
<colgroup>
@ -402,7 +401,7 @@ The Management database is required only if you are using the App-V 5.1 Manageme
<tbody>
<tr class="odd">
<td align="left"><p>Supported version of SQL Server</p></td>
<td align="left"><p>For supported versions, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).</p></td>
<td align="left"><p>For supported versions, see [App-V Supported Configurations](appv-supported-configurations.md).</p></td>
</tr>
<tr class="even">
<td align="left"><p>[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773)</p></td>
@ -468,7 +467,7 @@ The Management database is required only if you are using the App-V 5.1 Manageme
### Reporting database prerequisite software
The Reporting database is required only if you are using the App-V 5.1 Reporting server.
The Reporting database is required only if you are using the App-V Reporting server.
<table>
<colgroup>
@ -609,7 +608,7 @@ Install the following prerequisite software for the App-V Remote Desktop Service
- Best practice: The computer that runs the Sequencer should have the same hardware and software configurations as the computers that will run the virtual applications.
- The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Sequencer. For more information, see [App-V 5.1 Supported Configurations](appv-supported-configurations.md).
- The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Sequencer. For more information, see [App-V Supported Configurations](appv-supported-configurations.md).
<table>
<colgroup>
@ -649,9 +648,9 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Planning for App-V 5.1](appv-planning-for-appv.md)
[Planning for App-V](appv-planning-for-appv.md)
[App-V 5.1 Supported Configurations](appv-supported-configurations.md)
[App-V Supported Configurations](appv-supported-configurations.md)
 

5
windows/manage/appv-publish-a-connection-group.md
View File

@ -1,8 +1,7 @@
---
title: How to Publish a Connection Group
title: How to Publish a Connection Group (Windows 10)
description: How to Publish a Connection Group
author: jamiejdt
ms.assetid: fe89601c-23c6-4b7c-a61b-4ca50908f1b4
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -26,7 +25,7 @@ After you create a connection group, you must publish it to computers that run t
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[Managing Connection Groups](appv-managing-connection-groups.md)

13
windows/manage/appv-publish-a-packages-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Publish a Package by Using the Management Console
title: How to Publish a Package by Using the Management Console (Windows 10)
description: How to Publish a Package by Using the Management Console
author: jamiejdt
ms.assetid: e34d2bcf-15ac-4a75-9dc8-79380b36a25f
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,16 +12,16 @@ ms.prod: w10
# How to Publish a Package by Using the Management Console
Use the following procedure to publish an App-V 5.1 package. Once you publish a package, computers that are running the App-V 5.1 client can access and run the applications in that package.
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.
**Note**  
The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3.
 
**To publish an App-V 5.1 package**
**To publish an App-V package**
1. In the App-V 5.1 Management console. Click or right-click the name of the package to be published. Select **Publish**.
1. In the App-V Management console. Click or right-click the name of the package to be published. Select **Publish**.
2. Review the **Status** column to verify that the package has been published and is now available. If the package is available, the status **published** is displayed.
@ -36,14 +35,14 @@ The ability to enable only administrators to publish or unpublish packages (desc
2. Enable the **Require publish as administrator** Group Policy setting.
To alternatively use PowerShell to set this item, see [How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
To alternatively use PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).
**Got 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/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
[How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md)

7
windows/manage/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Register and Unregister a Publishing Server by Using the Management Console
title: How to Register and Unregister a Publishing Server by Using the Management Console (Windows 10)
description: How to Register and Unregister a Publishing Server by Using the Management Console
author: jamiejdt
ms.assetid: 69cef0a8-8102-4697-b1ba-f16e0f25216b
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,7 +12,7 @@ ms.prod: w10
# How to Register and Unregister a Publishing Server by Using the Management Console
You can register and unregister publishing servers that will synchronize with the App-V 5.1 management server. You can also see the last attempt that the publishing server made to synchronize the information with the management server.
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.
Use the following procedure to register or unregister a publishing server.
@ -40,7 +39,7 @@ Use the following procedure to register or unregister a publishing server.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

41
windows/manage/appv-release-notes-for-appv-for-windows.md
View File

@ -1,8 +1,7 @@
---
title: Release Notes for App-V 5.1
description: Release Notes for App-V 5.1
title: Release Notes for App-V (Windows 10)
description: Release Notes for App-V
author: jamiejdt
ms.assetid: 62c5be3b-0a46-4512-93ed-97c23184f343
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,37 +9,37 @@ ms.prod: w10
---
# Release Notes for App-V 5.1
# Release Notes for App-V
The following are known issues in Microsoft Application Virtualization (App-V) 5.1.
The following are known issues in Microsoft Application Virtualization (App-V).
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V 5.1 Client on Windows 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 5.1 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 5.1 publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier.
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 5.1 Management server for Windows 10 Clients.
**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 5.1 Server
## 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 5.1 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.
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 5.1 Dynamic Configuration](appv-dynamic-configuration.md) for more information.
- 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 5.1 Sequencer.
- Create a new package with the custom configuration using the App-V Sequencer.
## Server files not deleted after new App-V 5.1 Server installation
## 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 5.1 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.
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 5.1:
**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.
@ -54,7 +53,7 @@ File type associations added to an application package manually using the Shortc
## 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 5.1 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.
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
@ -74,7 +73,7 @@ On the Packages page of the Management Console, if you click **Add or Upgrade**
## <a href="" id="upgrading-app-v-management-server-to-5-1-sometimes-fails-with-the-message--a-database-error-occurred-"></a>Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V 5.1 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'.”
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:
@ -132,14 +131,14 @@ The Permissions.sql script should be updated according to **Step 2** in [KB arti
## Microsoft Visual Studio 2012 not supported
App-V 5.1 does not support Visual Studio 2012.
App-V does not support Visual Studio 2012.
**Workaround**: None
## Application filename restrictions for App-V 5.x Sequencer
## Application filename restrictions for App-V Sequencer
The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
The App-V Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
**Workaround**: Use a different filename
@ -151,7 +150,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[About App-V 5.1](appv-about-appv.md)
[About App-V](appv-about-appv.md)
 

77
windows/manage/appv-reporting.md
View File

@ -1,8 +1,7 @@
---
title: About App-V 5.1 Reporting
description: About App-V 5.1 Reporting
title: About App-V Reporting (Windows 10)
description: About App-V Reporting
author: jamiejdt
ms.assetid: 385dca00-7178-4e35-8d86-c58867ebd65c
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,17 +9,17 @@ ms.prod: w10
---
# About App-V 5.1 Reporting
# About App-V Reporting
Microsoft Application Virtualization (App-V) 5.1 includes a built-in reporting feature that helps you collect information about computers running the App-V 5.1 client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
Microsoft 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.
## <a href="" id="---------app-v-5-1-reporting-overview"></a> App-V 5.1 Reporting Overview
## <a href="" id="---------app-v-5-1-reporting-overview"></a> App-V Reporting Overview
The following list displays the end–to-end high-level workflow for reporting in App-V 5.1.
The following list displays the end–to-end high-level workflow for reporting in App-V.
1. The App-V 5.1 Reporting server has the following prerequisites:
1. The App-V Reporting server has the following prerequisites:
- Internet Information Service (IIS) web server role
@ -28,41 +27,41 @@ The following list displays the end–to-end high-level workflow for reporting i
- SQL Server installed and running with SQL Server Reporting Services (SSRS)
To confirm SQL Server Reporting Services is running, view `http://localhost/Reports` in a web browser as administrator on the server that will host App-V 5.1 Reporting. The SQL Server Reporting Services Home page should display.
To confirm SQL Server Reporting Services is running, view `http://localhost/Reports` in a web browser as administrator on the server that will host App-V Reporting. The SQL Server Reporting Services Home page should display.
2. Install the App-V 5.1 reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V 5.1 client should send data to the reporting server.
2. Install the App-V reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at <http://go.microsoft.com/fwlink/?LinkId=397255>.
**Note**  
If you are using the Configuration Manager integration with App-V 5.1, most reports are generated from Configuration Manager rather than from App-V 5.1.
If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
 
4. After importing the App-V 5.1 PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V 5.1 client. This sample PowerShell cmdlet enables App-V 5.1 reporting:
4. After importing the App-V PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample PowerShell cmdlet enables App-V reporting:
``` syntax
Set-AppvClientConfiguration –reportingserverurl <url>:<port> -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
```
To immediately send App-V 5.1 report data, run `Send-AppvClientReport` on the App-V 5.1 client.
To immediately send App-V report data, run `Send-AppvClientReport` on the App-V client.
For more information about installing the App-V 5.1 client with reporting enabled see [About Client Configuration Settings](appv-client-configuration-settings.md). To administer App-V 5.1 Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V 5.1 Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
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).
5. After the reporting server receives the data from the App-V 5.1 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 5.1 client.
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 5.1 client receives the success notification, it empties the data cache to conserve space.
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 5.1 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.
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.
### <a href="" id="-------------app-v-5-1-reporting-server-frequently-asked-questions"></a> App-V 5.1 reporting server frequently asked questions
### <a href="" id="-------------app-v-5-1-reporting-server-frequently-asked-questions"></a> App-V reporting server frequently asked questions
The following table displays answers to common questions about App-V 5.1 reporting
The following table displays answers to common questions about App-V reporting
<table>
<colgroup>
@ -78,14 +77,14 @@ The following table displays answers to common questions about App-V 5.1 reporti
<tbody>
<tr class="odd">
<td align="left"><p>What is the frequency that reporting information is sent to the reporting database?</p></td>
<td align="left"><p>The frequency depends on how the reporting task is configured on the computer running the App-V 5.1 client. You must configure the frequency / interval for sending the reporting data. App-V 5.1 Reporting is not enabled by default.</p></td>
<td align="left"><p>The frequency depends on how the reporting task is configured on the computer running the App-V client. You must configure the frequency / interval for sending the reporting data. App-V Reporting is not enabled by default.</p></td>
</tr>
<tr class="even">
<td align="left"><p>What information is stored in the reporting server database?</p></td>
<td align="left"><p>The following list displays what is stored in the reporting database:</p>
<ul>
<li><p>The operating system running on the computer running the App-V 5.1 client: host name, version, service pack, type - client/server, processor architecture.</p></li>
<li><p>App-V 5.1 Client information: version.</p></li>
<li><p>The operating system running on the computer running the App-V client: host name, version, service pack, type - client/server, processor architecture.</p></li>
<li><p>App-V Client information: version.</p></li>
<li><p>Published package list: GUID, version GUID, name.</p></li>
<li><p>Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time.</p></li>
</ul></td>
@ -94,7 +93,7 @@ The following table displays answers to common questions about App-V 5.1 reporti
<td align="left"><p>What is the average volume of information that is sent to the reporting server?</p></td>
<td align="left"><p>It depends. The following list displays the three sets of the data sent to the reporting server:</p>
<ol>
<li><p>Operating system, and App-V 5.1 client information. ~150 Bytes, every time this data is sent.</p></li>
<li><p>Operating system, and App-V client information. ~150 Bytes, every time this data is sent.</p></li>
<li><p>Published package list. ~7 KB for 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.</p></li>
<li><p>Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is <strong>DeleteOnSuccess</strong>.</p>
<p></p>
@ -125,21 +124,21 @@ The following table displays answers to common questions about App-V 5.1 reporti
 
## <a href="" id="---------app-v-5-1-client-reporting"></a> App-V 5.1 Client Reporting
## <a href="" id="---------app-v-5-1-client-reporting"></a> App-V Client Reporting
To use App-V 5.1 reporting you must install and configure the App-V 5.1 client. After the client has been installed, use the **Set-AppVClientConfiguration** 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 5.1 client reporting configuration using PowerShell.
To use App-V reporting you must install and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** 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 PowerShell.
### Configuring App-V Client reporting using PowerShell
The following examples show how PowerShell parameters can configure the reporting features of the App-V 5.1 client.
The following examples show how 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 5.1 ADMX template. For more information about using the ADMX template, see [How to Modify App-V 5.1 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. 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).
 
**To enable reporting and to initiate data collection on the computer running the App-V 5.1 client**:
**To enable reporting and to initiate data collection on the computer running the App-V client**:
`Set-AppVClientConfiguration –ReportingEnabled 1`
@ -157,7 +156,7 @@ This example configures the client to automatically send the reporting data to t
`Set-AppvClientConfiguration –ReportingDataCacheLimit 100`
Configures the maximum size of the reporting cache on the computer running the App-V 5.1 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.
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**:
@ -167,7 +166,7 @@ Specifies the maximum data block that the client sends to 10240 MB.
### Types of data collected
The following table displays the types of information you can collect by using App-V 5.1 reporting.
The following table displays the types of information you can collect by using App-V reporting.
<table>
<colgroup>
@ -189,7 +188,7 @@ The following table displays the types of information you can collect by using A
<td align="left"><p>Start and End Times</p></td>
</tr>
<tr class="even">
<td align="left"><p>App-V 5.1 Client Version</p></td>
<td align="left"><p>App-V Client Version</p></td>
<td align="left"><p>Package Version</p></td>
<td align="left"><p>Run Status</p></td>
</tr>
@ -227,7 +226,7 @@ The client collects and saves this data in an **.xml** format. The data cache is
### Sending data to the server
You can configure the computer that is running the App-V 5.1 client to automatically send data to the specified reporting server. To specify the server use the **Set-AppvClientConfiguration** cmdlet with the following settings:
You can configure the computer that is running the App-V client to automatically send data to the specified reporting server. To specify the server use the **Set-AppvClientConfiguration** cmdlet with the following settings:
- ReportingEnabled
@ -264,8 +263,8 @@ You can also use the **Send-AppVClientReport** cmdlet to manually collect data.
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>If you have an existing App-V 5.1 reporting Server, create a customized scheduled task or script. Specify that the client send the data to the specified location with the desired frequency.</p></td>
<td align="left"><p>If you do not have an existing App-V 5.1 reporting Server, use the <strong>–URL</strong> parameter to send the data to a specified share. For example:</p>
<td align="left"><p>If you have an existing App-V reporting Server, create a customized scheduled task or script. Specify that the client send the data to the specified location with the desired frequency.</p></td>
<td align="left"><p>If you do not have an existing App-V reporting Server, use the <strong>–URL</strong> parameter to send the data to a specified share. For example:</p>
<p><code>Send-AppVClientReport –URL \\Myshare\MyData\ -DeleteOnSuccess</code></p>
<p>The previous example will send the reporting data to <strong>\\MyShare\MyData\</strong> location indicated by the <strong>-URL</strong> parameter. After the data has been sent, the cache is cleared.</p>
<div class="alert">
@ -283,13 +282,13 @@ You can also use the **Send-AppVClientReport** cmdlet to manually collect data.
### Creating Reports
To retrieve report information and create reports using App-V 5.1 you must use one of the following methods:
To retrieve report information and create reports using App-V you must use one of the following methods:
- **Microsoft SQL Server Reporting Services (SSRS)** - Microsoft SQL Server Reporting Services is available with Microsoft SQL Server. SSRS is not installed when you install the App-V 5.1 reporting server. It must be deployed separately to generate the associated reports.
- **Microsoft SQL Server Reporting Services (SSRS)** - Microsoft SQL Server Reporting Services is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports.
Use the following link for more information about using [Microsoft SQL Server Reporting Services](http://go.microsoft.com/fwlink/?LinkId=285596).
- **Scripting** – You can generate reports by scripting directly against the App-V 5.1 reporting database. For example:
- **Scripting** – You can generate reports by scripting directly against the App-V reporting database. For example:
**Stored Procedure:**
@ -297,7 +296,7 @@ To retrieve report information and create reports using App-V 5.1 you must use o
To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. You should ensure that the Microsoft SQL Server Agent is set to **AutoStart**. For more information see [Autostart SQL Server Agent (SQL Server Management Studio)](http://go.microsoft.com/fwlink/?LinkId=287045).
The stored procedure is also created when using the App-V 5.1 database scripts.
The stored procedure is also created when using the App-V database scripts.
You should also ensure that the reporting server web service’s **Maximum Concurrent Connections** is set to a value that the server will be able to manage without impacting availability. The recommended number of **Maximum Concurrent Connections** for the **Reporting Web Service** is **10,000**.
@ -309,7 +308,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Deploying the App-V 5.1 Server](appv-deploying-the-appv-server.md)
[Deploying the App-V Server](appv-deploying-the-appv-server.md)
[How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md)

15
windows/manage/appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-a-specific-user.md
View File

@ -1,8 +1,7 @@
---
title: How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User
description: How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User
title: How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User (Windows 10)
description: How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User
author: jamiejdt
ms.assetid: bd53c5d6-7fd2-4816-b03b-d59da0a35819
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,14 +9,14 @@ ms.prod: w10
---
# How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User
# How to Revert Extension Points From an App-V Package to an App-V 4.6 Package for a Specific User
Use the following procedure to revert an App-V 5.1 package to the App-V file format using the user configuration file.
Use the following procedure to revert an App-V package to the App-V file format using the user configuration file.
**To revert a package**
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md).
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md).
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=&lt;Package ID&gt;**
@ -28,7 +27,7 @@ Use the following procedure to revert an App-V 5.1 package to the App-V file for
3. Perform a publishing refresh, or wait for the next scheduled publishing refresh for the App-V 4.6. Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6.
**Note**  
If you do not need the App-V 5.1 package anymore, you can unpublish the App-V 5.1 package and the extension points will automatically revert to App-V 4.6.
If you do not need the App-V package anymore, you can unpublish the App-V package and the extension points will automatically revert to App-V 4.6.
 
@ -37,7 +36,7 @@ Use the following procedure to revert an App-V 5.1 package to the App-V file for
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

15
windows/manage/appv-revert-extension-points-from-an-appv-51-package-to-an-appv-46-sp2-package-for-all-users-on-a-specific-computer.md
View File

@ -1,8 +1,7 @@
---
title: How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer
description: How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer
title: How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer (Windows 10)
description: How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer
author: jamiejdt
ms.assetid: 64640b8e-de6b-4006-a33e-353d285af15e
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,14 +9,14 @@ ms.prod: w10
---
# How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer
# How to Revert Extension Points from an App-V Package to an App-V 4.6 Package For All Users on a Specific Computer
Use the following procedure to revert extension points from an App-V 5.1 package to the App-V 4.6 file format using the deployment configuration file.
Use the following procedure to revert extension points from an App-V package to the App-V 4.6 file format using the deployment configuration file.
**To revert a package**
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V 5.1 package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md).
1. Ensure that App-V 4.6 package is published to the users but the FTAs and shortcuts have been assumed by App-V package using the following migration method, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md).
In the **userConfiguration** section of the deployment configuration file for the converted package, to set the policy, make the following update to the **userConfiguration** section: **ManagingAuthority TakeoverExtensionPointsFrom46="false" PackageName=&lt;Package ID&gt;**
@ -32,7 +31,7 @@ Use the following procedure to revert extension points from an App-V 5.1 package
Open the application using FTAs or shortcuts. The Application should now open using App-V 4.6.
**Note**  
If you do not need the App-V 5.1 package anymore, you can unpublish the App-V 5.1 package and the extension points will automatically revert to App-V 4.6.
If you do not need the App-V package anymore, you can unpublish the App-V package and the extension points will automatically revert to App-V 4.6.
 
@ -41,7 +40,7 @@ Use the following procedure to revert extension points from an App-V 5.1 package
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

7
windows/manage/appv-running-locally-installed-applications-inside-a-virtual-environment.md
View File

@ -1,8 +1,7 @@
---
title: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
title: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications (Windows 10)
description: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
author: jamiejdt
ms.assetid: 71baf193-a9e8-4ffa-aa7f-e0bffed2e4b2
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -53,7 +52,7 @@ There is no Group Policy setting available to manage this registry key, so you h
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V 5.0 SP3 and App-V 5.1</p></td>
<td align="left"><p>App-V 5.0 SP3 and App-V</p></td>
<td align="left"><p>Published globally or to the user</p></td>
</tr>
<tr class="even">
@ -179,7 +178,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Technical Reference for App-V 5.1](appv-technical-reference.md)
[Technical Reference for App-V](appv-technical-reference.md)
 

43
windows/manage/appv-security-considerations.md
View File

@ -1,8 +1,7 @@
---
title: App-V 5.1 Security Considerations
description: App-V 5.1 Security Considerations
title: App-V Security Considerations (Windows 10)
description: App-V Security Considerations
author: jamiejdt
ms.assetid: 6bc6c1fc-f813-47d4-b763-06fd4faf6a72
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,13 +9,13 @@ ms.prod: w10
---
# App-V 5.1 Security Considerations
# App-V Security Considerations
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V) 5.1.
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
**Important**  
App-V 5.1 is not a security product and does not provide any guarantees for a secure environment.
App-V is not a security product and does not provide any guarantees for a secure environment.
 
@ -28,27 +27,27 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa
## General security considerations
**Understand the security risks.** The most serious risk to App-V 5.1 is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V 5.1 clients. The loss of App-V 5.1 functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
**Understand the security risks.** The most serious risk to App-V is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V clients. The loss of App-V functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.1 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.1 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V 5.1, subscribe to the Security Notification service (<http://go.microsoft.com/fwlink/p/?LinkId=28819>).
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (<http://go.microsoft.com/fwlink/p/?LinkId=28819>).
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V 5.1 and App-V 5.1 administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet (<http://go.microsoft.com/fwlink/p/?LinkId=30009>).
**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 (<http://go.microsoft.com/fwlink/p/?LinkId=30009>).
## Accounts and groups in App-V 5.1
## Accounts and groups in App-V
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V 5.1 local groups on the App-V 5.1 servers.
A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V local groups on the App-V servers.
**Note**  
App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
 
### <a href="" id="-------------app-v-5-1-server-security"></a> App-V 5.1 server security
### <a href="" id="-------------app-v-5-1-server-security"></a> App-V server security
No groups are created automatically during App-V 5.1 Setup. You should create the following Active Directory Domain Services global groups to manage App-V 5.1 server operations.
No groups are created automatically during App-V Setup. You should create the following Active Directory Domain Services global groups to manage App-V server operations.
<table>
<colgroup>
@ -64,7 +63,7 @@ No groups are created automatically during App-V 5.1 Setup. You should create th
<tbody>
<tr class="odd">
<td align="left"><p>App-V Management Admin group</p></td>
<td align="left"><p>Used to manage the App-V 5.1 management server. This group is created during the App-V 5.1 Management Server installation.</p>
<td align="left"><p>Used to manage the App-V management server. This group is created during the App-V Management Server installation.</p>
<div class="alert">
<strong>Important</strong>  
<p>There is no method to create the group using the management console after you have completed the installation.</p>
@ -75,7 +74,7 @@ No groups are created automatically during App-V 5.1 Setup. You should create th
</tr>
<tr class="even">
<td align="left"><p>Database read/write for Management Service account</p></td>
<td align="left"><p>Provides read/write access to the management database. This account should be created during the App-V 5.1 management database installation.</p></td>
<td align="left"><p>Provides read/write access to the management database. This account should be created during the App-V management database installation.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>App-V Management Service install admin account</p>
@ -86,7 +85,7 @@ No groups are created automatically during App-V 5.1 Setup. You should create th
<div>
 
</div></td>
<td align="left"><p>Provides public access to schema-version table in management database. This account should be created during the App-V 5.1 management database installation.</p></td>
<td align="left"><p>Provides public access to schema-version table in management database. This account should be created during the App-V management database installation.</p></td>
</tr>
<tr class="even">
<td align="left"><p>App-V Reporting Service install admin account</p>
@ -97,7 +96,7 @@ No groups are created automatically during App-V 5.1 Setup. You should create th
<div>
 
</div></td>
<td align="left"><p>Public access to schema-version table in reporting database. This account should be created during the App-V 5.1 reporting database installation.</p></td>
<td align="left"><p>Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.</p></td>
</tr>
</tbody>
</table>
@ -115,16 +114,16 @@ Consider the following additional information:
- Registering publishing servers with Management Server - A publishing server must be registered with the Management server. For example, it must be added to the database, so that the Publishing server machine accounts are able to call into the Management service API.
### <a href="" id="-------------app-v-5-1-package-security"></a> App-V 5.1 package security
### <a href="" id="-------------app-v-5-1-package-security"></a> App-V package security
The following will help you plan how to ensure that virtualized packages are secure.
- If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. When the package is deployed, if the file or directory is modified by a user it will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former case occurs if the file or directory does not exist in a virtual file system location; the latter case occurs if the file or directory exists in a virtual file system location, for example **%windir%**.
## <a href="" id="---------app-v-5-1-log-files"></a> App-V 5.1 log files
## <a href="" id="---------app-v-5-1-log-files"></a> App-V log files
During App-V 5.1 Setup, setup log files are created in the **%temp%** folder of the installing user.
During App-V Setup, setup log files are created in the **%temp%** folder of the installing user.
## Got a suggestion for App-V?
@ -134,7 +133,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Preparing Your Environment for App-V 5.1](appv-preparing-your-environment.md)
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)
 

11
windows/manage/appv-sequence-a-new-application.md
View File

@ -1,8 +1,7 @@
---
title: How to Sequence a New Application with App-V 5.1
description: How to Sequence a New Application with App-V 5.1
title: How to Sequence a New Application with App-V (Windows 10)
description: How to Sequence a New Application with App-V
author: jamiejdt
ms.assetid: 7d7699b1-0cb8-450d-94e7-5af937e16c21
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,7 +9,7 @@ ms.prod: w10
---
# How to Sequence a New Application with App-V 5.1
# How to Sequence a New Application with App-V
**To review or do before you start sequencing**
@ -57,7 +56,7 @@ ms.prod: w10
- If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume.
**Note**
The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
The App-V Sequencer cannot sequence applications with filenames matching "CO_&lt;x&gt;" where x is any numeral. Error 0x8007139F will be generated.
**To sequence a new standard application**
@ -276,7 +275,7 @@ The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

13
windows/manage/appv-sequence-a-package-with-powershell.md
View File

@ -1,8 +1,7 @@
---
title: How to Sequence a Package by Using PowerShell
title: How to Sequence a Package by Using PowerShell (Windows 10)
description: How to Sequence a Package by Using PowerShell
author: jamiejdt
ms.assetid: 6134c6be-937d-4609-a516-92d49154b290
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -13,16 +12,16 @@ ms.prod: w10
# How to Sequence a Package by Using PowerShell
Use the following procedure to create a new App-V 5.1 package using PowerShell.
Use the following procedure to create a new App-V package using PowerShell.
**Note**  
Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V 5.1 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
 
**To create a new virtual application using PowerShell**
1. Install the App-V 5.1 sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
@ -54,14 +53,14 @@ Before you use this procedure you must copy the associated installer files to th
- TemplateFilePath - specifies the path to a template fileif you want to customize the sequencing process.
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V 5.1 before it can be opened.
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
**Got 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/home?forum=mdopappv).
## Related topics
[Administering App-V 5.1 by Using PowerShell](appv-administering-appv-with-powershell.md)
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
 

39
windows/manage/appv-supported-configurations.md
View File

@ -1,8 +1,7 @@
---
title: App-V 5.1 Supported Configurations
description: App-V 5.1 Supported Configurations
title: App-V Supported Configurations (Windows 10)
description: App-V Supported Configurations
author: jamiejdt
ms.assetid: 8b8db63b-f71c-4ae9-80e7-a6752334e1f6
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,23 +9,23 @@ ms.prod: w10
---
# App-V 5.1 Supported Configurations
# App-V Supported Configurations
This topic specifies the requirements to install and run Microsoft Application Virtualization (App-V) 5.1 in your environment.
This topic specifies the requirements to install and run Microsoft Application Virtualization (App-V) in your environment.
## App-V Server system requirements
This section lists the operating system and hardware requirements for all of the App-V Server components.
### Unsupported App-V 5.1 Server scenarios
### Unsupported App-V Server scenarios
The App-V 5.1 Server does not support the following scenarios:
The App-V Server does not support the following scenarios:
- Deployment to a computer that runs Microsoft Windows Server Core.
- Deployment to a computer that runs a previous version of App-V 5.1 Server components. You can install App-V 5.1 side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
- Deployment to a computer that runs a previous version of App-V Server components. You can install App-V side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
- Deployment to a computer that runs Microsoft SQL Server Express edition.
@ -36,7 +35,7 @@ The App-V 5.1 Server does not support the following scenarios:
### Management server operating system requirements
The following table lists the operating systems that are supported for the App-V 5.1 Management server installation.
The following table lists the operating systems that are supported for the App-V Management server installation.
**Note**  
Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](http://go.microsoft.com/fwlink/p/?LinkId=31975). See [Microsoft Support Lifecycle Support Policy FAQ](http://go.microsoft.com/fwlink/p/?LinkId=31976) for more information.
@ -92,7 +91,7 @@ Deployment of the Management server role to a computer with Remote Desktop Shari
### Management server database requirements
The following table lists the SQL Server versions that are supported for the App-V 5.1 Management database installation.
The following table lists the SQL Server versions that are supported for the App-V Management database installation.
<table>
<colgroup>
@ -130,7 +129,7 @@ The following table lists the SQL Server versions that are supported for the App
### Publishing server operating system requirements
The following table lists the operating systems that are supported for the App-V 5.1 Publishing server installation.
The following table lists the operating systems that are supported for the App-V Publishing server installation.
<table>
<colgroup>
@ -178,7 +177,7 @@ App-V adds no additional requirements beyond those of Windows Server.
### Reporting server operating system requirements
The following table lists the operating systems that are supported for the App-V 5.1 Reporting server installation.
The following table lists the operating systems that are supported for the App-V Reporting server installation.
<table>
<colgroup>
@ -226,7 +225,7 @@ App-V adds no additional requirements beyond those of Windows Server.
### Reporting server database requirements
The following table lists the SQL Server versions that are supported for the App-V 5.1 Reporting database installation.
The following table lists the SQL Server versions that are supported for the App-V Reporting database installation.
<table>
<colgroup>
@ -265,7 +264,7 @@ The following table lists the SQL Server versions that are supported for the App
## <a href="" id="bkmk-client-supp-cfgs"></a>App-V client system requirements
The following table lists the operating systems that are supported for the App-V 5.1 client installation.
The following table lists the operating systems that are supported for the App-V client installation.
<table>
<colgroup>
@ -312,11 +311,11 @@ The following App-V client installation scenarios are not supported, except as n
- Computers that run App-V 4.6 SP1 or earlier versions
- The App-V 5.1 Remote Desktop services client is supported only for RDS-enabled servers
- The App-V Remote Desktop services client is supported only for RDS-enabled servers
### <a href="" id="app-v-client-hardware-requirements-"></a>App-V client hardware requirements
The following list displays the supported hardware configuration for the App-V 5.1 client installation.
The following list displays the supported hardware configuration for the App-V client installation.
- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
@ -327,7 +326,7 @@ The following list displays the supported hardware configuration for the App-V 5
## Remote Desktop Services client system requirements
The following table lists the operating systems that are supported for App-V 5.1 Remote Desktop Services (RDS) client installation.
The following table lists the operating systems that are supported for App-V Remote Desktop Services (RDS) client installation.
<table>
<colgroup>
@ -376,7 +375,7 @@ App-V adds no additional requirements beyond those of Windows Server.
## Sequencer system requirements
The following table lists the operating systems that are supported for the App-V 5.1 Sequencer installation.
The following table lists the operating systems that are supported for the App-V Sequencer installation.
<table>
<colgroup>
@ -608,7 +607,7 @@ The following App-V and System Center Configuration Manager version matrix shows
<td align="left"><p>Yes</p></td>
</tr>
<tr class="even">
<td align="left"><p>App-V 5.1</p></td>
<td align="left"><p>App-V</p></td>
<td align="left"><p>MSI-Wrapper Only</p></td>
<td align="left"><p>No</p></td>
<td align="left"><p>2012 SP1 CU4</p></td>
@ -634,7 +633,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
[App-V 5.1 Prerequisites](appv-prerequisites.md)
[App-V Prerequisites](appv-prerequisites.md)
 

11
windows/manage/appv-technical-reference.md
View File

@ -1,8 +1,7 @@
---
title: Technical Reference for App-V 5.1
description: Technical Reference for App-V 5.1
title: Technical Reference for App-V (Windows 10)
description: Technical Reference for App-V
author: jamiejdt
ms.assetid: 2b9e8b2b-4cd1-46f3-ba08-e3bc8d5c6127
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,15 +9,15 @@ ms.prod: w10
---
# Technical Reference for App-V 5.1
# Technical Reference for App-V
This section provides reference information related to managing App-V 5.1.
This section provides reference information related to managing App-V.
## In This Section
- [Performance Guidance for Application Virtualization 5.1](appv-performance-guidance.md)
- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
Provides strategy and context for a number of performance optimization practices. Not all practices will be applicable although they are supported and have been tested. Using all suggested practices that are applicable to your organization will provide the optimal end-user experience.

7
windows/manage/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
title: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console (Windows 10)
description: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
author: jamiejdt
ms.assetid: bf53f064-76ae-4eac-9266-d087c480cda7
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -17,7 +16,7 @@ Use the following procedure to transfer the access and default package configura
**To transfer access and configurations to another version of a package**
1. To view the package that you want to configure, open the App-V 5.1 Management Console. Select the package to which you will transfer the new configuration, right-click the package and select **transfer default configuration from** or **transfer access and configurations from**, depending on the configuration that you want to transfer.
1. To view the package that you want to configure, open the App-V Management Console. Select the package to which you will transfer the new configuration, right-click the package and select **transfer default configuration from** or **transfer access and configurations from**, depending on the configuration that you want to transfer.
2. To transfer the configuration, in the **Select Previous Version** dialog box, select the package that contains the settings that you want to transfer, and then click **OK**.
@ -30,7 +29,7 @@ Use the following procedure to transfer the access and default package configura
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

19
windows/manage/appv-troubleshooting.md
View File

@ -1,8 +1,7 @@
---
title: Troubleshooting App-V 5.1
description: Troubleshooting App-V 5.1
title: Troubleshooting App-V (Windows 10)
description: Troubleshooting App-V
author: jamiejdt
ms.assetid: 435d0e56-0aa2-4168-b5a7-2f03a1f273d4
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,7 +9,7 @@ ms.prod: w10
---
# Troubleshooting App-V 5.1
# Troubleshooting App-V
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).
@ -65,18 +64,18 @@ If you have a troubleshooting tip or a best practice to share that is not alread
8. Click **Save** to publish the article to the TechNet Wiki.
## Other resources for troubleshooting App-V 5.1
## Other resources for troubleshooting App-V
- [Microsoft Application Virtualization 5.1 Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
- [Getting Started with App-V 5.1](appv-getting-started.md)
- [Getting Started with App-V](appv-getting-started.md)
- [Planning for App-V 5.1](appv-planning-for-appv.md)
- [Planning for App-V](appv-planning-for-appv.md)
- [Deploying App-V 5.1](appv-deploying-appv.md)
- [Deploying App-V](appv-deploying-appv.md)
- [Operations for App-V 5.1](appv-operations.md)
- [Operations for App-V](appv-operations.md)
## Got a suggestion for App-V?

17
windows/manage/appv-uninstall-the-appv-client.md
View File

@ -1,8 +1,7 @@
---
title: How to Uninstall the App-V 5.1 Client
description: How to Uninstall the App-V 5.1 Client
title: How to Uninstall the App-V Client (Windows 10)
description: How to Uninstall the App-V Client
author: jamiejdt
ms.assetid: 21f2d946-fc9f-4cd3-899b-ac52b3fbc306
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,17 +9,17 @@ ms.prod: w10
---
# How to Uninstall the App-V 5.1 Client
# How to Uninstall the App-V Client
Use the following procedure to uninstall the Microsoft Application Virtualization (App-V) 5.1 client from a computer. When you uninstall the App-V 5.1 client all packages published to the computer running the client are also removed. If the uninstall operation does not complete the packages will need to be re-published to the computer running the App-V 5.1 client.
Use the following procedure to uninstall the Microsoft Application Virtualization (App-V) client from a computer. When you uninstall the App-V client all packages published to the computer running the client are also removed. If the uninstall operation does not complete the packages will need to be re-published to the computer running the App-V client.
**Important**  
You should ensure that the App-V 5.1 client service is running prior to performing the uninstall procedure.
You should ensure that the App-V client service is running prior to performing the uninstall procedure.
 
**To uninstall the App-V 5.1 Client**
**To uninstall the App-V Client**
1. In Control Panel, double-click **Programs** / **Uninstall a Program**, and then double-click **Microsoft Application Virtualization Client**.
@ -34,7 +33,7 @@ You should ensure that the App-V 5.1 client service is running prior to performi
3. A progress bar shows the time remaining. When this step finishes, you must restart the computer so that all associated drivers can be stopped to complete the uninstall process.
**Note**  
You can also use the command line to uninstall the App-V 5.1 client with the following switch: **/UNINSTALL**.
You can also use the command line to uninstall the App-V client with the following switch: **/UNINSTALL**.
 
@ -43,7 +42,7 @@ You should ensure that the App-V 5.1 client service is running prior to performi
## Related topics
[Deploying App-V 5.1](appv-deploying-appv.md)
[Deploying App-V](appv-deploying-appv.md)
 

2
windows/manage/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md
View File

@ -10,7 +10,7 @@ ms.prod: w10
# Upgrading to App-V for Windows 10 from an existing installation
If you’re already using App-V 5.1 and you’re planning to upgrade user devices to Windows 10, you need to make only the following few adjustments to your existing environment to start using App-V for Windows 10.
If you’re already using App-V and you’re planning to upgrade user devices to Windows 10, you need to make only the following few adjustments to your existing environment to start using App-V for Windows 10.
1. [Upgrade user devices to Windows 10](#upgrade-user-devices-to-windows-10). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.

17
windows/manage/appv-use-an-appv-46-sp1-application-from-an-appv-51-application.md
View File

@ -1,8 +1,7 @@
---
title: How to Use an App-V 4.6 Application From an App-V 5.1 Application
description: How to Use an App-V 4.6 Application From an App-V 5.1 Application
title: How to Use an App-V 4.6 Application From an App-V Application (Windows 10)
description: How to Use an App-V 4.6 Application From an App-V Application
author: jamiejdt
ms.assetid: 909b4391-762b-4988-b0cf-32b67f1fcf0e
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,10 +9,10 @@ ms.prod: w10
---
# How to Use an App-V 4.6 Application From an App-V 5.1 Application
# How to Use an App-V 4.6 Application From an App-V Application
Use the following procedure to run an App-V 4.6 application with App-V 5.1 applications on a standalone client.
Use the following procedure to run an App-V 4.6 application with App-V applications on a standalone client.
**Note**  
This procedure assumes that you are running the latest version of App-V 4.6.
@ -22,18 +21,18 @@ This procedure assumes that you are running the latest version of App-V 4.6.
1. Select two applications in your environment that can be opened from one another. For example, Microsoft Outlook and Adobe Acrobat Reader. You can access an email attachment created using Adobe Acrobat.
2. Convert the packages, or create a new package for either of the applications using the App-V 5.1 format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md).
2. Convert the packages, or create a new package for either of the applications using the App-V format. For more information about converting packages see, [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V Package for All Users on a Specific Computer](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-a-converted-appv-51-package-for-all-users-on-a-specific-computer.md) or [How to Migrate Extension Points From an App-V 4.6 Package to App-V for a Specific User](appv-migrate-extension-points-from-an-appv-46-sp2-package-to-appv-51-for-a-specific-user.md).
3. Add and provision the package using the App-V 5.1 management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md).
3. Add and provision the package using the App-V management console. For more information adding and provisioning packages see, [How to Add or Upgrade Packages by Using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to Configure Access to Packages by Using the Management Console](appv-configure-access-to-packages-with-the-management-console.md).
4. The converted application now runs using App-V 5.1 and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V 5.1 package and Adobe Acrobat is still running as an App-V 4.6 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
4. The converted application now runs using App-V and you can open one application from the other. For example, if you converted a Microsoft Office package to an App-V package and Adobe Acrobat is still running as an App-V 4.6 package, you can open an Adobe Acrobat Reader attachment using Microsoft Outlook.
**Got 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/home?forum=mdopappv).
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

9
windows/manage/appv-use-optional-packages-in-connection-groups.md
View File

@ -1,8 +1,7 @@
---
title: How to Use Optional Packages in Connection Groups
title: How to Use Optional Packages in Connection Groups (Windows 10)
description: How to Use Optional Packages in Connection Groups
author: jamiejdt
ms.assetid: 67666f18-b704-4852-a1e4-d13633bd2baf
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -65,7 +64,7 @@ Before using optional packages, see [Requirements for using optional packages in
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>With App-V 5.0 SP3 and App-V 5.1</strong></p>
<td align="left"><p><strong>With App-V 5.0 SP3 and App-V</strong></p>
<p>You can add optional packages to connection groups, which enables you to provide different combinations of applications and plug-ins to different end users.</p>
<p><strong>Example</strong>: You want to distribute Microsoft Office to your end users, but enable a certain plug-in for only a subset of users.</p>
<p>To do this, create a connection group that contains a package with Office, and another package with Office plug-ins, and then make the plug-ins package optional.</p>
@ -178,7 +177,7 @@ Before using optional packages, see [Requirements for using optional packages in
</thead>
<tbody>
<tr class="odd">
<td align="left"><p><strong>With App-V 5.0 SP3 and App-V 5.1</strong></p>
<td align="left"><p><strong>With App-V 5.0 SP3 and App-V</strong></p>
<p>You can unpublish, delete, or republish an optional package, which is in a connection group, without having to disable or re-enable the connection group on the App-V Client.</p>
<p>You can also unpublish an optional package and republish it later without having to disable or republish the connection group.</p>
<p><strong>Example</strong>: If you publish an optional package that contains a Microsoft Office plug-in, and you want to remove the plug-in, you can unpublish the package without having to disable the connection group.</p></td>
@ -208,7 +207,7 @@ Before using optional packages, see [Requirements for using optional packages in
<li><p>Unpublish-AppvClientPackage</p></li>
<li><p>Remove-AppvClientPackage</p></li>
</ul>
<p>For more information, see [How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).</p></td>
<p>For more information, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).</p></td>
</tr>
</tbody>
</table>

19
windows/manage/appv-using-the-client-management-console.md
View File

@ -1,8 +1,7 @@
---
title: Using the App-V 5.1 Client Management Console
description: Using the App-V 5.1 Client Management Console
title: Using the App-V Client Management Console (Windows 10)
description: Using the App-V Client Management Console
author: jamiejdt
ms.assetid: be6d4e35-5701-4f9a-ba8a-bede12662cf1
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -10,20 +9,20 @@ ms.prod: w10
---
# Using the App-V 5.1 Client Management Console
# Using the App-V Client Management Console
This topic provides information about how you can configure and manage the Microsoft Application Virtualization (App-V) 5.1 client.
This topic provides information about how you can configure and manage the Microsoft Application Virtualization (App-V) client.
## Modify App-V 5.1 client configuration
## Modify App-V client configuration
The App-V 5.1 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).
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).
## <a href="" id="the-app-v-5-1-client-management-console-"></a>The App-V 5.1 client management console
## <a href="" id="the-app-v-5-1-client-management-console-"></a>The App-V client management console
You can obtain information about the App-V 5.1 client or perform specific tasks by using the App-V 5.1 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 5.1 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 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).
The client management console contains the following described main tabs.
@ -80,7 +79,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

7
windows/manage/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
View File

@ -1,8 +1,7 @@
---
title: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
title: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console (Windows 10)
description: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
author: jamiejdt
ms.assetid: 1e1941d3-fb22-4077-8ec6-7a0cb80335d8
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -17,7 +16,7 @@ Use the following procedure to view and configure default package extensions.
**To view and configure default virtual application extensions**
1. To view the package that you want to configure, open the App-V 5.1 Management Console. Select the package that you want to configure, right-click the package name and select **edit default configuration**.
1. To view the package that you want to configure, open the App-V Management Console. Select the package that you want to configure, right-click the package name and select **edit default configuration**.
2. To view the applications contained in the specified package, in the **Default Configuration** pane, click **Applications**. To view the shortcuts for that package, click **Shortcuts**. To view the file type associations for that package, click **File Types**.
@ -34,7 +33,7 @@ Use the following procedure to view and configure default package extensions.
## Related topics
[Operations for App-V 5.1](appv-operations.md)
[Operations for App-V](appv-operations.md)
 

17
windows/manage/appv-viewing-appv-server-publishing-metadata.md
View File

@ -1,8 +1,7 @@
---
title: Viewing App-V Server Publishing Metadata
title: Viewing App-V Server Publishing Metadata (Windows 10)
description: Viewing App-V Server Publishing Metadata
author: jamiejdt
ms.assetid: d5fa9eb5-647c-478d-8a4d-0ecda018bce6
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
@ -17,7 +16,7 @@ Use this procedure to view publishing metadata, which can help you resolve publi
This article contains the following information:
- [App-V 5.1 requirements for viewing publishing metadata](#bkmk-51-reqs-pub-meta)
- [App-V requirements for viewing publishing metadata](#bkmk-51-reqs-pub-meta)
- [Syntax to use for viewing publishing metadata](#bkmk-syntax-view-pub-meta)
@ -25,10 +24,10 @@ This article contains the following information:
- [Definition of publishing metadata](#bkmk-whatis-pub-metadata)
## <a href="" id="bkmk-51-reqs-pub-meta"></a>App-V 5.1 requirements for viewing publishing metadata
## <a href="" id="bkmk-51-reqs-pub-meta"></a>App-V requirements for viewing publishing metadata
In App-V 5.1, you must provide the following values in the address when you query the App-V Publishing server for metadata:
In App-V, you must provide the following values in the address when you query the App-V Publishing server for metadata:
<table>
<colgroup>
@ -78,7 +77,7 @@ The following table provides the syntax and query examples.
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>App-V 5.0 SP3 and App-V 5.1</p></td>
<td align="left"><p>App-V 5.0 SP3 and App-V</p></td>
<td align="left"><p><code>http://&lt;PubServer&gt;:&lt;Publishing Port#&gt;/?ClientVersion=&lt;AppvClientVersion&gt;&amp;ClientOS=&lt;OSStringValue&gt;</code></p></td>
<td align="left"><table>
<colgroup>
@ -124,12 +123,12 @@ The following table provides the syntax and query examples.
<td align="left"><p><code>http://&lt;PubServer&gt;:&lt;Publishing Port#&gt;/ </code></p>
<div class="alert">
<strong>Note</strong>  
<p><strong>ClientVersion</strong> and <strong>ClientOS</strong> are supported only in App-V 5.0 SP3 and App-V 5.1.</p>
<p><strong>ClientVersion</strong> and <strong>ClientOS</strong> are supported only in App-V 5.0 SP3 and App-V.</p>
</div>
<div>
 
</div></td>
<td align="left"><p>See the information for App-V 5.0 SP3 and App-V 5.1.</p></td>
<td align="left"><p>See the information for App-V 5.0 SP3 and App-V.</p></td>
<td align="left"><p><code>http://pubsvr01:2718</code></p>
<p>In the example, A Windows Server 2012 R2 named “pubsvr01” hosts the Management and Publishing services.</p></td>
</tr>
@ -253,7 +252,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
## Related topics
[Technical Reference for App-V 5.1](appv-technical-reference.md)
[Technical Reference for App-V](appv-technical-reference.md)
 

3
windows/manage/appv-whats-new-in-appv-for-windows.md
View File

@ -1,8 +1,7 @@
---
title: What's new in App-V 5.0 SP1
title: What's new in App-V 5.0 SP1 (Windows 10)
description: What's new in App-V 5.0 SP1
author: jamiejdt
ms.assetid: e97c2dbb-7b40-46a0-8137-9ee4fc2bd071
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library