From b9051ed7ac7a1004c4d75d1f9dfa3e0974c04dec Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 10 Jul 2018 14:29:36 -0700 Subject: [PATCH 01/33] Next round start --- .../app-v/appv-delete-a-connection-group.md | 24 ++++++++----------- ...e-a-package-with-the-management-console.md | 21 +++++++--------- ...ctronic-software-distribution-solutions.md | 3 +-- 3 files changed, 20 insertions(+), 28 deletions(-) diff --git a/windows/application-management/app-v/appv-delete-a-connection-group.md b/windows/application-management/app-v/appv-delete-a-connection-group.md index b6e27aece2..5ce582a4f3 100644 --- a/windows/application-management/app-v/appv-delete-a-connection-group.md +++ b/windows/application-management/app-v/appv-delete-a-connection-group.md @@ -1,6 +1,6 @@ --- -title: How to Delete a Connection Group (Windows 10) -description: How to Delete a Connection Group +title: How to delete a connection group (Windows 10) +description: How to delete a connection group. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,27 +8,23 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to delete a connection group - -# How to Delete a Connection Group - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 Use the following procedure to delete an existing App-V connection group. -**To delete a connection group** +## Delete a connection group -1. Open the App-V Management Console and select **CONNECTION GROUPS**. +1. Open the App-V Management Console and select **CONNECTION GROUPS**. -2. Right-click the connection group to be removed, and select **delete**. +2. Right-click the connection group to be removed and select **delete**. ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Related topics -[Operations for App-V](appv-operations.md) - -[Managing Connection Groups](appv-managing-connection-groups.md) +- [Operations for App-V](appv-operations.md) +- [Managing connection groups](appv-managing-connection-groups.md) diff --git a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md index 0a3464836a..3b66608534 100644 --- a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md +++ b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md @@ -1,6 +1,6 @@ --- -title: How to Delete a Package in the Management Console (Windows 10) -description: How to Delete a Package in the Management Console +title: How to delete a package in the Management Console (Windows 10) +description: How to delete a package in the Management Console. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,25 +8,22 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to delete a package in the Management Console - -# How to Delete a Package in the Management Console - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 Use the following procedure to delete an App-V package. -**To delete a package in the Management Console** +## Delete a package in the Management Console -1. To view the package you want to delete, open the App-V Management Console and select **Packages**. Select the package to be removed. +1. To view the package you want to delete, open the App-V Management Console and select **Packages**. Select the package to be removed. -2. Click or right-click the package. Select **Delete** to remove the package. +2. Select or right-click the package, then select **Delete** to remove the package. ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Related topics -[Operations for App-V](appv-operations.md) +- [Operations for App-V](appv-operations.md) diff --git a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md index 439a1617b9..f22925c33f 100644 --- a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md @@ -11,8 +11,7 @@ ms.date: 04/19/2017 # How to deploy App-V packages using electronic software distribution -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients. From c435e196e161be7c80ee16d9d7e082e9891d9bcb Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Wed, 11 Jul 2018 16:46:30 -0700 Subject: [PATCH 02/33] Edited ESD article --- ...ctronic-software-distribution-solutions.md | 31 ++++++++++--------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md index f22925c33f..3bb1e8a8c5 100644 --- a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md @@ -1,6 +1,6 @@ --- -title: How to deploy App-V Packages Using Electronic Software Distribution (Windows 10) -description: How to deploy App-V Packages Using Electronic Software Distribution +title: How to deploy App-V packages using electronic software distribution (Windows 10) +description: How to deploy App-V packages using electronic software distribution. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,37 +8,38 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - # How to deploy App-V packages using electronic software distribution >Applies to: Windows 10, version 1607 You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients. -For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md). +For component requirements and options for using an ESD to deploy App-V packages, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md). Use one of the following methods to publish packages to App-V client computers with an ESD: +- Use the functionality in a third-party ESD. +- Install the application on the target client computer with the associated Windows Installer (.msi) file that's created when you initially sequence the application. The .msi file contains the associated App-V package file information used to configure a package and copies the required package files to the client. +- Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md). + | Method | Description | -| - | - | -| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.| +|---|---| +| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.| | Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. | -| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).| +| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).| -  +## Deploy App-V packages with an ESD -**To deploy App-V packages by using an ESD** +1. Install the App-V Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md). -1. Install the App-V Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md). +2. Use the App-V Sequencer to create a virtual application. To learn more about creating virtual applications, see [Creating and managing App-V virtualized applications](appv-creating-and-managing-virtualized-applications.md). -2. Use the App-V Sequencer to create virtual application. For information about creating a virtual application, see [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md). - -3. After you create the virtual application, deploy the package by using your ESD solution. +3. After you create the virtual application, deploy the package by using your ESD solution. ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Related topics -- [Operations for App-V](appv-operations.md) +- [Operations for App-V](appv-operations.md) \ No newline at end of file From e32cd5eb30f82434bc9e7819a39248b16b59986d Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 12 Jul 2018 11:11:34 -0700 Subject: [PATCH 03/33] Continued edits --- ...ctronic-software-distribution-solutions.md | 41 ++----- .../app-v/appv-dynamic-configuration.md | 115 +++++++++--------- 2 files changed, 70 insertions(+), 86 deletions(-) diff --git a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 79da7a2972..66268ffa16 100644 --- a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -8,48 +8,27 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - - # Deploying App-V Packages by Using Electronic Software Distribution (ESD) -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 -You can deploy App-V packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md). +You can deploy App-V packages using an electronic software distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md). -To deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to Application Management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv) +To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv) ## How to deploy virtualized packages using an ESD +To learn more about how to deploy virtualized packages using an ESD, see [How to deploy App-V packages using electronic software distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md). -Describes the methods you can use to deploy App-V packages by using an ESD. +## How to enable only administrators to publish packages by using an ESD -[How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md) +To learn how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD, see [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 +## Related topics - -Explains how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD. - -[How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md) +- [App-V and Citrix integration](https://www.microsoft.com/en-us/download/details.aspx?id=40885) +- [Operations for App-V](appv-operations.md) ## Have a suggestion for App-V? - -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). - -## Other resources for using an ESD and App-V - - -Use the following link for more information about [App-V and Citrix Integration](https://www.microsoft.com/en-us/download/details.aspx?id=40885). - -[Operations for App-V](appv-operations.md) - -  - -  - - - - - +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). \ No newline at end of file diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index 5cc4247912..f6f9e73741 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -8,37 +8,34 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# About App-V dynamic configuration +>Applies to: Windows 10, version 1607 -# About App-V Dynamic Configuration +You can use dynamic configuration to customize an App-V package for a user. This article will tell you how to create or edit an existing dynamic configuration file. -**Applies to** -- Windows 10, version 1607 - -You can use the dynamic configuration to customize an App-V package for a user. Use the following information to create or edit an existing dynamic configuration file. - -When you edit the dynamic configuration file it customizes how an App-V package will run for a user or group. This helps to provide a more convenient method for package customization by removing the need to re-sequence packages using the desired settings, and provides a way to keep package content and custom settings independent. +When you edit the dynamic configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and providing a way to keep package content and custom settings independent. ## Advanced: Dynamic Configuration - Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no additional customization). If you want to adjust these defaults for a particular user or group, you can create and edit the following files: -- User Configuration file +- User Configuration file +- Deployment configuration file -- Deployment configuration file +These .xml files specify package settings and allow for packages to be customized without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed. -The previous .xml files specify package settings and allow for packages to be customized without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed. - -**Note**   -The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements. - -  +>[!NOTE] +>The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements. ### Dynamic Configuration file contents All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following table: +1. User configuration .xml file. +2. Deployment configuration .xml file. +3. Package manifest. + @@ -56,39 +53,38 @@ All of the additions, deletions, and updates in the configuration files need to
-  The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults. The following list displays more information about the two file types: -- **User Configuration File (UserConfig)** – Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. +- **User Configuration File (UserConfig)** – Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. -- **Deployment Configuration File (DeploymentConfig)** – Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. +- **Deployment Configuration File (DeploymentConfig)** – Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. To customize the settings for a package for a specific set of users on a computer or to make changes that will be applied to local user locations such as HKCU, the UserConfig file should be used. To modify the default settings of a package for all users on a machine or to make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the all users folder, the DeploymentConfig file should be used. The UserConfig file provides configuration settings that can be applied to a single user without affecting any other users on a client: -- Extensions that will be integrated into the native system per user:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM +- Extensions that will be integrated into the native system per user:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM -- Virtual Subsystems:- Application Objects, Environment variables, Registry modifications, Services and Fonts +- Virtual Subsystems:- Application Objects, Environment variables, Registry modifications, Services and Fonts -- Scripts (User context only) +- Scripts (User context only) The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the UserConfig list above: -- All UserConfig settings above +- All UserConfig settings above -- Extensions that can only be applied globally for all users +- Extensions that can only be applied globally for all users -- Virtual Subsystems that can be configured for global machine locations e.g. registry +- Virtual Subsystems that can be configured for global machine locations e.g. registry -- Product Source URL +- Product Source URL -- Scripts (Machine context only) +- Scripts (Machine context only) -- Controls to Terminate Child Processes +- Controls to Terminate Child Processes ### File structure @@ -98,7 +94,7 @@ The structure of the App-V Dynamic Configuration file is explained in the follow **Header** - the header of a dynamic user configuration file is as follows: -``` +```xml ``` @@ -109,7 +105,7 @@ The **PackageId** is the same value as exists in the Manifest file. **Applications** - All app-extensions that are contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored. -``` +```xml @@ -122,7 +118,7 @@ The **PackageId** is the same value as exists in the Manifest file. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under the : -``` +```xml .. @@ -143,7 +139,7 @@ Example using the shortcuts subsystem: **Example 1**
If the user defined this in either the dynamic or deployment config file: -``` +```xml                                                                        If the user defines the following -``` +```xml                                                                                                     @@ -173,7 +169,7 @@ The supported Extension Subsystems are: **Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts: -``` +```xml   @@ -211,7 +207,7 @@ The supported Extension Subsystems are: **File-Type Associations:** Associates File-types with programs to open by default as well as setup the context menu. (MIME types can also be setup using this susbsystem). Sample File-type Association is below: -``` +```xml @@ -277,7 +273,7 @@ The supported Extension Subsystems are: **URL Protocols**: This controls the URL Protocols that are integrated into the local registry of the client machine e.g. “mailto:”. -``` +```xml @@ -324,7 +320,7 @@ The supported Extension Subsystems are: **Software Clients**: Allows the app to register as an Email client, news reader, media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases you should only need to enable and disable it. There is also a control to enable and disable the email client specifically if you want the other clients still enabled except for that client. -``` +```xml   @@ -332,7 +328,7 @@ The supported Extension Subsystems are: **AppPaths**: If an application for example contoso.exe is registered with an apppath name of “myapp”, it allows you type “myapp” under the run menu and it will open contoso.exe. -``` +```xml @@ -363,7 +359,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: **Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU -``` +```xml @@ -385,7 +381,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: **Virtual Environment Variables** -``` +```xml         @@ -407,7 +403,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: **Header** - The header of a Deployment Configuration file is as follows: -``` +```xml ``` @@ -419,7 +415,7 @@ The **PackageId** is the same value as exists in the manifest file. - Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS. -``` +```xml   .. @@ -438,7 +434,7 @@ Machine Configuration - the Machine configuration section of the Deployment Conf 1. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under : -``` +```xml     .. @@ -455,7 +451,7 @@ Some subsystems (Extension Subsystems) control Extensions which can only apply t **Application Capabilities**: Used by default programs in windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain windows MIME types.  This extension also makes the virtual application visible in the Set Default Programs UI.: -``` +```xml       @@ -497,7 +493,7 @@ In addition to Extensions, other subsystems can be edited: **Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine -``` +```xml   @@ -511,7 +507,7 @@ In addition to Extensions, other subsystems can be edited: **Machine Wide Virtual Kernel Objects** -``` +```xml     @@ -521,7 +517,7 @@ In addition to Extensions, other subsystems can be edited: **ProductSourceURLOptOut**: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch. -``` +```xml   ..     @@ -533,7 +529,7 @@ In addition to Extensions, other subsystems can be edited: **TerminateChildProcess**:- An application executable can be specified, whose child processes will be terminated when the application exe process is terminated. -``` +```xml   ..       @@ -549,6 +545,17 @@ In addition to Extensions, other subsystems can be edited: The following table describes the various script events and the context under which they can be run. +|Script Execution Time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the Virtual Environment of the package|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)| +|---|---|---|---|---|---| +||||||| +||||||| +||||||| +||||||| +||||||| +||||||| +||||||| +||||||| + @@ -655,7 +662,7 @@ We recommended that you run the multi-script line from a command prompt first to Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run. -``` syntax +```xml ScriptRunner.exe @@ -735,12 +742,10 @@ To create the file manually, the information above in previous sections can be c ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Related topics -[How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) - -[How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) - -[Operations for App-V](appv-operations.md) +- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md) +- [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md) +- [Operations for App-V](appv-operations.md) From 3a4766aa21bb3ff987502ba686721b07f159eed6 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 12 Jul 2018 14:13:41 -0700 Subject: [PATCH 04/33] Continued making edits --- .../app-v/appv-dynamic-configuration.md | 38 +++++++++---------- 1 file changed, 17 insertions(+), 21 deletions(-) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index f6f9e73741..09f6c41e1b 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -14,16 +14,16 @@ ms.date: 04/19/2017 You can use dynamic configuration to customize an App-V package for a user. This article will tell you how to create or edit an existing dynamic configuration file. -When you edit the dynamic configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and providing a way to keep package content and custom settings independent. +When you edit the dynamic configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and provides a way to keep package content and custom settings independent. -## Advanced: Dynamic Configuration +## Advanced: dynamic configuration Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no additional customization). If you want to adjust these defaults for a particular user or group, you can create and edit the following files: - User Configuration file -- Deployment configuration file +- Deployment Configuration file -These .xml files specify package settings and allow for packages to be customized without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed. +These .xml files specify package settings let you customize packages without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed. >[!NOTE] >The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements. @@ -546,15 +546,15 @@ In addition to Extensions, other subsystems can be edited: The following table describes the various script events and the context under which they can be run. |Script Execution Time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the Virtual Environment of the package|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)| -|---|---|---|---|---|---| -||||||| -||||||| -||||||| -||||||| -||||||| -||||||| -||||||| -||||||| +|---|:---:|:---:|:---:|:---:|:---:| +|AddPackage|X||||(SYSTEM, N/A)| +|PublishPackage|X|X|||(SYSTEM, User)| +|UnpublishPackage|X|X|||(SYSTEM, User)| +|RemovePackage|X||||(SYSTEM, N/A)| +|StartProcess|X|X|X|X|(User, User)| +|ExitProcess|X|X||X|(User, User)| +|StartVirtualEnvironment|X|X|X||(User, User)| +|TerminateVirtualEnvironment|X|X|||(User, User)|
@@ -643,22 +643,18 @@ The following table describes the various script events and the context under wh
-  - ### Using multiple scripts on a single event trigger App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client. -**How to use multiple scripts on a single event trigger:** +#### How to use multiple scripts on a single event trigger For each script that you want to run, pass that script as an argument to the ScriptRunner.exe application. The application then runs each script separately, along with the arguments that you specify for each script. Use only one script (ScriptRunner.exe) per trigger. -**Note**   -We recommended that you run the multi-script line from a command prompt first to make sure that all arguments are built correctly before adding them to the deployment configuration file. +>[!NOTE] +>We recommended that you run the multi-script line from a command prompt first to make sure that all arguments are built correctly before adding them to the deployment configuration file. -  - -**Example script and parameter descriptions** +#### Example script and parameter descriptions Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run. From 169b71babf30da4d1c6ebb72bdefbcf1f3d619c0 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 12 Jul 2018 15:27:22 -0700 Subject: [PATCH 05/33] Editorial changes --- .../application-management/app-v/appv-dynamic-configuration.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index 09f6c41e1b..e6b4d4aeed 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -23,7 +23,7 @@ Virtual application packages contain a manifest that provides all the core infor - User Configuration file - Deployment Configuration file -These .xml files specify package settings let you customize packages without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed. +These .xml files specify package settings let you customize packages without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. These automatically generated configuration files reflect the package's default settings that were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed. >[!NOTE] >The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements. @@ -53,7 +53,6 @@ All of the additions, deletions, and updates in the configuration files need to - The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults. The following list displays more information about the two file types: From 3241360757bdaa0ac725b254daca6d1908915b90 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 6 Aug 2018 11:00:05 -0700 Subject: [PATCH 06/33] Attempt to rejigger table into text This is to check to see if the text would be better off as a table or as plain text/bulleted lists. --- ...-powershell-cmdlets-and-get-cmdlet-help.md | 50 +++++++++++-------- 1 file changed, 28 insertions(+), 22 deletions(-) diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 2a510d8f89..9d525573b1 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -8,28 +8,20 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to load the Windows PowerShell cmdlets for App-V and get cmdlet help +>Applies to: Windows 10, version 1607 -# How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help - -**Applies to** -- Windows 10, version 1607 - -What this topic covers: - -- [Requirements for using Windows PowerShell cmdlets](#bkmk-reqs-using-posh) - -- [Loading the Windows PowerShell cmdlets](#bkmk-load-cmdlets) - -- [Getting help for the Windows PowerShell cmdlets](#bkmk-get-cmdlet-help) - -- [Displaying the help for a Windows PowerShell cmdlet](#bkmk-display-help-cmdlet) - -## Requirements for using Windows PowerShell cmdlets - +## Requirements for using Windows PowerShell cmdlets Review the following requirements for using the Windows PowerShell cmdlets: +|Requirement|Details| +|---|---| +||| +||| +||| + @@ -85,10 +77,26 @@ Review the following requirements for using the Windows PowerShell cmdlets:
-  +Alt: -## Loading the Windows PowerShell cmdlets +This section will tell you what you'll need to use the PowerShell cmdlets. +### How to let users use cmdlets + +You can grant your users access to PowerShell cmdlets through one of the following methods: + +* While you're deploying and configuring the App-V server, specify an Active Directory group or individual user with permissions to manage the App-V environment. For more information, see [How to deploy the App-V Server](appv-deploy-the-appv-server.md). +* After you've deployed the App-V server, you can use the App-V Management console to add an additional Active Directory group or user. For more information, see [How to add or remove an administrator by using the Management console](appv-add-or-remove-an-administrator-with-the-management-console.md). + +### Elevated command prompt + +You'll need an elevated command prompt to run the following cmdlets: + +* Add-AppvClientPackage +* Remove-AppvClientPackage +* Set-AppvClientConfiguration + +## Loading the Windows PowerShell cmdlets To load the Windows PowerShell cmdlet modules: @@ -123,9 +131,7 @@ To load the Windows PowerShell cmdlet modules: -  - -## Getting help for the Windows PowerShell cmdlets +## Getting help for the Windows PowerShell cmdlets Starting in App-V 5.0 SP3, cmdlet help is available in two formats: From 2fac31f46bcc7906a49e7a13d889beaadd3fce11 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Wed, 8 Aug 2018 16:02:55 -0700 Subject: [PATCH 07/33] Finished making alternate section --- ...-powershell-cmdlets-and-get-cmdlet-help.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 9d525573b1..175ca868f0 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -95,6 +95,28 @@ You'll need an elevated command prompt to run the following cmdlets: * Add-AppvClientPackage * Remove-AppvClientPackage * Set-AppvClientConfiguration +* Add-AppvClientConnectionGroup +* Remove-AppvClientConnectionGroup +* Add-AppvPublishingServer +* Remove-AppvPublishingServer +* Send-AppvClientReport +* Set-AppvClientMode +* Set-AppvClientPackage +* Set-AppvPublishingServer + +### Other cmdlets + +The following cmdlets are ones that end-users can run unless you configure them to require an elevated command prompt. + +* Publish-AppvClientPackage +* Unpublish-AppvClientPackage + +To configure these cmdlets to require an elevated command prompt, use one of the following methods: + +* Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following articles: + * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) + * [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs) +* Enable the “Require publish as administrator” Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Loading the Windows PowerShell cmdlets From 311a29e3a688596a17c59cef0fa655a7371b60b1 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Wed, 8 Aug 2018 16:55:00 -0700 Subject: [PATCH 08/33] Continued updating tables etc. --- ...-powershell-cmdlets-and-get-cmdlet-help.md | 28 ++++++++++++------- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 175ca868f0..fe19df8b7f 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -122,9 +122,14 @@ To configure these cmdlets to require an elevated command prompt, use one of the To load the Windows PowerShell cmdlet modules: -1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). +1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). +2. Enter one of the following cmdlets to load a list of usable cmdlets for the module you want: -2. Type one of the following commands to load the cmdlets for the module you want: +|App-v component|Cmdlet to enter| +|---|---| +|App-V Server|**Import-Module AppvServer**| +|App-V Sequencer|**Import-Module AppvSequencer**| +|App-V Client|**Import-Module AppvClient**| @@ -157,7 +162,13 @@ To load the Windows PowerShell cmdlet modules: Starting in App-V 5.0 SP3, cmdlet help is available in two formats: -- **As a downloadable module**: To download the latest help after downloading the cmdlet module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE), and type one of the following commands: +* **As a downloadable module**: To download the latest help after downloading the cmdlet module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE), and type one of the following commands: + +|App-v component|Cmdlet to enter| +|---|---| +||| +||| +|||
@@ -188,17 +199,14 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
-- **On TechNet as web pages**: See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](https://technet.microsoft.com/library/dn520245.aspx). - -## Displaying the help for a Windows PowerShell cmdlet +* **On TechNet as web pages**: See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](https://technet.microsoft.com/library/dn520245.aspx). +## Displaying the help for a Windows PowerShell cmdlet To display help for a specific Windows PowerShell cmdlet: -1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). - -2. Type **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. - +1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). +2. Enter **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. ## Have a suggestion for App-V? From 1f73123b553088da0d72841d1a78415c5bd3e3ff Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 9 Aug 2018 14:49:01 -0700 Subject: [PATCH 09/33] Continued edits --- ...-powershell-cmdlets-and-get-cmdlet-help.md | 168 +++--------------- .../app-v/appv-maintaining-appv.md | 29 +-- 2 files changed, 31 insertions(+), 166 deletions(-) diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index fe19df8b7f..78d1788c7a 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -14,74 +14,9 @@ ms.date: 04/19/2017 ## Requirements for using Windows PowerShell cmdlets -Review the following requirements for using the Windows PowerShell cmdlets: - -|Requirement|Details| -|---|---| -||| -||| -||| - -
---- - - - - - - - - - - - - - - - - - - - - -
RequirementDetails

Users can run App-V Server cmdlets only if you grant them access by using one of the following methods:

    -

  • When you are deploying and configuring the App-V Server:

    -

    Specify an Active Directory group or individual user that has permissions to manage the App-V environment. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md).

    • -

  • After you’ve deployed the App-V Server:

    -

    Use the App-V Management console to add an additional Active Directory group or user. See [How to Add or Remove an Administrator by Using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md).

    • -

Cmdlets that require an elevated command prompt

    -

  • Add-AppvClientPackage

    • -

  • Remove-AppvClientPackage

    • -

  • Set-AppvClientConfiguration

    • -

  • Add-AppvClientConnectionGroup

    • -

  • Remove-AppvClientConnectionGroup

    • -

  • Add-AppvPublishingServer

    • -

  • Remove-AppvPublishingServer

    • -

  • Send-AppvClientReport

    • -

  • Set-AppvClientMode

    • -

  • Set-AppvClientPackage

    • -

  • Set-AppvPublishingServer

    • -

Cmdlets that end users can run, unless you configure them to require an elevated command prompt

    -

  • Publish-AppvClientPackage

    • -

  • Unpublish-AppvClientPackage

    • -
-

To configure these cmdlets to require an elevated command prompt, use one of the following methods:

-
    -

  • Run the Set-AppvClientConfiguration cmdlet with the -RequirePublishAsAdmin parameter.

    -

    For more information, see:
    [How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)
    [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs).

    • -

  • Enable the “Require publish as administrator” Group Policy setting for App-V Clients.

    -

    For more information, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md)

    • -
-
- -Alt: - This section will tell you what you'll need to use the PowerShell cmdlets. -### How to let users use cmdlets +### How to let users access PowerShell cmdlets You can grant your users access to PowerShell cmdlets through one of the following methods: @@ -92,28 +27,28 @@ You can grant your users access to PowerShell cmdlets through one of the followi You'll need an elevated command prompt to run the following cmdlets: -* Add-AppvClientPackage -* Remove-AppvClientPackage -* Set-AppvClientConfiguration -* Add-AppvClientConnectionGroup -* Remove-AppvClientConnectionGroup -* Add-AppvPublishingServer -* Remove-AppvPublishingServer -* Send-AppvClientReport -* Set-AppvClientMode -* Set-AppvClientPackage -* Set-AppvPublishingServer +* **Add-AppvClientPackage** +* **Remove-AppvClientPackage** +* **Set-AppvClientConfiguration** +* **Add-AppvClientConnectionGroup** +* **Remove-AppvClientConnectionGroup** +* **Add-AppvPublishingServer** +* **Remove-AppvPublishingServer** +* **Send-AppvClientReport** +* **Set-AppvClientMode** +* **Set-AppvClientPackage** +* **Set-AppvPublishingServer** ### Other cmdlets The following cmdlets are ones that end-users can run unless you configure them to require an elevated command prompt. -* Publish-AppvClientPackage -* Unpublish-AppvClientPackage +* **Publish-AppvClientPackage** +* **Unpublish-AppvClientPackage** To configure these cmdlets to require an elevated command prompt, use one of the following methods: -* Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following articles: +* Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources: * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) * [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs) * Enable the “Require publish as administrator” Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). @@ -131,83 +66,30 @@ To load the Windows PowerShell cmdlet modules: |App-V Sequencer|**Import-Module AppvSequencer**| |App-V Client|**Import-Module AppvClient**| - ---- - - - - - - - - - - - - - - - - - - - - -
App-V componentCommand to type

App-V Server

Import-Module AppvServer

App-V Sequencer

Import-Module AppvSequencer

App-V Client

Import-Module AppvClient

- ## Getting help for the Windows PowerShell cmdlets Starting in App-V 5.0 SP3, cmdlet help is available in two formats: -* **As a downloadable module**: To download the latest help after downloading the cmdlet module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE), and type one of the following commands: +* As a downloadable module in PowerShell. To access the module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE) and enter one of the cmdlets from the following table. |App-v component|Cmdlet to enter| |---|---| -||| -||| -||| +|App-V Server|**Update-Help -Module AppvServer**| +|App-V Sequencer|**Update-Help -Module AppvSequencer**| +|App-V Client|**Update-Help -Module AppvClient**| - ---- - - - - - - - - - - - - - - - - - - - - -
App-V componentCommand to type

App-V Server

Update-Help -Module AppvServer

App-V Sequencer

Update-Help -Module AppvSequencer

App-V Client

Update-Help -Module AppvClient

- -
- -* **On TechNet as web pages**: See the App-V node under [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](https://technet.microsoft.com/library/dn520245.aspx). +* Online in the [Microsoft Desktop Optimization Pack](https://docs.microsoft.com/en-us/powershell/mdop/get-started?view=win-mdop2-ps). ## Displaying the help for a Windows PowerShell cmdlet To display help for a specific Windows PowerShell cmdlet: 1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE). -2. Enter **Get-Help** <*cmdlet*>, for example, **Get-Help Publish-AppvClientPackage**. +2. Enter **Get-Help** followed by the cmdlet you need help with. For example: + ```PowerShell + Get-Help Publish-AppvClientPackage + ``` ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). \ No newline at end of file diff --git a/windows/application-management/app-v/appv-maintaining-appv.md b/windows/application-management/app-v/appv-maintaining-appv.md index 3db885c191..6e1292f604 100644 --- a/windows/application-management/app-v/appv-maintaining-appv.md +++ b/windows/application-management/app-v/appv-maintaining-appv.md @@ -8,43 +8,26 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - - # Maintaining App-V -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure. ## Moving the App-V server -The App-V server connects to the App-V database. Therefore you can install the management component on any computer on the network and then connect it to the App-V database. - -[How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md) - -## Determine if an App-V Application is Running Virtualized +The App-V server connects to the App-V database. Therefore you can install the management component on any computer on the network and then connect it to the App-V database. For more information, see [How to move the App-V server to another computer](appv-move-the-appv-server-to-another-computer.md). +## Determine if an App-V application is running virtualized Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual. -Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V 5.1 and later, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized. +Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific APIs with App-V 5.1 and later, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized. ## Have a suggestion for App-V? - -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Other resources for maintaining App-V - -[Operations for App-V](appv-operations.md) - -  - -  - - - - - +* [Operations for App-V](appv-operations.md) \ No newline at end of file From 143abd8bedcc1baadf04d38648162780429a6ed4 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 10 Aug 2018 16:54:38 -0700 Subject: [PATCH 10/33] Continued edit --- .../app-v/appv-maintaining-appv.md | 8 +- ...-a-stand-alone-computer-with-powershell.md | 144 ++++++------------ 2 files changed, 54 insertions(+), 98 deletions(-) diff --git a/windows/application-management/app-v/appv-maintaining-appv.md b/windows/application-management/app-v/appv-maintaining-appv.md index 6e1292f604..6372fefcc7 100644 --- a/windows/application-management/app-v/appv-maintaining-appv.md +++ b/windows/application-management/app-v/appv-maintaining-appv.md @@ -16,13 +16,15 @@ After you have deployed App-V for Windows 10, you can use the following informat ## Moving the App-V server -The App-V server connects to the App-V database. Therefore you can install the management component on any computer on the network and then connect it to the App-V database. For more information, see [How to move the App-V server to another computer](appv-move-the-appv-server-to-another-computer.md). +The App-V server connects to the App-V database, which means you can install the management component and connect it to the App-V database on any computer on the network. For more information, see [How to move the App-V server to another computer](appv-move-the-appv-server-to-another-computer.md). ## Determine if an App-V application is running virtualized -Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual. +Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace (PID stands for process ID). To find the process ID of the process you're currently using, enter the Windows API **GetCurrentProcessId()**. -Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific APIs with App-V 5.1 and later, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized. +For example, let's say the process ID is 4052. If you can successfully open a named Event object called **AppVVirtual-4052** with the **OpenEvent()** API in the default read access namespace, then the application is virtual. If the **OpenEvent()** call fails, the application isn't virtual. + +Additionally, ISVs who want to explicitly virtualize or not virtualize calls on specific APIs with App-V 5.1 and later can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module to hint to a downstream component whether the call should be virtualized or not. ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index e3c9eca586..dd6ed9a6ca 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -1,6 +1,6 @@ --- -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 +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 ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,128 +8,82 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to manage App-V packages running on a stand-alone computer by using Windows PowerShell +>Applies to: Windows 10, version 1607 -# How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell +The following sections explain how to perform various management tasks on a stand-alone client computer with Windows PowerShell cmdlets. -**Applies to** -- Windows 10, version 1607 +## Return a list of packages +Enter the **Get-AppvClientPackage** cmdlet to return a list of packages entitled to a specific user. Its parameters are *-Name*, *-Version*, *-PackageID*, and *-VersionID*. -The following sections explain how to perform various management tasks on a stand-alone client computer by using Windows PowerShell: +For example: -- [To return a list of packages](#bkmk-return-pkgs-standalone-posh) +```PowerShell +Get-AppvClientPackage –Name “ContosoApplication” -Version 2 +``` -- [To add a package](#bkmk-add-pkgs-standalone-posh) +## Add a package -- [To publish a package](#bkmk-pub-pkg-standalone-posh) +Use the **Add-AppvClientPackage** cmdlet to add a package to a computer. -- [To publish a package to a specific user](#bkmk-pub-pkg-a-user-standalone-posh) +>[!IMPORTANT] +>This example only adds a package. It does not publish the package to the user or the computer. -- [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh) +For example: -- [To unpublish an existing package](#bkmk-unpub-pkg-standalone-posh) +```PowerShell +$Contoso = Add-AppvClientPackage \\\\path\\to\\appv\\package.appv +``` -- [To unpublish a package for a specific user](#bkmk-unpub-pkg-specfc-use) +## Publish a package -- [To remove an existing package](#bkmk-remove-pkg-standalone-posh) +Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been added to a specific user or globally to any user on the computer. -- [To enable only administrators to publish or unpublish packages](#bkmk-admins-pub-pkgs) +Enter the cmdlet with the application name to publish it to the user. -- [Understanding pending packages (UserPending and GlobalPending)](#bkmk-understd-pend-pkgs) +```PowerShell +Publish-AppvClientPackage “ContosoApplication” +``` -## To return a list of packages +To publish the application globally, just add the *-Global* parameter. +```Powershell +Publish-AppvClientPackage “ContosoApplication” -Global +``` -Use the following information to return a list of packages that are entitled to a specific user: +## Publish a package to a specific user -**Cmdlet**: Get-AppvClientPackage +>[!NOTE]   +>You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter. -**Parameters**: -Name -Version -PackageID -VersionID - -**Example**: Get-AppvClientPackage –Name “ContosoApplication” -Version 2 - -## To add a package - - -Use the following information 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. - -  - -**Cmdlet**: Add-AppvClientPackage - -**Example**: $Contoso = Add-AppvClientPackage \\\\path\\to\\appv\\package.appv - -## To publish a package - - -Use the following information to publish a package that has been added to a specific user or globally to any user on the computer. - - ---- - - - - - - - - - - - - - - - - -
Publishing methodCmdlet and example

Publishing to the user

Cmdlet: Publish-AppvClientPackage

-

Example: Publish-AppvClientPackage “ContosoApplication”

Publishing globally

Cmdlet: Publish-AppvClientPackage

-

Example: Publish-AppvClientPackage “ContosoApplication” -Global

- -  - -## To 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. - -  - -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). +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). To use this parameter: -- You can run this cmdlet from the user or administrator session. +- You can run this cmdlet from the user or administrator session. +- You must be logged in with administrative credentials to use the parameter. +- The end-user must be signed in. +- You must provide the end user’s security identifier (SID). -- You must be logged in with administrative credentials to use the parameter. +For example: -- The end user must be logged in. +```PowerShell +Publish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 +``` -- You must provide the end user’s security identifier (SID). +## Add and publish a package -**Cmdlet**: Publish-AppvClientPackage +Use the **Add-AppvClientPackage** cmdlet to add a package to a computer and publish it to the user. -**Example**: Publish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 +For example: -## To add and publish a package - - -Use the following information to add a package to a computer and publish it to the user. - -**Cmdlet**: Add-AppvClientPackage - -**Example**: Add-AppvClientPackage \\\\path\\to\\appv\\package.appv | Publish-AppvClientPackage - -## To unpublish an existing package +```PowerShell +Add-AppvClientPackage \\\\path\\to\\appv\\package.appv | Publish-AppvClientPackage +``` +## Unpublish an existing package Use the following information to unpublish a package which has been entitled to a user but not remove the package from the computer. @@ -137,7 +91,7 @@ Use the following information to unpublish a package which has been entitled to **Example**: Unpublish-AppvClientPackage “ContosoApplication” -## To unpublish a package for a specific user +## Unpublish a package for a specific user **Note**   From cf02815d79117797943136844649395c8d8fc89b Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 13 Aug 2018 10:52:49 -0700 Subject: [PATCH 11/33] Continued updating article and adjusting formatting Some tables seem unnecessary. --- ...-a-stand-alone-computer-with-powershell.md | 61 +++++++++++-------- 1 file changed, 35 insertions(+), 26 deletions(-) diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index dd6ed9a6ca..405fa939dd 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -64,7 +64,7 @@ To use this parameter: - You can run this cmdlet from the user or administrator session. - You must be logged in with administrative credentials to use the parameter. -- The end-user must be signed in. +- The end user must be signed in. - You must provide the end user’s security identifier (SID). For example: @@ -85,53 +85,62 @@ Add-AppvClientPackage \\\\path\\to\\appv\\package.appv | Publish-AppvClientPacka ## Unpublish an existing package -Use the following information to unpublish a package which has been entitled to a user but not remove the package from the computer. +Use the **Unpublish-AppvClientPackage** cmdlet to unpublish a package which has been entitled to a user but not remove the package from the computer. -**Cmdlet**: Unpublish-AppvClientPackage +For example: -**Example**: Unpublish-AppvClientPackage “ContosoApplication” +```PowerShell +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). +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). To use this parameter: -- You can run this cmdlet from the user or administrator session. +- You can run this cmdlet from the user or administrator session. +- You must be logged in with administrative credentials to use the parameter. +- The end user must be signed in. +- You must provide the end user’s security identifier (SID). -- You must be logged in with administrative credentials to use the parameter. +For example: -- The end user must be logged in. +```PowerShell +Unpublish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 +``` -- You must provide the end user’s security identifier (SID). +## Remove an existing package -**Cmdlet**: Unpublish-AppvClientPackage +Use the **Remove-AppvClientPackage** cmdlet to remove a package from the computer. -**Example**: Unpublish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 +For example: -## To remove an existing package +```PowerShell +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/). -Use the following information to remove a package from the computer. +## Enable only administrators to publish or unpublish packages -**Cmdlet**: Remove-AppvClientPackage +Starting in App-V 5.0 SP3, you can use the **Set-AppvClientConfiguration** cmdlet and *-RequirePublishAsAdmin* parameter to enable only administrators (not end users) to publish or unpublish packages. -**Example**: Remove-AppvClientPackage “ContosoApplication” +You can set the -RequirePublishAsAdmin parameter to the following values: -**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 [To add and publish a package](#bkmk-add-pub-pkg-standalone-posh). 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/). +- 0: False +- 1: True -  +For example: -## To enable only administrators to publish or unpublish packages +```PowerShell +Set-AppvClientConfiguration –RequirePublishAsAdmin1 +``` -Starting in App-V 5.0 SP3, you can use the following cmdlet and parameter to enable only administrators (not end users) to publish or unpublish packages: @@ -158,7 +167,7 @@ Starting in App-V 5.0 SP3, you can use the following cmdlet and parameter to ena   -To use the App-V Management console to set this configuration, see [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md). +To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Understanding pending packages (UserPending and GlobalPending) From fe65b827d6e5bca2c7d8327bae947515e2207548 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 16 Aug 2018 10:56:14 -0700 Subject: [PATCH 12/33] Attempt to fix broken link --- ...lectronic-software-distribution-solutions.md | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 3ae3740c77..f060215b1b 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -8,25 +8,22 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to enable only administrators to publish packages by using an ESD - -# How to Enable Only Administrators to Publish Packages by Using an ESD - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you could not prevent end users from performing these tasks. -**To enable only administrators to publish or unpublish packages** +To enable only administrators to publish or unpublish packages: -1. Navigate to the following Group Policy Object node: +1. Navigate to the following Group Policy Object node: **Computer Configuration > Administrative Templates > System > App-V > Publishing**. -2. Enable the **Require publish as administrator** Group Policy setting. +2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs). + To instead use Windows PowerShell to set this item, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages-(userpending-and-globalpending)). ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). From e6b6d52e1550836811cf159cba4280c91317924c Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 16 Aug 2018 16:58:13 -0700 Subject: [PATCH 13/33] Editorial change --- ...-packages-with-electronic-software-distribution-solutions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index f060215b1b..86f8b6bccf 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -14,7 +14,7 @@ ms.date: 04/19/2017 Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you could not prevent end users from performing these tasks. -To enable only administrators to publish or unpublish packages: +Here's how to enable only administrators to publish or unpublish packages: 1. Navigate to the following Group Policy Object node: From aa0b448769a94c09f59269811e0feccec4eb721e Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 17 Aug 2018 16:35:45 -0700 Subject: [PATCH 14/33] Continued update --- ...ctronic-software-distribution-solutions.md | 2 +- ...ting-on-the-appv-client-with-powershell.md | 2 - .../app-v/appv-for-windows.md | 57 +++++++++---------- ...-a-stand-alone-computer-with-powershell.md | 29 ++++++---- 4 files changed, 46 insertions(+), 44 deletions(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 86f8b6bccf..71bfff5fc5 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -18,7 +18,7 @@ Here's how to enable only administrators to publish or unpublish packages: 1. Navigate to the following Group Policy Object node: - **Computer Configuration > Administrative Templates > System > App-V > Publishing**. + **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Publishing**. 2. Enable the **Require publish as administrator** Group Policy setting. diff --git a/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md b/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md index c21abca90a..b6df634063 100644 --- a/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md +++ b/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md @@ -8,8 +8,6 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - - # How to Enable Reporting on the App-V Client by Using Windows PowerShell **Applies to** diff --git a/windows/application-management/app-v/appv-for-windows.md b/windows/application-management/app-v/appv-for-windows.md index 857938e467..3b0a24c87d 100644 --- a/windows/application-management/app-v/appv-for-windows.md +++ b/windows/application-management/app-v/appv-for-windows.md @@ -8,62 +8,59 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - - # Application Virtualization (App-V) for Windows 10 overview -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 -The topics in this section provide information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users. +The topics in this section provide information and instructions to help you administer App-V and its components. This information is for system administrators who manage large installations with many servers and clients, and for support personnel who interact directly with the computers or users. -[Getting Started with App-V](appv-getting-started.md) +[Getting started with App-V](appv-getting-started.md) - [What's new in App-V](appv-about-appv.md) - [Evaluating App-V](appv-evaluating-appv.md) -- [High Level Architecture for App-V](appv-high-level-architecture.md) +- [High-level architecture for App-V](appv-high-level-architecture.md) [Planning for App-V](appv-planning-for-appv.md) -- [Preparing Your Environment for App-V](appv-preparing-your-environment.md) -- [App-V Prerequisites](appv-prerequisites.md) -- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md) -- [App-V Supported Configurations](appv-supported-configurations.md) -- [App-V Planning Checklist](appv-planning-checklist.md) +- [Preparing your environment for App-V](appv-preparing-your-environment.md) +- [App-V prerequisites](appv-prerequisites.md) +- [Planning to deploy App-V](appv-planning-to-deploy-appv.md) +- [App-V supported configurations](appv-supported-configurations.md) +- [App-V planning checklist](appv-planning-checklist.md) [Deploying App-V](appv-deploying-appv.md) -- [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) - [Deploying the App-V Server](appv-deploying-the-appv-server.md) -- [App-V Deployment Checklist](appv-deployment-checklist.md) -- [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) +- [App-V deployment checklist](appv-deployment-checklist.md) +- [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) [Operations for App-V](appv-operations.md) -- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md) +- [Creating and managing App-V virtualized applications](appv-creating-and-managing-virtualized-applications.md) - [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) - [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) - [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) -- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md) -- [Managing Connection Groups](appv-managing-connection-groups.md) -- [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md) +- [Administering App-V Virtual Applications by using the Management Console](appv-administering-virtual-applications-with-the-management-console.md) +- [Managing connection groups](appv-managing-connection-groups.md) +- [Deploying App-V packages by using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md) - [Using the App-V Client Management Console](appv-using-the-client-management-console.md) -- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) -- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) +- [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) +- [Migrating to App-V from a previous version](appv-migrating-to-appv-from-a-previous-version.md) - [Maintaining App-V](appv-maintaining-appv.md) -- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) +- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md) [Troubleshooting App-V](appv-troubleshooting.md) -[Technical Reference for App-V](appv-technical-reference.md) +[Technical reference for App-V](appv-technical-reference.md) -- [Performance Guidance for Application Virtualization](appv-performance-guidance.md) -- [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md) -- [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md) -- [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md) +- [Performance guidance for Application Virtualization](appv-performance-guidance.md) +- [Application publishing and client interaction](appv-application-publishing-and-client-interaction.md) +- [Viewing App-V Server publishing metadata](appv-viewing-appv-server-publishing-metadata.md) +- [Running a locally installed application inside a virtual environment with virtualized applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md) ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). \ No newline at end of file diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 405fa939dd..6a8ef9c33c 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -80,7 +80,7 @@ Use the **Add-AppvClientPackage** cmdlet to add a package to a computer and publ For example: ```PowerShell -Add-AppvClientPackage \\\\path\\to\\appv\\package.appv | Publish-AppvClientPackage +Add-AppvClientPackage | Publish-AppvClientPackage ``` ## Unpublish an existing package @@ -98,12 +98,12 @@ Unpublish-AppvClientPackage “ContosoApplication” >[!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). +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). To use this parameter: - You can run this cmdlet from the user or administrator session. -- You must be logged in with administrative credentials to use the parameter. +- You must sign in with administrative credentials to use the parameter. - The end user must be signed in. - You must provide the end user’s security identifier (SID). @@ -130,7 +130,7 @@ Remove-AppvClientPackage “ContosoApplication” Starting in App-V 5.0 SP3, you can use the **Set-AppvClientConfiguration** cmdlet and *-RequirePublishAsAdmin* parameter to enable only administrators (not end users) to publish or unpublish packages. -You can set the -RequirePublishAsAdmin parameter to the following values: +You can set the *-RequirePublishAsAdmin* parameter to the following values: - 0: False - 1: True @@ -169,10 +169,14 @@ Set-AppvClientConfiguration –RequirePublishAsAdmin1 To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). -## Understanding pending packages (UserPending and GlobalPending) +## Understanding pending packages (UserPending and GlobalPending) +Starting in App-V 5.0 SP2, if you run a Windows PowerShell cmdlet that affects a package currently in use, the task you're trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows: -**Starting in App-V 5.0 SP2**: If you run a Windows PowerShell cmdlet that affects a package that is currently in use, the task that you are trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows: +|Cmdlet output item|Description| +|---|---| +|UserPending|Indicates whether the listed package has a pending task that is being applied to the user:
- True
- False| +|GlobalPending|Indicates whether the listed package has a pending task that is being applied globally to the computer:
- True
- False|
@@ -209,6 +213,11 @@ To use the App-V Management console to set this configuration, see [How to publi The pending task will run later, according to the following rules: +|Task type|Applicable rule| +|---|---| +|User-based
(for example, publishing a package to a user)|The pending task will be performed after the user logs off and then logs back on.| +|Globally based
(for example, enabling a connection group globally)|The pending task will be performed when the computer is shut down and then restarted.| +
@@ -236,11 +245,9 @@ For more information about pending tasks, see [Upgrading an in-use App-V package ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Related topics -[Operations for App-V](appv-operations.md) - -[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md) - +- [Operations for App-V](appv-operations.md) +- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md) \ No newline at end of file From 2c5f41be7cc2a8274c9e911b947f26618e164f3f Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 20 Aug 2018 11:04:07 -0700 Subject: [PATCH 15/33] Attempt to fix broken links Changed title of problem section to remove parentheses. --- ...-packages-with-electronic-software-distribution-solutions.md | 2 +- .../app-v/appv-enable-the-app-v-desktop-client.md | 2 +- .../appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md | 2 +- ...ackages-running-on-a-stand-alone-computer-with-powershell.md | 2 +- .../appv-publish-a-packages-with-the-management-console.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 71bfff5fc5..0da1342f72 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -22,7 +22,7 @@ Here's how to enable only administrators to publish or unpublish packages: 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages-(userpending-and-globalpending)). + To instead use Windows PowerShell to set this item, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md b/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md index ff0ad45667..0696778b9f 100644 --- a/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md +++ b/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md @@ -35,7 +35,7 @@ Check out these articles for more information about how to configure the App-V c * [Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md) * [How to modify client configuration by using Windows PowerShell](appv-modify-client-configuration-with-powershell.md) * [Using the client management console](appv-using-the-client-management-console.md) -* [How to configure the client to receive package and connection group updates From the Publishing server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md) +* [How to configure the client to receive package and connection group updates from the Publishing server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md) ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 78d1788c7a..8292073ac6 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -50,7 +50,7 @@ To configure these cmdlets to require an elevated command prompt, use one of the * Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources: * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) - * [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs) + * [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending) * Enable the “Require publish as administrator” Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Loading the Windows PowerShell cmdlets diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 6a8ef9c33c..dfdc8d31dd 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -169,7 +169,7 @@ Set-AppvClientConfiguration –RequirePublishAsAdmin1 To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). -## Understanding pending packages (UserPending and GlobalPending) +## Understanding pending packages: UserPending and GlobalPending Starting in App-V 5.0 SP2, if you run a Windows PowerShell cmdlet that affects a package currently in use, the task you're trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows: diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index fb9ad9b19f..d822f2d71b 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -38,7 +38,7 @@ The ability to enable only administrators to publish or unpublish packages (desc 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#bkmk-admins-pub-pkgs). + To instead use Windows PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? From e2f9aa4a5d2271938ebf8511b231bbcb32213322 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 20 Aug 2018 15:16:40 -0700 Subject: [PATCH 16/33] Next attempt to fix links --- ...-packages-with-electronic-software-distribution-solutions.md | 2 +- .../appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md | 2 +- .../appv-publish-a-packages-with-the-management-console.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 0da1342f72..17d9d5d847 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -22,7 +22,7 @@ Here's how to enable only administrators to publish or unpublish packages: 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 8292073ac6..eca903404a 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -50,7 +50,7 @@ To configure these cmdlets to require an elevated command prompt, use one of the * Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources: * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) - * [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending) + * [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending) * Enable the “Require publish as administrator” Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Loading the Windows PowerShell cmdlets diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index d822f2d71b..892b4e9a92 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -38,7 +38,7 @@ The ability to enable only administrators to publish or unpublish packages (desc 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? From 7897db31848b67f2717dfe7fd66d2e7cf7f3d427 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 20 Aug 2018 16:12:46 -0700 Subject: [PATCH 17/33] Removed extra tables --- ...-a-stand-alone-computer-with-powershell.md | 82 ------------------- 1 file changed, 82 deletions(-) diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index dfdc8d31dd..1083fdf7ff 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -141,32 +141,6 @@ For example: Set-AppvClientConfiguration –RequirePublishAsAdmin1 ``` - -
---- - - - - - - - - - - -

Cmdlet

Set-AppvClientConfiguration

Parameter

-RequirePublishAsAdmin

-

Parameter values:

-
    -

  • 0 - False

    • -

  • 1 - True

    • -
-

Example:: Set-AppvClientConfiguration –RequirePublishAsAdmin1

- -  - To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Understanding pending packages: UserPending and GlobalPending @@ -178,39 +152,6 @@ Starting in App-V 5.0 SP2, if you run a Windows PowerShell cmdlet that affects a |UserPending|Indicates whether the listed package has a pending task that is being applied to the user:
- True
- False| |GlobalPending|Indicates whether the listed package has a pending task that is being applied globally to the computer:
- True
- False| - ---- - - - - - - - - - - - - - - - - -
Cmdlet output itemDescription

UserPending

Indicates whether the listed package has a pending task that is being applied to the user:

-
    -

  • True

    • -

  • False

    • -

GlobalPending

Indicates whether the listed package has a pending task that is being applied globally to the computer:

-
    -

  • True

    • -

  • False

    • -
- -  - The pending task will run later, according to the following rules: |Task type|Applicable rule| @@ -218,29 +159,6 @@ The pending task will run later, according to the following rules: |User-based
(for example, publishing a package to a user)|The pending task will be performed after the user logs off and then logs back on.| |Globally based
(for example, enabling a connection group globally)|The pending task will be performed when the computer is shut down and then restarted.| - ---- - - - - - - - - - - - - - - - - -
Task typeApplicable rule

User-based task, e.g., publishing a package to a user

The pending task will be performed after the user logs off and then logs back on.

Globally based task, e.g., enabling a connection group globally

The pending task will be performed when the computer is shut down and then restarted.

- For more information about pending tasks, see [Upgrading an in-use App-V package](appv-application-publishing-and-client-interaction.md#upgrading-an-in-use-app-v-package). ## Have a suggestion for App-V? From 8a10955489a51162cef377d199d71343c3176c14 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 20 Aug 2018 16:34:44 -0700 Subject: [PATCH 18/33] Attempt to fix link by changing title --- ...kages-with-electronic-software-distribution-solutions.md | 2 +- .../appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md | 4 ++-- ...ges-running-on-a-stand-alone-computer-with-powershell.md | 6 +++--- .../appv-publish-a-packages-with-the-management-console.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 17d9d5d847..5cbffc5547 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -22,7 +22,7 @@ Here's how to enable only administrators to publish or unpublish packages: 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index eca903404a..895882e4e4 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -50,8 +50,8 @@ To configure these cmdlets to require an elevated command prompt, use one of the * Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources: * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) - * [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending) -* Enable the “Require publish as administrator” Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). + * [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending) +* Enable the **Require publish as administrator** Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Loading the Windows PowerShell cmdlets diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 1083fdf7ff..6d3f09d4fc 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -39,7 +39,7 @@ $Contoso = Add-AppvClientPackage \\\\path\\to\\appv\\package.appv ## Publish a package -Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been added to a specific user or globally to any user on the computer. +Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been added to either a specific user or globally to any user on the computer. Enter the cmdlet with the application name to publish it to the user. @@ -58,7 +58,7 @@ Publish-AppvClientPackage “ContosoApplication” -Global >[!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). +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). To use this parameter: @@ -143,7 +143,7 @@ Set-AppvClientConfiguration –RequirePublishAsAdmin1 To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). -## Understanding pending packages: UserPending and GlobalPending +## About pending packages: UserPending and GlobalPending Starting in App-V 5.0 SP2, if you run a Windows PowerShell cmdlet that affects a package currently in use, the task you're trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows: diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index 892b4e9a92..14a0f349cf 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -38,7 +38,7 @@ The ability to enable only administrators to publish or unpublish packages (desc 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#understanding-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? From 1edf3b04c8e3865e6f818b68149ded8e51b68c3a Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 21 Aug 2018 15:25:56 -0700 Subject: [PATCH 19/33] Attempt to fix broken link --- .../appv-publish-a-packages-with-the-management-console.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index 14a0f349cf..16398d236f 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -38,7 +38,7 @@ The ability to enable only administrators to publish or unpublish packages (desc 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending). ## Have a suggestion for App-V? From 6132886989ee70820f0a77b6a6d1f6d422758294 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 21 Aug 2018 15:32:14 -0700 Subject: [PATCH 20/33] Changed link back because it didn't fix the problem --- .../appv-publish-a-packages-with-the-management-console.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index 16398d236f..14a0f349cf 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -38,7 +38,7 @@ The ability to enable only administrators to publish or unpublish packages (desc 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending). ## Have a suggestion for App-V? From df99dd5de91cc6f5acbe8b7fa728f68797516857 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 21 Aug 2018 16:06:11 -0700 Subject: [PATCH 21/33] Attempt to fix links by removing colon --- ...ctronic-software-distribution-solutions.md | 2 +- ...-powershell-cmdlets-and-get-cmdlet-help.md | 2 +- ...-a-packages-with-the-management-console.md | 42 ++++++++----------- 3 files changed, 20 insertions(+), 26 deletions(-) diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md index 5cbffc5547..803d11d76e 100644 --- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md @@ -22,7 +22,7 @@ Here's how to enable only administrators to publish or unpublish packages: 2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending). ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index 895882e4e4..efd4e69e63 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -50,7 +50,7 @@ To configure these cmdlets to require an elevated command prompt, use one of the * Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources: * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md) - * [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending) + * [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending) * Enable the **Require publish as administrator** Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md). ## Loading the Windows PowerShell cmdlets diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index 14a0f349cf..cbae070288 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -1,6 +1,6 @@ --- -title: How to Publish a Package by Using the Management Console (Windows 10) -description: How to Publish a Package by Using the Management Console +title: How to publish a package by using the Management console (Windows 10) +description: How to publish a package by using the Management console. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,44 +8,38 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to publish a package by using the Management console +>Applies to: Windows 10, version 1607 -# How to Publish a Package by Using the Management Console +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. -**Applies to** -- Windows 10, version 1607 +>[!NOTE]   +>The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3. -Use the following procedure to publish an App-V package. Once you publish a package, computers that are running the App-V client can access and run the applications in that package. +## Publish an App-V package -**Note**   -The ability to enable only administrators to publish or unpublish packages (described below) is supported starting in App-V 5.0 SP3. +1. In the App-V Management console. Select or right-click the name of the package to be published. Select **Publish**. -  - -**To publish an App-V package** - -1. In the App-V Management console. Click or right-click the name of the package to be published. Select **Publish**. - -2. Review the **Status** column to verify that the package has been published and is now available. If the package is available, the status **published** is displayed. +2. Review the **Status** column to verify that the package has been published and is now available. If the package is available, the status **published** is displayed. If the package is not published successfully, the status **unpublished** is displayed, along with error text that explains why the package is not available. -**To enable only administrators to publish or unpublish packages** +## Enable only administrators to publish or unpublish packages -1. Navigate to the following Group Policy Object node: +1. Navigate to the following Group Policy Object node: - **Computer Configuration > Administrative Templates > System > App-V > Publishing**. + **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Publishing**. -2. Enable the **Require publish as administrator** Group Policy setting. +2. Enable the **Require publish as administrator** Group Policy setting. - To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages:-userpending-and-globalpending). + To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending). ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## 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) +* [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) From 7d6d2bcdcfaafd650373b656d49167abc783012f Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 21 Aug 2018 16:43:33 -0700 Subject: [PATCH 22/33] Continued editorial changes --- .../app-v/appv-deploying-microsoft-office-2016-with-appv.md | 6 +++--- ...kages-with-electronic-software-distribution-solutions.md | 6 +++--- .../app-v/appv-deploying-the-appv-sequencer-and-client.md | 4 ++-- .../appv-publish-a-packages-with-the-management-console.md | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md b/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md index e43a70509e..8e9bb9ec5c 100644 --- a/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md +++ b/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md @@ -1,6 +1,6 @@ --- -title: Deploying Microsoft Office 2016 by Using App-V (Windows 10) -description: Deploying Microsoft Office 2016 by Using App-V +title: Deploying Microsoft Office 2016 by using App-V (Windows 10) +description: Deploying Microsoft Office 2016 by using App-V author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,7 +8,7 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/18/2018 --- -# Deploying Microsoft Office 2016 by Using App-V +# Deploying Microsoft Office 2016 by using App-V >Applies to: Windows 10, version 1607 diff --git a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 66268ffa16..ffa1363a03 100644 --- a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -1,6 +1,6 @@ --- -title: Deploying App-V Packages by Using Electronic Software Distribution (ESD) -description: Deploying App-V Packages by Using Electronic Software Distribution (ESD) +title: Deploying App-V packages by using electronic software distribution (ESD) +description: Deploying App-V Packages by using electronic software distribution (ESD) author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,7 +8,7 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- -# Deploying App-V Packages by Using Electronic Software Distribution (ESD) +# Deploying App-V packages by using electronic software distribution (ESD) >Applies to: Windows 10, version 1607 diff --git a/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md b/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md index 58d77d2a5a..638235a066 100644 --- a/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md +++ b/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md @@ -1,6 +1,6 @@ --- -title: Deploying the App-V Sequencer and Configuring the Client (Windows 10) -description: Deploying the App-V Sequencer and Configuring the Client +title: Deploying the App-V Sequencer and configuring the client (Windows 10) +description: Deploying the App-V Sequencer and configuring the client author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index cbae070288..62abefd38a 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -42,4 +42,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## 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) \ No newline at end of file From bd74b8f218929abab7ab46e0cb79632050cfc0c6 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 24 Aug 2018 13:57:19 -0700 Subject: [PATCH 23/33] Beginning prep for next pull request --- .../app-v/appv-delete-a-connection-group.md | 2 +- .../appv-delete-a-package-with-the-management-console.md | 2 +- ...ackages-with-electronic-software-distribution-solutions.md | 2 +- ...ackages-with-electronic-software-distribution-solutions.md | 4 ++-- .../app-v/appv-dynamic-configuration.md | 4 ++-- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/windows/application-management/app-v/appv-delete-a-connection-group.md b/windows/application-management/app-v/appv-delete-a-connection-group.md index 5ce582a4f3..b0d9d87b41 100644 --- a/windows/application-management/app-v/appv-delete-a-connection-group.md +++ b/windows/application-management/app-v/appv-delete-a-connection-group.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 08/24/2018 --- # How to delete a connection group diff --git a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md index 3b66608534..d7d7d9558c 100644 --- a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md +++ b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 08/24/2018 --- # How to delete a package in the Management Console diff --git a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md index 3bb1e8a8c5..54f8ebc877 100644 --- a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 08/24/2018 --- # How to deploy App-V packages using electronic software distribution diff --git a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md index ffa1363a03..5c8be25f3c 100644 --- a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -1,12 +1,12 @@ --- title: Deploying App-V packages by using electronic software distribution (ESD) -description: Deploying App-V Packages by using electronic software distribution (ESD) +description: Deploying App-V packages by using electronic software distribution (ESD) author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 08/24/2018 --- # Deploying App-V packages by using electronic software distribution (ESD) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index e6b4d4aeed..dd1366cbea 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 08/24/2018 --- # About App-V dynamic configuration @@ -30,7 +30,7 @@ These .xml files specify package settings let you customize packages without dir ### Dynamic Configuration file contents -All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following table: +All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following list: 1. User configuration .xml file. 2. Deployment configuration .xml file. From 4eb7732f50956f16d10fcc2a1d6d88aaaf50a80e Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 24 Aug 2018 15:49:58 -0700 Subject: [PATCH 24/33] Discovered dynamic configuration style needs massive overhaul --- .../app-v/appv-dynamic-configuration.md | 84 ++++++++++--------- 1 file changed, 46 insertions(+), 38 deletions(-) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index dd1366cbea..ba644f8cb7 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -28,7 +28,7 @@ These .xml files specify package settings let you customize packages without dir >[!NOTE] >The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements. -### Dynamic Configuration file contents +## Dynamic Configuration file contents All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following list: @@ -55,21 +55,21 @@ All of the additions, deletions, and updates in the configuration files need to The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults. -The following list displays more information about the two file types: +There are two types of configuration files: - **User Configuration File (UserConfig)** – Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. - **Deployment Configuration File (DeploymentConfig)** – Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. -To customize the settings for a package for a specific set of users on a computer or to make changes that will be applied to local user locations such as HKCU, the UserConfig file should be used. To modify the default settings of a package for all users on a machine or to make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the all users folder, the DeploymentConfig file should be used. +You can use the UserConfig file to customize the settings for a package for a specific set of users on a computer or make changes that will be applied to local user locations such as HKCU. You can use the DeploymentConfig file to modify the default settings of a package for all users on a machine or make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the All Users folder. The UserConfig file provides configuration settings that can be applied to a single user without affecting any other users on a client: -- Extensions that will be integrated into the native system per user:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM +- Extensions that will be integrated into the native system per user: shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM. -- Virtual Subsystems:- Application Objects, Environment variables, Registry modifications, Services and Fonts +- Virtual Subsystems: Application Objects, Environment variables, Registry modifications, Services, and Fonts. -- Scripts (User context only) +- Scripts (user context only). The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the UserConfig list above: @@ -77,7 +77,7 @@ The DeploymentConfig file provides configuration settings in two sections, one r - Extensions that can only be applied globally for all users -- Virtual Subsystems that can be configured for global machine locations e.g. registry +- Virtual Subsystems that can be configured for global machine locations, such as the registry - Product Source URL @@ -85,24 +85,28 @@ The DeploymentConfig file provides configuration settings in two sections, one r - Controls to Terminate Child Processes -### File structure +## File structure The structure of the App-V Dynamic Configuration file is explained in the following section. -### Dynamic User Configuration file +## Dynamic User Configuration file -**Header** - the header of a dynamic user configuration file is as follows: +### Header + +The following is an example of a Dynamic User Configuration file's header: ```xml ``` -The **PackageId** is the same value as exists in the Manifest file. +The **PackageId** is the same value that exists in the Manifest file. -**Body** - the body of the Dynamic User Configuration file can include all the app extension points that are defined in the Manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body: +### Body -**Applications** - All app-extensions that are contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored. +The Dynamic User Configuration file's body can include all app extension points defined in the Manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body: + +**Applications**: All app-extensions contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored. ```xml @@ -115,7 +119,7 @@ The **PackageId** is the same value as exists in the Manifest file. ``` -**Subsystems** - AppExtensions and other subsystems are arranged as subnodes under the : +**Subsystems**: AppExtensions and other subsystems are arranged as subnodes under ``, as show in the following example. ```xml @@ -128,15 +132,17 @@ The **PackageId** is the same value as exists in the Manifest file. Each subsystem can be enabled/disabled using the “**Enabled**” attribute. Below are the various subsystems and usage samples. -**Extensions:** +### Extensions -Some subsystems (Extension Subsystems) control Extensions. Those subsystems are:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM +Extension Subsystems control extensions. These subsystems are Shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM. -Extension Subsystems can be enabled and disabled independently of the content.  Thus if Shortcuts are enabled, The client will use the shortcuts contained within the manifest by default. Each Extension Subsystem can contain an node. If this child element is present, the client will ignore the content in the Manifest file for that subsystem and only use the content in the configuration file. +Extension Subsystems can be enabled and disabled independently of the content.  Therefore, if Shortcuts are enabled, the client will use the shortcuts contained within the manifest by default. Each Extension Subsystem can contain an `` node. If this child element is present, the client will ignore the content in the Manifest file for that subsystem and only use the content in the configuration file. -Example using the shortcuts subsystem: +### Examples of the shortcuts subsystem -**Example 1**
If the user defined this in either the dynamic or deployment config file: +#### Example 1 + +Content will be ignored if the user defined the following in either the dynamic or deployment config file: ```xml                               @@ -146,15 +152,15 @@ Example using the shortcuts subsystem:                               ``` -Content in the manifest will be ignored.    +#### Example 2 -**Example 2**
If the user defined only the following: +Content in the manifest will be integrated during publishing if the user defined only the following:                             `` - -Then the content in the Manifest will be integrated during publishing. -**Example 3**
If the user defines the following +#### Example 3 + +All shortcuts in the manifest will be ignored and no shortcuts will be integrated if the user defines the following: ```xml                             @@ -162,9 +168,7 @@ Then the content in the Manifest will be integrated during publishing.                               ``` -Then all the shortcuts within the manifest will still be ignored. There will be no shortcuts integrated. - -The supported Extension Subsystems are: +### Supported Extension Subsystems **Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts: @@ -348,11 +352,11 @@ The supported Extension Subsystems are: ` ` -**Other Settings**: +### Other Settings In addition to Extensions, other subsystems can be enabled/disabled and edited: -**Virtual Kernel Objects**: +#### Virtual Kernel Objects ` ` @@ -370,15 +374,15 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited:   ``` -**Virtual File System** +#### Virtual File System `       ` -**Virtual Fonts** +#### Virtual Fonts `       ` -**Virtual Environment Variables** +#### Virtual Environment Variables ```xml @@ -392,15 +396,17 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited:          ``` -**Virtual services** +#### Virtual services `       ` **UserScripts** – Scripts can be used to setup or alter the virtual environment as well as execute scripts at time of deployment or removal, before an application executes, or they can be used to “clean up” the environment after the application terminates. Please reference a sample User configuration file that is output by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used. -### Dynamic Deployment Configuration file +## Dynamic Deployment Configuration file -**Header** - The header of a Deployment Configuration file is as follows: +### Header + +The header of a Deployment Configuration file is as follows: ```xml @@ -408,11 +414,13 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: The **PackageId** is the same value as exists in the manifest file. -**Body** - The body of the deployment configuration file includes two sections: +### Body -- User Configuration section –allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest. +The body of the deployment configuration file includes two sections: -- Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS. +- User Configuration section –allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest. + +- Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS. ```xml From 6010bc1a4e1a7603d5d5220498a55bec1c0280d2 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 24 Aug 2018 16:56:57 -0700 Subject: [PATCH 25/33] Editorial changes --- .../app-v/appv-dynamic-configuration.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index ba644f8cb7..47ab665c4d 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -418,9 +418,9 @@ The **PackageId** is the same value as exists in the manifest file. The body of the deployment configuration file includes two sections: -- User Configuration section –allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest. +- The User Configuration section allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest. -- Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS. +- The Machine Configuration section contains information that can only be configured for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS. ```xml @@ -439,7 +439,9 @@ The body of the deployment configuration file includes two sections: Machine Configuration - the Machine configuration section of the Deployment Configuration File is used to configure information that can be set only for an entire machine, not for a specific user on the computer. For example, HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. There are four subsections allowed in under this element -1. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under : +#### Subsystems + +AppExtensions and other subsystems are arranged as subnodes under ``: ```xml @@ -452,11 +454,11 @@ Machine Configuration - the Machine configuration section of the Deployment Conf The following section displays the various subsystems and usage samples. -**Extensions**: +### Extensions Some subsystems (Extension Subsystems) control Extensions which can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section. -**Application Capabilities**: Used by default programs in windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain windows MIME types.  This extension also makes the virtual application visible in the Set Default Programs UI.: +**Application Capabilities**: Used by default programs in Windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain Windows MIME types.  This extension also makes the virtual application visible in the Set Default Programs UI.: ```xml From b3726b9ba35e8d5e44623c6bd55819df6c311432 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 27 Aug 2018 16:54:40 -0700 Subject: [PATCH 26/33] Continued fixing up dynamic configuration article --- .../app-v/appv-dynamic-configuration.md | 29 +++++++++++++------ 1 file changed, 20 insertions(+), 9 deletions(-) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index 47ab665c4d..1eb18ab2a6 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -456,9 +456,11 @@ The following section displays the various subsystems and usage samples. ### Extensions -Some subsystems (Extension Subsystems) control Extensions which can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section. +Some subsystems (Extension Subsystems) control extensions that can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section. -**Application Capabilities**: Used by default programs in Windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain Windows MIME types.  This extension also makes the virtual application visible in the Set Default Programs UI.: +#### Application Capabilities + +Used by default programs in the Windows OS interface, the Application Capabilities extension allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, and as capable of opening certain Windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI. ```xml @@ -496,11 +498,11 @@ Some subsystems (Extension Subsystems) control Extensions which can only apply t ``` -**Other Settings**: +#### Other Settings -In addition to Extensions, other subsystems can be edited: +You can edit other subsystems in addition to Extensions: -**Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine +* Machine-wide Virtual Registry: use this when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine. ```xml @@ -514,7 +516,7 @@ In addition to Extensions, other subsystems can be edited: ``` -**Machine Wide Virtual Kernel Objects** +* Machine-wide Virtual Kernel Objects ```xml @@ -524,7 +526,7 @@ In addition to Extensions, other subsystems can be edited: ``` -**ProductSourceURLOptOut**: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch. +* ProductSourceURLOptOut: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch. ```xml @@ -534,9 +536,9 @@ In addition to Extensions, other subsystems can be edited: ``` -**MachineScripts** – Package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used +* MachineScripts: The package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used -**TerminateChildProcess**:- An application executable can be specified, whose child processes will be terminated when the application exe process is terminated. +* TerminateChildProcess: an application executable can be specified whose child processes will be terminated when the application exe process is terminated. ```xml @@ -681,6 +683,15 @@ Using the following example file and table, modify the deployment or user config ``` +|Parameter in the example file|Description| +|---|---| +||| +||| +||| +||| + + + From eadcc7afa6d3d2656f7c3ccef13353e8ae6d45c8 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 24 Sep 2018 16:52:00 -0700 Subject: [PATCH 27/33] Continued making edits for pull request --- .../app-v/appv-delete-a-connection-group.md | 2 +- ...e-a-package-with-the-management-console.md | 2 +- ...ctronic-software-distribution-solutions.md | 2 +- ...ctronic-software-distribution-solutions.md | 2 +- .../app-v/appv-dynamic-configuration.md | 184 +++++------------- .../app-v/appv-for-windows.md | 2 +- ...-powershell-cmdlets-and-get-cmdlet-help.md | 2 +- .../app-v/appv-maintaining-appv.md | 2 +- ...-a-stand-alone-computer-with-powershell.md | 2 +- .../app-v/appv-publish-a-connection-group.md | 20 +- ...-a-packages-with-the-management-console.md | 2 +- 11 files changed, 63 insertions(+), 159 deletions(-) diff --git a/windows/application-management/app-v/appv-delete-a-connection-group.md b/windows/application-management/app-v/appv-delete-a-connection-group.md index b0d9d87b41..38682667e8 100644 --- a/windows/application-management/app-v/appv-delete-a-connection-group.md +++ b/windows/application-management/app-v/appv-delete-a-connection-group.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 08/24/2018 +ms.date: 09/25/2018 --- # How to delete a connection group diff --git a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md index d7d7d9558c..be85faa43f 100644 --- a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md +++ b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 08/24/2018 +ms.date: 09/25/2018 --- # How to delete a package in the Management Console diff --git a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md index 54f8ebc877..f9a0ddbd9c 100644 --- a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 08/24/2018 +ms.date: 09/25/2018 --- # How to deploy App-V packages using electronic software distribution diff --git a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 5c8be25f3c..5ed8fcc2a2 100644 --- a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 08/24/2018 +ms.date: 09/25/2018 --- # Deploying App-V packages by using electronic software distribution (ESD) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index 1eb18ab2a6..5dbe9dc477 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 08/24/2018 +ms.date: 09/25/2018 --- # About App-V dynamic configuration @@ -30,40 +30,25 @@ These .xml files specify package settings let you customize packages without dir ## Dynamic Configuration file contents -All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following list: +All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. The following table represents in which order the files will be read: -1. User configuration .xml file. -2. Deployment configuration .xml file. -3. Package manifest. +|| +|---| +|User Configuration .xml file| +|Deployment Configuration .xml file| +|Package Manifest| -
--- - - - - - - - - - - - -

User Configuration .xml file

Deployment Configuration .xml file

Package Manifest

- -The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults. +The previous table represents how the files will be read. The first entry represents what will be read last. Therefore, its content takes precedence. This means all packages inherently contain and provide default settings from the Package Manifest. If you apply a Deployment Configuration .xml file with customized settings, it will override the package manifest defaults. If you apply a User Configuration .xml file with customized settings prior to that, it will override both the deployment configuration and the Package Manifest defaults. There are two types of configuration files: -- **User Configuration File (UserConfig)** – Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. +- **User Configuration File (UserConfig)**: Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. -- **Deployment Configuration File (DeploymentConfig)** – Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. +- **Deployment Configuration File (DeploymentConfig)**: Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. You can use the UserConfig file to customize the settings for a package for a specific set of users on a computer or make changes that will be applied to local user locations such as HKCU. You can use the DeploymentConfig file to modify the default settings of a package for all users on a machine or make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the All Users folder. -The UserConfig file provides configuration settings that can be applied to a single user without affecting any other users on a client: +The UserConfig file provides configuration settings that you can apply to a single user without affecting any other users on a client: - Extensions that will be integrated into the native system per user: shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM. @@ -119,7 +104,7 @@ The Dynamic User Configuration file's body can include all app extension points ``` -**Subsystems**: AppExtensions and other subsystems are arranged as subnodes under ``, as show in the following example. +**Subsystems**: AppExtensions and other subsystems are arranged as subnodes under ``, as shown in the following example. ```xml @@ -130,7 +115,7 @@ The Dynamic User Configuration file's body can include all app extension points ``` -Each subsystem can be enabled/disabled using the “**Enabled**” attribute. Below are the various subsystems and usage samples. +Each subsystem can be enabled/disabled using the **Enabled** attribute. The following sections describe the various subsystems and usage samples. ### Extensions @@ -170,7 +155,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ### Supported Extension Subsystems -**Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts: +**Shortcuts:** This controls shortcuts that will be integrated into the local system. The following example has two shortcuts: ```xml @@ -208,7 +193,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ``` -**File-Type Associations:** Associates File-types with programs to open by default as well as setup the context menu. (MIME types can also be setup using this susbsystem). Sample File-type Association is below: +**File Type Associations:** Associates file types with programs to open by default as well as setup the context menu. (MIME types can also be set up with this susbsystem). The following is an example of a FileType association: ```xml @@ -274,7 +259,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ``` -**URL Protocols**: This controls the URL Protocols that are integrated into the local registry of the client machine e.g. “mailto:”. +**URL Protocols**: This controls the URL Protocols integrated into the local registry of the client machine. The following example illustrates the “mailto:” ptrotocol. ```xml @@ -321,7 +306,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate   ``` -**Software Clients**: Allows the app to register as an Email client, news reader, media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases you should only need to enable and disable it. There is also a control to enable and disable the email client specifically if you want the other clients still enabled except for that client. +**Software Clients**: Allows the app to register as an email client, news reader, or media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases, you only need to enable and disable it. There's also a control that lets you enable and disable the email client if you want all other clients besides the email client to stay enabled. ```xml @@ -329,7 +314,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ``` -**AppPaths**: If an application for example contoso.exe is registered with an apppath name of “myapp”, it allows you type “myapp” under the run menu and it will open contoso.exe. +**AppPaths**: If an application, such as contoso.exe, is registered with an apppath name of “myapp”, this subsystem lets you open the app by entering “myapp” into the run menu. ```xml @@ -348,19 +333,23 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ``` -**COM**: Allows an Application register Local COM servers. Mode can be Integration, Isolated or Off. When Isol. +**COM**: Allows an Application to register Local COM servers. Mode can be Integration, Isolated or Off. When Isol. -` ` +```xml + +``` -### Other Settings +### Other settings In addition to Extensions, other subsystems can be enabled/disabled and edited: #### Virtual Kernel Objects -` ` +```xml + +```xml -**Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU +**Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU. ```xml @@ -376,11 +365,15 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: #### Virtual File System -`       ` +```xml +       +``` #### Virtual Fonts -`       ` +```xml +       +``` #### Virtual Environment Variables @@ -398,9 +391,11 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: #### Virtual services -`       ` +```xml +       +``` -**UserScripts** – Scripts can be used to setup or alter the virtual environment as well as execute scripts at time of deployment or removal, before an application executes, or they can be used to “clean up” the environment after the application terminates. Please reference a sample User configuration file that is output by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used. +**UserScripts**: Scripts can be used to set up or alter the virtual environment and execute scripts on deployment or removal, before an application executes, or they can clean up the environment after the application terminates. Please refer to a sample User Configuration file output by the sequencer to see a sample script. The following Scripts section provides more information about the various triggers you can use to set up scripts. ## Dynamic Deployment Configuration file @@ -412,7 +407,7 @@ The header of a Deployment Configuration file is as follows: ``` -The **PackageId** is the same value as exists in the manifest file. +The **PackageId** is the same value as the one that exists in the Manifest file. ### Body @@ -425,7 +420,7 @@ The body of the deployment configuration file includes two sections: ```xml -  .. +.. .. @@ -435,9 +430,9 @@ The body of the deployment configuration file includes two sections: ``` -**User Configuration** - use the previous **Dynamic User Configuration file** section for information on settings that are provided in the user configuration section of the Deployment Configuration file. +User Configuration: see [Dynamic User Configuration](appv-dynamic-configuration.md#dynamic-user-configuration) for more information about this section. -Machine Configuration - the Machine configuration section of the Deployment Configuration File is used to configure information that can be set only for an entire machine, not for a specific user on the computer. For example, HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. There are four subsections allowed in under this element +Machine Configuration: The Machine Configuration section of the Deployment Configuration File is used to configure information that can be set only for an entire machine, not for a specific user on the computer. For example, HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. This element can have the following four subsections. #### Subsystems @@ -556,7 +551,7 @@ You can edit other subsystems in addition to Extensions: The following table describes the various script events and the context under which they can be run. -|Script Execution Time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the Virtual Environment of the package|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)| +|Script Execution Time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the package's virtual environment|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)| |---|:---:|:---:|:---:|:---:|:---:| |AddPackage|X||||(SYSTEM, N/A)| |PublishPackage|X|X|||(SYSTEM, User)| @@ -567,93 +562,6 @@ The following table describes the various script events and the context under wh |StartVirtualEnvironment|X|X|X||(User, User)| |TerminateVirtualEnvironment|X|X|||(User, User)| - -------- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Script Execution TimeCan be specified in Deployment ConfigurationCan be specified in User ConfigurationCan run in the Virtual Environment of the packageCan be run in the context of a specific applicationRuns in system/user context: (Deployment Configuration, User Configuration)

AddPackage

X

(SYSTEM, N/A)

PublishPackage

X

X

(SYSTEM, User)

UnpublishPackage

X

X

(SYSTEM, User)

RemovePackage

X

(SYSTEM, N/A)

StartProcess

X

X

X

X

(User, User)

ExitProcess

X

X

X

(User, User)

StartVirtualEnvironment

X

X

X

(User, User)

TerminateVirtualEnvironment

X

X

(User, User)

- ### Using multiple scripts on a single event trigger App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows 10. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client. @@ -685,10 +593,10 @@ Using the following example file and table, modify the deployment or user config |Parameter in the example file|Description| |---|---| -||| -||| -||| -||| +||Name of the event trigger for which you are running a script, such as adding a package or publishing a package.| +|`ScriptRunner.exe`|The script launcher application included in the App-V client.

Although ScriptRunner.exe is included in the App-V client, the App-V client's location must be in %path% or ScriptRunner won't run. `ScriptRunner.exe` is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.| +|`-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10`

`-appvscript script2.vbs arg1 arg2`

`-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror`|`-appvscript`: token that represents the actual script you want to run.
`script1.exe`: name of the script you want to run.
`arg1 arg2`: arguments for the script you want to run.
`-appvscriptrunnerparameters`: token that represents the execution options for script1.exe
`-wait`: token that informs ScriptRunner to wait for execution of script1.exe to complete before proceeding to the next script.
`-timeout=x`: token that informs ScriptRunner to stop running the current script after x number of seconds. All other specified scripts will still run.
`-rollbackonerror`: token that informs ScriptRunner to stop running all scripts that haven't yet run and to roll back an error to the App-V client.| +||Waits for overall completion of ScriptRunner.exe.

Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.

If any individual script reported an error and rollbackonerror was set to true, then ScriptRunner would report the error to App-V client.| diff --git a/windows/application-management/app-v/appv-for-windows.md b/windows/application-management/app-v/appv-for-windows.md index 3b0a24c87d..a68e40142b 100644 --- a/windows/application-management/app-v/appv-for-windows.md +++ b/windows/application-management/app-v/appv-for-windows.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 09/25/2018 --- # Application Virtualization (App-V) for Windows 10 overview diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index efd4e69e63..ace19757e8 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 09/25/2018 --- # How to load the Windows PowerShell cmdlets for App-V and get cmdlet help diff --git a/windows/application-management/app-v/appv-maintaining-appv.md b/windows/application-management/app-v/appv-maintaining-appv.md index 6372fefcc7..4320156e54 100644 --- a/windows/application-management/app-v/appv-maintaining-appv.md +++ b/windows/application-management/app-v/appv-maintaining-appv.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 09/25/2018 --- # Maintaining App-V diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md index 6d3f09d4fc..dc187289aa 100644 --- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md +++ b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 09/24/2018 --- # How to manage App-V packages running on a stand-alone computer by using Windows PowerShell diff --git a/windows/application-management/app-v/appv-publish-a-connection-group.md b/windows/application-management/app-v/appv-publish-a-connection-group.md index 739de9f0a3..1df205137e 100644 --- a/windows/application-management/app-v/appv-publish-a-connection-group.md +++ b/windows/application-management/app-v/appv-publish-a-connection-group.md @@ -6,29 +6,25 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 09/25/2018 --- - - # How to Publish a Connection Group -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 After you create a connection group, you must publish it to computers that run the App-V client. -**To publish a connection group** +## Publish a connection group -1. Open the App-V Management Console, and select **CONNECTION GROUPS**. +1. Open the App-V Management Console and select **CONNECTION GROUPS**. -2. Right-click the connection group to be published, and select **publish**. +2. Right-click the connection group to be published, and select **publish**. ## Have a suggestion for App-V? -Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization).
For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). +Add or vote on suggestions on the [Application Virtualization feedback site](https://appv.uservoice.com/forums/280448-microsoft-application-virtualization). ## Related topics -[Operations for App-V](appv-operations.md) - -[Managing Connection Groups](appv-managing-connection-groups.md) +* [Operations for App-V](appv-operations.md) +* [Managing connection groups](appv-managing-connection-groups.md) diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index 62abefd38a..97b464ac1f 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 04/19/2017 +ms.date: 09/25/2018 --- # How to publish a package by using the Management console From b3128a69d6d615dc278a8931bd7fc0bd0fcba38e Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 25 Sep 2018 16:40:51 -0700 Subject: [PATCH 28/33] Continued editing article --- .../app-v/appv-dynamic-configuration.md | 89 ++++++++++--------- 1 file changed, 47 insertions(+), 42 deletions(-) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index 5dbe9dc477..1a4ed7f29c 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -14,7 +14,7 @@ ms.date: 09/25/2018 You can use dynamic configuration to customize an App-V package for a user. This article will tell you how to create or edit an existing dynamic configuration file. -When you edit the dynamic configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and provides a way to keep package content and custom settings independent. +When you edit the Dynamic Configuration file, it customizes how an App-V package will run for a user or group. This makes package customization more convenient by removing the need to resequence packages using the desired settings and provides a way to keep package content and custom settings independent. ## Advanced: dynamic configuration @@ -42,9 +42,9 @@ The previous table represents how the files will be read. The first entry repres There are two types of configuration files: -- **User Configuration File (UserConfig)**: Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. +- **User Configuration file (UserConfig)**: Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. -- **Deployment Configuration File (DeploymentConfig)**: Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. +- **Deployment Configuration file (DeploymentConfig)**: Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. You can use the UserConfig file to customize the settings for a package for a specific set of users on a computer or make changes that will be applied to local user locations such as HKCU. You can use the DeploymentConfig file to modify the default settings of a package for all users on a machine or make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the All Users folder. @@ -56,9 +56,9 @@ The UserConfig file provides configuration settings that you can apply to a sing - Scripts (user context only). -The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the UserConfig list above: +The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the preceding UserConfig list: -- All UserConfig settings above +- All UserConfig settings from the preceding section in this topic - Extensions that can only be applied globally for all users @@ -68,7 +68,7 @@ The DeploymentConfig file provides configuration settings in two sections, one r - Scripts (Machine context only) -- Controls to Terminate Child Processes +- Controls to terminate child processes ## File structure @@ -87,7 +87,7 @@ The following is an example of a Dynamic User Configuration file's header: The **PackageId** is the same value that exists in the Manifest file. -### Body +### Dynamic User Configuration file body The Dynamic User Configuration file's body can include all app extension points defined in the Manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body: @@ -117,7 +117,7 @@ The Dynamic User Configuration file's body can include all app extension points Each subsystem can be enabled/disabled using the **Enabled** attribute. The following sections describe the various subsystems and usage samples. -### Extensions +### Dynamic User Configuration file extensions Extension Subsystems control extensions. These subsystems are Shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM. @@ -141,7 +141,10 @@ Content will be ignored if the user defined the following in either the dynamic Content in the manifest will be integrated during publishing if the user defined only the following: +```xml +                             `` +``` #### Example 3 @@ -155,7 +158,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ### Supported Extension Subsystems -**Shortcuts:** This controls shortcuts that will be integrated into the local system. The following example has two shortcuts: +**Shortcuts**: This controls shortcuts that will be integrated into the local system. The following example has two shortcuts: ```xml @@ -193,7 +196,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ``` -**File Type Associations:** Associates file types with programs to open by default as well as setup the context menu. (MIME types can also be set up with this susbsystem). The following is an example of a FileType association: +**File Type Associations**: Associates file types with programs to open by default as well as setup the context menu. (MIME types can also be set up with this susbsystem). The following is an example of a FileType association: ```xml @@ -306,7 +309,7 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate   ``` -**Software Clients**: Allows the app to register as an email client, news reader, or media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases, you only need to enable and disable it. There's also a control that lets you enable and disable the email client if you want all other clients besides the email client to stay enabled. +**Software Clients**: Allows the app to register as an email client, news reader, or media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases, you only need to enable and disable it. There's also a control that lets you enable or disable the email client only in case you want all the other clients to remain as they are. ```xml @@ -339,9 +342,9 @@ All shortcuts in the manifest will be ignored and no shortcuts will be integrate ``` -### Other settings +### Other settings for Dynamic User Configuration file -In addition to Extensions, other subsystems can be enabled/disabled and edited: +In addition to Extensions, the following other subsystems can be enabled/disabled and edited. #### Virtual Kernel Objects @@ -349,7 +352,7 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited: ```xml -**Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU. +**Virtual Registry**: use this if you want to set a registry in the Virtual Registry within HKCU. ```xml @@ -395,13 +398,15 @@ In addition to Extensions, other subsystems can be enabled/disabled and edited:       ``` -**UserScripts**: Scripts can be used to set up or alter the virtual environment and execute scripts on deployment or removal, before an application executes, or they can clean up the environment after the application terminates. Please refer to a sample User Configuration file output by the sequencer to see a sample script. The following Scripts section provides more information about the various triggers you can use to set up scripts. +#### UserScripts + +Scripts can be used to set up or alter the virtual environment and execute scripts on deployment or removal, before an application executes, or they can clean up the environment after the application terminates. Please refer to a sample User Configuration file output by the sequencer to see a sample script. See the [Scripts](appv-dynamic-configuration.md#scripts) section for more information about the various triggers you can use to set up scripts. ## Dynamic Deployment Configuration file -### Header +### Dynamic Deployment Configuration file header -The header of a Deployment Configuration file is as follows: +The header of a Deployment Configuration file should look something like this: ```xml @@ -409,7 +414,7 @@ The header of a Deployment Configuration file is as follows: The **PackageId** is the same value as the one that exists in the Manifest file. -### Body +### Dynamic Deployment Configuration file body The body of the deployment configuration file includes two sections: @@ -432,7 +437,7 @@ The body of the deployment configuration file includes two sections: User Configuration: see [Dynamic User Configuration](appv-dynamic-configuration.md#dynamic-user-configuration) for more information about this section. -Machine Configuration: The Machine Configuration section of the Deployment Configuration File is used to configure information that can be set only for an entire machine, not for a specific user on the computer. For example, HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. This element can have the following four subsections. +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. #### Subsystems @@ -447,15 +452,15 @@ AppExtensions and other subsystems are arranged as subnodes under `` ``` -The following section displays the various subsystems and usage samples. +The following section describes the various subsystems and usage samples. -### Extensions +#### Extensions -Some subsystems (Extension Subsystems) control extensions that can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section. +Some subsystems (Extension Subsystems) control extensions that can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The rules for User Configuration extension controls and settings also apply to the ones in Machine Configuration. #### Application Capabilities -Used by default programs in the Windows OS interface, the Application Capabilities extension allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, and as capable of opening certain Windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI. +Used by default programs in the Windows OS interface, the Application Capabilities extension allows an application to register itself as capable of opening certain file extensions, as a contender for the Start menu's internet browser slot, and as capable of opening certain Windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI. ```xml @@ -493,11 +498,11 @@ Used by default programs in the Windows OS interface, the Application Capabiliti ``` -#### Other Settings +#### Other settings for Dynamic Deployment Configuration file -You can edit other subsystems in addition to Extensions: +You can edit other subsystems in addition to extensions: -* Machine-wide Virtual Registry: use this when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine. +- Machine-wide Virtual Registry: use this when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine. ```xml @@ -511,7 +516,7 @@ You can edit other subsystems in addition to Extensions: ``` -* Machine-wide Virtual Kernel Objects +- Machine-wide Virtual Kernel Objects ```xml @@ -521,23 +526,23 @@ You can edit other subsystems in addition to Extensions: ``` -* ProductSourceURLOptOut: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch. +- ProductSourceURLOptOut: Indicates whether the URL for the package can be modified globally through PackageSourceRoot to support branch office scenarios. It's set to False by default. Changes to the value take effect on the next launch. ```xml -   ..  +   ..      .. ``` -* MachineScripts: The package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used +- MachineScripts: The package can be configured to execute scripts upon deployment, publishing, or removal. To see an example script, please see a sample deployment configuration file generated by the sequencer. The following section provides more information about the various triggers you can use to set up scripts. -* TerminateChildProcess: an application executable can be specified whose child processes will be terminated when the application exe process is terminated. +- TerminateChildProcess: you can use this to specify that an application executable's child processes will be terminated when the application.exe process is terminated. ```xml -   ..    +   ..              @@ -551,7 +556,7 @@ You can edit other subsystems in addition to Extensions: The following table describes the various script events and the context under which they can be run. -|Script Execution Time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the package's virtual environment|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)| +|Script execution time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the package's virtual environment|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)| |---|:---:|:---:|:---:|:---:|:---:| |AddPackage|X||||(SYSTEM, N/A)| |PublishPackage|X|X|||(SYSTEM, User)| @@ -568,10 +573,10 @@ App-V supports the use of multiple scripts on a single event trigger for App-V p #### How to use multiple scripts on a single event trigger -For each script that you want to run, pass that script as an argument to the ScriptRunner.exe application. The application then runs each script separately, along with the arguments that you specify for each script. Use only one script (ScriptRunner.exe) per trigger. +For each script that you want to run, pass that script as an argument to the ScriptRunner.exe application. The application will run each script separately, along with the arguments that you specify for each script. Use only one script (ScriptRunner.exe) per trigger. >[!NOTE] ->We recommended that you run the multi-script line from a command prompt first to make sure that all arguments are built correctly before adding them to the deployment configuration file. +>We recommended you first run the multi-script line from a command prompt to make sure all arguments are built correctly before adding them to the deployment configuration file. #### Example script and parameter descriptions @@ -593,10 +598,10 @@ Using the following example file and table, modify the deployment or user config |Parameter in the example file|Description| |---|---| -||Name of the event trigger for which you are running a script, such as adding a package or publishing a package.| +||Name of the event trigger you're running a script for, such as when adding or publishing a package.| |`ScriptRunner.exe`|The script launcher application included in the App-V client.

Although ScriptRunner.exe is included in the App-V client, the App-V client's location must be in %path% or ScriptRunner won't run. `ScriptRunner.exe` is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.| -|`-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10`

`-appvscript script2.vbs arg1 arg2`

`-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror`|`-appvscript`: token that represents the actual script you want to run.
`script1.exe`: name of the script you want to run.
`arg1 arg2`: arguments for the script you want to run.
`-appvscriptrunnerparameters`: token that represents the execution options for script1.exe
`-wait`: token that informs ScriptRunner to wait for execution of script1.exe to complete before proceeding to the next script.
`-timeout=x`: token that informs ScriptRunner to stop running the current script after x number of seconds. All other specified scripts will still run.
`-rollbackonerror`: token that informs ScriptRunner to stop running all scripts that haven't yet run and to roll back an error to the App-V client.| -||Waits for overall completion of ScriptRunner.exe.

Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.

If any individual script reported an error and rollbackonerror was set to true, then ScriptRunner would report the error to App-V client.| +|`-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10`

`-appvscript script2.vbs arg1 arg2`

`-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror`|`-appvscript`: token that represents the actual script you want to run.
`script1.exe`: name of the script you want to run.
`arg1 arg2`: arguments for the script you want to run.
`-appvscriptrunnerparameters`: token that represents the execution options for script1.exe.
`-wait`: token that tells ScriptRunner to wait for execution of script1.exe to finish before proceeding to the next script.
`-timeout=x`: token that informs ScriptRunner to stop running the current script after *x* number of seconds. All other specified scripts will still run.
`-rollbackonerror`: token that tells ScriptRunner to stop running all scripts that haven't yet run and roll back an error to the App-V client.| +||Waits for overall completion of ScriptRunner.exe.

Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.

If any individual script reported an error and rollbackonerror was set to True, then ScriptRunner would report the error to App-V client.| @@ -654,15 +659,15 @@ Using the following example file and table, modify the deployment or user config   -ScriptRunner will run any script whose file type is associated with an application installed on the computer. If the associated application is missing, or the script’s file type is not associated with any application on the computer, the script will not run. +ScriptRunner will run any script whose file type is associated with an application installed on the computer. If the associated application is missing, or the script’s file type isn't associated with any of the computer's applications, the script won't run. ### Create a Dynamic Configuration file using an App-V Manifest file -You can create the Dynamic Configuration file using one of three methods: either manually, using the App-V Management Console or sequencing a package, which will be generated with 2 sample files. +You can create the Dynamic Configuration file using one of three methods: manually, using the App-V Management Console, or by sequencing a package, which will generate a package with two sample files. -For more information about how to create the file using the App-V Management Console see, [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md). +For more information about how to create the file using the App-V Management Console, see [How to create a Custom Configuration file by using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md). -To create the file manually, the information above in previous sections can be combined into a single file. We recommend you use files generated by the sequencer. +To create the file manually, you can combine the components listed in the previous sections into a single file. However, we recommend you use files generated by the sequencer instead of manually created ones. ## Have a suggestion for App-V? From de5243f324cef648b2ae40c89c95e5a15f7cf623 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 27 Sep 2018 18:38:36 +0000 Subject: [PATCH 29/33] Updated fileless-threats.md --- .../intelligence/fileless-threats.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/intelligence/fileless-threats.md b/windows/security/threat-protection/intelligence/fileless-threats.md index 050b8e2733..a677699653 100644 --- a/windows/security/threat-protection/intelligence/fileless-threats.md +++ b/windows/security/threat-protection/intelligence/fileless-threats.md @@ -22,11 +22,11 @@ To shed light on this loaded term, we grouped fileless threats into different ca ![Comprehensive diagram of fileless malware](images/fileless-malware.png)
*Figure 1. Comprehensive diagram of fileless malware* -First, we can classify the entry point (inner circle in the diagram), which indicates how fileless malware can arrive on a machine: via an exploit; through compromised hardware; or via regular execution of applications and scripts. +We can classify fileless threats by their entry point (i.e., execution/injection, exploit, hardware), then the form of entry point (e.g., file, script, etc.), and finally by the host of the infection (e.g., Flash, Java, documents). -Next, we can list the form of entry point (intermediate circle): for example, exploits can be based on files or network data; PCI peripherals are a type of hardware vector; and scripts and executables are sub-categories of the execution vector. +Next, we can list the form of entry point: for example, exploits can be based on files or network data; PCI peripherals are a type of hardware vector; and scripts and executables are sub-categories of the execution vector. -Finally, we can classify the host of the infection (outer circle): for example, a Flash application that may contain an exploit; a simple executable; a malicious firmware from a hardware device; or an infected MBR, which could bootstrap the execution of a malware before the operating system even loads. +Finally, we can classify the host of the infection: for example, a Flash application that may contain an exploit; a simple executable; a malicious firmware from a hardware device; or an infected MBR, which could bootstrap the execution of a malware before the operating system even loads. This helps us divide and categorize the various kinds of fileless threats. Clearly, the categories are not all the same: some are more dangerous but also more difficult to implement, while others are more commonly used despite (or precisely because of) not being very advanced. @@ -89,3 +89,8 @@ Having described the broad categories, we can now dig into the details and provi **Disk-based** (Type II: Boot Record): The [Boot Record](https://en.wikipedia.org/wiki/Boot_sector) is the first sector of a disk or volume and contains executable code required to start the boot process of the operating system. Threats like [Petya](https://cloudblogs.microsoft.com/microsoftsecure/2017/06/27/new-ransomware-old-techniques-petya-adds-worm-capabilities/?source=mmpc) are capable of infecting the Boot Record by overwriting it with malicious code, so that when the machine is booted the malware immediately gains control (and in the case of Petya, with disastrous consequences). The Boot Record resides outside the file system, but it’s accessible by the operating system, and modern antivirus products have the capability to scan and restore it. +##Defeating fileless malware + +At Microsoft, we actively monitor the security landscape to identify new threat trends and develop solutions that continuously enhance Windows security and mitigate classes of threats. We instrument durable protections that are effective against a wide range of threats. Through AntiMalware Scan Interface (AMSI), behavior monitoring, memory scanning, and boot sector protection, Windows Defender Advanced Threat Protection [(Windows Defender ATP)](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-fileless) can inspect fileless threats even with heavy obfuscation. Machine learning technologies in the cloud allow us to scale these protections against new and emerging threats. + +To learn more, read: Out of sight but not invisible: [Defeating fileless malware with behavior monitoring, AMSI, and next-gen AV](https://cloudblogs.microsoft.com/microsoftsecure/2018/09/27/out-of-sight-but-not-invisible-defeating-fileless-malware-with-behavior-monitoring-amsi-and-next-gen-av/) \ No newline at end of file From 10b8bc351660c0f85db977c88311ee37942d8d51 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 27 Sep 2018 18:42:25 +0000 Subject: [PATCH 30/33] Updated fileless-threats.md --- .../security/threat-protection/intelligence/fileless-threats.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/intelligence/fileless-threats.md b/windows/security/threat-protection/intelligence/fileless-threats.md index a677699653..d5aa29c09f 100644 --- a/windows/security/threat-protection/intelligence/fileless-threats.md +++ b/windows/security/threat-protection/intelligence/fileless-threats.md @@ -22,7 +22,7 @@ To shed light on this loaded term, we grouped fileless threats into different ca ![Comprehensive diagram of fileless malware](images/fileless-malware.png)
*Figure 1. Comprehensive diagram of fileless malware* -We can classify fileless threats by their entry point (i.e., execution/injection, exploit, hardware), then the form of entry point (e.g., file, script, etc.), and finally by the host of the infection (e.g., Flash, Java, documents). +We can classify fileless threats by their entry point, which indicates how fileless malware can arrive on a machine: via an exploit; through compromised hardware; or via regular execution of applications and scripts. Next, we can list the form of entry point: for example, exploits can be based on files or network data; PCI peripherals are a type of hardware vector; and scripts and executables are sub-categories of the execution vector. From d579ee97bd02f8907c4187c60e706460149a7fa9 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Thu, 27 Sep 2018 18:43:39 +0000 Subject: [PATCH 31/33] Updated fileless-threats.md --- .../security/threat-protection/intelligence/fileless-threats.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/intelligence/fileless-threats.md b/windows/security/threat-protection/intelligence/fileless-threats.md index d5aa29c09f..75d4bdeedd 100644 --- a/windows/security/threat-protection/intelligence/fileless-threats.md +++ b/windows/security/threat-protection/intelligence/fileless-threats.md @@ -93,4 +93,4 @@ Having described the broad categories, we can now dig into the details and provi At Microsoft, we actively monitor the security landscape to identify new threat trends and develop solutions that continuously enhance Windows security and mitigate classes of threats. We instrument durable protections that are effective against a wide range of threats. Through AntiMalware Scan Interface (AMSI), behavior monitoring, memory scanning, and boot sector protection, Windows Defender Advanced Threat Protection [(Windows Defender ATP)](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-fileless) can inspect fileless threats even with heavy obfuscation. Machine learning technologies in the cloud allow us to scale these protections against new and emerging threats. -To learn more, read: Out of sight but not invisible: [Defeating fileless malware with behavior monitoring, AMSI, and next-gen AV](https://cloudblogs.microsoft.com/microsoftsecure/2018/09/27/out-of-sight-but-not-invisible-defeating-fileless-malware-with-behavior-monitoring-amsi-and-next-gen-av/) \ No newline at end of file +To learn more, read: [Out of sight but not invisible: Defeating fileless malware with behavior monitoring, AMSI, and next-gen AV](https://cloudblogs.microsoft.com/microsoftsecure/2018/09/27/out-of-sight-but-not-invisible-defeating-fileless-malware-with-behavior-monitoring-amsi-and-next-gen-av/) \ No newline at end of file From fd06af4735276cd8dfb4ff618f4b0245074c7c8d Mon Sep 17 00:00:00 2001 From: Eric Avena Date: Thu, 27 Sep 2018 18:58:08 +0000 Subject: [PATCH 32/33] Updated fileless-threats.md --- .../security/threat-protection/intelligence/fileless-threats.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/intelligence/fileless-threats.md b/windows/security/threat-protection/intelligence/fileless-threats.md index 75d4bdeedd..ec5da8fb32 100644 --- a/windows/security/threat-protection/intelligence/fileless-threats.md +++ b/windows/security/threat-protection/intelligence/fileless-threats.md @@ -13,7 +13,7 @@ ms.date: 09/14/2018 #Fileless threats -What exactly is a fileless threat? The term "fileless" suggests that a threat that does not come in a file, such as a backdoor that lives only in the memory of a machine. However, there's no generally accepted definition. The terms is used broadly; it's also used to describe malware families that do rely on files in order to operate. In the Sharpshooter example, while the payload itself is fileless, the entry point relies on scripts that need to be dropped on the target’s machine and executed. This, too, is considered a fileless attack. +What exactly is a fileless threat? The term "fileless" suggests that a threat that does not come in a file, such as a backdoor that lives only in the memory of a machine. However, there's no generally accepted definition. The terms is used broadly; it's also used to describe malware families that do rely on files in order to operate. Given that attacks involve [several stages](https://attack.mitre.org/wiki/ATT&CK_Matrix) for functionalities like execution, persistence, information theft, lateral movement, communication with command-and-control, etc., some parts of the attack chain may be fileless, while others may involve the filesystem in some form or another. From a81b799c01798f41a8553646a153211f419e0d18 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 27 Sep 2018 14:40:34 -0700 Subject: [PATCH 33/33] Preparing update for pull request --- .../app-v/appv-delete-a-connection-group.md | 2 +- ...e-a-package-with-the-management-console.md | 2 +- ...ctronic-software-distribution-solutions.md | 2 +- ...ctronic-software-distribution-solutions.md | 2 +- .../app-v/appv-dynamic-configuration.md | 85 ++----------------- .../app-v/appv-for-windows.md | 2 +- ...-powershell-cmdlets-and-get-cmdlet-help.md | 2 +- .../app-v/appv-maintaining-appv.md | 2 +- .../app-v/appv-publish-a-connection-group.md | 2 +- ...-a-packages-with-the-management-console.md | 2 +- 10 files changed, 18 insertions(+), 85 deletions(-) diff --git a/windows/application-management/app-v/appv-delete-a-connection-group.md b/windows/application-management/app-v/appv-delete-a-connection-group.md index 38682667e8..ee3f71058e 100644 --- a/windows/application-management/app-v/appv-delete-a-connection-group.md +++ b/windows/application-management/app-v/appv-delete-a-connection-group.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # How to delete a connection group diff --git a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md index be85faa43f..81a067b1eb 100644 --- a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md +++ b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # How to delete a package in the Management Console diff --git a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md index f9a0ddbd9c..29eafeeefa 100644 --- a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # How to deploy App-V packages using electronic software distribution diff --git a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md index 5ed8fcc2a2..0c17ea490a 100644 --- a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md +++ b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # Deploying App-V packages by using electronic software distribution (ESD) diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md index 1a4ed7f29c..e0b0f8d0f6 100644 --- a/windows/application-management/app-v/appv-dynamic-configuration.md +++ b/windows/application-management/app-v/appv-dynamic-configuration.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # About App-V dynamic configuration @@ -30,20 +30,17 @@ These .xml files specify package settings let you customize packages without dir ## Dynamic Configuration file contents -All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. The following table represents in which order the files will be read: +All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. The following list represents the relationship between these files in how they'll be read, from most to least precedence: -|| -|---| -|User Configuration .xml file| -|Deployment Configuration .xml file| -|Package Manifest| +- User Configuration .xml file +- Deployment Configuration .xml file +- Package Manifest -The previous table represents how the files will be read. The first entry represents what will be read last. Therefore, its content takes precedence. This means all packages inherently contain and provide default settings from the Package Manifest. If you apply a Deployment Configuration .xml file with customized settings, it will override the package manifest defaults. If you apply a User Configuration .xml file with customized settings prior to that, it will override both the deployment configuration and the Package Manifest defaults. +The first item represents what will be read last. Therefore, its content takes precedence. All packages inherently contain and provide default settings from the Package Manifest, but it also has the least precedence. If you apply a Deployment Configuration .xml file with customized settings, it will override the Package Manifest's defaults. If you apply a User Configuration .xml file with customized settings prior to that, it will override both the deployment configuration and the Package Manifest's defaults. There are two types of configuration files: - **User Configuration file (UserConfig)**: Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client. - - **Deployment Configuration file (DeploymentConfig)**: Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client. You can use the UserConfig file to customize the settings for a package for a specific set of users on a computer or make changes that will be applied to local user locations such as HKCU. You can use the DeploymentConfig file to modify the default settings of a package for all users on a machine or make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the All Users folder. @@ -51,23 +48,16 @@ You can use the UserConfig file to customize the settings for a package for a sp The UserConfig file provides configuration settings that you can apply to a single user without affecting any other users on a client: - Extensions that will be integrated into the native system per user: shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM. - - Virtual Subsystems: Application Objects, Environment variables, Registry modifications, Services, and Fonts. - - Scripts (user context only). The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the preceding UserConfig list: - All UserConfig settings from the preceding section in this topic - - Extensions that can only be applied globally for all users - - Virtual Subsystems that can be configured for global machine locations, such as the registry - - Product Source URL - - Scripts (Machine context only) - - Controls to terminate child processes ## File structure @@ -419,7 +409,6 @@ The **PackageId** is the same value as the one that exists in the Manifest file. The body of the deployment configuration file includes two sections: - The User Configuration section allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest. - - The Machine Configuration section contains information that can only be configured for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS. ```xml @@ -598,66 +587,10 @@ Using the following example file and table, modify the deployment or user config |Parameter in the example file|Description| |---|---| -||Name of the event trigger you're running a script for, such as when adding or publishing a package.| +|``|Name of the event trigger you're running a script for, such as when adding or publishing a package.| |`ScriptRunner.exe`|The script launcher application included in the App-V client.

Although ScriptRunner.exe is included in the App-V client, the App-V client's location must be in %path% or ScriptRunner won't run. `ScriptRunner.exe` is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.| -|`-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10`

`-appvscript script2.vbs arg1 arg2`

`-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror`|`-appvscript`: token that represents the actual script you want to run.
`script1.exe`: name of the script you want to run.
`arg1 arg2`: arguments for the script you want to run.
`-appvscriptrunnerparameters`: token that represents the execution options for script1.exe.
`-wait`: token that tells ScriptRunner to wait for execution of script1.exe to finish before proceeding to the next script.
`-timeout=x`: token that informs ScriptRunner to stop running the current script after *x* number of seconds. All other specified scripts will still run.
`-rollbackonerror`: token that tells ScriptRunner to stop running all scripts that haven't yet run and roll back an error to the App-V client.| -||Waits for overall completion of ScriptRunner.exe.

Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.

If any individual script reported an error and rollbackonerror was set to True, then ScriptRunner would report the error to App-V client.| - - - - ---- - - - - - - - - - - - - - - - - - - - - - - - - -
Parameter in the example fileDescription

Name of the event trigger for which you are running a script, such as adding a package or publishing a package.

ScriptRunner.exe

The script launcher application that is included in the App-V client.

-
-Note   -

Although ScriptRunner.exe is included in the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.

-
-
-  -

--appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10
-
--appvscript script2.vbs arg1 arg2
-
--appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror
-

-appvscript - Token that represents the actual script that you want to run.

-

script1.exe – Name of the script that you want to run.

-

arg1 arg2 – Arguments for the script that you want to run.

-

-appvscriptrunnerparameters – Token that represents the execution options for script1.exe

-

-wait – Token that informs ScriptRunner to wait for execution of script1.exe to complete before proceeding to the next script.

-

-timeout=x – Token that informs ScriptRunner to stop running the current script after x number of seconds. All other specified scripts will still run.

-

-rollbackonerror – Token that informs ScriptRunner to stop running all scripts that haven't yet run and to roll back an error to the App-V client.

Waits for overall completion of ScriptRunner.exe.

-

Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.

-

If any individual script reported an error and rollbackonerror was set to true, then ScriptRunner would report the error to App-V client.

- -  +|`-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10`

`-appvscript script2.vbs arg1 arg2`

`-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror`|`-appvscript`—token that represents the actual script you want to run.
`script1.exe`—name of the script you want to run.
`arg1 arg2`—arguments for the script you want to run.
`-appvscriptrunnerparameters`—token that represents the execution options for script1.exe.
`-wait`—token that tells ScriptRunner to wait for execution of script1.exe to finish before proceeding to the next script.
`-timeout=x`—token that informs ScriptRunner to stop running the current script after *x* number of seconds. All other specified scripts will still run.
`-rollbackonerror`—token that tells ScriptRunner to stop running all scripts that haven't yet run and roll back an error to the App-V client.| +|``|Waits for overall completion of ScriptRunner.exe.

Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.

If any individual script reported an error and rollbackonerror was set to True, then ScriptRunner should report the error to App-V client.| ScriptRunner will run any script whose file type is associated with an application installed on the computer. If the associated application is missing, or the script’s file type isn't associated with any of the computer's applications, the script won't run. diff --git a/windows/application-management/app-v/appv-for-windows.md b/windows/application-management/app-v/appv-for-windows.md index a68e40142b..3642e254c5 100644 --- a/windows/application-management/app-v/appv-for-windows.md +++ b/windows/application-management/app-v/appv-for-windows.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # Application Virtualization (App-V) for Windows 10 overview diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md index ace19757e8..f914466f82 100644 --- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md +++ b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # How to load the Windows PowerShell cmdlets for App-V and get cmdlet help diff --git a/windows/application-management/app-v/appv-maintaining-appv.md b/windows/application-management/app-v/appv-maintaining-appv.md index 4320156e54..f98668cea5 100644 --- a/windows/application-management/app-v/appv-maintaining-appv.md +++ b/windows/application-management/app-v/appv-maintaining-appv.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # Maintaining App-V diff --git a/windows/application-management/app-v/appv-publish-a-connection-group.md b/windows/application-management/app-v/appv-publish-a-connection-group.md index 1df205137e..cebbaac7ad 100644 --- a/windows/application-management/app-v/appv-publish-a-connection-group.md +++ b/windows/application-management/app-v/appv-publish-a-connection-group.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # How to Publish a Connection Group diff --git a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md index 97b464ac1f..8451509577 100644 --- a/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md +++ b/windows/application-management/app-v/appv-publish-a-packages-with-the-management-console.md @@ -6,7 +6,7 @@ ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy ms.sitesec: library ms.prod: w10 -ms.date: 09/25/2018 +ms.date: 09/27/2018 --- # How to publish a package by using the Management console