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

Fixed merge conflict

Browse Source
This commit is contained in:
ManikaDhiman
2019-06-12 11:50:10 -07:00
parent 4abcbc3962 900d5e79fd
commit c16f92df3b
5102 changed files with 78018 additions and 47477 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
windows/access-protection/docfx.json
View File

@ -20,7 +20,7 @@
"files": [
"**/*.png",
"**/*.jpg",
"**/*.gif"
"**/*.gif"
],
"exclude": [
"**/obj/**",
@ -31,20 +31,21 @@
"overwrite": [],
"externalReference": [],
"globalMetadata": {
"uhfHeaderId": "MSDocsHeader-WindowsIT",
"breadcrumb_path": "/windows/windows-10/breadcrumb/toc.json",
"ms.technology": "windows",
"ms.topic": "article",
"ms.author": "justinha",
"_op_documentIdPathDepotMapping": {
"./": {
"depot_name": "MSDN.win-access-protection",
"folder_relative_path_in_docset": "./"
}
}
},
"uhfHeaderId": "MSDocsHeader-WindowsIT",
"breadcrumb_path": "/windows/windows-10/breadcrumb/toc.json",
"ms.technology": "windows",
"ms.topic": "article",
"ms.author": "justinha",
"_op_documentIdPathDepotMapping": {
"./": {
"depot_name": "MSDN.win-access-protection",
"folder_relative_path_in_docset": "./"
}
}
},
"fileMetadata": {},
"template": [],
"dest": "win-access-protection"
"dest": "win-access-protection",
"markdownEngineName": "markdig"
}
}

8
windows/application-management/add-apps-and-features.md
View File

@ -5,10 +5,12 @@ ms.prod: w10
ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: article
ms.author: elizapo
author: lizap
ms.author: tracyp
author: msfttracyp
ms.localizationpriority: medium
ms.date: 04/26/2018
ms.reviewer:
manager: dansimp
ms.topic: article
---
# How to add apps and features to Windows 10
@ -25,4 +27,4 @@ Here's how you do that:
And that's it. You can see the apps you have installed on the **Apps & features** page and the features on **Manage optional features**.
You can manage and uninstall apps and features from the same Settings page. Just select the app or feature, and then select **Uninstall**.
You can manage and uninstall apps and features from the same Settings page. Just select the app or feature, and then select **Uninstall**.

11
windows/application-management/app-v/appv-about-appv.md
View File

@ -1,12 +1,15 @@
---
title: What's new in App-V for Windows 10, version 1703 and earlier (Windows 10)
description: Information about what's new in App-V for Windows 10, version 1703 and earlier.
author: jdeckerms
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# What's new in App-V for Windows 10, version 1703 and earlier
@ -48,8 +51,8 @@ The changes in App-V for Windows 10, version 1607 impact existing implementation
* The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
* In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
>[!NOTE]
>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release.
> [!NOTE]
>If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release.
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](../app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](../app-v/appv-migrating-to-appv-from-a-previous-version.md).
@ -67,4 +70,4 @@ App-V supports System Center 2016 and System Center 2012 R2 Configuration Manage
## Related topics
* [Release Notes for App-V for Windows 10, version 1607](../app-v/appv-release-notes-for-appv-for-windows.md)
* [Release Notes for App-V for Windows 10, version 1703](../app-v/appv-release-notes-for-appv-for-windows-1703.md)
* [Release Notes for App-V for Windows 10, version 1703](../app-v/appv-release-notes-for-appv-for-windows-1703.md)

5
windows/application-management/app-v/appv-add-or-remove-an-administrator-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to add or remove an administrator by using the Management Console

5
windows/application-management/app-v/appv-add-or-upgrade-packages-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to add or upgrade packages by using the Management Console

7
windows/application-management/app-v/appv-administering-appv-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: Administering App-V by using Windows PowerShell (Windows 10)
description: Administering App-V by Using Windows PowerShell
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Administering App-V by using Windows PowerShell
@ -51,4 +54,4 @@ The following table describes Windows PowerShell error handling for App-V.
## Related topics
* [Operations for App-V](appv-operations.md)
* [Operations for App-V](appv-operations.md)

7
windows/application-management/app-v/appv-administering-virtual-applications-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Administering App-V Virtual Applications by using the Management Console
@ -58,4 +61,4 @@ The main elements of the App-V Management Console are:
## Other resources for this App-V deployment
- [Application Virtualization (App-V) overview](appv-for-windows.md)
- [Operations for App-V](appv-operations.md)
- [Operations for App-V](appv-operations.md)

5
windows/application-management/app-v/appv-allow-administrators-to-enable-connection-groups.md
View File

@ -1,12 +1,15 @@
---
title: How to Allow Only Administrators to Enable Connection Groups (Windows 10)
description: How to Allow Only Administrators to Enable Connection Groups
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to allow only administrators to enable connection groups

41
windows/application-management/app-v/appv-application-publishing-and-client-interaction.md
View File

@ -1,12 +1,15 @@
---
title: Application Publishing and Client Interaction (Windows 10)
description: Application publishing and client interaction.
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/08/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Application publishing and client interaction
@ -376,46 +379,46 @@ The process then configures the client for package or connection group additions
3. Configure the packages by identifying the **Add** or **Update** operations.
1. The App-V Client utilizes the AppX API from Windows and accesses the appv file from the publishing server.
1. The App-V Client utilizes the AppX API from Windows and accesses the appv file from the publishing server.
2. The package file is opened and the **AppXManifest.xml** and **StreamMap.xml** files are downloaded to the Package Store.
2. The package file is opened and the **AppXManifest.xml** and **StreamMap.xml** files are downloaded to the Package Store.
3. Completely stream publishing block data defined in the **StreamMap.xml** file. Publishing block data is stored in Package Store\\PkgGUID\\VerGUID\\Root.
3. Completely stream publishing block data defined in the **StreamMap.xml** file. Publishing block data is stored in Package Store\\PkgGUID\\VerGUID\\Root.
- Icons: Targets of extension points.
- Portable Executable Headers (PE Headers): Targets of extension points that contain the base information about the image need on disk, accessed directly or through file types.
- Scripts: Download scripts directory for use throughout the publishing process.
- Icons: Targets of extension points.
- Portable Executable Headers (PE Headers): Targets of extension points that contain the base information about the image need on disk, accessed directly or through file types.
- Scripts: Download scripts directory for use throughout the publishing process.
4. Populate the Package store by doing the following:
4. Populate the Package store by doing the following:
1. Create sparse files on disk that represent the extracted package for any directories listed.
1. Create sparse files on disk that represent the extracted package for any directories listed.
2. Stage top-level files and directories under root.
2. Stage top-level files and directories under root.
All other files are created when the directory is listed as sparse on disk and streamed on demand.
All other files are created when the directory is listed as sparse on disk and streamed on demand.
5. Create the machine catalog entries. Create the **Manifest.xml** and **DeploymentConfiguration.xml** files from the package files (if no **DeploymentConfiguration.xml** file in the package a placeholder is created).
5. Create the machine catalog entries. Create the **Manifest.xml** and **DeploymentConfiguration.xml** files from the package files (if no **DeploymentConfiguration.xml** file in the package a placeholder is created).
6. Create location of the package store in the registry **HKLM\\Software\\Microsoft\\AppV\\Client\\Packages\\PkgGUID\\Versions\\VerGUID\\Catalog**.
6. Create location of the package store in the registry **HKLM\\Software\\Microsoft\\AppV\\Client\\Packages\\PkgGUID\\Versions\\VerGUID\\Catalog**.
7. Create the **Registry.dat** file from the package store to **%ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat**.
7. Create the **Registry.dat** file from the package store to **%ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat**.
8. Register the package with the App-V Kernel Mode Driver at **HKLM\\Microsoft\\Software\\AppV\\MAV**.
8. Register the package with the App-V Kernel Mode Driver at **HKLM\\Microsoft\\Software\\AppV\\MAV**.
9. Invoke scripting from the **AppxManifest.xml** or **DeploymentConfig.xml** file for Package Add timing.
9. Invoke scripting from the **AppxManifest.xml** or **DeploymentConfig.xml** file for Package Add timing.
4. Configure Connection Groups by adding and enabling or disabling.
5. Remove objects that are not published to the target (user or machine).
>[!NOTE]
> [!NOTE]
>This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).
6. Invoke background load mounting based on client configuration.
7. Packages that already have publishing information for the machine or user are immediately restored.
>[!NOTE]
> [!NOTE]
>This condition occurs as a product of removal without unpublishing with background addition of the package.
This completes an App-V package add for the publishing refresh process. The next step is publishing the package to a specific target (machine or user).
@ -444,7 +447,7 @@ During the Publishing Refresh operation, the specific publishing operation, **Pu
2. Store backup information in the user’s registry and roaming profile (Shortcut Backups).
>[!NOTE]
> [!NOTE]
>This enables restore extension points if the package is unpublished.
3. Run scripts targeted for publishing timing.

19
windows/application-management/app-v/appv-apply-the-deployment-configuration-file-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to apply the deployment configuration file by using Windows PowerShell (Windows 10)
description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10.
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/15/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to apply the deployment configuration file by using Windows PowerShell
@ -17,13 +20,13 @@ When you add or set a package to a computer running the App-V client before it's
## Apply the deployment configuration file with Windows PowerShell
>[!NOTE]
>The following example cmdlet uses the following two file paths for the package and configuration files:
>
>* C:\\Packages\\Contoso\\MyApp.appv
>* C:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml
>
>If your package and configuration files use different file paths than the example, feel free to replace them as needed.
> [!NOTE]
> The following example cmdlet uses the following two file paths for the package and configuration files:
>
> * C:\\Packages\\Contoso\\MyApp.appv
> * C:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml
>
> If your package and configuration files use different file paths than the example, feel free to replace them as needed.
To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, enter the following cmdlet:

17
windows/application-management/app-v/appv-apply-the-user-configuration-file-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to apply the user configuration file by using Windows PowerShell (Windows 10)
description: How to apply the user configuration file by using Windows PowerShell (Windows 10).
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/15/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to apply the user configuration file by using Windows PowerShell
@ -19,12 +22,12 @@ When you publish a package to a specific user, you'll also need to specify a dyn
Here's how to specify a user-specific configuration file:
>[!NOTE]
>The following example cmdlets use this example file path for its package:
>
>* C:\\Packages\\Contoso\\MyApp.appv.
>
>If your package file uses a different file path than the example, feel free to replace it as needed.
> [!NOTE]
> The following example cmdlets use this example file path for its package:
>
> * C:\\Packages\\Contoso\\MyApp.appv.
>
> If your package file uses a different file path than the example, feel free to replace it as needed.
1. Enter the following cmdlet in Windows PowerShell to add the package to the computer:

5
windows/application-management/app-v/appv-auto-batch-sequencing.md
View File

@ -1,12 +1,15 @@
---
title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
description: How to automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
author: jdeckerms
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)

5
windows/application-management/app-v/appv-auto-batch-updating.md
View File

@ -1,12 +1,15 @@
---
title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
description: How to automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
author: jdeckerms
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)

7
windows/application-management/app-v/appv-auto-clean-unpublished-packages.md
View File

@ -1,12 +1,15 @@
---
title: Automatically clean up unpublished packages on the App-V client (Windows 10)
description: How to automatically clean up any unpublished packages on your App-V client devices.
author: jdeckerms
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/15/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Automatically clean up unpublished packages on the App-V client
@ -60,4 +63,4 @@ Using Group Policy, you can turn on the **Enable automatic cleanup of unused App
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186)
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)

5
windows/application-management/app-v/appv-auto-provision-a-vm.md
View File

@ -1,12 +1,15 @@
---
title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface.
author: jdeckerms
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)

7
windows/application-management/app-v/appv-available-mdm-settings.md
View File

@ -1,12 +1,15 @@
---
title: Available Mobile Device Management (MDM) settings for App-V (Windows 10)
description: A list of the available MDM settings for App-V on Windows 10.
author: jdeckerms
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/15/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# Available Mobile Device Management (MDM) settings for App-V
@ -29,4 +32,4 @@ With Windows 10, version 1703, you can configure, deploy, and manage your App-V
|SyncStatusDescription|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncStatusDescription|String|- **0**: App-V publishing is idle.<br>- **1**: App-V connection groups publish in progress.<br>- **2**: App-V packages (non-connection group) publish in progress.<br>- **3**: App-V packages (connection group) publish in progress.<br>- **4**: App-V packages unpublish in progress.|
|SyncProgress|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncProgress|String|- **0**: App-V Sync is idle.<br>- **1**: App-V Sync is initializing.<br>- **2**: App-V Sync is in progress.<br>- **3**: App-V Sync is complete.<br>- **4**: App-V Sync requires device reboot.|
|PublishXML|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
|Policy|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|Policy|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|

27
windows/application-management/app-v/appv-capacity-planning.md
View File

@ -1,12 +1,15 @@
---
title: App-V Capacity Planning (Windows 10)
description: App-V Capacity Planning
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# App-V Capacity Planning
@ -123,11 +126,11 @@ Example: Random delay for 500 clients with 120 requests per second is *4 × 500/
Computers running the App-V client connect to the App-V publishing server to send a publishing refresh request and receive a response. Round trip response time is measured on the computer running the App-V client, while 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 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 publishing server.
> [!IMPORTANT]
> 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 publishing server.
|Scenario|Summary|
|---|---|
@ -148,11 +151,11 @@ Computers running the App-V client connect to the App-V publishing server to sen
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 streaming server:
* The number of clients streaming application packages simultaneously from a single streaming server.
* The size of the package being streamed.
* The available network bandwidth in your environment between the client and the streaming server.
> [!IMPORTANT]
> 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.
> * The size of the package being streamed.
> * The available network bandwidth in your environment between the client and the streaming server.
|Scenario|Summary|
|---|---|
@ -193,4 +196,4 @@ Although there are many fault-tolerance strategies and technologies you can use,
* [App-V supported configurations](appv-supported-configurations.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)
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)

169
windows/application-management/app-v/appv-client-configuration-settings.md
View File

@ -1,12 +1,15 @@
---
---
title: About Client Configuration Settings (Windows 10)
description: About Client Configuration Settings
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# About Client Configuration Settings
@ -21,94 +24,92 @@ You can use Group Policy to configure App-V client settings by navigating to the
The following table provides information about App-V client configuration settings that can be configured through Windows PowerShell cmdlets:
| Windows PowerShell cmdlet or cmdlets,<br>**Option**<br>Type | Description | Disabled policy state keys and values |
|------------|------------|------------|------------|
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageInstallationRoot**<br>String | Specifies directory where all new applications and updates will be installed. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageSourceRoot**<br>String | Overrides source location for downloading package content. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows 10 machines connected by a metered network connection (for example, 4G). | 0 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentRetries**<br>Integer (0–99) | Specifies the number of times to retry a dropped session. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentInterval**<br>Integer (0–3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-LocationProvider**<br>String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-CertFilterForClientSsl**<br>String | Specifies the path to a valid certificate in the certificate store. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-VerifyCertificateRevocationList**<br>True (enabled); False (Disabled state) | Verifies Server certificate revocation status before streaming with HTTPS. | 0 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-SharedContentStoreMode**<br>True (enabled); False (Disabled state) | Specifies that streamed package contents will be not be saved to the local hard disk. | 0 |
| Set-AppvPublishingServer<br><br>**-Name**<br>String | Displays the name of publishing server. | Policy value not written (same as Not Configured) |
| Set-AppvPublishingServer<br><br>**-URL**<br>String | Displays the URL of publishing server. | Policy value not written (same as Not Configured) |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables global publishing refresh (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a global publishing refresh on sign in. (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshInterval**<br>Integer (0–744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, specify 0. | 0 |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
| Set-AppvPublishingServer<br><br>**-UserRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables user publishing refresh (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-UserRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a user publishing refresh on sign in. (Boolean) Word count (with spaces): 60 | False |
| Set-AppvPublishingServer<br><br>**-UserRefreshInterval**<br>Word count (with spaces): 85<br>Integer (0–744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | 0 |
| Set-AppvPublishingServer<br><br>**-UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-MigrationMode**<br>True (enabled state); False (Disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created by a previous version of App-V. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePackageScripts**<br>True (enabled); False (Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | |
| Set-AppvClientConfiguration<br><br>**-RoamingFileExclusions**<br>String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. For example, ```/ROAMINGFILEEXCLUSIONS='desktop;my pictures'``` | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-RoamingRegistryExclusions**<br>String | Specifies the registry paths that do not roam with a user profile. For example, ```/ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients``` | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-IntegrationRootUser**<br>String | Specifies the location to create symbolic links associated with the current version of a per-user published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links will not be used when you publish the package. For example, ```%localappdata%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-IntegrationRootGlobal**<br>String | Specifies the location to create symbolic links associated with the current version of a globally published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links will not be used when you publish the package. For example, ```%allusersprofile%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-VirtualizableExtensions**<br>String | A comma-delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command-line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a locally installed application inside a virtual environment with virtualized applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Policy value not written |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingEnabled**<br>True (enabled); False (Disabled state) | Returns information to a reporting server. | False |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingServerURL**<br>String | Specifies the location on the reporting server where client information is saved. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingDataCacheLimit**<br>Integer \[0–1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingStartTime**<br>Integer (0–23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0–23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22.<br>**Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingInterval**<br>Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This can help to prevent collisions on the server. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | |
| Sync-AppvPublishingServer<br><br>**-HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ProcessesUsingVirtualComponents**<br>String | Specifies a list of process paths (that may contain wildcards) that are candidates for using dynamic virtualization (such as supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Empty string. |
| Windows PowerShell cmdlet or cmdlets,<br>**Option**<br>Type | Description | Disabled policy state keys and values |
|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageInstallationRoot**<br>String | Specifies directory where all new applications and updates will be installed. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-PackageSourceRoot**<br>String | Overrides source location for downloading package content. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows 10 machines connected by a metered network connection (for example, 4G). | 0 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentRetries**<br>Integer (0–99) | Specifies the number of times to retry a dropped session. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReestablishmentInterval**<br>Integer (0–3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-LocationProvider**<br>String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-CertFilterForClientSsl**<br>String | Specifies the path to a valid certificate in the certificate store. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-VerifyCertificateRevocationList**<br>True (enabled); False (Disabled state) | Verifies Server certificate revocation status before streaming with HTTPS. | 0 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-SharedContentStoreMode**<br>True (enabled); False (Disabled state) | Specifies that streamed package contents will be not be saved to the local hard disk. | 0 |
| Set-AppvPublishingServer<br><br>**-Name**<br>String | Displays the name of publishing server. | Policy value not written (same as Not Configured) |
| Set-AppvPublishingServer<br><br>**-URL**<br>String | Displays the URL of publishing server. | Policy value not written (same as Not Configured) |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables global publishing refresh (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a global publishing refresh on sign in. (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshInterval**<br>Integer (0–744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, specify 0. | 0 |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
| Set-AppvPublishingServer<br><br>**-UserRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables user publishing refresh (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-UserRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a user publishing refresh on sign in. (Boolean) Word count (with spaces): 60 | False |
| Set-AppvPublishingServer<br><br>**-UserRefreshInterval**<br>Word count (with spaces): 85<br>Integer (0–744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | 0 |
| Set-AppvPublishingServer<br><br>**-UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-MigrationMode**<br>True (enabled state); False (Disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created by a previous version of App-V. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePackageScripts**<br>True (enabled); False (Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | |
| Set-AppvClientConfiguration<br><br>**-RoamingFileExclusions**<br>String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. For example, ```/ROAMINGFILEEXCLUSIONS='desktop;my pictures'``` | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-RoamingRegistryExclusions**<br>String | Specifies the registry paths that do not roam with a user profile. For example, ```/ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients``` | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-IntegrationRootUser**<br>String | Specifies the location to create symbolic links associated with the current version of a per-user published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links will not be used when you publish the package. For example, ```%localappdata%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-IntegrationRootGlobal**<br>String | Specifies the location to create symbolic links associated with the current version of a globally published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links will not be used when you publish the package. For example, ```%allusersprofile%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-VirtualizableExtensions**<br>String | A comma-delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command-line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a locally installed application inside a virtual environment with virtualized applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Policy value not written |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingEnabled**<br>True (enabled); False (Disabled state) | Returns information to a reporting server. | False |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingServerURL**<br>String | Specifies the location on the reporting server where client information is saved. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingDataCacheLimit**<br>Integer \[0–1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingStartTime**<br>Integer (0–23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0–23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22.<br>**Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingInterval**<br>Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This can help to prevent collisions on the server. | Policy value not written (same as Not Configured) |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br><strong>-EnableDynamicVirtualization<br></strong>1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | |
| Sync-AppvPublishingServer<br><br>**-HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-ProcessesUsingVirtualComponents**<br>String | Specifies a list of process paths (that may contain wildcards) that are candidates for using dynamic virtualization (such as supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Empty string. |
## App-V client configuration settings: registry keys
The following table provides information about App-V client configuration settings that can be configured through the registry:
| **Setting name**<br>Type | Registry key value | Disabled policy state keys and values |
|---------------------------|---------------------|---------------------------------------|
| **PackageInstallationRoot**<br>String | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
| **PackageSourceRoot**<br>String | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
| **AllowHighCostLaunch**<br>True (Enabled); False (Disabled state) | Streaming\\AllowHighCostLaunch | 0 |
| **ReestablishmentRetries**<br>Integer (0–99) | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
| **ReestablishmentInterval**<br>Integer (0–3600) | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
| **LocationProvider**<br>String | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
| **CertFilterForClientSsl**<br>String | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
| **VerifyCertificateRevocationList**<br>True (Enabled); False (Disabled state) | Streaming\\VerifyCertificateRevocationList | 0 |
| **SharedContentStoreMode**<br>True (Enabled); False (Disabled state) | Streaming\\SharedContentStoreMode | 0 |
| **Name**<br>String | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
| **URL**<br>String | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
| **GlobalRefreshEnabled**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalEnabled | False |
| **GlobalRefreshOnLogon**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
| **GlobalRefreshInterval**<br>Integer (0–744) | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
| **UserRefreshEnabled**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserEnabled | False |
| **UserRefreshOnLogon**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
| **UserRefreshInterval**<br>Word count (with spaces): 85; Integer (0–744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
| **MigrationMode**<br>True(Enabled state); False (Disabled state) | Coexistence\\MigrationMode | |
| **EnablePackageScripts**<br>True (Enabled); False (Disabled state) | \\Scripting\\EnablePackageScripts | |
| **RoamingFileExclusions**<br>String | | |
| **RoamingRegistryExclusions**<br>String | Integration\\RoamingReglstryExclusions | Policy value not written (same as Not Configured) |
| **IntegrationRootUser**<br>String | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
| **IntegrationRootGlobal**<br>String | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
| **VirtualizableExtensions**<br>String | Integration\\VirtualizableExtensions | Policy value not written |
| **ReportingEnabled**<br>True (Enabled); False (Disabled state) | Reporting\\EnableReporting | False |
| **ReportingServerURL**<br>String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
| **ReportingDataCacheLimit**<br>Integer \[0–1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
| **ReportingDataBlockSize**<br>Integer \[1024–Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
| **ReportingStartTime**<br>Integer (0–23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
| **ReportingInterval**<br>Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
| **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | | |
| **ProcessesUsingVirtualComponents**<br>String | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
| **Setting name**<br>Type | Registry key value | Disabled policy state keys and values |
|--------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------|
| **PackageInstallationRoot**<br>String | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
| **PackageSourceRoot**<br>String | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
| **AllowHighCostLaunch**<br>True (Enabled); False (Disabled state) | Streaming\\AllowHighCostLaunch | 0 |
| **ReestablishmentRetries**<br>Integer (0–99) | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
| **ReestablishmentInterval**<br>Integer (0–3600) | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
| **LocationProvider**<br>String | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
| **CertFilterForClientSsl**<br>String | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
| **VerifyCertificateRevocationList**<br>True (Enabled); False (Disabled state) | Streaming\\VerifyCertificateRevocationList | 0 |
| **SharedContentStoreMode**<br>True (Enabled); False (Disabled state) | Streaming\\SharedContentStoreMode | 0 |
| **Name**<br>String | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
| **URL**<br>String | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
| **GlobalRefreshEnabled**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalEnabled | False |
| **GlobalRefreshOnLogon**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
| **GlobalRefreshInterval**<br>Integer (0–744) | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
| **UserRefreshEnabled**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserEnabled | False |
| **UserRefreshOnLogon**<br>True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
| **UserRefreshInterval**<br>Word count (with spaces): 85; Integer (0–744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
| **MigrationMode**<br>True(Enabled state); False (Disabled state) | Coexistence\\MigrationMode | |
| **EnablePackageScripts**<br>True (Enabled); False (Disabled state) | \\Scripting\\EnablePackageScripts | |
| **RoamingFileExclusions**<br>String | | |
| **RoamingRegistryExclusions**<br>String | Integration\\RoamingReglstryExclusions | Policy value not written (same as Not Configured) |
| **IntegrationRootUser**<br>String | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
| **IntegrationRootGlobal**<br>String | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
| **VirtualizableExtensions**<br>String | Integration\\VirtualizableExtensions | Policy value not written |
| **ReportingEnabled**<br>True (Enabled); False (Disabled state) | Reporting\\EnableReporting | False |
| **ReportingServerURL**<br>String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
| **ReportingDataCacheLimit**<br>Integer \[0–1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
| **ReportingDataBlockSize**<br>Integer \[1024–Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
| **ReportingStartTime**<br>Integer (0–23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
| **ReportingInterval**<br>Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
| <strong>EnableDynamicVirtualization<br></strong>1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | | |
| **ProcessesUsingVirtualComponents**<br>String | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
## Related topics
* [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
* [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)

9
windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
title: How to configure access to packages by using the Management Console (Windows 10)
description: How to configure access to packages by using the App-V Management Console.
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to configure access to packages by using the Management Console
@ -31,8 +34,8 @@ Use the following procedure to configure access to virtualized packages.
1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**.
>[!NOTE]  
>Ensure that you provide an associated domain name for the group that you are searching for.
> [!NOTE]
> Ensure that you provide an associated domain name for the group that you are searching for.
3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane.

7
windows/application-management/app-v/appv-configure-connection-groups-to-ignore-the-package-version.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/18/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to make a connection group ignore the package version
@ -63,4 +66,4 @@ For more information, see [How to manage App-V packages running on a stand-alone
## Related topics
- [Managing connection groups](appv-managing-connection-groups.md)
- [Managing connection groups](appv-managing-connection-groups.md)

5
windows/application-management/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/25/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# How to configure the client to receive package and connection groups updates from the publishing server

5
windows/application-management/app-v/appv-connect-to-the-management-console.md
View File

@ -1,12 +1,15 @@
---
title: How to connect to the Management Console (Windows 10)
description: How to Connect to the App-V Management Console.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/25/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to connect to the Management Console

7
windows/application-management/app-v/appv-connection-group-file.md
View File

@ -1,12 +1,15 @@
---
title: About the connection group file (Windows 10)
description: A summary of what the connection group file is and how to configure it.
author: MaggiePucciEvans
author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/25/2018
ms.reviewer:
manager: dansimp
ms.author: dansimp
ms.topic: article
---
# About the connection group file
@ -90,7 +93,7 @@ You can use the connection group file to configure each connection group by usin
- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, select the connection group and then select **Edit**.
>[!NOTE]
> [!NOTE]
>A package only requires priority if it's associated with more than one connection group.
- Specify package precedence within the connection group.

22
windows/application-management/app-v/appv-connection-group-virtual-environment.md
View File

@ -1,12 +1,15 @@
---
title: About the connection group virtual environment (Windows 10)
description: Overview of how the connection group virtual environment works.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 06/25/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# About the connection group virtual environment
@ -27,7 +30,20 @@ The connection group that is used is based on the order in which a package appea
Consider the following example section:
```XML
<appv:Packages><appv:PackagePackageId="A8731008-4523-4713-83A4-CD1363907160"VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"/><appv:PackagePackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"/><appv:PackagePackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"/></appv:Packages>
<appv:Packages>
<appv:Package
PackageId="A8731008-4523-4713-83A4-CD1363907160"
VersionId="E889951B-7F30-418B-A69C-B37283BC0DB9"
/>
<appv:Package
PackageId="1DC709C8-309F-4AB4-BD47-F75926D04276"
VersionId="01F1943B-C778-40AD-BFAD-AC34A695DF3C"
/>
<appv:Package
PackageId="04220DCA-EE77-42BE-A9F5-96FD8E8593F2"
VersionId="E15EFFE9-043D-4C01-BC52-AD2BD1E8BAFA"
/>
</appv:Packages>
```
Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package.
@ -67,4 +83,4 @@ When a virtualized application tries to find a specific file, App-V will first f
## Related topics
- [Managing Connection Groups](appv-managing-connection-groups.md)
- [Managing Connection Groups](appv-managing-connection-groups.md)

27
windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md
View File

@ -1,12 +1,15 @@
---
title: How to convert a package created in a previous version of App-V (Windows 10)
description: How to convert a package created in a previous version of App-V.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to convert a package created in a previous version of App-V
@ -15,7 +18,7 @@ ms.topic: article
You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade.
>[!NOTE]
>[!NOTE]
>If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell.
The package converter can only directly convert packages created by an App-V sequencer version 4.5 or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion.
@ -35,24 +38,24 @@ The App-V package converter will save the App-V 4.6 installation root folder and
2. You can enter the following cmdlets to check or convert packages:
- **Test-AppvLegacyPackage**—This cmdlet checks packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in-depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, enter the following cmdlet:
- **Test-AppvLegacyPackage**—This cmdlet checks packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in-depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, enter the following cmdlet:
```PowerShell
Test-AppvLegacyPackage -?
```
```PowerShell
Test-AppvLegacyPackage -?
```
- **ConvertFrom-AppvLegacyPackage**—This cmdlet converts packages from legacy versions to updated versions. To convert an existing package, enter the following cmdlet:
- **ConvertFrom-AppvLegacyPackage**—This cmdlet converts packages from legacy versions to updated versions. To convert an existing package, enter the following cmdlet:
```PowerShell
ConvertFrom-AppvLegacyPackage C:\contentStore C:\convertedPackages
```
```PowerShell
ConvertFrom-AppvLegacyPackage C:\contentStore C:\convertedPackages
```
In this cmdlet, `C:\contentStore` represents the location of the existing package and `C:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used.
Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default.
>[!NOTE]
>Before you specify the output directory, you must create the output directory.
> [!NOTE]
>Before you specify the output directory, you must create the output directory.
### Advanced Conversion Tips

5
windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md
View File

@ -1,12 +1,15 @@
---
title: How to create a connection croup with user-published and globally published packages (Windows 10)
description: How to create a connection croup with user-published and globally published packages.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to create a connection croup with user-published and globally published packages

5
windows/application-management/app-v/appv-create-a-connection-group.md
View File

@ -1,12 +1,15 @@
---
title: How to create a connection group (Windows 10)
description: How to create a connection group with the App-V Management Console.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to create a connection group

14
windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to create a custom configuration file by using the App-V Management Console
@ -27,13 +30,10 @@ You can create a dynamic user configuration file with the App-V Management Conso
4. Select **Advanced**, and then select **Export Configuration**. Enter a file name and select **Save**. Now you can edit the file to configure a package for a user.
>[!NOTE]  
>If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server.
> [!NOTE]
> If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enalbed and set to block downloads, you won't be able to download anything from the App-V Server.
## Related topics
- [Operations for App-V](appv-operations.md)
- [Operations for App-V](appv-operations.md)

25
windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to create a package accelerator by using Windows PowerShell (Windows 10)
description: How to create a package accelerator with Windows PowerShell.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to create a package accelerator by using Windows PowerShell
@ -24,20 +27,20 @@ App-V Package Accelerators automatically sequence large, complex applications. A
The following parameters are required to use the package accelerator cmdlet:
- *InstalledFilesPath* specifies the application installation path.
- *Installer* specifies the path to the application installer media.
- *InputPackagePath* specifies the path to the .appv package.
- *Path* specifies the output directory for the package.
- *InstalledFilesPath* specifies the application installation path.
- *Installer* specifies the path to the application installer media.
- *InputPackagePath* specifies the path to the .appv package.
- *Path* specifies the output directory for the package.
The following example cmdlet shows how you can create a package accelerator with an .appv package and the installation media:
The following example cmdlet shows how you can create a package accelerator with an .appv package and the installation media:
```PowerShell
New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>
```
```PowerShell
New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>
```
You can also use the following optional parameter with the **New-AppvPackageAccelerator** cmdlet:
You can also use the following optional parameter with the **New-AppvPackageAccelerator** cmdlet:
- *AcceleratorDescriptionFile* specifies the path to user-created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator.
- *AcceleratorDescriptionFile* specifies the path to user-created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator.

7
windows/application-management/app-v/appv-create-a-package-accelerator.md
View File

@ -1,12 +1,15 @@
---
title: How to create a package accelerator (Windows 10)
description: How to create a package accelerator.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to create a package accelerator
@ -50,7 +53,7 @@ Use the following procedure to create a package accelerator.
6. On the **Gathering Information** page, review the files that you couldn't find in the location specified by the **Installation Files** page. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page.
>[!NOTE]
> [!NOTE]
>You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard.
7. On the **Select Files** page, carefully review the detected files. Clear any file the package accelerator doesn't need to run successfully and select only the files that the application requires. When you're done, select **Next**.

7
windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to create a virtual application package using an App-V Package Accelerator
@ -37,7 +40,7 @@ Use the following procedure to create a virtual application package with the App
Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, then select **Next**.
>[!NOTE]
> [!NOTE]
>You can specify the following types of supported installation files:
> - Windows Installer files (**.msi**)
> - Cabinet files (.cab)

7
windows/application-management/app-v/appv-create-and-use-a-project-template.md
View File

@ -1,12 +1,15 @@
---
title: Create and apply an App-V project template to a sequenced App-V package (Windows 10)
description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package.
author: jdeckerms
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Create and apply an App-V project template to a sequenced App-V package
@ -24,7 +27,7 @@ You must first create and save a project template, including a virtual app packa
1. On the device running the App-V Sequencer, select **Start**, select **All Programs**, select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
>[!NOTE]
> [!NOTE]
>If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure.
2. On the **File** menu, select **Open**, select **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V Project Template, and then select **Edit** to change any of the settings or info included in the file.

20
windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md
View File

@ -1,12 +1,15 @@
---
title: Creating and managing App-V virtualized applications (Windows 10)
description: Creating and managing App-V virtualized applications
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Creating and managing App-V virtualized applications
@ -28,7 +31,7 @@ You can use the App-V Sequencer to perform the following tasks:
- 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]
> [!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 client.
- Convert existing virtual packages.
@ -93,20 +96,11 @@ The following table lists the supported shell extensions:
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 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, since App-V 5.1, but which cannot be updated on the computer running the App-V client. All other files and directories can be modified.
| File Type||||||
|---|---|---|---|---|---|
| .acm | .asa | .asp | .aspx | .ax | .bat |
| .cer | .chm | .clb | .cmd | .cnt | .cnv |
| .com | .cpl | .cpx | .crt | .dll | .drv |
| .esc | .exe | .fon | .grp | .hlp | .hta |
| .ime | .inf | .ins | .isp | .its | .js |
| .jse | .lnk | .msc | .msi | .msp | .mst |
| .mui | .nls | .ocx | .pal | .pcd | .pif |
| .reg | .scf | .scr | .sct | .shb | .shs |
| .sys | .tlb | .tsp | .url | .vb | .vbe |
| .vbs | .vsmacros | .ws | .wsf | .wsh | |
| .com | .exe | .dll | .ocx | |
## Modifying an existing virtual application package

5
windows/application-management/app-v/appv-customize-virtual-application-extensions-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
title: How to customize virtual application extensions for a specific AD group by using the Management Console (Windows 10)
description: How to customize virtual application extensions for a specific AD group by using the Management Console.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 07/10/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to customize virtual applications extensions for a specific AD group by using the Management Console

5
windows/application-management/app-v/appv-delete-a-connection-group.md
View File

@ -1,12 +1,15 @@
---
title: How to delete a connection group (Windows 10)
description: How to delete a connection group.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to delete a connection group

5
windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
title: How to delete a package in the Management Console (Windows 10)
description: How to delete a package in the Management Console.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to delete a package in the Management Console

5
windows/application-management/app-v/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -1,12 +1,15 @@
---
title: How to Deploy the App-V Databases by Using SQL Scripts (Windows 10)
description: How to Deploy the App-V Databases by Using SQL Scripts
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to deploy the App-V databases by using SQL scripts

7
windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to deploy App-V packages using electronic software distribution
@ -43,4 +46,4 @@ Use one of the following methods to publish packages to App-V client computers w
## Related topics
- [Operations for App-V](appv-operations.md)
- [Operations for App-V](appv-operations.md)

9
windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md
View File

@ -1,12 +1,15 @@
---
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to deploy the App-V server using a script
@ -520,4 +523,4 @@ To use a custom instance of Microsoft SQL Server, use these parameters:
## Related topics
* [Deploying the App-V Server](appv-deploying-the-appv-server.md)
* [Deploying the App-V Server](appv-deploying-the-appv-server.md)

11
windows/application-management/app-v/appv-deploy-the-appv-server.md
View File

@ -1,12 +1,15 @@
---
title: How to Deploy the App-V Server (Windows 10)
description: How to Deploy the App-V Server in App-V for Windows 10
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to Deploy the App-V Server (new installation)
@ -51,7 +54,7 @@ ms.topic: article
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
8. On the **Configure** page, accept the default value, **Use this local computer**.
>[!NOTE]
> [!NOTE]
>If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
9. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below.
@ -61,7 +64,7 @@ ms.topic: article
| You are using a custom database name. | Select **Custom configuration** and type the database name.<br/>The database name must be unique, or the installation will fail.|
10. On the **Configure** page, accept the default value: **Use this local computer**.
>[!NOTE]
> [!NOTE]
>If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
11. On the **Configure** (Management Server Configuration) page, specify the following:
@ -95,4 +98,4 @@ ms.topic: article
* [Deploying App-V](appv-deploying-appv.md)
* [How to install the management and reporting databases on separate computers from the management and reporting services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
* [How to install the publishing server on a remote computer](appv-install-the-publishing-server-on-a-remote-computer.md)
* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md)
* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md)

5
windows/application-management/app-v/appv-deploying-appv.md
View File

@ -1,12 +1,15 @@
---
title: Deploying App-V (Windows 10)
description: Deploying App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying App-V for Windows 10

5
windows/application-management/app-v/appv-deploying-microsoft-office-2010-wth-appv.md
View File

@ -1,12 +1,15 @@
---
title: Deploying Microsoft Office 2010 by Using App-V (Windows 10)
description: Deploying Microsoft Office 2010 by Using App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying Microsoft Office 2010 by Using App-V

105
windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md
View File

@ -1,12 +1,15 @@
---
title: Deploying Microsoft Office 2013 by Using App-V (Windows 10)
description: Deploying Microsoft Office 2013 by Using App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying Microsoft Office 2013 by Using App-V
@ -107,7 +110,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
</Configuration>
```
>[!NOTE]
> [!NOTE]
>The configuration XML is a sample XML file. This file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
The previous example of an XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications by specifying licensing in a later stage. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-xml-file), later in this topic.
@ -160,51 +163,51 @@ After you download the Office 2013 applications through the Office Deployment To
1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
* **SourcePath**: Point to the Office applications downloaded earlier.
* **ProductID**: Specify the type of licensing, as shown in the following examples:
* Subscription Licensing:
```XML
<Configuration>
<Add SourcePath= "\\server\Office 2013" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
```
In this example, the following changes were made to create a package with Subscription licensing:
* **SourcePath**: Point to the Office applications downloaded earlier.
* **ProductID**: Specify the type of licensing, as shown in the following examples:
* Subscription Licensing:
```XML
<Configuration>
<Add SourcePath= "\\server\Office 2013" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
```
In this example, the following changes were made to create a package with Subscription licensing:
* **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
* **Product ID** for Office was changed to `O365ProPlusRetail`.
* **Product ID** for Visio was changed to `VisioProRetail`.
* Volume Licensing
```XML
<Configuration>
<Add SourcePath= "\\Server\Office2013" OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
```
In this example, the following changes were made to create a package with Volume licensing:
* **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
* **Product ID** for Office was changed to `O365ProPlusRetail`.
* **Product ID** for Visio was changed to `VisioProRetail`.
* Volume Licensing
```XML
<Configuration>
<Add SourcePath= "\\Server\Office2013" OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
```
In this example, the following changes were made to create a package with Volume licensing:
* **SourcePath** is the source's path, which was changed to point to the Office applications that were downloaded earlier.
* **Product ID** for Office was changed to `ProPlusVolume`.
* **Product ID** for Visio was changed to `VisioProVolume`.
* **ExcludeApp** (optional) lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
* **PACKAGEGUID** (optional)—By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
* **SourcePath** is the source's path, which was changed to point to the Office applications that were downloaded earlier.
* **Product ID** for Office was changed to `ProPlusVolume`.
* **Product ID** for Visio was changed to `VisioProVolume`.
* **ExcludeApp** (optional) lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
* **PACKAGEGUID** (optional)—By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
>[!NOTE]
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
> [!NOTE]
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
2. Use the **/packager** command to convert the Office applications to an Office 2013 App-V package.
For example:
@ -225,11 +228,11 @@ After you download the Office 2013 applications through the Office Deployment To
After you run the **/packager** command, the following folders will appear in the directory where you specified the package should be saved:
* **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.<br>
* **WorkingDir**
* **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.<br>
* **WorkingDir**
>[!NOTE]
>To troubleshoot any issues, see the log files in the %temp% directory (default).
> [!NOTE]
>To troubleshoot any issues, see the log files in the %temp% directory (default).
3. Verify that the Office 2013 App-V package works correctly:
1. Publish the Office 2013 App-V package that you created globally to a test computer and verify that the Office 2013 shortcuts appear.
@ -378,10 +381,10 @@ To upgrade an Office 2013 package, use the Office Deployment Tool. To upgrade a
1. Create a new Office 2013 package through the Office Deployment Tool that uses the most recent Office 2013 application software. The most recent Office 2013 bits can always be obtained through the download stage of creating an Office 2013 App-V Package. The newly created Office 2013 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
>[!NOTE]
>Office App-V packages have two Version IDs:
* An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
* A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
> [!NOTE]
> Office App-V packages have two Version IDs:
> * An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
> * A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
2. Globally publish the newly created Office 2013 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2013 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.

87
windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md
View File

@ -1,12 +1,15 @@
---
title: Deploying Microsoft Office 2016 by using App-V (Windows 10)
description: Deploying Microsoft Office 2016 by using App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying Microsoft Office 2016 by using App-V
@ -92,8 +95,8 @@ After you download the Office Deployment Tool, you can use it to get the latest
The XML file included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
1. Open the sample XML file in Notepad or your favorite text editor.
2. With the sample **configuration.xml** file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the **configuration.xml** file:
1. Open the sample XML file in Notepad or your favorite text editor.
2. With the sample **configuration.xml** file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the **configuration.xml** file:
```XML
<Configuration>
@ -108,7 +111,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
</Configuration>
```
>[!NOTE]
> [!NOTE]
>The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To uncomment these lines, remove the ```<! - -``` from the beginning of the line, and the ```-- >``` from the end of the line.
The previous example of an XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016 location where Office applications will be saved. Note that the Product ID of the applications will not affect Office's final licensing. You can create Office 2016 App-V packages with various licensing from the same applications by specifying licensing in a later stage. The following table summarizes the XML file's customizable attributes and elements:
@ -121,21 +124,21 @@ The XML file included in the Office Deployment Tool specifies the product detail
| Language element | Specifies which language the applications support. | `Language ID="en-us"` |
| Version (attribute of **Add** element) | Optional. Specifies which build the package will use.<br>Defaults to latest advertised build (as defined in v32.CAB at the Office source). | `16.1.2.3` |
| SourcePath (attribute of **Add** element) | Specifies the location the applications will be saved to. | `Sourcepath = "\\Server\Office2016"` |
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Office 365 ProPlus and **Current** for Visio Pro for Office 365 and Project Online Desktop Client. <br>For more information about update channels, see [Overview of update channels for Office 365 ProPlus](https://docs.microsoft.com/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Office 365 ProPlus and **Current** for Visio Pro for Office 365 and Project Desktop Client. <br>For more information about update channels, see [Overview of update channels for Office 365 ProPlus](https://docs.microsoft.com/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
After editing the **configuration.xml** file to specify the desired product, languages, and the location where the Office 2016 applications will be saved to, you can save the configuration file under a name of your choice, such as "Customconfig.xml."
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2016 applications that will later be converted into an App-V package. The following is an example command:
`\\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml`
`\\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml`
The following table describes the example command's elements:
The following table describes the example command's elements:
| Element | Description |
|-------------------------------|--------------------------------------|
| ```\\server\Office2016``` | This is the network share location that contains the Office Deployment Tool and the custom **Configuration.xml** file, which in this example is **Customconfig.xml**. |
| ``Setup.exe`` | This is the Office Deployment Tool. |
| ```/download``` | Downloads the Office 2016 applications that you specify in the **Customconfig.xml** file. |
| ```\\server\Office2016\Customconfig.xml```| This passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After using the download command, Office applications should be found in the location specified in the configuration file, which in this example is ```\\Server\Office2016```. |
| Element | Description |
|-------------------------------|--------------------------------------|
| ```\\server\Office2016``` | This is the network share location that contains the Office Deployment Tool and the custom **Configuration.xml** file, which in this example is **Customconfig.xml**. |
| ``Setup.exe`` | This is the Office Deployment Tool. |
| ```/download``` | Downloads the Office 2016 applications that you specify in the **Customconfig.xml** file. |
| ```\\server\Office2016\Customconfig.xml```| This passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After using the download command, Office applications should be found in the location specified in the configuration file, which in this example is ```\\Server\Office2016```. |
### Convert the Office applications into an App-V package
@ -161,34 +164,34 @@ After you download the Office 2016 applications through the Office Deployment To
1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
* **SourcePath**: Change to the location where you saved the Office applications you downloaded during setup.
* **ProductID**: Specify the type of licensing, as shown in the following example:
* **SourcePath**: Change to the location where you saved the Office applications you downloaded during setup.
* **ProductID**: Specify the type of licensing, as shown in the following example:
* Subscription Licensing:
```XML
<Configuration>
<Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
```
This example made the following changes to create this Subscription Licensing package:
* Subscription Licensing:
```XML
<Configuration>
<Add SourcePath= "\\server\Office 2016" OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
```
This example made the following changes to create this Subscription Licensing package:
* **SourcePath** was changed to point to the Office applications that were downloaded earlier.
* **Product ID** for Office was changed to `O365ProPlusRetail`.
* **Product ID** for Visio was changed to `VisioProRetail`.
* **ExcludeApp** (optional): Lets you specify Office programs that you don’t want included in the App-V package created by the Office Deployment Tool. For example, you can exclude Access.
* **PACKAGEGUID** (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use **PACKAGEGUID** to specify a different package ID for each package, which allows you to publish multiple App-V packages created by the Office Deployment Tool, and then manage your published packages with the App-V Server.
* **SourcePath** was changed to point to the Office applications that were downloaded earlier.
* **Product ID** for Office was changed to `O365ProPlusRetail`.
* **Product ID** for Visio was changed to `VisioProRetail`.
* **ExcludeApp** (optional): Lets you specify Office programs that you don’t want included in the App-V package created by the Office Deployment Tool. For example, you can exclude Access.
* **PACKAGEGUID** (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use **PACKAGEGUID** to specify a different package ID for each package, which allows you to publish multiple App-V packages created by the Office Deployment Tool, and then manage your published packages with the App-V Server.
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
>[!NOTE]
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
> [!NOTE]
>Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
The following is an example packager command:
@ -209,11 +212,11 @@ After you download the Office 2016 applications through the Office Deployment To
After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
* **App-V Packages**—contains an Office 2016 App-V package and two deployment configuration files.
* **WorkingDir**
* **App-V Packages**—contains an Office 2016 App-V package and two deployment configuration files.
* **WorkingDir**
>[!NOTE]
>To troubleshoot any issues, see the log files in the %temp% directory (default).
> [!NOTE]
>To troubleshoot any issues, see the log files in the %temp% directory (default).
3. Verify that the Office 2016 App-V package works correctly:
1. Publish the Office 2016 App-V package that you created globally to a test computer and verify that the Office 2016 shortcuts appear.
@ -356,7 +359,7 @@ To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a
1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
>[!NOTE]
> [!NOTE]
>Office App-V packages have two Version IDs:
>* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
>* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.

5
windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md
View File

@ -1,12 +1,15 @@
---
title: Deploying App-V packages by using electronic software distribution (ESD)
description: Deploying App-V packages by using electronic software distribution (ESD)
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying App-V packages by using electronic software distribution (ESD)

5
windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md
View File

@ -1,12 +1,15 @@
---
title: Deploying the App-V Sequencer and configuring the client (Windows 10)
description: Deploying the App-V Sequencer and configuring the client
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying the App-V Sequencer and configuring the client

7
windows/application-management/app-v/appv-deploying-the-appv-server.md
View File

@ -1,12 +1,15 @@
---
title: Deploying the App-V Server (Windows 10)
description: Deploying the App-V Server in App-V for Windows 10
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Deploying the App-V server
@ -32,7 +35,7 @@ App-V offers the following five server components, each of which serves a specif
* **Management server.** Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server.
>[!NOTE]
> [!NOTE]
>If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you may want to take advantage of the reporting and streaming capabilities in App-V.
* **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. For more information about the management database, see [How to deploy the App-V server](appv-deploy-the-appv-server.md).
* **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. To learn how to configure the publishing server, see [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md).

5
windows/application-management/app-v/appv-deployment-checklist.md
View File

@ -1,12 +1,15 @@
---
title: App-V Deployment Checklist (Windows 10)
description: App-V Deployment Checklist
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# App-V Deployment Checklist

7
windows/application-management/app-v/appv-dynamic-configuration.md
View File

@ -1,12 +1,15 @@
---
title: About App-V Dynamic Configuration (Windows 10)
description: About App-V Dynamic Configuration
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# About App-V dynamic configuration
@ -425,7 +428,7 @@ The body of the deployment configuration file includes two sections:
</DeploymentConfiguration>
```
User Configuration: see [Dynamic User Configuration](appv-dynamic-configuration.md#dynamic-user-configuration) for more information about this section.
User Configuration: see [Dynamic User Configuration](#dynamic-user-configuration-file) for more information about this section.
Machine Configuration: The Machine Configuration section of the Deployment Configuration File configures information that can only be set for an entire machine, not a specific user on the computer, like the HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. This element can have the following four subsections.

5
windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to enable only administrators to publish packages by using an ESD

112
windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to Enable Reporting on the App-V Client by Using Windows PowerShell (Windows 10)
description: How to Enable Reporting on the App-V Client by Using Windows PowerShell
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to Enable Reporting on the App-V Client by Using Windows PowerShell
@ -18,65 +21,64 @@ Use the following procedure to configure the App-V for reporting.
**To configure the computer running the App-V client for reporting**
1. Enable the App-V client. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
1. Enable the App-V client. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings:
2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings:
<table>
<colgroup>
<col width="30%" />
<col width="70%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Setting</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>ReportingEnabled</p></td>
<td align="left"><p>Enables the client to return information to a reporting server. This setting is required for the client to collect the reporting data on the client.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ReportingServerURL</p></td>
<td align="left"><p>Specifies the location on the reporting server where client information is saved. For example, https://&lt;reportingservername&gt;:&lt;reportingportnumber&gt;.</p>
<div class="alert">
<strong>Note</strong>  
<p>This is the port number that was assigned during the Reporting Server setup</p>
</div>
<div>
 
</div></td>
</tr>
<tr class="odd">
<td align="left"><p>Reporting Start Time</p></td>
<td align="left"><p>This is set to schedule the client to automatically send the data to the server. This setting will indicate the hour at which the reporting data will start to send. It is in the 24 hour format and will take a number between 0-23.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ReportingRandomDelay</p></td>
<td align="left"><p>Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and ReportingRandomDelay and will wait the specified duration before sending data.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>ReportingInterval</p></td>
<td align="left"><p>Specifies the retry interval that the client will use to resend data to the reporting server.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ReportingDataCacheLimit</p></td>
<td align="left"><p>Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>ReportingDataBlockSize</p></td>
<td align="left"><p>Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.</p></td>
</tr>
</tbody>
</table>
<table>
<colgroup>
<col width="30%" />
<col width="70%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Setting</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>ReportingEnabled</p></td>
<td align="left"><p>Enables the client to return information to a reporting server. This setting is required for the client to collect the reporting data on the client.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ReportingServerURL</p></td>
<td align="left"><p>Specifies the location on the reporting server where client information is saved. For example, https://&lt;reportingservername&gt;:&lt;reportingportnumber&gt;.</p>
<div class="alert">
<strong>Note</strong><br/><p>This is the port number that was assigned during the Reporting Server setup</p>
</div>
<div>
 
</div></td>
</tr>
<tr class="odd">
<td align="left"><p>Reporting Start Time</p></td>
<td align="left"><p>This is set to schedule the client to automatically send the data to the server. This setting will indicate the hour at which the reporting data will start to send. It is in the 24 hour format and will take a number between 0-23.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ReportingRandomDelay</p></td>
<td align="left"><p>Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and ReportingRandomDelay and will wait the specified duration before sending data.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>ReportingInterval</p></td>
<td align="left"><p>Specifies the retry interval that the client will use to resend data to the reporting server.</p></td>
</tr>
<tr class="even">
<td align="left"><p>ReportingDataCacheLimit</p></td>
<td align="left"><p>Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>ReportingDataBlockSize</p></td>
<td align="left"><p>Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.</p></td>
</tr>
</tbody>
</table>
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** cmdlet.
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** cmdlet.

5
windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md
View File

@ -1,12 +1,15 @@
---
title: Enable the App-V in-box client (Windows 10)
description: How to enable the App-V in-box client installed with Windows 10.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Enable the App-V in-box client

5
windows/application-management/app-v/appv-evaluating-appv.md
View File

@ -1,12 +1,15 @@
---
title: Evaluating App-V (Windows 10)
description: Evaluating App-V for Windows 10
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

5
windows/application-management/app-v/appv-for-windows.md
View File

@ -1,12 +1,15 @@
---
title: Application Virtualization (App-V) (Windows 10)
description: Application Virtualization (App-V)
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Application Virtualization (App-V) for Windows 10 overview

7
windows/application-management/app-v/appv-getting-started.md
View File

@ -1,12 +1,15 @@
---
title: Getting Started with App-V (Windows 10)
description: Getting Started with App-V for Windows 10
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Getting started with App-V for Windows 10
@ -55,4 +58,4 @@ If you're new to App-V, it's a good idea to read the documentation thoroughly. B
* [Deploying App-V](appv-deploying-appv.md)
* [Operations for App-V](appv-operations.md)
* [Troubleshooting App-V](appv-troubleshooting.md)
* [Technical reference for App-V](appv-technical-reference.md)
* [Technical reference for App-V](appv-technical-reference.md)

7
windows/application-management/app-v/appv-high-level-architecture.md
View File

@ -1,12 +1,15 @@
---
title: High-level architecture for App-V (Windows 10)
description: High-level Architecture for App-V.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# High-level architecture for App-V
@ -31,4 +34,4 @@ A typical App-V implementation consists of the following elements.
## Related topics
- [Getting Started with App-V](appv-getting-started.md)
- [Getting Started with App-V](appv-getting-started.md)

5
windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell (Windows 10)
description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

31
windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services
@ -26,11 +29,11 @@ Use the following procedure to install the database server and management server
4. On the **Feature selection** page, select the components you want to install by first selecting the **Management Server Database** checkbox, then selecting **Next**.
5. On the **Installation location** page, accept the default location and select **Next**.
6. On the initial **Create new management server database** page, accept the default selections if appropriate, then select **Next**.
* If you are using a custom SQL Server instance, select **Use a custom instance** and enter the name of the instance.
* If you are using a custom database name, select **Custom configuration** and enter the database name.
* If you are using a custom SQL Server instance, select **Use a custom instance** and enter the name of the instance.
* If you are using a custom database name, select **Custom configuration** and enter the database name.
7. On the next **Create new management server database** page, select **Use a remote computer**, then enter the remote machine account using the following format: ```Domain\MachineAccount```.
>[!NOTE]
> [!NOTE]
>If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: ```Domain\AdministratorLoginName```. After that, select **Next**.
8. To start the installation, select **Install**.
@ -42,11 +45,11 @@ Use the following procedure to install the database server and management server
4. On the **Feature selection** page, select the components you want to install by first selecting the **Reporting Server Database** checkbox, then selecting **Next**.
5. On the **Installation Location** page, accept the default location and select **Next**.
6. On the initial **Create new management server database** page, accept the default selections if appropriate, then select **Next**.
* If you're using a custom SQL Server instance, select **Use a custom instance** and enter the instance name.
* If you're using a custom database name, select **Custom configuration** and enter the database name.
* If you're using a custom SQL Server instance, select **Use a custom instance** and enter the instance name.
* If you're using a custom database name, select **Custom configuration** and enter the database name.
7. On the next **Create new management server database** page, select **Use a remote computer**, and enter the remote machine account using the following format: ```Domain\MachineAccount```.
>[!NOTE]
> [!NOTE]
>If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. After that, select **Next**.
8. To start the installation, select **Install**.
@ -55,18 +58,18 @@ Use the following procedure to install the database server and management server
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 database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
```SQL
```SQL
appv\_server\_setup.exe /LAYOUT /LAYOUTDIR=”InstallationExtractionLocation”
```
```
3. After the extraction has been completed, to access the App-V database scripts and instructions readme file:
* The App-V Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
* The App-V Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
* The App-V Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management 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.
>[!NOTE]
>For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
> [!NOTE]
>For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
5. Run the scripts on the computer running Microsoft SQL Server.
@ -75,4 +78,4 @@ Use the following procedure to install the database server and management server
## Related topics
* [Deploying App-V](appv-deploying-appv.md)
* [Deploying App-V](appv-deploying-appv.md)

17
windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to install the Management Server on a Standalone Computer and Connect it to the Database
@ -22,12 +25,12 @@ To install the management server on a standalone computer and connect it to the
5. On the **Installation Location** page, accept the default location, then select **Next**.
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, then enter the computer running Microsoft SQL's machine name, such as ```SqlServerMachine```.
>[!NOTE]
>If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance**, then enter the instance's name. Specify the **SQL Server Database name** that this management server will use, such as ```AppvManagement```.
> [!NOTE]
>If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance**, then enter the instance's name. Specify the **SQL Server Database name** that this management server will use, such as ```AppvManagement```.
7. On the **Configure management server configuration** page, specify the following items:
* The AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
* The **Website Name** you want to use for the management service. Accept the default if you do not have a custom name.
* For the **Port Binding**, specify a unique port number, such as **12345**.
* The AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
* The **Website Name** you want to use for the management service. Accept the default if you do not have a custom name.
* For the **Port Binding**, specify a unique port number, such as **12345**.
8. Select **Install**.
9. To confirm that the setup has completed successfully, open a web browser and enter the following URL: https://managementserver:portnumber/Console. If the installation was successful, you should see the **Management Console** appear without any error messages or warnings displayed.
@ -37,4 +40,4 @@ To install the management server on a standalone computer and connect it to the
## Related topics
* [Deploying App-V](appv-deploying-appv.md)
* [Deploying App-V](appv-deploying-appv.md)

15
windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md
View File

@ -1,12 +1,15 @@
---
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
description: How to Install the App-V Publishing Server on a Remote Computer
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to install the publishing server on a remote computer
@ -24,16 +27,16 @@ Use the following procedure to install the publishing server on a separate compu
5. On the **Installation location** page, accept the default location, then select **Next**.
6. On the **Configure publishing server configuration** page, specify the following items:
* The URL for the management service that the publishing server will connect to. For example, **http:<span></span>//ManagementServerName:12345**.
* Specify the website name that you want to use for the publishing service. If you don't have a custom name, then use the default name.
* For the **Port binding**, specify a unique port number that will be used by App-V. For example, **54321**.
* The URL for the management service that the publishing server will connect to. For example, **http:<span></span>//ManagementServerName:12345**.
* Specify the website name that you want to use for the publishing service. If you don't have a custom name, then use the default name.
* 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, select **Install**.
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 management server console.
2. In the left pane, select **Servers**, then select **Register New Server**.
3. Enter the server name and a description (if required), then select **Add**.
9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle that package to an AD group, then publish it. Using an internet browser, open the following URL: **https://publishingserver:pubport**. If the server is running correctly, information like the following example should appear.
9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle that package to an AD group, then publish it. Using an internet browser, open the following URL: <strong>https://publishingserver:pubport</strong>. If the server is running correctly, information like the following example should appear.
```SQL
<Publishing Protocol="1.0">
@ -59,4 +62,4 @@ Use the following procedure to install the publishing server on a separate compu
## Related topics
* [Deploying App-V](appv-deploying-appv.md)
* [Deploying App-V](appv-deploying-appv.md)

9
windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md
View File

@ -1,12 +1,15 @@
---
title: How to install the Reporting Server on a standalone computer and connect it to the database (Windows 10)
description: How to install the App-V Reporting Server on a Standalone Computer and Connect it to the Database
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to install the reporting server on a standalone computer and connect it to the database
@ -27,7 +30,7 @@ Use the following procedure to install the reporting server on a standalone comp
5. On the **Installation location** page, accept the default location and select **Next**.
6. On the **Configure existing reporting database** page, select **Use a remote SQL Server**, then enter the machine name of the computer running Microsoft SQL Server. For example, you can name your computer **SqlServerMachine**.
>[!NOTE]
> [!NOTE]
>If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server instance, select **Use the default instance**. If you're using a custom Microsoft SQL Server instance, select **Use a custom instance**, then enter the name of your custom instance. Specify the **SQL Server Database name** that this reporting server will use; for example, you can name the server **AppvReporting**.
7. On the **Configure reporting server configuration** page.
@ -43,4 +46,4 @@ Use the following procedure to install the reporting server on a standalone comp
* [About App-V reporting](appv-reporting.md)
* [Deploying App-V](appv-deploying-appv.md)
* [How to enable reporting on the App-V client by using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
* [How to enable reporting on the App-V client by using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)

5
windows/application-management/app-v/appv-install-the-sequencer.md
View File

@ -1,12 +1,15 @@
---
title: Install the App-V Sequencer (Windows 10)
description: Install the App-V Sequencer
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Install the App-V Sequencer

5
windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
View File

@ -1,12 +1,15 @@
---
title: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help (Windows 10)
description: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to load the Windows PowerShell cmdlets for App-V and get cmdlet help

7
windows/application-management/app-v/appv-maintaining-appv.md
View File

@ -1,12 +1,15 @@
---
title: Maintaining App-V (Windows 10)
description: Maintaining App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Maintaining App-V
@ -33,4 +36,4 @@ Additionally, ISVs who want to explicitly virtualize or not virtualize calls on
## Other resources for maintaining App-V
* [Operations for App-V](appv-operations.md)
* [Operations for App-V](appv-operations.md)

23
windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell (Windows 10)
description: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell.
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/24/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to manage App-V packages running on a stand-alone computer by using Windows PowerShell
@ -29,8 +32,8 @@ Get-AppvClientPackage –Name "ContosoApplication" -Version 2
Use the **Add-AppvClientPackage** cmdlet to add a package to a computer.
>[!IMPORTANT]
>This example only adds a package. It does not publish the package to the user or the computer.
> [!IMPORTANT]
> This example only adds a package. It does not publish the package to the user or the computer.
For example:
@ -56,8 +59,8 @@ Publish-AppvClientPackage "ContosoApplication" -Global
## Publish a package to a specific user
>[!NOTE]  
>You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
> [!NOTE]
> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
@ -96,8 +99,8 @@ Unpublish-AppvClientPackage "ContosoApplication"
## Unpublish a package for a specific user
>[!NOTE]
>You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
> [!NOTE]
> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
An administrator can unpublish a package for a specific user by using the optional *-UserSID* parameter with the **Unpublish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
@ -124,8 +127,8 @@ For example:
Remove-AppvClientPackage "ContosoApplication"
```
>[!NOTE]
>App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).
> [!NOTE]
> App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).
## Enable only administrators to publish or unpublish packages
@ -169,4 +172,4 @@ For more information about pending tasks, see [Upgrading an in-use App-V package
## Related topics
- [Operations for App-V](appv-operations.md)
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)

5
windows/application-management/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell (Windows 10)
description: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

27
windows/application-management/app-v/appv-managing-connection-groups.md
View File

@ -1,12 +1,15 @@
---
title: Managing Connection Groups (Windows 10)
description: Managing Connection Groups
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
@ -29,40 +32,40 @@ In some previous versions of App-V, connection groups were referred to as Dynami
</colgroup>
<tbody>
<tr class="odd">
<td align="left"><p>[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)</p></td>
<td align="left"><p><a href="appv-connection-group-virtual-environment.md" data-raw-source="[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)">About the Connection Group Virtual Environment</a></p></td>
<td align="left"><p>Describes the connection group virtual environment.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[About the Connection Group File](appv-connection-group-file.md)</p></td>
<td align="left"><p><a href="appv-connection-group-file.md" data-raw-source="[About the Connection Group File](appv-connection-group-file.md)">About the Connection Group File</a></p></td>
<td align="left"><p>Describes the connection group file.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[How to Create a Connection Group](appv-create-a-connection-group.md)</p></td>
<td align="left"><p><a href="appv-create-a-connection-group.md" data-raw-source="[How to Create a Connection Group](appv-create-a-connection-group.md)">How to Create a Connection Group</a></p></td>
<td align="left"><p>Explains how to create a new connection group.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)</p></td>
<td align="left"><p><a href="appv-create-a-connection-group-with-user-published-and-globally-published-packages.md" data-raw-source="[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)">How to Create a Connection Group with User-Published and Globally Published Packages</a></p></td>
<td align="left"><p>Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[How to Delete a Connection Group](appv-delete-a-connection-group.md)</p></td>
<td align="left"><p><a href="appv-delete-a-connection-group.md" data-raw-source="[How to Delete a Connection Group](appv-delete-a-connection-group.md)">How to Delete a Connection Group</a></p></td>
<td align="left"><p>Explains how to delete a connection group.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[How to Publish a Connection Group](appv-publish-a-connection-group.md)</p></td>
<td align="left"><p><a href="appv-publish-a-connection-group.md" data-raw-source="[How to Publish a Connection Group](appv-publish-a-connection-group.md)">How to Publish a Connection Group</a></p></td>
<td align="left"><p>Explains how to publish a connection group.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>[How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)</p></td>
<td align="left"><p><a href="appv-configure-connection-groups-to-ignore-the-package-version.md" data-raw-source="[How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)">How to Make a Connection Group Ignore the Package Version</a></p></td>
<td align="left"><p>Explains how to configure a connection group to accept any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.</p></td>
</tr>
<tr class="even">
<td align="left"><p>[How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)</p></td>
<td align="left"><p><a href="appv-allow-administrators-to-enable-connection-groups.md" data-raw-source="[How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)">How to Allow Only Administrators to Enable Connection Groups</a></p></td>
<td align="left"><p>Explains how to configure the App-V client so that only administrators (not end users) can enable or disable connection groups.</p></td>
</tr></tbody>
</table>
 
@ -74,9 +77,9 @@ In some previous versions of App-V, connection groups were referred to as Dynami
- [Operations for App-V](appv-operations.md)
 
 

23
windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version.md
View File

@ -1,12 +1,15 @@
---
title: Migrating to App-V from a Previous Version (Windows 10)
description: Migrating to App-V for Windows 10 from a previous version
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
@ -52,7 +55,7 @@ You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom
</tbody>
</table>
 
### Example conversion statement
@ -158,7 +161,7 @@ ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
</tbody>
</table>
 
## Converting packages created using a prior version of App-V
@ -169,7 +172,7 @@ Use the package converter utility to upgrade virtual application packages create
**Important**  
After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful.
 
**What to know before you convert existing packages**
@ -187,7 +190,7 @@ After you convert an existing package you should test the package prior to deplo
<tbody>
<tr class="odd">
<td align="left"><p>Virtual packages using DSC are not linked after conversion.</p></td>
<td align="left"><p>Link the packages using connection groups. See [Managing Connection Groups](appv-managing-connection-groups.md).</p></td>
<td align="left"><p>Link the packages using connection groups. See <a href="appv-managing-connection-groups.md" data-raw-source="[Managing Connection Groups](appv-managing-connection-groups.md)">Managing Connection Groups</a>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Environment variable conflicts are detected during conversion.</p></td>
@ -200,7 +203,7 @@ After you convert an existing package you should test the package prior to deplo
</tbody>
</table>
 
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.
@ -230,19 +233,19 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
<tbody>
<tr class="odd">
<td align="left"><p>Review prerequisites.</p></td>
<td align="left"><p>[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software).</p></td>
<td align="left"><p><a href="appv-prerequisites.md#app-v-server-prerequisite-software" data-raw-source="[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software)">App-V Server prerequisite software</a>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Enable the App-V client.</p></td>
<td align="left"><p>[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
<td align="left"><p><a href="appv-enable-the-app-v-desktop-client.md" data-raw-source="[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)">Enable the App-V desktop client</a>.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Install App-V Server.</p></td>
<td align="left"><p>[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).</p></td>
<td align="left"><p><a href="appv-deploy-the-appv-server.md" data-raw-source="[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)">How to Deploy the App-V Server</a>.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Migrate existing packages.</p></td>
<td align="left"><p>See [Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this topic.</p></td>
<td align="left"><p>See <a href="#converting-packages-created-using-a-prior-version-of-app-v" data-raw-source="[Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v)">Converting packages created using a prior version of App-V</a> earlier in this topic.</p></td>
</tr>
</tbody>
</table>

5
windows/application-management/app-v/appv-modify-an-existing-virtual-application-package.md
View File

@ -1,12 +1,15 @@
---
title: How to Modify an Existing Virtual Application Package (Windows 10)
description: How to Modify an Existing Virtual Application Package
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

5
windows/application-management/app-v/appv-modify-client-configuration-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to Modify Client Configuration by Using Windows PowerShell (Windows 10)
description: How to Modify Client Configuration by Using Windows PowerShell
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

5
windows/application-management/app-v/appv-move-the-appv-server-to-another-computer.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

5
windows/application-management/app-v/appv-operations.md
View File

@ -1,12 +1,15 @@
---
title: Operations for App-V (Windows 10)
description: Operations for App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Operations for App-V

49
windows/application-management/app-v/appv-performance-guidance.md
View File

@ -1,12 +1,15 @@
---
title: Performance Guidance for Application Virtualization (Windows 10)
description: Performance Guidance for Application Virtualization
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
@ -86,7 +89,7 @@ Deployment Environment
</tbody>
</table>
 
Expected Configuration
@ -107,7 +110,7 @@ Expected Configuration
</tbody>
</table>
 
IT Administration
@ -124,7 +127,7 @@ IT Administration
</tbody>
</table>
 
### <a href="" id="bkmk-us"></a>Usage Scenarios
@ -144,14 +147,14 @@ As you review the two scenarios, keep in mind that these approach the extremes.
<tbody>
<tr class="odd">
<td align="left"><p>To provide the most optimal user experience, this approach leverages the capabilities of a UPM solution and requires additional image preparation and can incur some additional image management overhead.</p>
<p>The following describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) later in this topic.</p></td>
<p>The following describes many performance improvements in stateful non-persistent deployments. For more information, see <a href="#sequencing-steps-to-optimize-packages-for-publishing-performance" data-raw-source="[Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance)">Sequencing Steps to Optimize Packages for Publishing Performance</a> later in this topic.</p></td>
<td align="left"><p>The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in very costly arrays; a slight alteration has been made to the approach. Do not pre-configure user-targeted virtual application packages in the base image.</p>
<p>The impact of this alteration is detailed in the [User Experience Walk-through](#bkmk-uewt) section of this document.</p></td>
<p>The impact of this alteration is detailed in the <a href="#bkmk-uewt" data-raw-source="[User Experience Walk-through](#bkmk-uewt)">User Experience Walk-through</a> section of this document.</p></td>
</tr>
</tbody>
</table>
 
### <a href="" id="bkmk-pe"></a>Preparing your Environment
@ -174,9 +177,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>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).</p></li>
<li><p>Enable the App-V client as described in <a href="appv-enable-the-app-v-desktop-client.md" data-raw-source="[Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md)">Enable the App-V in-box client</a>.</p></li>
<li><p>Enable 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 [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).</p></li>
<li><p>Configure for Shared Content Store (SCS) mode. For more information see <a href="appv-deploying-the-appv-sequencer-and-client.md" data-raw-source="[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)">Deploying the App-V Sequencer and Configuring the Client</a>.</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>
@ -194,9 +197,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>Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).</p></li>
<li><p>Enable the App-V client as described in <a href="appv-enable-the-app-v-desktop-client.md" data-raw-source="[Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md)">Enable the App-V in-box client</a>.</p></li>
<li><p>Enable 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 [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).</p></li>
<li><p>Configure for Shared Content Store (SCS) mode. For more information see <a href="appv-deploying-the-appv-sequencer-and-client.md" data-raw-source="[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)">Deploying the App-V Sequencer and Configuring the Client</a>.</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>
@ -207,7 +210,7 @@ The following table displays the required steps to prepare the base image and th
</tbody>
</table>
 
**Configurations** - For critical App-V Client configurations and for a little more context and how-to, review the following information:
@ -228,7 +231,7 @@ The following table displays the required steps to prepare the base image and th
<tr class="odd">
<td align="left"><p>Shared Content Store (SCS) Mode</p>
<ul>
<li><p>Configurable in Windows PowerShell with `Set-AppvClientConfiguration -SharedContentStoreMode 1`<br>or configurable with Group Policy, as described in [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).</p></li>
<li><p>Configurable in Windows PowerShell with <code>Set-AppvClientConfiguration -SharedContentStoreMode 1</code><br>or configurable with Group Policy, as described in <a href="appv-deploying-the-appv-sequencer-and-client.md" data-raw-source="[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)">Deploying the App-V Sequencer and Configuring the Client</a>.</p></li>
</ul></td>
<td align="left"><p>When running the shared content store only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM).</p>
<p>This helps to conserve local storage and minimize disk I/O per second (IOPS).</p></td>
@ -259,7 +262,7 @@ The following table displays the required steps to prepare the base image and th
</tbody>
</table>
 
### Configure UE-V solution for App-V Approach
@ -285,7 +288,7 @@ UE-V will only support removing the .lnk file type from the exclusion list in th
**Important**  
This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
 
Using the Microsoft Registry Editor (regedit.exe), navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **UEV** \\ **Agent** \\ **Configuration** \\ **ExcludedFileTypes** and remove **.lnk** from the excluded file types.
@ -308,7 +311,7 @@ To enable an optimized login experience, for example the App-V approach for the
App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver does not handle UPD selected folders.
 
- Capturing changes to the locations, which constitute the user integrations, prior to session logoff.
@ -401,7 +404,7 @@ This following is a step-by-step walk-through of the App-V and UPM operations an
</tbody>
</table>
 
<table>
<colgroup>
@ -426,7 +429,7 @@ This following is a step-by-step walk-through of the App-V and UPM operations an
</tbody>
</table>
 
### <a href="" id="bkmk-plc"></a>Impact to Package Life Cycle
@ -513,7 +516,7 @@ Several App-V features facilitate new scenarios or enable new customer deploymen
</tbody>
</table>
 
### Removing FB1
@ -552,7 +555,7 @@ Removing FB1 does not require the original application installer. After completi
**Note**  
This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file.
 
<table>
<colgroup>
@ -579,7 +582,7 @@ Removing FB1 does not require the original application installer. After completi
</tbody>
</table>
 
### Creating a new virtual application package on the sequencer
@ -616,7 +619,7 @@ When publishing a virtual application package, the App-V Client will detect if a
</tbody>
</table>
 
### Disabling a Dynamic Configuration by using Windows PowerShell
@ -666,7 +669,7 @@ For documentation on How to Apply a Dynamic Configuration, see:
</tbody>
</table>
 
### Determining what virtual fonts exist in the package

5
windows/application-management/app-v/appv-planning-checklist.md
View File

@ -1,12 +1,15 @@
---
title: App-V Planning Checklist (Windows 10)
description: App-V Planning Checklist
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# App-V Planning Checklist

5
windows/application-management/app-v/appv-planning-folder-redirection-with-appv.md
View File

@ -1,12 +1,15 @@
---
title: Planning to Use Folder Redirection with App-V (Windows 10)
description: Planning to Use Folder Redirection with App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning to Use Folder Redirection with App-V

5
windows/application-management/app-v/appv-planning-for-appv-server-deployment.md
View File

@ -1,12 +1,15 @@
---
title: Planning for the App-V Server Deployment (Windows 10)
description: Planning for the App-V 5.1 Server Deployment
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning for the App-V server deployment

5
windows/application-management/app-v/appv-planning-for-appv.md
View File

@ -1,12 +1,15 @@
---
title: Planning for App-V (Windows 10)
description: Planning for App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning for App-V

9
windows/application-management/app-v/appv-planning-for-high-availability-with-appv.md
View File

@ -1,12 +1,15 @@
---
title: Planning for High Availability with App-V Server
description: Planning for High Availability with App-V Server
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning for high availability with App-V Server
@ -84,8 +87,8 @@ Use the following steps to modify the connection string to include ```failover p
2. Navigate to **HKEY\_LOCAL\_MACHINE** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService**.
3. Modify the **MANAGEMENT\_SQL\_CONNECTION\_STRING** value with the ```failover partner = <server2>``` value.
4. Restart management service using the IIS console.
>[!NOTE]
>Database Mirroring is on the list of [deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>) due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012.
> [!NOTE]
>Database Mirroring is on the list of [deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>) due to the **AlwaysOn** feature available starting with Microsoft SQL Server 2012.
Click any of the following links for more information:

5
windows/application-management/app-v/appv-planning-for-sequencer-and-client-deployment.md
View File

@ -1,12 +1,15 @@
---
title: Planning for the App-V Sequencer and Client Deployment (Windows 10)
description: Planning for the App-V Sequencer and Client Deployment
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning for the App-V Sequencer and Client Deployment

13
windows/application-management/app-v/appv-planning-for-using-appv-with-office.md
View File

@ -1,12 +1,15 @@
---
title: Planning for Deploying App-V with Office (Windows 10)
description: Planning for Using App-V with Office
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning for deploying App-V with Office
@ -87,11 +90,11 @@ To bypass the auto-registration operation for native Word 2010, follow these ste
1. Exit Word 2010.
2. Start the Registry Editor by doing the following:
* In Windows 7k, select **Start**, type **regedit** in the Start Search box, then select the Enter key.
* In Windows 7k, select **Start**, type **regedit** in the Start Search box, then select the Enter key.
* In Windows 8.1 or Windows 10, enter **regedit**, select **Enter** on the Start page, then select the Enter key.
* In Windows 8.1 or Windows 10, enter **regedit**, select **Enter** on the Start page, then select the Enter key.
If you're prompted for an administrator password, enter the password. If you're prompted for a confirmation, select **Continue**.
If you're prompted for an administrator password, enter the password. If you're prompted for a confirmation, select **Continue**.
3. Locate and then select the following registry subkey:
``` syntax
@ -136,4 +139,4 @@ The Office 2013 or Office 2016 App-V package supports the following integration
* [Deploying Microsoft Office 2016 by Using App-V](appv-deploying-microsoft-office-2016-with-appv.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 Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)

7
windows/application-management/app-v/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
View File

@ -1,12 +1,15 @@
---
title: Planning to Deploy App-V with an Electronic Software Distribution System (Windows 10)
description: Planning to Deploy App-V with an Electronic Software Distribution System
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning to Deploy App-V with an electronic software distribution system
@ -30,4 +33,4 @@ Review the following component and architecture requirements options that apply
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
* [How to deploy App-V packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
* [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
* [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)

5
windows/application-management/app-v/appv-planning-to-deploy-appv.md
View File

@ -1,12 +1,15 @@
---
title: Planning to Deploy App-V (Windows 10)
description: Planning to Deploy App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Planning to Deploy App-V for Windows 10

5
windows/application-management/app-v/appv-preparing-your-environment.md
View File

@ -1,12 +1,15 @@
---
title: Preparing Your Environment for App-V (Windows 10)
description: Preparing Your Environment for App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Preparing your environment for App-V

7
windows/application-management/app-v/appv-prerequisites.md
View File

@ -1,12 +1,15 @@
---
title: App-V Prerequisites (Windows 10)
description: App-V Prerequisites
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/18/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# App-V for Windows 10 prerequisites
@ -160,4 +163,4 @@ What to know before installing the prerequisites:
## Related topics
* [Planning for App-V](appv-planning-for-appv.md)
* [App-V Supported Configurations](appv-supported-configurations.md)
* [App-V Supported Configurations](appv-supported-configurations.md)

5
windows/application-management/app-v/appv-publish-a-connection-group.md
View File

@ -1,12 +1,15 @@
---
title: How to Publish a Connection Group (Windows 10)
description: How to Publish a Connection Group
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to Publish a Connection Group

11
windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 09/27/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# How to publish a package by using the Management console
@ -15,8 +18,8 @@ ms.topic: article
Use the following procedure to publish an App-V package. Once you publish a package, computers 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.
> [!NOTE]
> The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3.
## Publish an App-V package
@ -43,4 +46,4 @@ Use the following procedure to publish an App-V package. Once you publish a pack
## Related topics
* [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)
* [How to configure access to packages by using the Management console](appv-configure-access-to-packages-with-the-management-console.md)

5
windows/application-management/app-v/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

116
windows/application-management/app-v/appv-release-notes-for-appv-for-windows-1703.md
View File

@ -1,12 +1,15 @@
---
title: Release Notes for App-V for Windows 10, version 1703 (Windows 10)
description: A list of known issues and workarounds for App-V running on Windows 10, version 1703.
author: jdeckerms
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
@ -25,7 +28,7 @@ The following are known issues and workarounds for Application Virtualization (A
<tbody>
<tr>
<td>Unable to manually create a system-owned folder needed for the <code>set-AppVClientConfiguration</code> PowerShell cmdlet when using the <i>PackageInstallationRoot</i>, <i>IntegrationRootUser</i>, or <i>IntegrationRootGlobal</i> parameters.</td>
<td>Don't create this file manually, instead let the <code>Add-AppVClientPackage</code> cmdlet auto-generate it.</td>
<td>Don&#39;t create this file manually, instead let the <code>Add-AppVClientPackage</code> cmdlet auto-generate it.</td>
</tr>
<tr>
<td>Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands.</td>
@ -33,71 +36,70 @@ The following are known issues and workarounds for Application Virtualization (A
</tr>
<tr>
<td>Unable to modify the locale for auto-sequencing.</td>
<td>Open the <code>C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml</code> file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: <strong>es-ES</strong>.</td>
<td>Open the <code>C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml</code> file and include the language code for your locale. For example, if you wanted Spanish (Spain), you&#39;d use: <strong>es-ES</strong>.</td>
</tr>
<tr>
<td>Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the <strong>Settings > Apps> Default Apps</strong> area.</td>
<td>Filetype and protocol handlers aren&#39;t registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the <strong>Settings &gt; Apps&gt; Default Apps</strong> area.</td>
<td>The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the <strong>&lt;appv:Extensions&gt;</strong> tag:
<pre><code>
&lt;appv:Extension Category="AppV.URLProtocol"&gt;
&lt;appv:URLProtocol&gt;
&lt;appv:Name&gt;ftp&lt;/appv:Name&gt;
&lt;appv:ApplicationURLProtocol&gt;
&lt;appv:DefaultIcon&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0&lt;/appv:DefaultIcon&gt;
&lt;appv:ShellCommands&gt;
&lt;appv:DefaultCommand&gt;open&lt;/appv:DefaultCommand&gt;
&lt;appv:ShellCommand&gt;
&lt;appv:ApplicationId&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe&lt;/appv:ApplicationId&gt;
&lt;appv:Name&gt;open&lt;/appv:Name&gt;
&lt;appv:CommandLine&gt;"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"&lt;/appv:CommandLine&gt;
&lt;appv:DdeExec&gt;
&lt;appv:DdeCommand /&gt;
&lt;/appv:DdeExec&gt;
&lt;/appv:ShellCommand&gt;
&lt;/appv:ShellCommands&gt;
&lt;/appv:ApplicationURLProtocol&gt;
&lt;/appv:URLProtocol&gt;
&lt;appv:URLProtocol&gt;
&lt;appv:Name&gt;ftp&lt;/appv:Name&gt;
&lt;appv:ApplicationURLProtocol&gt;
&lt;appv:DefaultIcon&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0&lt;/appv:DefaultIcon&gt;
&lt;appv:ShellCommands&gt;
&lt;appv:DefaultCommand&gt;open&lt;/appv:DefaultCommand&gt;
&lt;appv:ShellCommand&gt;
&lt;appv:ApplicationId&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe&lt;/appv:ApplicationId&gt;
&lt;appv:Name&gt;open&lt;/appv:Name&gt;
&lt;appv:CommandLine&gt;"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"&lt;/appv:CommandLine&gt;
&lt;appv:DdeExec&gt;
&lt;appv:DdeCommand /&gt;
&lt;/appv:DdeExec&gt;
&lt;/appv:ShellCommand&gt;
&lt;/appv:ShellCommands&gt;
&lt;/appv:ApplicationURLProtocol&gt;
&lt;/appv:URLProtocol&gt;
&lt;/appv:Extension&gt;
&lt;appv:Extension Category="AppV.URLProtocol"&gt;
&lt;appv:URLProtocol&gt;
&lt;appv:Name&gt;http&lt;/appv:Name&gt;
&lt;appv:ApplicationURLProtocol&gt;
&lt;appv:DefaultIcon&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0&lt;/appv:DefaultIcon&gt;
&lt;appv:ShellCommands&gt;
&lt;appv:DefaultCommand&gt;open&lt;/appv:DefaultCommand&gt;
&lt;appv:ShellCommand&gt;
&lt;appv:ApplicationId&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe&lt;/appv:ApplicationId&gt;
&lt;appv:Name&gt;open&lt;/appv:Name&gt;
&lt;appv:CommandLine&gt;"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"&lt;/appv:CommandLine&gt;
&lt;appv:DdeExec&gt;
&lt;appv:DdeCommand /&gt;
&lt;/appv:DdeExec&gt;
&lt;/appv:ShellCommand&gt;
&lt;/appv:ShellCommands&gt;
&lt;/appv:ApplicationURLProtocol&gt;
&lt;/appv:URLProtocol&gt;
&lt;appv:URLProtocol&gt;
&lt;appv:Name&gt;http&lt;/appv:Name&gt;
&lt;appv:ApplicationURLProtocol&gt;
&lt;appv:DefaultIcon&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0&lt;/appv:DefaultIcon&gt;
&lt;appv:ShellCommands&gt;
&lt;appv:DefaultCommand&gt;open&lt;/appv:DefaultCommand&gt;
&lt;appv:ShellCommand&gt;
&lt;appv:ApplicationId&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe&lt;/appv:ApplicationId&gt;
&lt;appv:Name&gt;open&lt;/appv:Name&gt;
&lt;appv:CommandLine&gt;"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"&lt;/appv:CommandLine&gt;
&lt;appv:DdeExec&gt;
&lt;appv:DdeCommand /&gt;
&lt;/appv:DdeExec&gt;
&lt;/appv:ShellCommand&gt;
&lt;/appv:ShellCommands&gt;
&lt;/appv:ApplicationURLProtocol&gt;
&lt;/appv:URLProtocol&gt;
&lt;/appv:Extension&gt;
&lt;appv:Extension Category="AppV.URLProtocol"&gt;
&lt;appv:URLProtocol&gt;
&lt;appv:Name&gt;https&lt;/appv:Name&gt;
&lt;appv:ApplicationURLProtocol&gt;
&lt;appv:DefaultIcon&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0&lt;/appv:DefaultIcon&gt;
&lt;appv:ShellCommands&gt;
&lt;appv:DefaultCommand&gt;open&lt;/appv:DefaultCommand&gt;
&lt;appv:ShellCommand&gt;
&lt;appv:ApplicationId&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe&lt;/appv:ApplicationId&gt;
&lt;appv:Name&gt;open&lt;/appv:Name&gt;
&lt;appv:CommandLine&gt;"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"&lt;/appv:CommandLine&gt;
&lt;appv:DdeExec&gt;
&lt;appv:DdeCommand /&gt;
&lt;/appv:DdeExec&gt;
&lt;/appv:ShellCommand&gt;
&lt;/appv:ShellCommands&gt;
&lt;/appv:ApplicationURLProtocol&gt;
&lt;/appv:URLProtocol&gt;
&lt;appv:URLProtocol&gt;
&lt;appv:Name&gt;https&lt;/appv:Name&gt;
&lt;appv:ApplicationURLProtocol&gt;
&lt;appv:DefaultIcon&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0&lt;/appv:DefaultIcon&gt;
&lt;appv:ShellCommands&gt;
&lt;appv:DefaultCommand&gt;open&lt;/appv:DefaultCommand&gt;
&lt;appv:ShellCommand&gt;
&lt;appv:ApplicationId&gt;[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe&lt;/appv:ApplicationId&gt;
&lt;appv:Name&gt;open&lt;/appv:Name&gt;
&lt;appv:CommandLine&gt;"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"&lt;/appv:CommandLine&gt;
&lt;appv:DdeExec&gt;
&lt;appv:DdeCommand /&gt;
&lt;/appv:DdeExec&gt;
&lt;/appv:ShellCommand&gt;
&lt;/appv:ShellCommands&gt;
&lt;/appv:ApplicationURLProtocol&gt;
&lt;/appv:URLProtocol&gt;
&lt;/appv:Extension&gt;
</code></pre>
</td>
</code></pre><br/> </td>
</tr>
</tbody>
</table>

11
windows/application-management/app-v/appv-release-notes-for-appv-for-windows.md
View File

@ -1,12 +1,15 @@
---
title: Release Notes for App-V for Windows 10, version 1607 (Windows 10)
description: A list of known issues and workarounds for App-V running on Windows 10, version 1607.
author: jdeckerms
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
# Release Notes for App-V for Windows 10, version 1607
@ -33,7 +36,7 @@ MSI packages that were generated using an App-V sequencer from previous versions
4. From an elevated Windows PowerShell prompt, navigate to the following folder:
&lt;Windows Kits 10 installation folder&gt;**\Microsoft Application Virtualization\Sequencer\**
&lt;Windows Kits 10 installation folder&gt;**\Microsoft Application Virtualization\Sequencer\\**
By default, this path will be:<br>**C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer**
@ -134,8 +137,8 @@ The InsertVersionInfo.sql script is not required for versions of the App-V manag
The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340).
>[!IMPORTANT] 
>**Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3.
> [!IMPORTANT]
> **Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3.
## Microsoft Visual Studio 2012 not supported
App-V doesn't support Visual Studio 2012.

21
windows/application-management/app-v/appv-reporting.md
View File

@ -1,12 +1,15 @@
---
title: About App-V Reporting (Windows 10)
description: About App-V Reporting
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/16/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# About App-V reporting
@ -21,15 +24,15 @@ The following list displays the end–to-end high-level workflow for reporting i
1. The App-V Reporting server requires the following things:
* Internet Information Service (IIS) web server role
* Windows Authentication role (under **IIS / Security**)
* SQL Server installed and running with SQL Server Reporting Services (SSRS)
* Internet Information Service (IIS) web server role
* Windows Authentication role (under **IIS / Security**)
* SQL Server installed and running with SQL Server Reporting Services (SSRS)
To confirm SQL Server Reporting Services is running, enter <https://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 appear.
To confirm SQL Server Reporting Services is running, enter <https://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 appear.
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 [Application Virtualization SSRS Reports](https://www.microsoft.com/en-us/download/details.aspx?id=42630).
>[!NOTE]
> [!NOTE]
>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 Windows PowerShell module using **Import-Module AppvClient** as administrator, enable App-V client reporting. This sample Windows PowerShell command enables App-V reporting:
@ -43,7 +46,7 @@ The following list displays the end–to-end high-level workflow for reporting i
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, which then notifies the App-V client.
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
>[!NOTE]
> [!NOTE]
>By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
@ -88,7 +91,7 @@ Yes. Besides manually sending reporting using Windows PowerShell cmdlets (**Send
For a complete list of client configuration settings, go to [About client configuration settings](appv-client-configuration-settings.md) and look for the following entries: **ReportingEnabled**, **ReportingServerURL**, **ReportingDataCacheLimit**, **ReportingDataBlockSize**, **ReportingStartTime**, **ReportingRandomDelay**, **ReportingInterval**.
* Using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.
>[!NOTE]
> [!NOTE]
>Group Policy settings override local settings configured using Windows PowerShell.
## App-V Client reporting
@ -212,4 +215,4 @@ You should also ensure that the reporting server web service’s **Maximum Concu
## Related topics
* [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)
* [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)

5
windows/application-management/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 03/08/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

9
windows/application-management/app-v/appv-security-considerations.md
View File

@ -1,12 +1,15 @@
---
title: App-V Security Considerations (Windows 10)
description: App-V Security Considerations
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/16/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# App-V security considerations
@ -53,7 +56,7 @@ No groups are created automatically during App-V setup. You should create the fo
Consider the following additional information:
* Access to the package shares: If a share exists on the same computer as the management Server, the **Network** service requires read access to the share. In addition, each App-V client computer must have read access to the package share.
>[!NOTE]
> [!NOTE]
>In previous versions of App-V, package share was referred to as content share.
* 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.
@ -69,4 +72,4 @@ During App-V setup, setup log files are created in the **%temp%** folder of the
## Related topics
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)

13
windows/application-management/app-v/appv-sequence-a-new-application.md
View File

@ -1,12 +1,15 @@
---
title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
description: How to manually sequence a new app using the App-V Sequencer
author: jdeckerms
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/16/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)
@ -52,7 +55,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
5. On the **Select Installer** page, select **Browse** and specify the installation file for the application.
>[!NOTE]
> [!NOTE]
>If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then select **Next**.
@ -70,7 +73,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then select **Run All**. To run specific programs, select the program or programs, and then select **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run.
>[!NOTE]
> [!NOTE]
>To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
Select **Next**.
@ -86,7 +89,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then select **Next**.
>[!NOTE]
> [!NOTE]
>If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened. After that, depending on how the background loading is configured, it will load the rest of the application.
13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. After that, select **Next**.
@ -150,7 +153,7 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
13. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all applications to run. After all applications have run, close each application. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Select **Next**.
>[!NOTE]
> [!NOTE]
>If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, select **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
14. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box, and then select the operating systems that can run this package. Select **Next**.

15
windows/application-management/app-v/appv-sequence-a-package-with-powershell.md
View File

@ -1,12 +1,15 @@
---
title: How to sequence a package by using Windows PowerShell (Windows 10)
description: How to sequence a package by using Windows PowerShell
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
@ -17,10 +20,10 @@ ms.date: 04/19/2017
Use the following procedure to create a new App-V package using Windows PowerShell.
> [!NOTE]  
> [!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 Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
 
**To create a new virtual application by using Windows PowerShell**
1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
@ -62,8 +65,8 @@ The following list displays additional optional parameters that can be used with
In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
>[!IMPORTANT]
>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
> [!IMPORTANT]
> If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
## Related topics
@ -71,4 +74,4 @@ In Windows 10, version 1703, running the new-appvsequencerpackage or the update-
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).

7
windows/application-management/app-v/appv-supported-configurations.md
View File

@ -1,12 +1,15 @@
---
title: App-V Supported Configurations (Windows 10)
description: App-V Supported Configurations
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/16/2018
ms.reviewer:
manager: dansimp
ms.author: lomayor
ms.topic: article
---
# App-V Supported Configurations
@ -118,4 +121,4 @@ The App-V client works with System Center Configuration Manager versions startin
## Related topics
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
* [App-V prerequisites](appv-prerequisites.md)
* [App-V prerequisites](appv-prerequisites.md)

5
windows/application-management/app-v/appv-technical-reference.md
View File

@ -1,12 +1,15 @@
---
title: Technical Reference for App-V (Windows 10)
description: Technical Reference for App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

5
windows/application-management/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
View File

@ -1,12 +1,15 @@
---
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: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

5
windows/application-management/app-v/appv-troubleshooting.md
View File

@ -1,12 +1,15 @@
---
title: Troubleshooting App-V (Windows 10)
description: Troubleshooting App-V
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---

7
windows/application-management/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md
View File

@ -1,12 +1,15 @@
---
title: Upgrading to App-V for Windows 10 from an existing installation (Windows 10)
description: Upgrading to App-V for Windows 10 from an existing installation
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
# Upgrading to App-V for Windows 10 from an existing installation
@ -96,4 +99,4 @@ Type the following cmdlet in a Windows PowerShell window:
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).

9
windows/application-management/app-v/appv-using-the-client-management-console.md
View File

@ -1,12 +1,15 @@
---
title: Using the App-V Client Management Console (Windows 10)
description: Using the App-V Client Management Console
author: MaggiePucciEvans
author: lomayor
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 04/19/2017
ms.reviewer:
manager: dansimp
ms.author: lomayor
---
@ -21,8 +24,8 @@ This topic provides information about using the Application Virtualization (App-
The client management console is separate from the App-V client itself. You can download the client management console from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41186).
> [!NOTE]
To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
> [!NOTE]
> To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
## Options for managing the App-V client

Some files were not shown because too many files have changed in this diff Show More