From f59310623221ce347b56d15ed900b204c99f3f77 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 25 Jun 2018 14:53:13 -0700 Subject: [PATCH 01/43] Started next wave of revisions --- .../app-v/appv-connection-group-file.md | 2 +- ...e-created-in-a-previous-version-of-appv.md | 41 ++++++++----------- 2 files changed, 19 insertions(+), 24 deletions(-) diff --git a/windows/application-management/app-v/appv-connection-group-file.md b/windows/application-management/app-v/appv-connection-group-file.md index a421659a7a..06c74f260d 100644 --- a/windows/application-management/app-v/appv-connection-group-file.md +++ b/windows/application-management/app-v/appv-connection-group-file.md @@ -44,7 +44,7 @@ The following table describes the parameters in the XML file that define the con ### Parameters that define the packages in the connection group -In the <Packages> section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence. +In the **<Packages>** section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence. |Field|Description| |---|---| diff --git a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md index 83cff76b90..3c6902a7e4 100644 --- a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md +++ b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md @@ -1,6 +1,6 @@ --- -title: How to Convert a Package Created in a Previous Version of App-V (Windows 10) -description: How to Convert a Package Created in a Previous Version of App-V +title: How to convert a package created in a previous version of App-V (Windows 10) +description: How to convert a package created in a previous version of App-V. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,40 +8,35 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- - - # How to Convert a Package Created in a Previous Version of App-V -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 -You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V. +You can use the package converter utility to upgrade virtual application packages created by previous versions of App-V. This section will tell you how to convert existing virtual application packages for upgrade. -> [!NOTE] -> If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell. +>[!NOTE] +>If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell. -The package converter can only directly convert packages that were created by using the App-V 4.5 sequencer or later. Packages that were created using a version prior to App-V 4.5 must be upgraded to at least App-V 4.5 before conversion. +The package converter can only directly convert packages created by the App-V 4.5 sequencer or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion. -The following information provides direction for converting existing virtual application packages. - -> [!IMPORTANT] -> You must configure the package converter to always save the package ingredients file to a secure location and directory. A secure location is accessible only by an administrator. Additionally, when you deploy the package, you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion process. +>[!IMPORTANT] +>In order to keep your files secure, you must configure the package converter to always save the package ingredients file to a secure location and directory that can only be accessed by an administrator. When you deploy the package, you should either save the package to a secure location or make sure that no other users can sign in during the conversion process. ## App-V 4.6 installation folder is redirected to virtual file system root -When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.) +When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive is drive Q.) **Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V for Windows 10 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root. ## Getting started -1. Install the App-V Sequencer on a computer in your environment. For information about how to install 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 information about how to install the Sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md). -2. The following cmdlets are available: +2. You can enter the following cmdlets to check or convert packages: - - **Test-AppvLegacyPackage** – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, type `Test-AppvLegacyPackage -?`. + - **Test-AppvLegacyPackage** – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, type `Test-AppvLegacyPackage -?`. - - **ConvertFrom-AppvLegacyPackage** – To convert an existing package, type `ConvertFrom-AppvLegacyPackage c:\contentStore c:\convertedPackages`. In this command, `c:\contentStore` represents the location of the existing package and `c:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used. + - **ConvertFrom-AppvLegacyPackage** – To convert an existing package, type `ConvertFrom-AppvLegacyPackage c:\contentStore c:\convertedPackages`. In this command, `c:\contentStore` represents the location of the existing package and `c:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used. Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default. @@ -50,15 +45,15 @@ When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for ### Advanced Conversion Tips -- Piping - Windows PowerShell supports piping. Piping allows you to call `dir c:\contentStore\myPackage | Test-AppvLegacyPackage`. In this example, the directory object that represents `myPackage` will be given as input to the `Test-AppvLegacyPackage` command and bound to the `-Source` parameter. Piping like this is especially useful when you want to batch commands together; for example, `dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages`. This piped command would test the packages and then pass those objects on to actually be converted. You can also apply a filter on packages without errors or only specify a directory which contains an **.sprj** file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V client. +- Piping - Windows PowerShell supports piping. Piping allows you to call `dir c:\contentStore\myPackage | Test-AppvLegacyPackage`. In this example, the directory object that represents `myPackage` will be given as input to the `Test-AppvLegacyPackage` command and bound to the `-Source` parameter. Piping like this is especially useful when you want to batch commands together; for example, `dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages`. This piped command would test the packages and then pass those objects on to actually be converted. You can also apply a filter on packages without errors or only specify a directory which contains an **.sprj** file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V client. -- Batching - The Windows PowerShell command enables batching. More specifically, the cmdlets support taking a string\[\] object for the `-Source` parameter which represents a list of directory paths. This allows you to enter `$packages = dir c:\contentStore` and then call `ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target c:\ConvertedPackages` or to use piping and call `dir c:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages`. +- Batching - The Windows PowerShell command enables batching. More specifically, the cmdlets support taking a string\[\] object for the `-Source` parameter which represents a list of directory paths. This allows you to enter `$packages = dir c:\contentStore` and then call `ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target c:\ConvertedPackages` or to use piping and call `dir c:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages`. -- Other functionality - Windows PowerShell has other built-in functionality for features such as aliases, piping, lazy-binding, .NET object, and many others. All of these are usable in Windows PowerShell and can help you create advanced scenarios for the Package Converter. +- Other functionality - Windows PowerShell has other built-in functionality for features such as aliases, piping, lazy-binding, .NET object, and many others. All of these are usable in Windows PowerShell and can help you create advanced scenarios for the Package Converter. ## 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 From f886ede50152fa81ce305a74496c925b6a666370 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 26 Jun 2018 11:07:02 -0700 Subject: [PATCH 02/43] Continued changing for voice etc. --- ...e-created-in-a-previous-version-of-appv.md | 53 +++++++++++++++---- ...blished-and-globally-published-packages.md | 22 ++++---- 2 files changed, 55 insertions(+), 20 deletions(-) diff --git a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md index 3c6902a7e4..54817a281a 100644 --- a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md +++ b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md @@ -17,7 +17,7 @@ You can use the package converter utility to upgrade virtual application package >[!NOTE] >If you are running a computer with a 64-bit architecture, you must use the x86 version of Windows PowerShell. -The package converter can only directly convert packages created by the App-V 4.5 sequencer or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion. +The package converter can only directly convert packages created by an App-V sequencer version 4.5 or later. Packages created with an App-V version earlier than 4.5 must be upgraded to at least App-V 4.5 before conversion. >[!IMPORTANT] >In order to keep your files secure, you must configure the package converter to always save the package ingredients file to a secure location and directory that can only be accessed by an administrator. When you deploy the package, you should either save the package to a secure location or make sure that no other users can sign in during the conversion process. @@ -26,7 +26,7 @@ The package converter can only directly convert packages created by the App-V 4 When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for Windows 10 package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive is drive Q.) -**Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V for Windows 10 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root. +The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the **Filesystem** element. When the App-V for Windows 10 client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root. ## Getting started @@ -34,22 +34,55 @@ When you convert packages from App-V 4.6 to App-V for Windows 10, the App-V for 2. You can enter the following cmdlets to check or convert packages: - - **Test-AppvLegacyPackage** – This cmdlet is designed to check packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, type `Test-AppvLegacyPackage -?`. + - **Test-AppvLegacyPackage**—This cmdlet checks packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet will not parse the **.sft** file or do any in-depth validation. For information about options and basic functionality for this cmdlet, using Windows PowerShell, enter the following cmdlet: + + ```PowerShell + Test-AppvLegacyPackage -? + ``` - - **ConvertFrom-AppvLegacyPackage** – To convert an existing package, type `ConvertFrom-AppvLegacyPackage c:\contentStore c:\convertedPackages`. In this command, `c:\contentStore` represents the location of the existing package and `c:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used. + - **ConvertFrom-AppvLegacyPackage**—This cmdlet converts packages from legacy versions to updated versions. To convert an existing package, enter the following cmdlet: - Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default. + ```PowerShell + ConvertFrom-AppvLegacyPackage C:\contentStore C:\convertedPackages + ``` - > [!NOTE] - > Before you specify the output directory, you must create the output directory. + In this cmdlet, `C:\contentStore` represents the location of the existing package and `C:\convertedPackages` is the output directory to which the resulting App-V for Windows 10 virtual application package file will be saved. By default, if you do not specify a new name, the old package name will be used. + + Additionally, the package converter optimizes performance of packages in App-V for Windows 10 by setting the package to stream fault the App-V package.  This is more performant than the primary feature block and fully downloading the package. The flag **DownloadFullPackageOnFirstLaunch** allows you to convert the package and set the package to be fully downloaded by default. + + >[!NOTE] + >Before you specify the output directory, you must create the output directory. ### Advanced Conversion Tips -- Piping - Windows PowerShell supports piping. Piping allows you to call `dir c:\contentStore\myPackage | Test-AppvLegacyPackage`. In this example, the directory object that represents `myPackage` will be given as input to the `Test-AppvLegacyPackage` command and bound to the `-Source` parameter. Piping like this is especially useful when you want to batch commands together; for example, `dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages`. This piped command would test the packages and then pass those objects on to actually be converted. You can also apply a filter on packages without errors or only specify a directory which contains an **.sprj** file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V client. +- Piping—Windows PowerShell supports piping. Piping allows you to enter cmdlets like this example: -- Batching - The Windows PowerShell command enables batching. More specifically, the cmdlets support taking a string\[\] object for the `-Source` parameter which represents a list of directory paths. This allows you to enter `$packages = dir c:\contentStore` and then call `ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target c:\ConvertedPackages` or to use piping and call `dir c:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages`. + ```PowerShell + dir C:\contentStore\myPackage | Test-AppvLegacyPackage + ``` -- Other functionality - Windows PowerShell has other built-in functionality for features such as aliases, piping, lazy-binding, .NET object, and many others. All of these are usable in Windows PowerShell and can help you create advanced scenarios for the Package Converter. + In this example, the directory object that represents `myPackage` will be given as input to the **Test-AppvLegacyPackage** cmdlet and bound to the *-Source* parameter. Piping like this is especially useful when you want to batch commands together, such as in the following example cmdlet: + + ```PowerShell + dir .\ | Test-AppvLegacyPackage | ConvertFrom-AppvLegacyAppvPackage -Target .\ConvertedPackages + ``` + + This piped example command tests packages, then passes the objects on for conversion. You can also apply a filter on packages without errors or only specify a directory which contains an **.sprj** file or pipe them to another cmdlet that adds the filtered package to the server or publishes them to the App-V client. + +- Batching—The Windows PowerShell command enables batching. More specifically, the cmdlets support taking a string\[\] object for the *-Source* parameter that represents a list of directory paths. This allows you to enter the following cmdlets together: + + ```PowerShell + $packages = dir C:\contentStore + ConvertFrom-AppvLegacyAppvPackage-Source $packages -Target C:\ConvertedPackages + ``` + + Alternatively, you can use piping like this: + + ```PowerShell + dir C:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages + ``` + +- Other functionality—Windows PowerShell has other built-in functionality for features such as aliases, lazy-binding, .NET object, and many others. These features can help you create advanced scenarios for the Package Converter. ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md b/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md index 5a13170e82..e2ddb8deae 100644 --- a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md +++ b/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md @@ -1,6 +1,6 @@ --- -title: How to Create a Connection Group with User-Published and Globally Published Packages (Windows 10) -description: How to Create a Connection Group with User-Published and Globally Published Packages +title: How to create a connection croup with user-published and globally published packages (Windows 10) +description: How to create a connection croup with user-published and globally published packages. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,12 +8,9 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to create a connection croup with user-published and globally published packages - -# How to Create a Connection Group with User-Published and Globally Published Packages - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods: @@ -21,7 +18,12 @@ You can create user-entitled connection groups that contain both user-published - [How to use the App-V Server to create user-entitled connection groups](#how-to-use-the-app-v-server-to-create-user-entitled-connection-groups) -## What to know before you start: +## Unsupported scenarios and potential issues + +Here are some important things to know before you get started: + +- If you add user-published packages in globally entitled connection groups, the connection group will fail. +- @@ -53,7 +55,7 @@ You can create user-entitled connection groups that contain both user-published 1. Add and publish packages by using the following commands: - ``` + ```PowerShell Add-AppvClientPackage Add-AppvClientPackage Publish-AppvClientPackage -PackageId  -VersionId -Global @@ -64,7 +66,7 @@ You can create user-entitled connection groups that contain both user-published 3. Add and publish the connection group by using the following commands: - ``` + ```PowerShell Add-AppvClientConnectionGroup Enable-AppvClientConnectionGroup -GroupId  -VersionId ``` From 92a75c4363a9107024cc5c3090695b389eee180a Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 26 Jun 2018 14:33:05 -0700 Subject: [PATCH 03/43] Next few articles --- ...blished-and-globally-published-packages.md | 23 +++++----- .../app-v/appv-create-a-connection-group.md | 42 +++++++++---------- ...ration-file-with-the-management-console.md | 33 +++++++-------- 3 files changed, 45 insertions(+), 53 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md b/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md index e2ddb8deae..aad867297f 100644 --- a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md +++ b/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md @@ -23,7 +23,9 @@ You can create user-entitled connection groups that contain both user-published Here are some important things to know before you get started: - If you add user-published packages in globally entitled connection groups, the connection group will fail. -- +- Track the connection groups where you've used a non-optional package before removing it with the **Unpublish-AppvClientPackage <package> -global** cmdlet. + + In situations where you have a gobally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running that cmdlet can unpublish the package from every connection group containing that package.
@@ -49,11 +51,9 @@ Here are some important things to know before you get started:
-  - ## How to use Windows PowerShell cmdlets to create user-entitled connection groups -1. Add and publish packages by using the following commands: +1. Add and publish packages by using the following commands: ```PowerShell Add-AppvClientPackage @@ -62,9 +62,9 @@ Here are some important things to know before you get started: Publish-AppvClientPackage -PackageId -VersionId  ``` -2. Create the connection group XML file. For more information, see [About the Connection Group File](appv-connection-group-file.md). +2. Create the connection group XML file. For more information, see [About the connection group file](appv-connection-group-file.md). -3. Add and publish the connection group by using the following commands: +3. Add and publish the connection group by using the following commands: ```PowerShell Add-AppvClientConnectionGroup @@ -73,17 +73,16 @@ Here are some important things to know before you get started: ## How to use the App-V Server to create user-entitled connection groups -1. Open the App-V Management Console. +1. Open the App-V Management Console. -2. Follow the instructions in [How to Publish a Package by Using the Management Console](appv-publish-a-packages-with-the-management-console.md) to publish packages globally and to the user. +2. Follow the instructions in [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md) to publish packages globally and to the user. -3. Follow the instructions in [How to Create a Connection Group](appv-create-a-connection-group.md) to create the connection group, and add the user-published and globally published packages. +3. Follow the instructions in [How to create a connection group](appv-create-a-connection-group.md) to create the connection group and add the user-published and globally published packages. ## 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 - -[Managing Connection Groups](appv-managing-connection-groups.md) +- [Managing Connection Groups](appv-managing-connection-groups.md) diff --git a/windows/application-management/app-v/appv-create-a-connection-group.md b/windows/application-management/app-v/appv-create-a-connection-group.md index 144900c14b..2d209c4975 100644 --- a/windows/application-management/app-v/appv-create-a-connection-group.md +++ b/windows/application-management/app-v/appv-create-a-connection-group.md @@ -1,6 +1,6 @@ --- -title: How to Create a Connection Group (Windows 10) -description: How to Create a Connection Group +title: How to create a connection group (Windows 10) +description: How to create a connection group with the App-V Management Console. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,44 +8,40 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to create a connection group +>Applies to: Windows 10, version 1607 -# How to Create a Connection Group +Use these steps to create a connection group by using the App-V Management Console. To use Windows PowerShell to create connection groups, 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). -**Applies to** -- Windows 10, version 1607 +When you place packages in a connection group, their package root paths merge. If you remove packages, only the remaining packages maintain the merged root. -Use these steps to create a connection group by using the App-V Management Console. To use Windows PowerShell to create connection groups, 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). +## Create a connection group -When you place packages in a connection group, their package root paths are merged. If you remove packages, only the remaining packages maintain the merged root. +1. In the App-V Management Console, select **CONNECTION GROUPS** to display the Connection Groups library. -**To create a connection group** +2. Select **ADD CONNECTION GROUP** to create a new connection group. -1. In the App-V Management Console, select **CONNECTION GROUPS** to display the Connection Groups library. +3. In the **New Connection Group** pane, enter a description for the group. -2. Select **ADD CONNECTION GROUP** to create a new connection group. +4. Select **EDIT** in the **CONNECTED PACKAGES** pane to add a new application to the connection group. -3. In the **New Connection Group** pane, type a description for the group. +5. In the **PACKAGES Entire Library** pane, select the application to be added, then select the arrow to add the application. -4. Click **EDIT** in the **CONNECTED PACKAGES** pane to add a new application to the connection group. - -5. In the **PACKAGES Entire Library** pane, select the application to be added, and click the arrow to add the application. - - To remove an application, select the application to be removed in the **PACKAGES IN** pane and click the arrow. + To remove an application, select the application to be removed in the **PACKAGES IN** pane and select the arrow. To reprioritize the applications in your connection group, use the arrows in the **PACKAGES IN** pane. - **Important**
- By default, the Active Directory Domain Services access configurations that are associated with a specific application are not added to the connection group. To transfer the Active Directory access configuration, select **ADD PACKAGE ACCESS TO GROUP ACCESS**, which is located in the **PACKAGES IN** pane. + >[!IMPORTANT] + >By default, the Active Directory Domain Services access configurations that are associated with a specific application are not added to the connection group. To transfer the Active Directory access configuration, select **ADD PACKAGE ACCESS TO GROUP ACCESS**, which is located in the **PACKAGES IN** pane. -6. After adding all the applications and configuring Active Directory access, click **Apply**. +6. After adding all the applications and configuring Active Directory access, select **Apply**. ## 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-create-a-custom-configuration-file-with-the-management-console.md b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md index 3aea6099e5..1a2a13fa27 100644 --- a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md +++ b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md @@ -1,6 +1,6 @@ --- -title: How to Create a Custom Configuration File by Using the App-V Management Console (Windows 10) -description: How to Create a Custom Configuration File by Using the App-V Management Console +title: How to create a custom configuration file by using the App-V Management Console (Windows 10) +description: How to create a custom configuration file by using the App-V Management Console. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,34 +8,31 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to create a custom configuration file by using the App-V Management Console +>Applies to: Windows 10, version 1607 -# How to Create a Custom Configuration File by Using the App-V Management Console +You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V dynamic configuration](appv-dynamic-configuration.md). -**Applies to** -- Windows 10, version 1607 +You can create a dynamic user configuration file with the App-V Management Console by following the steps in this article. -You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V Dynamic Configuration](appv-dynamic-configuration.md). +## Create a dynamic user configuration file -Use the following procedure to create a Dynamic User Configuration file by using the App-V Management console. +1. Right-click the name of the package that you want to view and select **Edit active directory access** to view the configuration that is assigned to a given user group. Alternatively, select the package, and click **Edit**. -**To create a Dynamic User Configuration file** +2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list, if it is not already selected. A link named **Edit** will be displayed. -1. Right-click the name of the package that you want to view and select **Edit active directory access** to view the configuration that is assigned to a given user group. Alternatively, select the package, and click **Edit**. +3. Click **Edit**. The Dynamic User Configuration that is assigned to the AD Group will be displayed. -2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list, if it is not already selected. A link named **Edit** will be displayed. +4. Click **Advanced**, and then click **Export Configuration**. Type in a filename and click **Save**. Now you can edit the file to configure a package for a user. -3. Click **Edit**. The Dynamic User Configuration that is assigned to the AD Group will be displayed. - -4. Click **Advanced**, and then click **Export Configuration**. Type in a filename and click **Save**. Now you can edit the file to configure a package for a user. - - **Note**   - To export a configuration while running on Windows Server, you must disable "IE Enhanced Security Configuration". If this is enabled and set to block downloads, you cannot download anything from the App-V Server. + >[!NOTE]   + >To export a configuration while running on Windows Server, you must disable "IE Enhanced Security Configuration". If this is enabled and set to block downloads, you cannot download anything from the App-V Server. ## 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) From 925437d886ebe753156320d68217a88d003f0e4d Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 26 Jun 2018 16:56:40 -0700 Subject: [PATCH 04/43] Continued edits --- ...stom-configuration-file-with-the-management-console.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md index 1a2a13fa27..4462bd5320 100644 --- a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md +++ b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md @@ -20,14 +20,14 @@ You can create a dynamic user configuration file with the App-V Management Conso 1. Right-click the name of the package that you want to view and select **Edit active directory access** to view the configuration that is assigned to a given user group. Alternatively, select the package, and click **Edit**. -2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list, if it is not already selected. A link named **Edit** will be displayed. +2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list. A link named **Edit** will be displayed. -3. Click **Edit**. The Dynamic User Configuration that is assigned to the AD Group will be displayed. +3. Select **Edit**. The Dynamic User Configuration assigned to the AD Group will appear. -4. Click **Advanced**, and then click **Export Configuration**. Type in a filename and click **Save**. Now you can edit the file to configure a package for a user. +4. Select **Advanced**, and then select **Export Configuration**. Enter a filename and select **Save**. Now you can edit the file to configure a package for a user. >[!NOTE]   - >To export a configuration while running on Windows Server, you must disable "IE Enhanced Security Configuration". If this is enabled and set to block downloads, you cannot download anything from the App-V Server. + >To export a configuration while running on Windows Server, you must disable "IE Enhanced Security Configuration". If the setting is enabled and set to block downloads, you cannot download anything from the App-V Server. ## Have a suggestion for App-V? From 74a519d6be29c5c7f0f3ccbe0a82bad618c8e00c Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 28 Jun 2018 09:47:44 -0700 Subject: [PATCH 05/43] Set up note and cleaned up table column width --- windows/application-management/apps-in-windows-10.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/windows/application-management/apps-in-windows-10.md b/windows/application-management/apps-in-windows-10.md index 2a601d2d47..fa93e9f6bf 100644 --- a/windows/application-management/apps-in-windows-10.md +++ b/windows/application-management/apps-in-windows-10.md @@ -97,7 +97,7 @@ System apps are integral to the operating system. Here are the typical system ap Here are the typical installed Windows apps in Windows 10 versions 1703, 1709, and 1803. | Name | Full name | 1703 | 1709 | 1803 |Uninstall through UI? | -|--------------------|------------------------------------------|:------:|:------:|:------:|----------------------| +|--------------------|------------------------------------------|:----:|:----:|:----:|----------------------| | Remote Desktop | Microsoft.RemoteDesktop | x | x | | Yes | | PowerBI | Microsoft.Microsoft PowerBIforWindows | x | | | Yes | | Code Writer | ActiproSoftwareLLC.562882FEEB491 | x | x | x | Yes | @@ -106,7 +106,7 @@ Here are the typical installed Windows apps in Windows 10 versions 1703, 1709, a | Photoshop Express | AdobeSystemIncorporated. AdobePhotoshop | x | x | x | Yes | | Duolingo | D5EA27B7.Duolingo- LearnLanguagesforFree | x | x | x | Yes | | Network Speed Test | Microsoft.NetworkSpeedTest | x | x | x | Yes | -| News | Microsoft.BingNews | x | x | x | Yes | +| News | Microsoft.BingNews | x | x | x | Yes | | Flipboard | | | | | Yes | | | Microsoft.Advertising.Xaml | x | x | x | Yes | | | Microsoft.NET.Native.Framework.1.2 | x | x | x | Yes | @@ -171,4 +171,7 @@ Here are the typical provisioned Windows apps in Windows 10 versions 1703, 1709, | | Microsoft.XboxGameOverlay | x | x | x | No | | | Microsoft.XboxGamingOverlay | | | x | No | | | Microsoft.XboxIdentityProvider | x | x | x | No | -| | Microsoft.XboxSpeech ToTextOverlay | x | x | x | No | \ No newline at end of file +| | Microsoft.XboxSpeech ToTextOverlay | x | x | x | No | + +>[!NOTE] +>If you want to remove and reinstall the Store app, the only supported methods for restoring a removed Store app are either by restoring the system from a backup, or by resetting your system. If you really want to remove the Store app, you should use group policies to hide or disable it. \ No newline at end of file From 60c1d81afe2c09d220a9cad88185914b33951814 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 28 Jun 2018 10:30:17 -0700 Subject: [PATCH 06/43] Editorial changes --- ...custom-configuration-file-with-the-management-console.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md index 4462bd5320..a65a14d2df 100644 --- a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md +++ b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md @@ -12,7 +12,7 @@ ms.date: 04/19/2017 >Applies to: Windows 10, version 1607 -You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V dynamic configuration](appv-dynamic-configuration.md). +You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see [About App-V dynamic configuration](appv-dynamic-configuration.md). You can create a dynamic user configuration file with the App-V Management Console by following the steps in this article. @@ -20,14 +20,14 @@ You can create a dynamic user configuration file with the App-V Management Conso 1. Right-click the name of the package that you want to view and select **Edit active directory access** to view the configuration that is assigned to a given user group. Alternatively, select the package, and click **Edit**. -2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list. A link named **Edit** will be displayed. +2. Using the list of **AD Entities with Access**, select the AD group that you want to customize. Select **Custom** from the drop-down list. A link named **Edit** will appear. 3. Select **Edit**. The Dynamic User Configuration assigned to the AD Group will appear. 4. Select **Advanced**, and then select **Export Configuration**. Enter a filename and select **Save**. Now you can edit the file to configure a package for a user. >[!NOTE]   - >To export a configuration while running on Windows Server, you must disable "IE Enhanced Security Configuration". If the setting is enabled and set to block downloads, you cannot download anything from the App-V Server. + >If you want to export a configuration while running on Windows Server, make sure to disable "IE Enhanced Security Configuration". If the setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server. ## Have a suggestion for App-V? From 42e4f22c6976ccceabdae79f63783b270a1b0016 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 28 Jun 2018 10:54:31 -0700 Subject: [PATCH 07/43] Turned note into footnote to attract reader's attention --- windows/application-management/apps-in-windows-10.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/windows/application-management/apps-in-windows-10.md b/windows/application-management/apps-in-windows-10.md index fa93e9f6bf..a19e92ed18 100644 --- a/windows/application-management/apps-in-windows-10.md +++ b/windows/application-management/apps-in-windows-10.md @@ -157,7 +157,7 @@ Here are the typical provisioned Windows apps in Windows 10 versions 1703, 1709, | Print 3D | Microsoft.Print3D | | x | x | No | | Solitaire | Microsoft.Microsoft SolitaireCollection| x | x | x | Yes | | Sticky Notes | Microsoft.MicrosoftStickyNotes | x | x | x | No | -| Store | Microsoft.WindowsStore | x | x | x | No | +| Store* | Microsoft.WindowsStore | x | x | x | No | | Sway | Microsoft.Office.Sway | * | x | x | Yes | | Voice Recorder | Microsoft.SoundRecorder | x | x | x | No | | Wallet | Microsoft.Wallet | x | x | x | No | @@ -173,5 +173,4 @@ Here are the typical provisioned Windows apps in Windows 10 versions 1703, 1709, | | Microsoft.XboxIdentityProvider | x | x | x | No | | | Microsoft.XboxSpeech ToTextOverlay | x | x | x | No | ->[!NOTE] ->If you want to remove and reinstall the Store app, the only supported methods for restoring a removed Store app are either by restoring the system from a backup, or by resetting your system. If you really want to remove the Store app, you should use group policies to hide or disable it. \ No newline at end of file +* Because the Store app can't be removed, if you want to remove and reinstall the Store app, the only supported methods for restoring it are either by restoring the system from a backup or by resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it. \ No newline at end of file From e713cbedfc032f01a701bf526f035bb3d40b3aba Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 28 Jun 2018 12:32:40 -0700 Subject: [PATCH 08/43] Editorial changes --- ...custom-configuration-file-with-the-management-console.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md index a65a14d2df..6c5a363d8f 100644 --- a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md +++ b/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md @@ -24,10 +24,10 @@ You can create a dynamic user configuration file with the App-V Management Conso 3. Select **Edit**. The Dynamic User Configuration assigned to the AD Group will appear. -4. Select **Advanced**, and then select **Export Configuration**. Enter a filename and select **Save**. Now you can edit the file to configure a package for a user. +4. Select **Advanced**, and then select **Export Configuration**. Enter a file name and select **Save**. Now you can edit the file to configure a package for a user. >[!NOTE]   - >If you want to export a configuration while running on Windows Server, make sure to disable "IE Enhanced Security Configuration". If the setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server. + >If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enabled and set to block downloads, you won't be able to download anything from the App-V Server. ## Have a suggestion for App-V? @@ -35,4 +35,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## Related topics -- [Operations for App-V](appv-operations.md) +- [Operations for App-V](appv-operations.md) \ No newline at end of file From aa630622963a5e982bbb0d469ad319f2303b33b8 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 28 Jun 2018 12:50:10 -0700 Subject: [PATCH 09/43] Reverted note to !NOTE tagging, editorial changes on note text --- windows/application-management/apps-in-windows-10.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/windows/application-management/apps-in-windows-10.md b/windows/application-management/apps-in-windows-10.md index a19e92ed18..35b31a8407 100644 --- a/windows/application-management/apps-in-windows-10.md +++ b/windows/application-management/apps-in-windows-10.md @@ -157,7 +157,7 @@ Here are the typical provisioned Windows apps in Windows 10 versions 1703, 1709, | Print 3D | Microsoft.Print3D | | x | x | No | | Solitaire | Microsoft.Microsoft SolitaireCollection| x | x | x | Yes | | Sticky Notes | Microsoft.MicrosoftStickyNotes | x | x | x | No | -| Store* | Microsoft.WindowsStore | x | x | x | No | +| Store | Microsoft.WindowsStore | x | x | x | No | | Sway | Microsoft.Office.Sway | * | x | x | Yes | | Voice Recorder | Microsoft.SoundRecorder | x | x | x | No | | Wallet | Microsoft.Wallet | x | x | x | No | @@ -173,4 +173,5 @@ Here are the typical provisioned Windows apps in Windows 10 versions 1703, 1709, | | Microsoft.XboxIdentityProvider | x | x | x | No | | | Microsoft.XboxSpeech ToTextOverlay | x | x | x | No | -* Because the Store app can't be removed, if you want to remove and reinstall the Store app, the only supported methods for restoring it are either by restoring the system from a backup or by resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it. \ No newline at end of file +>[!NOTE] +>The Store app can't be removed. If you want to remove and reinstall the Store app, you can only bring Store back by either restoring your system from a backup or resetting your system. Instead of removing the Store app, you should use group policies to hide or disable it. \ No newline at end of file From 773851e314c7e45b2c0f82c91bc441887ed0a913 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Tue, 3 Jul 2018 17:10:34 -0700 Subject: [PATCH 10/43] Updated package accelerator article --- ...blished-and-globally-published-packages.md | 5 +-- ...e-a-package-accelerator-with-powershell.md | 43 ++++++++----------- 2 files changed, 21 insertions(+), 27 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md b/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md index aad867297f..25b8964d2c 100644 --- a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md +++ b/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md @@ -14,9 +14,8 @@ ms.date: 04/19/2017 You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods: -- [How to use Windows PowerShell cmdlets to create user-entitled connection groups](#how-to-use-windows-powershell-cmdlets-to-create-user-entitled-connection-groups) - -- [How to use the App-V Server to create user-entitled connection groups](#how-to-use-the-app-v-server-to-create-user-entitled-connection-groups) +- [How to use Windows PowerShell cmdlets to create user-entitled connection groups](#how-to-use-windows-powershell-cmdlets-to-create-user-entitled-connection-groups) +- [How to use the App-V Server to create user-entitled connection groups](#how-to-use-the-app-v-server-to-create-user-entitled-connection-groups) ## Unsupported scenarios and potential issues diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md b/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md index 5d001bf498..2364dd4b2e 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md @@ -1,6 +1,6 @@ --- -title: How to Create a Package Accelerator by Using Windows PowerShell (Windows 10) -description: How to Create a Package Accelerator by Using Windows PowerShell +title: How to create a package accelerator by using Windows PowerShell (Windows 10) +description: How to create a package accelerator with Windows PowerShell. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,43 +8,38 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to create a package accelerator by using Windows PowerShell - -# How to Create a Package Accelerator by Using Windows PowerShell - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 App-V package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V package accelerator, you are not always required to manually install an application to create the virtualized package. -**To create a package accelerator** +## Create a package accelerator -1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md). +1. Install the App-V sequencer. For more information about installing the sequencer, see [How to install the sequencer](appv-install-the-sequencer.md). +2. To open a Windows PowerShell console, select **Start** and enter **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. +3. Enter the **New-AppvPackageAccelerator** cmdlet. +4. To create a package accelerator, make sure that you have the .appv package to create an accelerator from the installation media or installation files, and optionally a readme file for the accelerator's consumers to use. The following parameters are required to use the package accelerator cmdlet: -2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. Use the **New-AppvPackageAccelerator** cmdlet. - -3. To create a package accelerator, make sure that you have the .appv package to create an accelerator from, the installation media or installation files, and optionally a read me file for consumers of the accelerator to use. The following parameters are required to use the package accelerator cmdlet: - - - **InstalledFilesPath** - specifies the application installation path. - - - **Installer** – specifies the path to the application installer media - - - **InputPackagePath** – specifies the path to the .appv package - - - **Path** – specifies the output directory for the package. + - **InstalledFilesPath** specifies the application installation path. + - **Installer** specifies the path to the application installer media + - **InputPackagePath** specifies the path to the .appv package + - **Path** specifies the output directory for the package. The following example displays how you can create a package accelerator with an .appv package and the installation media: - **New-AppvPackageAccelerator -InputPackagePath <path to the .appv file> -Installer <path to the installer executable> -Path <directory of the output path>** + ```PowerShell + New-AppvPackageAccelerator -InputPackagePath -Installer -Path + ``` An additional optional parameter that can be used with the **New-AppvPackageAccelerator** cmdlet is as follows: - - **AcceleratorDescriptionFile** - specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be packaged with the package created using the package accelerator. + - **AcceleratorDescriptionFile** specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created using the package accelerator. ## 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 -[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) From 618bbe5dc4d8276cf6cafe5b2b73c2b440ac33a8 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 5 Jul 2018 11:03:04 -0700 Subject: [PATCH 11/43] Finished old file and started updating new file. --- ...e-a-package-accelerator-with-powershell.md | 20 +++--- .../appv-create-a-package-accelerator.md | 70 +++++++++---------- 2 files changed, 45 insertions(+), 45 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md b/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md index 2364dd4b2e..73e03486ab 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md @@ -18,23 +18,25 @@ App-V package accelerators automatically sequence large, complex applications. A 1. Install the App-V sequencer. For more information about installing the sequencer, see [How to install the sequencer](appv-install-the-sequencer.md). 2. To open a Windows PowerShell console, select **Start** and enter **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**. -3. Enter the **New-AppvPackageAccelerator** cmdlet. -4. To create a package accelerator, make sure that you have the .appv package to create an accelerator from the installation media or installation files, and optionally a readme file for the accelerator's consumers to use. The following parameters are required to use the package accelerator cmdlet: +3. Make sure that you have the .appv package to create an accelerator from the installation media or installation files. You can also optionally use a readme file for the accelerator's users to reference. +4. Enter the **New-AppvPackageAccelerator** cmdlet. - - **InstalledFilesPath** specifies the application installation path. - - **Installer** specifies the path to the application installer media - - **InputPackagePath** specifies the path to the .appv package - - **Path** specifies the output directory for the package. + The following parameters are required to use the package accelerator cmdlet: - The following example displays how you can create a package accelerator with an .appv package and the installation media: + - *InstalledFilesPath* specifies the application installation path. + - *Installer* specifies the path to the application installer media. + - *InputPackagePath* specifies the path to the .appv package. + - *Path* specifies the output directory for the package. + + The following example cmdlet shows how you can create a package accelerator with an .appv package and the installation media: ```PowerShell New-AppvPackageAccelerator -InputPackagePath -Installer -Path ``` - An additional optional parameter that can be used with the **New-AppvPackageAccelerator** cmdlet is as follows: + You can also use the following optional parameter with the **New-AppvPackageAccelerator** cmdlet: - - **AcceleratorDescriptionFile** specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created using the package accelerator. + - *AcceleratorDescriptionFile* specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator. ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index b62f27281a..a36c7033bc 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -1,6 +1,6 @@ --- -title: How to Create a Package Accelerator (Windows 10) -description: How to Create a Package Accelerator +title: How to create a package accelerator (Windows 10) +description: How to create a package accelerator. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,72 +8,70 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to create a package accelerator - -# How to Create a Package Accelerator - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 App-V package accelerators automatically generate new virtual application packages. ->**Note**  You can use Windows PowerShell to create a package accelerator. For more information see [How to Create a Package Accelerator by Using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md). +>[!NOTE] +>You can use Windows PowerShell to create a package accelerator. For more information, see [How to create a package accelerator by using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md). Use the following procedure to create a package accelerator. ->**Important** +>[!IMPORTANT] +> > - Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied. > - Before you begin the following procedure, perform the following: - - Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. - - Copy all required installation files associated with the virtual application package to the computer running the sequencer. -> - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using App-V Sequencer. + >- Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. + >- Copy all required installation files associated with the virtual application package to the computer running the sequencer. +> - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a package accelerator with the App-V sequencer. -## To create a package accelerator +## Create a package accelerator -1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. +1. To start the App-V sequencer on the computer running the sequencer, select **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**. -2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, click **Tools** / **Create Accelerator**. +2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, select **Tools** > **Create Accelerator**. -3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, click **Browse**, and locate the existing virtual application package (.appv file). +3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, select **Browse**, then locate the existing virtual application package (it will appear as an .appv file). - **Tip**
- Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer. - - Click **Next**. + >[!TIP] + >Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer. -4. On the **Installation Files** page, to specify the folder that contains the installation files that you used to create the original virtual application package, click **Browse**, and then select the directory that contains the installation files. + Select **Next**. - **Tip**
- Copy the folder that contains the required installation files to the computer running the Sequencer. +4. To specify the folder containing original virtual package's installation files, go to the **Installation Files** page and select **Browse**, then select the directory that contains the installation files. -5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location. + >[!TIP] + >Copy the folder that contains the required installation files to the computer running the Sequencer. -6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, and then click **Next**. If the files are required, click **Previous** and copy the required files to the directory specified on the **Installation Files** page. +5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location. - **Note**
- You must either remove the unrequired files, or click **Previous** and locate the required files to advance to the next page of this wizard. +6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. -7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**. + >[!NOTE] + >You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard. -8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package. +7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**. + +8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package. If necessary, to add additional Installer files, click **Add**. To remove unnecessary installation files, select the Installer file, and then click **Delete**. To edit the properties associated with an installer, click **Edit**. The installation files specified in this step will be required when the Package Accelerator is used to create a new virtual application package. After you have confirmed the information displayed, click **Next**. -9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**. +9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**. 10. On the **Create Package Accelerator** page, to specify where to save the Package Accelerator, click **Browse** and select the directory. 11. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**. - **Important**
- To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator. + >[!IMPORTANT] + >To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator. ## 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 Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md) +- [Operations for App-V](appv-operations.md) +- [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md) From 833580a3962fbd9de44ce95ef43557c5c195555e Mon Sep 17 00:00:00 2001 From: "Andrea Bichsel (Aquent LLC)" Date: Thu, 5 Jul 2018 14:11:50 -0700 Subject: [PATCH 12/43] Changed Intune instructions in Enable cloud protection topic. --- ...d-protection-windows-defender-antivirus.md | 29 +++++++++---------- 1 file changed, 13 insertions(+), 16 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/enable-cloud-protection-windows-defender-antivirus.md b/windows/security/threat-protection/windows-defender-antivirus/enable-cloud-protection-windows-defender-antivirus.md index 52804b3481..7a3ce500c7 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/enable-cloud-protection-windows-defender-antivirus.md +++ b/windows/security/threat-protection/windows-defender-antivirus/enable-cloud-protection-windows-defender-antivirus.md @@ -11,7 +11,7 @@ ms.pagetype: security ms.localizationpriority: medium author: andreabichsel ms.author: v-anbic -ms.date: 04/30/2018 +ms.date: 07/05/2018 --- # Enable cloud-delivered protection in Windows Defender AV @@ -108,25 +108,22 @@ See the following for more information and allowed parameters: **Use Intune to enable cloud-delivered protection** -1. Open the [Microsoft Intune administration console](https://manage.microsoft.com/), and navigate to the associated policy you want to configure. -2. Under the **Endpoint Protection** setting, scroll down to the **Endpoint Protection Service** section set the **Submit files automatically when further analysis is required** setting to either of the following: - 1. **Send samples automatically** - 1. **Send all samples automatically** +1. Sign in to the [Azure portal](https://portal.azure.com). +2. Select **All services > Intune**. +3. In the **Intune** pane, select **Device configuration > Profiles**, and then select the **Device restrictions** profile type you want to configure. If you haven't yet created a **Device restrictions** profile type, or if you want to create a new one, see [Configure device restriction settings in Microsoft Intune](https://docs.microsoft.com/en-us/intune/device-restrictions-configure). +4. Select **Properties**, select **Settings: Configure**, and then select **Windows Defender Antivirus**. +5. On the **Cloud-delivered protection** switch, select **Enable**. +6. In the **Prompt users before sample submission** dropdown, select **Send all data without prompting**. +7. In the **Submit samples consent** dropdown, select one of the following: + 1. **Send safe samples automatically** + 2. **Send all samples automatically** > [!WARNING] > Setting to **Always Prompt** will lower the protection state of the device. Setting to **Never send** means the [Block at First Sight](configure-block-at-first-sight-windows-defender-antivirus.md) feature will not function. -5. Scroll down to the **Microsoft Active Protection Service** section and set the following settings: - - Setting | Set to - --|-- - Join Microsoft Active Protection Service | Yes - Membership level | Advanced - Receive dynamic definitions based on Microsoft Active Protection Service reports | Yes +8. Click **OK** to exit the **Windows Defender Antivirus** settings pane, click **OK** to exit the **Device restrictions** pane, and then click **Save** to save the changes to your **Device restrictions** profile. + +For more information about Intune device profiles, including how to create and configure their settings, see [What are Microsoft Intune device profiles?](https://docs.microsoft.com/en-us/intune/device-profiles). -3. Save and [deploy the policy as usual](https://docs.microsoft.com/en-us/intune/deploy-use/common-windows-pc-management-tasks-with-the-microsoft-intune-computer-client). - -See [Help secure Windows PCs with Endpoint Protection for Microsoft Intune](https://docs.microsoft.com/en-us/intune/deploy-use/help-secure-windows-pcs-with-endpoint-protection-for-microsoft-intune) for more details. - **Enable cloud-delivered protection on individual clients with the Windows Defender Security Center app** > [!NOTE] > If the **Configure local setting override for reporting Microsoft MAPS** Group Policy setting is set to **Disabled**, then the **Cloud-based protection** setting in Windows Settings will be greyed-out and unavailable. Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings. From e4514b2ad7f4602925b3fc68c0c676bc92970c75 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Thu, 5 Jul 2018 16:34:24 -0700 Subject: [PATCH 13/43] Continued updating article --- .../app-v/appv-create-a-package-accelerator.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index a36c7033bc..054a60c923 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -47,16 +47,16 @@ Use the following procedure to create a package accelerator. 5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location. -6. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. +6. On the **Gathering Information** page, review the files that you couldn't find in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. >[!NOTE] >You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard. -7. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the package accelerator. Select only files that are required for the application to run successfully, and then click **Next**. +7. On the **Select Files** page, carefully review the detected files and clear any file the package accelerator does not need to run successfully. Select only files that the application requires, then select **Next**. -8. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package. +8. Confirm that the **Verify Applications** page displays all installation files required to build the package. The Package Accelerator requires all installation files displayed in the **Applications** pane in order to create the package. - If necessary, to add additional Installer files, click **Add**. To remove unnecessary installation files, select the Installer file, and then click **Delete**. To edit the properties associated with an installer, click **Edit**. The installation files specified in this step will be required when the Package Accelerator is used to create a new virtual application package. After you have confirmed the information displayed, click **Next**. + If you need to add additional Installer files, select **Add**. To remove unnecessary installation files, select the **Installer file**, then select **Delete**. To edit the properties associated with an installer, select **Edit**. The Package Accelerator requires the installation files specified in this step to create a new virtual application package. After you have confirmed the information displayed, click **Next**. 9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**. From a01057accaac47c2b874752438015d9dbeb9377b Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 6 Jul 2018 09:53:29 -0700 Subject: [PATCH 14/43] Continued update --- .../app-v/appv-create-a-package-accelerator.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index 054a60c923..34cc5b7acb 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -21,10 +21,10 @@ Use the following procedure to create a package accelerator. >[!IMPORTANT] > -> - Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied. -> - Before you begin the following procedure, perform the following: - >- Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. - >- Copy all required installation files associated with the virtual application package to the computer running the sequencer. +> - Because Package Accelerators can contain password and user-specific information, you should save Package Accelerators and the associated installation media in a secure location, and you should also digitally sign the Package Accelerator after creating it so that you can verify the publisher when applying the App-V Package Accelerator. +> - Before you begin creating a package accelerator, do the following: +> - Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. +> - Copy all required installation files associated with the virtual application package to the computer running the sequencer. > - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a package accelerator with the App-V sequencer. ## Create a package accelerator From 94b198a791d2bc6e8d9131460b3f1787b079bd24 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 6 Jul 2018 10:44:19 -0700 Subject: [PATCH 15/43] Continued editing article --- .../app-v/appv-create-a-package-accelerator.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index 34cc5b7acb..74b6995939 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -33,19 +33,19 @@ Use the following procedure to create a package accelerator. 2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, select **Tools** > **Create Accelerator**. -3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, select **Browse**, then locate the existing virtual application package (it will appear as an .appv file). +3. On the **Select Package** page, select **Browse** tospecify an existing virtual application package to use to create the Package Accelerator, then locate the existing virtual application package (it will appear as an .appv file). >[!TIP] >Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer. Select **Next**. -4. To specify the folder containing original virtual package's installation files, go to the **Installation Files** page and select **Browse**, then select the directory that contains the installation files. +4. Go to the **Installation Files** page and select **Browse**, then select the directory that contains the installation files to specify the folder containing the original virtual package's installation files. >[!TIP] >Copy the folder that contains the required installation files to the computer running the Sequencer. -5. If the application is already installed on the computer running the sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location. +5. If the application is already installed on the computer running the sequencer, then select **Files installed on local system** to specify the installation file,. To use this option, the application must already be installed in the default installation location. 6. On the **Gathering Information** page, review the files that you couldn't find in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. From da3b7b6f565454e492eaf7f3b732f60e5b95a5aa Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 6 Jul 2018 16:07:28 -0700 Subject: [PATCH 16/43] Finished first round of editing --- .../appv-create-a-package-accelerator.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index 74b6995939..f03f89d09d 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -21,11 +21,11 @@ Use the following procedure to create a package accelerator. >[!IMPORTANT] > -> - Because Package Accelerators can contain password and user-specific information, you should save Package Accelerators and the associated installation media in a secure location, and you should also digitally sign the Package Accelerator after creating it so that you can verify the publisher when applying the App-V Package Accelerator. -> - Before you begin creating a package accelerator, do the following: +>- Because Package Accelerators can contain password and user-specific information, you should save Package Accelerators and the associated installation media in a secure location, and you should also digitally sign the Package Accelerator after creating it so that you can verify the publisher when applying the App-V Package Accelerator. +>- Before you begin creating a package accelerator, do the following: > - Copy the virtual application package that you will use to create the package accelerator locally to the computer running the sequencer. > - Copy all required installation files associated with the virtual application package to the computer running the sequencer. -> - The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a package accelerator with the App-V sequencer. +>- The App-V Sequencer does not grant any license rights to the software application you are using to create the Package Accelerator. You must abide by all end user license terms for the application you are using. It is your responsibility to make sure the software application’s license terms allow you to create a package accelerator with the App-V sequencer. ## Create a package accelerator @@ -45,27 +45,27 @@ Use the following procedure to create a package accelerator. >[!TIP] >Copy the folder that contains the required installation files to the computer running the Sequencer. -5. If the application is already installed on the computer running the sequencer, then select **Files installed on local system** to specify the installation file,. To use this option, the application must already be installed in the default installation location. +5. If the application is already installed on the computer running the sequencer, then select **Files installed on local system** to specify the installation file. To use this option, the application must already be installed in the default installation location. -6. On the **Gathering Information** page, review the files that you couldn't find in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. +6. On the **Gathering Information** page, review the files that you couldn't find in the location specified by the **Installation Files** page. If the files displayed are not required, select **Remove these files**, then select **Next**. If the files are required, select **Previous** and copy the required files to the directory specified on the **Installation Files** page. >[!NOTE] >You must either remove the unrequired files or select **Previous** and locate the required files to advance to the next page of this wizard. -7. On the **Select Files** page, carefully review the detected files and clear any file the package accelerator does not need to run successfully. Select only files that the application requires, then select **Next**. +7. On the **Select Files** page, carefully review the detected files. Clear any file the package accelerator doesn't need to run successfully and select only the files that the application requires. When you're done, select **Next**. 8. Confirm that the **Verify Applications** page displays all installation files required to build the package. The Package Accelerator requires all installation files displayed in the **Applications** pane in order to create the package. - If you need to add additional Installer files, select **Add**. To remove unnecessary installation files, select the **Installer file**, then select **Delete**. To edit the properties associated with an installer, select **Edit**. The Package Accelerator requires the installation files specified in this step to create a new virtual application package. After you have confirmed the information displayed, click **Next**. + If you need to add additional Installer files, select **Add**. To remove unnecessary installation files, select the **Installer file**, then select **Delete**. To edit the properties associated with an installer, select **Edit**. The Package Accelerator requires the installation files specified in this step to create a new virtual application package. After you have confirmed the information displayed, select **Next**. -9. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**. +9. On the **Select Guidance** page, select **Browse** to specify a file that contains information about how the Package Accelerator will be applied. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all information required for successful application of the Package Accelerator. The file you select must be in rich text (.rtf) or text file (.txt) format. After specifying the file, select **Next**. -10. On the **Create Package Accelerator** page, to specify where to save the Package Accelerator, click **Browse** and select the directory. +10. On the **Create Package Accelerator** page, select **Browse** and select the directory where you want to save the Package Accelerator. -11. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**. +11. On the **Completion** page, select **Close**. >[!IMPORTANT] - >To help ensure that the package accelerator is as secure as possible, and so that the publisher can be verified when the package accelerator is applied, you should always digitally sign the package accelerator. + >You should always digitally sign the package accelerator to ensure that the Package Accelerator is secure and can be verified by a publisher during application. ## Have a suggestion for App-V? @@ -74,4 +74,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## Related topics - [Operations for App-V](appv-operations.md) -- [How to Create a Virtual Application Package Using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md) +- [How to create a virtual application package using an App-V Package Accelerator](appv-create-a-virtual-application-package-package-accelerator.md) From 87a0453ffb9cf639c7e74cd4d234e2801188c2ce Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Fri, 6 Jul 2018 16:58:10 -0700 Subject: [PATCH 17/43] Began revising next article --- ...application-package-package-accelerator.md | 54 +++++++++---------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md b/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md index d816a91315..61cd5e09b2 100644 --- a/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md @@ -1,6 +1,6 @@ --- -title: How to Create a Virtual Application Package Using an App-V Package Accelerator (Windows 10) -description: How to Create a Virtual Application Package Using an App-V Package Accelerator +title: How to create a virtual application package using an App-V Package Accelerator (Windows 10) +description: How to create a virtual application package using an App-V Package Accelerator. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,71 +8,71 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/19/2017 --- +# How to create a virtual application package using an App-V Package Accelerator - -# How to Create a Virtual Application Package Using an App-V Package Accelerator - -**Applies to** -- Windows 10, version 1607 +>Applies to: Windows 10, version 1607 Use the following procedure to create a virtual application package with the App-V Package Accelerator. -> **Important**  The App-V Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V Sequencer. +>[!IMPORTANT] +>The App-V Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V Sequencer. -**To create a virtual application package with an App-V Package Accelerator** +## Create a virtual application package with an App-V Package Accelerator 1. Be sure that the required Package Accelerator has been copied locally to the computer that runs the App-V Sequencer. Also copy all required installation files for the package to a local folder on the computer that runs the Sequencer. This is the folder that you have to specify in step 6 of this procedure. -2. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. +2. To start the App-V Sequencer, on the computer that runs the App-V Sequencer, go to **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**. -3. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, and then click **Next**. +3. Select **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, then select **Next**. -4. To specify the package accelerator that will be used to create the new virtual application package, click **Browse** on the **Select Package Accelerator** page. Click **Next**. +4. To specify the package accelerator that will be used to create the new virtual application package, select **Browse** on the **Select Package Accelerator** page. Select **Next**. - > **Important**  If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you click **Run**, you must confirm that you trust the source of the package accelerator. Confirm your choice in the **Security Warning** dialog box. + >[!IMPORTANT] + >If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you select **Run**, you must confirm that you trust the source of the package accelerator. Confirm your choice in the **Security Warning** dialog box. -5. On the **Guidance** page, review the publishing guidance information that is displayed in the information pane. This information was added when the Package Accelerator was created and it contains guidance about how to create and publish the package. To export the guidance information to a text (.txt) file, click **Export** and specify the location where the file should be saved, and then click **Next**. +5. On the **Guidance** page, review the publishing guidance information that is displayed in the information pane. This information was added when the Package Accelerator was created and it contains guidance about how to create and publish the package. To export the guidance information to a text (.txt) file, select **Export** and specify the location where the file should be saved, and then select **Next**. -6. On the **Select Installation Files** page, click **Make New Folder** to create a local folder that contains all required installation files for the package, and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer that runs the Sequencer, click **Browse** to select the folder. +6. On the **Select Installation Files** page, select **Make New Folder** to create a local folder that contains all required installation files for the package, and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer that runs the Sequencer, select **Browse** to select the folder. - Alternatively, if you have already copied the installation files to a directory on this computer, click **Make New Folder**, browse to the folder that contains the installation files, and then click **Next**. + Alternatively, if you have already copied the installation files to a directory on this computer, select **Make New Folder**, browse to the folder that contains the installation files, and then select **Next**. - > **Note**  You can specify the following types of supported installation files: + >[!NOTE] + >You can specify the following types of supported installation files: > - Windows Installer files (**.msi**) > - Cabinet files (.cab) > - Compressed files with a .zip file name extension > - The actual application files > The following file types are not supported: **.msp** and **.exe** files. If you specify an **.exe** file, you must extract the installation files manually. -7. If the package accelerator requires an application to be installed before you apply the Package Accelerator, and if you have already installed the required application, select **I have installed all applications**, and then click **Next** on the **Local Installation** page. +7. If the package accelerator requires an application to be installed before you apply the Package Accelerator, and if you have already installed the required application, select **I have installed all applications**, and then select **Next** on the **Local Installation** page. -8. On the **Package Name** page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Click **Next**. +8. On the **Package Name** page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Select **Next**. -9. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information that is displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network, or when the package size exceeds 4 GB. +9. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information that is displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network, or when the package size exceeds 4 GB. -10. To create the package, click **Create**. After the package is created, click **Next**. +10. To create the package, select **Create**. After the package is created, select **Next**. -11. On the **Configure Software** page, to enable the Sequencer to configure the applications that are contained in the package, select **Configure Software**. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements. +11. On the **Configure Software** page, to enable the Sequencer to configure the applications that are contained in the package, select **Configure Software**. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements. If you select **Configure Software**, the following items can be configured using the Sequencer as part of this step: - **Load Package**. The Sequencer loads the files that are associated with the package. It can take several seconds to an hour to decode the package. - - **Run Each Program**. Optionally run the programs that are contained in the package. This step is helpful to complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at once, select at least one program, and then click **Run All**. To run specific programs, select the program or programs that you want to run, and then click **Run Selected**. Complete the required configuration tasks, and then close the applications. It can take several minutes for all programs to run. Click **Next**. + - **Run Each Program**. Optionally run the programs that are contained in the package. This step is helpful to complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at once, select at least one program, and then select **Run All**. To run specific programs, select the program or programs that you want to run, and then select **Run Selected**. Complete the required configuration tasks, and then close the applications. It can take several minutes for all programs to run. Select **Next**. - **Save Package**. The Sequencer saves the package. - **Primary Feature Block**. The Sequencer optimizes the package for streaming by rebuilding the primary feature block. - If you do not want to configure the applications, click **Skip this step**, and then click **Next**. + If you do not want to configure the applications, select **Skip this step**, and then select **Next**. -12. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, click **Close**. +12. On the **Completion** page, after you review the information that is displayed in the **Virtual Application Package Report** pane, select **Close**. - The package is now available in the Sequencer. To edit the package properties, click **Edit \[Package Name\]**. For more information about how to modify a package, see [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md). + The package is now available in the Sequencer. To edit the package properties, select **Edit \[Package Name\]**. For more information about how to modify a package, see [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.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). ## Related topics From 4ef06323860b1213ea6e592a1c14146ce3b93e80 Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 9 Jul 2018 16:28:33 -0700 Subject: [PATCH 18/43] Editorial changes --- .../appv-create-a-package-accelerator-with-powershell.md | 4 ++-- .../app-v/appv-create-a-package-accelerator.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md b/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md index 73e03486ab..4fa2eb181d 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md @@ -12,7 +12,7 @@ ms.date: 04/19/2017 >Applies to: Windows 10, version 1607 -App-V package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V package accelerator, you are not always required to manually install an application to create the virtualized package. +App-V package accelerators automatically sequence large, complex applications. Also, when you apply an App-V package accelerator, you don't have to manually install an application to create the virtualized package. ## Create a package accelerator @@ -36,7 +36,7 @@ App-V package accelerators automatically sequence large, complex applications. A You can also use the following optional parameter with the **New-AppvPackageAccelerator** cmdlet: - - *AcceleratorDescriptionFile* specifies the path to user created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator. + - *AcceleratorDescriptionFile* specifies the path to user-created package accelerator instructions. The package accelerator instructions are **.txt** or **.rtf** description files that will be included in the package created by the package accelerator. ## Have a suggestion for App-V? diff --git a/windows/application-management/app-v/appv-create-a-package-accelerator.md b/windows/application-management/app-v/appv-create-a-package-accelerator.md index f03f89d09d..97b46957eb 100644 --- a/windows/application-management/app-v/appv-create-a-package-accelerator.md +++ b/windows/application-management/app-v/appv-create-a-package-accelerator.md @@ -33,7 +33,7 @@ Use the following procedure to create a package accelerator. 2. To start the App-V **Create Package Accelerator** wizard, in the App-V sequencer console, select **Tools** > **Create Accelerator**. -3. On the **Select Package** page, select **Browse** tospecify an existing virtual application package to use to create the Package Accelerator, then locate the existing virtual application package (it will appear as an .appv file). +3. On the **Select Package** page, select **Browse** to specify an existing virtual application package to use to create the Package Accelerator, then locate the existing virtual application package (it will appear as an .appv file). >[!TIP] >Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer. @@ -58,7 +58,7 @@ Use the following procedure to create a package accelerator. If you need to add additional Installer files, select **Add**. To remove unnecessary installation files, select the **Installer file**, then select **Delete**. To edit the properties associated with an installer, select **Edit**. The Package Accelerator requires the installation files specified in this step to create a new virtual application package. After you have confirmed the information displayed, select **Next**. -9. On the **Select Guidance** page, select **Browse** to specify a file that contains information about how the Package Accelerator will be applied. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all information required for successful application of the Package Accelerator. The file you select must be in rich text (.rtf) or text file (.txt) format. After specifying the file, select **Next**. +9. On the **Select Guidance** page, select **Browse** to specify the file that will provide the Package Accelerator with application instructions. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for successful Package Accelerator application. The file you select must be in rich text (.rtf) or text file (.txt) format. After specifying the file, select **Next**. 10. On the **Create Package Accelerator** page, select **Browse** and select the directory where you want to save the Package Accelerator. From 3994111fdd0e709a293db3cc49911529a67268ae Mon Sep 17 00:00:00 2001 From: Heidi Lohr Date: Mon, 9 Jul 2018 16:48:40 -0700 Subject: [PATCH 19/43] Editorial change object --- ...v-convert-a-package-created-in-a-previous-version-of-appv.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md index 54817a281a..cd90e4ed48 100644 --- a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md +++ b/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md @@ -82,7 +82,7 @@ The App-V package converter will save the App-V 4.6 installation root folder and dir C:\ContentStore | ConvertFrom-AppvLegacyAppvPackage -Target C:\ConvertedPackages ``` -- Other functionality—Windows PowerShell has other built-in functionality for features such as aliases, lazy-binding, .NET object, and many others. These features can help you create advanced scenarios for the Package Converter. +- Other functionality—Windows PowerShell has other built-in functionality for features such as aliases, lazy-binding, .NET Object, and many others. These features can help you create advanced scenarios for the Package Converter. ## Have a suggestion for App-V? From 49de3b8c90d353e2b217c562e6f2e9a65985dbe4 Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Tue, 10 Jul 2018 09:25:55 -0700 Subject: [PATCH 20/43] added new block list for 8b --- .../microsoft-recommended-block-rules.md | 59 ++++++++++++++++++- 1 file changed, 56 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md b/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md index 336b74e40b..2dfc1630ad 100644 --- a/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md +++ b/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md @@ -6,7 +6,7 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.localizationpriority: medium author: jsuther1974 -ms.date: 06/14/2018 +ms.date: 07/10/2018 --- # Microsoft recommended block rules @@ -655,7 +655,33 @@ Microsoft recommends that you block the following Microsoft-signed applications - + + + + + + + + + + + + + + + + + + + + + + + + + + + +## TaskManager policies + +
+
+ TaskManager/AllowEndTask +
+
+ + +
+ + +**TaskManager/AllowEndTask** + + + + + + + + + + + + + + + + + + + + + +
HomeProBusinessEnterpriseEducationMobileMobile Enterprise
cross markcheck mark5cross markcheck mark5check mark5
+ + + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +This setting determines whether non-administrators can use Task Manager to end tasks. + +Value type is integer. Supported values: + - 0 - Disabled. EndTask functionality is blocked in TaskManager. + - 1 - Enabled (default). Users can perform EndTask in TaskManager. + + + + + + + + + +**Validation procedure:** +When this policy is set to 1 - users CAN execute 'End task' on processes in TaskManager +When the policy is set to 0 - users CANNOT execute 'End task' on processes in TaskManager + + + +
+ +Footnote: + +- 1 - Added in Windows 10, version 1607. +- 2 - Added in Windows 10, version 1703. +- 3 - Added in Windows 10, version 1709. +- 4 - Added in Windows 10, version 1803. +- 5 - Added in the next major release of Windows 10. + + + From 48d3f8cc6f8d07269f146581a01c557afe489b8f Mon Sep 17 00:00:00 2001 From: Justin Hall Date: Tue, 10 Jul 2018 14:02:11 -0700 Subject: [PATCH 43/43] added xml formatting --- .../microsoft-recommended-block-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md b/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md index 2dfc1630ad..b019f68b3c 100644 --- a/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md +++ b/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md @@ -78,7 +78,7 @@ For October 2017, we are announcing an update to system.management.automation.dl Microsoft recommends that you block the following Microsoft-signed applications and PowerShell files by merging the following policy into your existing policy to add these deny rules using the Merge-CIPolicy cmdlet: -``` +```xml 10.0.0.0