|
[!INCLUDE [intune-custom-settings-2](../../includes/configure/intune-custom-settings-2.md)]
-[!INCLUDE [intune-custom-settings-info](../../includes/configure/intune-custom-settings-info.md)]
> [!TIP]
> Use the following Graph call to automatically create the custom policy in your tenant without assignments nor scope tags. [1](#footnote1)
@@ -52,32 +51,26 @@ Content-Type: application/json
#### [:::image type="icon" source="images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
-To configure devices using a provisioning package, [create a provisioning package][WIN-1] using Windows Configuration Designer (WCD) with the following settings:
+[!INCLUDE [provisioning-package-1](../../includes/configure/provisioning-package-1.md)]
| Setting |
|--------|
|
Path: **`Education/AllowStickers`**
Value: **True**
|
-Follow the steps in [Apply a provisioning package][WIN-2] to apply the package that you created.
-
+[!INCLUDE [provisioning-package-2](../../includes/configure/provisioning-package-2.md)]
---
## How to use Stickers
-Once the Stickers feature is enabled, the sticker editor can be opened by either:
+Once the Stickers feature is enabled, open sticker editor by either:
- using the contextual menu on the desktop and selecting the option **Add or edit stickers**
- opening the Settings app > **Personalization** > **Background** > **Add stickers**
:::image type="content" source="./images/win-11-se-stickers-menu.png" alt-text="Windows 11 SE desktop contextual menu to open the sticker editor" border="true":::
-Multiple stickers can be added from the picker by selecting them. The stickers can be resized, positioned or deleted from the desktop by using the mouse, keyboard, or touch.
+Multiple stickers can be added from the picker by selecting them. The stickers can be resized, positioned, or deleted from the desktop by using the mouse, keyboard, or touch.
:::image type="content" source="./images/win-11-se-stickers-animation.gif" alt-text="animation showing Windows 11 SE desktop with 4 pirate stickers being resized and moved" border="true":::
Select the *X button* at the top of the screen to save your progress and close the sticker editor.
-
-[MEM-1]: /mem/intune/configuration/custom-settings-windows-10
-
-[WIN-1]: /windows/configuration/provisioning-packages/provisioning-create-package
-[WIN-2]: /windows/configuration/provisioning-packages/provisioning-apply-package
\ No newline at end of file
diff --git a/education/windows/edu-take-a-test-kiosk-mode.md b/education/windows/edu-take-a-test-kiosk-mode.md
index ba510327cf5..21664c95bd4 100644
--- a/education/windows/edu-take-a-test-kiosk-mode.md
+++ b/education/windows/edu-take-a-test-kiosk-mode.md
@@ -26,7 +26,7 @@ The other options allow you to configure Take a Test in kiosk mode using a local
Follow the instructions below to configure your devices, selecting the option that best suits your needs.
-#### [:::image type="icon" source="images/icons/intune.svg"::: **Intune**](#tab/intune)
+# [:::image type="icon" source="images/icons/intune.svg"::: **Intune**](#tab/intune)
You can use Intune for Education or a custom profile in Microsoft Intune:
@@ -68,9 +68,8 @@ To configure devices using Intune for Education, follow these steps:
:::image type="content" source="./images/takeatest/intune-take-a-test-custom-profile.png" alt-text="Intune portal - creation of a custom policy to configure Take a Test." lightbox="./images/takeatest/intune-take-a-test-custom-profile.png" border="true":::
[!INCLUDE [intune-custom-settings-2](../../includes/configure/intune-custom-settings-2.md)]
-[!INCLUDE [intune-custom-settings-info](../../includes/configure/intune-custom-settings-info.md)]
-#### [:::image type="icon" source="images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
+# [:::image type="icon" source="images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
To create a provisioning package, you can either use Set up School PCs or Windows Configuration Designer:
@@ -85,7 +84,7 @@ Create a provisioning package using the Set up School PCs app, configuring the s
### Create a provisioning package using Windows Configuration Designer
-[Create a provisioning package][WIN-1] using Windows Configuration Designer with the following settings:
+[!INCLUDE [provisioning-package-1](../../includes/configure/provisioning-package-1.md)]
| Setting |
|--------|
@@ -99,22 +98,11 @@ Create a provisioning package using the Set up School PCs app, configuring the s
:::image type="content" source="./images/takeatest/wcd-take-a-test.png" alt-text="Windows Configuration Designer - configuration of policies to enable Take a Test to run in kiosk mode" lightbox="./images/takeatest/wcd-take-a-test.png" border="true":::
-Follow the steps in [Apply a provisioning package][WIN-2] to apply the package that you created.
+[!INCLUDE [provisioning-package-2](../../includes/configure/provisioning-package-2.md)]
-#### [:::image type="icon" source="images/icons/powershell.svg"::: **PowerShell**](#tab/powershell)
+# [:::image type="icon" source="images/icons/powershell.svg"::: **PowerShell**](#tab/powershell)
-Configure your devices using PowerShell scripts via the [MDM Bridge WMI Provider](/windows/win32/dmwmibridgeprov/mdm-bridge-wmi-provider-portal). For more information, see [Using PowerShell scripting with the WMI Bridge Provider](/windows/client-management/mdm/using-powershell-scripting-with-the-wmi-bridge-provider).
-
-> [!TIP]
-> PowerShell scripts can be executed as scheduled tasks via Group Policy.
-
-> [!IMPORTANT]
-> For all device settings, the WMI Bridge client must be executed as SYSTEM (LocalSystem) account.
->
-> To test a PowerShell script, you can:
-> 1. [Download the psexec tool](/sysinternals/downloads/psexec)
-> 1. Open an elevated command prompt and run: `psexec.exe -i -s powershell.exe`
-> 1. Run the script in the PowerShell session
+[!INCLUDE [powershell-wmi-bridge-1](../../includes/configure/powershell-wmi-bridge-1.md)]
Edit the following sample PowerShell script to:
@@ -171,7 +159,9 @@ $cimObject.HideFastUserSwitching = 1
Set-CimInstance -CimInstance $cimObject
```
-#### [:::image type="icon" source="images/icons/settings.svg"::: **Settings app**](#tab/settings)
+[!INCLUDE [powershell-wmi-bridge-2](../../includes/configure/powershell-wmi-bridge-2.md)]
+
+# [:::image type="icon" source="images/icons/settings.svg"::: **Settings app**](#tab/settings)
To create a local account, and configure Take a Test in kiosk mode using the Settings app:
diff --git a/education/windows/edu-themes.md b/education/windows/edu-themes.md
index c30c7fd79a0..b0d6efa6390 100644
--- a/education/windows/edu-themes.md
+++ b/education/windows/edu-themes.md
@@ -1,7 +1,7 @@
---
title: Configure education themes for Windows 11
description: Learn about education themes for Windows 11 and how to configure them via Intune and provisioning package.
-ms.date: 09/11/2023
+ms.date: 04/10/2024
ms.topic: how-to
appliesto:
- ✅ Windows 11
diff --git a/education/windows/federated-sign-in.md b/education/windows/federated-sign-in.md
index 3d414e043d5..aca908bb450 100644
--- a/education/windows/federated-sign-in.md
+++ b/education/windows/federated-sign-in.md
@@ -1,7 +1,7 @@
---
title: Configure federated sign-in for Windows devices
description: Learn how federated sign-in in Windows works and how to configure it.
-ms.date: 09/11/2023
+ms.date: 06/03/2024
ms.topic: how-to
appliesto:
- ✅ Windows 11
@@ -87,7 +87,7 @@ Review the following instructions to configure your devices using either Microso
|--|--|--|
| Education | Is Education Environment | Enabled |
| Federated Authentication | Enable Web Sign In For Primary User | Enabled |
-| Authentication | Configure Web Sign In Allowed Urls | Semicolon separated list of domains, for example: `samlidp.clever.com;clever.com;mobile-redirector.clever.com` |
+| Authentication | Configure Web Sign In Allowed Urls | Enter the list of domains, with each URL in a separate row. For example: - `samlidp.clever.com` - `clever.com` - `mobile-redirector.clever.com` |
| Authentication | Configure Webcam Access Domain Names | This setting is optional, and it should be configured if you need to use the webcam during the sign-in process. Specify the list of domains that are allowed to use the webcam during the sign-in process, separated by a semicolon. For example: `clever.com` |
[!INCLUDE [intune-settings-catalog-2](../../includes/configure/intune-settings-catalog-2.md)]
@@ -134,7 +134,7 @@ Review the following instructions to configure your shared devices using either
| Education | Is Education Environment | Enabled |
| SharedPC | Enable Shared PC Mode With OneDrive Sync | True |
| Authentication | Enable Web Sign In | Enabled |
-| Authentication | Configure Web Sign In Allowed Urls | Semicolon separated list of domains, for example: `samlidp.clever.com;clever.com;mobile-redirector.clever.com` |
+| Authentication | Configure Web Sign In Allowed Urls | Enter the list of domains, with each URL in a separate row. For example: - `samlidp.clever.com` - `clever.com` - `mobile-redirector.clever.com` |
| Authentication | Configure Webcam Access Domain Names | This setting is optional, and it should be configured if you need to use the webcam during the sign-in process. Specify the list of domains that are allowed to use the webcam during the sign-in process, separated by a semicolon. For example: `clever.com` |
[!INCLUDE [intune-settings-catalog-2](../../includes/configure/intune-settings-catalog-2.md)]
diff --git a/education/windows/get-minecraft-for-education.md b/education/windows/get-minecraft-for-education.md
index 4e8222d98d0..d5a0cb61fae 100644
--- a/education/windows/get-minecraft-for-education.md
+++ b/education/windows/get-minecraft-for-education.md
@@ -2,7 +2,7 @@
title: Get and deploy Minecraft Education
description: Learn how to obtain and distribute Minecraft Education to Windows devices.
ms.topic: how-to
-ms.date: 09/11/2023
+ms.date: 04/10/2024
ms.collection:
- education
- tier2
@@ -16,15 +16,15 @@ Minecraft Education is a game-based platform that inspires creative and inclusiv
**Prepare students for the future**: learners develop key skills like problem solving, collaboration, digital citizenship, and critical thinking to help them thrive now and in the future workplace. Spark a passion for STEM.
-**Game based learning**: unlock creativity and deep learning with immersive content created with partners including BBC Earth, NASA, and the Nobel Peace Center. Inspire students to engage in real-world topics, with culturally relevant lessons and build challenges.
+**Game based learning**: unlock creativity and deep learning with immersive content created with partners including BBC Earth, NASA, and the Nobel Peace Center. Inspire students to engage in real-world topics, with culturally relevant lessons and build challenges.
## Minecraft Education key features
-- Multiplayer mode enables collaboration in-game across platforms, devices, and hybrid environments
-- Code Builder supports block-based coding, JavaScript, and Python with intuitive interface and in-game execution
-- Immersive Reader helps players read and translate text
-- Camera and Book & Quill items allow documentation and export of in-game creations
-- Integration with Microsoft Teams and Flipgrid supports assessment and teacher controls
+- Multiplayer mode enables collaboration in-game across platforms, devices, and hybrid environments
+- Code Builder supports block-based coding, JavaScript, and Python with intuitive interface and in-game execution
+- Immersive Reader helps players read and translate text
+- Camera and Book & Quill items allow documentation and export of in-game creations
+- Integration with Microsoft Teams and Flipgrid supports assessment and teacher controls
## Try or purchase Minecraft Education
@@ -34,7 +34,7 @@ Organizations can [purchase subscriptions][EDU-2] directly in the *Microsoft 3
When you sign up for a Minecraft Education trial, or purchase a subscription, Minecraft Education licenses are linked to your Microsoft Entra tenant. If you don't have a Microsoft Entra tenant:
-- Microsoft-verified academic organizations can set up a free [Office 365 Education subscription][EDU-3], which includes a Microsoft Entra tenant
+- Microsoft-verified academic organizations can set up a free [Office 365 Education subscription][EDU-3], which includes a Microsoft Entra tenant
- Non-Microsoft-verified academic organizations can set up a free Microsoft Entra tenant when they [purchase Minecraft Education commercial licenses][EDU-4]
### Direct purchase
@@ -78,7 +78,7 @@ To pay with an invoice:
1. During the purchase, select **Add a new payment method.**
2. Select the **Invoice** option, and provide the information needed for an invoice. The **PO number** item allows you to add a tracking number or info that is meaningful to your organization.
-For more information about invoices and how to pay by invoice, see [Payment options for your Microsoft subscription][M365-1].
+For more information about invoices and how to pay by invoice, see [Payment options for your Microsoft subscription][M365-1].
## Assign Minecraft Education licenses
diff --git a/education/windows/images/setedupolicies_omauri.png b/education/windows/images/setedupolicies_omauri.png
deleted file mode 100644
index eb3d9e216c5..00000000000
Binary files a/education/windows/images/setedupolicies_omauri.png and /dev/null differ
diff --git a/education/windows/images/wcd/setedupolicies.png b/education/windows/images/wcd/setedupolicies.png
deleted file mode 100644
index e240063f683..00000000000
Binary files a/education/windows/images/wcd/setedupolicies.png and /dev/null differ
diff --git a/education/windows/images/wcd/wcd_settings_assignedaccess.png b/education/windows/images/wcd/wcd_settings_assignedaccess.png
deleted file mode 100644
index 443a5d0688d..00000000000
Binary files a/education/windows/images/wcd/wcd_settings_assignedaccess.png and /dev/null differ
diff --git a/education/windows/index.yml b/education/windows/index.yml
index d14d00dd632..1c2008d3c90 100644
--- a/education/windows/index.yml
+++ b/education/windows/index.yml
@@ -9,20 +9,19 @@ metadata:
ms.collection:
- education
- tier1
- - essentials-navigation
author: paolomatarazzo
ms.author: paoloma
manager: aaroncz
- ms.date: 10/30/2023
+ ms.date: 07/22/2024
highlightedContent:
items:
- title: Get started with Windows 11 SE
itemType: get-started
url: windows-11-se-overview.md
- - title: Windows 11, version 22H2
+ - title: Windows 11, version 23H2
itemType: whats-new
- url: /windows/whats-new/whats-new-windows-11-version-22H2
+ url: /windows/whats-new/whats-new-windows-11-version-23h2
- title: Explore all Windows trainings and learning paths for IT pros
itemType: learn
url: https://learn.microsoft.com/en-us/training/browse/?products=windows&roles=administrator
@@ -63,10 +62,8 @@ productDirectory:
- title: Learn how to manage Windows devices
imageSrc: /media/common/i_management.svg
links:
- - url: tutorial-school-deployment/manage-overview.md
+ - url: /mem/intune/industry/education/tutorial-school-deployment/manage-overview
text: Manage devices with Microsoft Intune
- - url: tutorial-school-deployment/manage-surface-devices.md
- text: Management functionalities for Surface devices
- url: /education/windows/get-minecraft-for-education
text: Get and deploy Minecraft Education
- url: /windows/client-management
@@ -139,4 +136,4 @@ additionalContent:
- text: Microsoft Intune community
url: https://techcommunity.microsoft.com/t5/microsoft-intune/bd-p/Microsoft-Intune
- text: Microsoft Support community
- url: https://answers.microsoft.com/windows/forum
\ No newline at end of file
+ url: https://answers.microsoft.com/
\ No newline at end of file
diff --git a/education/windows/set-up-school-pcs-provisioning-package.md b/education/windows/set-up-school-pcs-provisioning-package.md
index 6086d0f017f..8b49992af01 100644
--- a/education/windows/set-up-school-pcs-provisioning-package.md
+++ b/education/windows/set-up-school-pcs-provisioning-package.md
@@ -1,7 +1,7 @@
---
title: What's in Set up School PCs provisioning package
description: Learn about the settings that are configured in the provisioning package created with the Set up School PCs app.
-ms.date: 06/02/2023
+ms.date: 04/10/2024
ms.topic: reference
appliesto:
- ✅ Windows 10
@@ -34,15 +34,15 @@ For a more detailed look at the policies, see the Windows article [Set up shared
| Disk level caching | 50% | Sets 50% of total disk space to be used as the disk space threshold for account caching. |
| Disk level deletion | For shared device setup, 25%; for single device-student setup, 0%. | When devices are optimized for shared use, the policy sets 25% of total disk space as the disk space threshold for account caching. When devices are optimized for use by a single student, the policy sets the value to 0% and doesn't delete accounts. |
| Enable account manager | True | Enables automatic account management. |
-| Inactive threshold | For shared device setup, 30 days; for single device-student setup, 180 days. | After 30 or 180 days, respectively, if an account hasn't signed in, it will be deleted. |
+| Inactive threshold | For shared device setup, 30 days; for single device-student setup, 180 days. | After the threshold, if an account hasn't signed in, its user profile is deleted. |
| Kiosk Mode AMUID | `Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy!App` | Configures the kiosk account on student devices to only run the Take a Test secure assessment browser. |
| Kiosk Mode User Tile Display Text | Take a Test | Displays "Take a Test" as the name of the kiosk account on student devices. |
| Restrict local storage | For shared device setup, True; for single device-student setup, False. | When devices are optimized for shared use across multiple PCs, this policy forces students to save to the cloud to prevent data loss. When your devices are optimized for use by a single student, this policy doesn't prevent students from saving on the PCs local hard drive. |
| Maintenance start time | 0 - midnight | The maintenance start time when automatic maintenance tasks, such as Windows Update, run on student devices. |
-| Max page file size in MB | 1024 | Sets the maximum size of the paging file to 1024 MB. Applies only to systems with less than 32-GB storage and at least 3 GB of RAM. |
+| Max page file size in MB | 1024 | Sets the maximum size of the paging file to 1,024 MB. Applies only to systems with less than 32-GB storage and at least 3 GB of RAM. |
| Set power policies | True | Prevents users from changing power settings and turns off hibernate. Also overrides all power state transitions to sleep, such as lid close. |
| Sign in on resume | True | Requires the device user to sign in with a password when the PC wakes from sleep. |
-| Sleep timeout | 3600 seconds | Specifies the maximum idle time before the PC should sleep. If you don't set sleep timeout, the default time, 3600 seconds (1 hour), is applied. |
+| Sleep timeout | 3,600 seconds | Specifies the maximum idle time before the PC should sleep. If you don't set sleep timeout, the default time, 3,600 seconds (1 hour), is applied. |
## MDM and local group policies
@@ -58,7 +58,7 @@ For a more detailed look of each policy listed, see [Policy CSP](/windows/client
| Hide OOBE for desktop | True | Hides the interactive OOBE flow for Windows 10. |
| Download Mode | 1 - HTTP blended with peering behind the same NAT | Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps, and App updates |
| Select when Preview Builds and Feature Updates are received | 32 - Semi-annual Channel. Device gets feature updates from Semi-annual Channel | Specifies how frequently devices receive preview builds and feature updates. |
-| Allow auto update | 4 - Auto-installs and restarts without device-user control | When an auto update is available, it auto-installs and restarts the device without any input or action from the device user. |
+| Allow auto update | 4 - Autoinstalls and restarts without device-user control | When an auto update is available, it autoinstalls and restarts the device without any input or action from the device user. |
| Configure automatic updates | 3 - Set to install at 3am | Scheduled time to install updates. |
| Update power policy for cart restarts | 1 - Configured | Skips all restart checks to ensure that the reboot will happen at the scheduled install time. |
| Select when Preview Builds and Feature Updates are received | 365 days | Defers Feature Updates for the specified number of days. When not specified, defaults to 365 days. |
@@ -70,7 +70,7 @@ For a more detailed look of each policy listed, see [Policy CSP](/windows/client
| Allow add provisioning package | Disabled | Students can't add and upload new provisioning packages to their device. |
| Allow remove provisioning package | Disabled | Students can't remove packages that you've uploaded to their device, including the Set up School PCs app |
| Start Layout | Enabled | Lets you specify the Start layout for users and prevents them from changing the configuration. |
-| Import Edge Assets | Enabled | Import Microsoft Edge assets, such as PNG and JPG files, for secondary tiles on the Start layout. Tiles will appear as weblinks and will be tied to the relevant image asset files. |
+| Import Microsoft Edge Assets | Enabled | Import Microsoft Edge assets, such as PNG and JPG files, for secondary tiles on the Start layout. Tiles will appear as weblinks and will be tied to the relevant image asset files. |
| Allow pinned folder downloads | 1 - The shortcut is visible and disables the setting in the Settings app | Makes the Downloads shortcut on the Start menu visible to students. |
| Allow pinned folder File Explorer | 1 - The shortcut is visible and disables the setting in the Settings app | Makes the File Explorer shortcut on the Start menu visible to students. |
| Personalization | Deploy lock screen image | Set to the image you picked when you customized the lock screen during device setup. If you didn't customize the image, the computer will show the default. |
@@ -112,7 +112,7 @@ The time it takes to install a package on a device depends on the:
- Number of policies and apps within the package
- Other configurations made to the device
-Review the table below to estimate your expected provisioning time. A package that only applies Set Up School PC's default configurations will provision the fastest. A package that removes preinstalled apps, through CleanPC, will take much longer to provision.
+Review the table below to estimate your expected provisioning time. A package that only applies Set Up School PC's default configurations provisions the fastest. A package that removes preinstalled apps, through CleanPC, will take longer to provision.
| Configurations | Connection type | Estimated provisioning time |
|--|--|--|
diff --git a/education/windows/take-tests-in-windows.md b/education/windows/take-tests-in-windows.md
index d9663d6d32d..8c46ac4b935 100644
--- a/education/windows/take-tests-in-windows.md
+++ b/education/windows/take-tests-in-windows.md
@@ -1,7 +1,7 @@
---
title: Take tests and assessments in Windows
description: Learn about the built-in Take a Test app for Windows and how to use it.
-ms.date: 03/31/2023
+ms.date: 02/29/2024
ms.topic: how-to
---
@@ -48,7 +48,7 @@ This is an ideal option for teachers who want to create a link to a specific ass
For this option, you embed a URL with a specific prefix and specify parameters depending on what you want to allow during the test.
The URL must be in the following format:
-```
+```text
ms-edu-secureassessment:#enforceLockdown
```
diff --git a/education/windows/toc.yml b/education/windows/toc.yml
index 667c2ddc07a..62e4c0d85cb 100644
--- a/education/windows/toc.yml
+++ b/education/windows/toc.yml
@@ -4,8 +4,6 @@ items:
- name: Tutorials
expanded: true
items:
- - name: Deploy and manage Windows devices in a school
- href: tutorial-school-deployment/toc.yml
- name: Deploy applications to Windows 11 SE
href: tutorial-deploy-apps-winse/toc.yml
- name: Concepts
diff --git a/education/windows/tutorial-deploy-apps-winse/considerations.md b/education/windows/tutorial-deploy-apps-winse/considerations.md
index 73d202a2020..7f2a9f92075 100644
--- a/education/windows/tutorial-deploy-apps-winse/considerations.md
+++ b/education/windows/tutorial-deploy-apps-winse/considerations.md
@@ -1,7 +1,7 @@
---
title: Important considerations before deploying apps with managed installer
description: Learn about important aspects to consider before deploying apps with managed installer.
-ms.date: 06/19/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
diff --git a/education/windows/tutorial-deploy-apps-winse/create-policies.md b/education/windows/tutorial-deploy-apps-winse/create-policies.md
index 8841f736bdc..26e022bbbf8 100644
--- a/education/windows/tutorial-deploy-apps-winse/create-policies.md
+++ b/education/windows/tutorial-deploy-apps-winse/create-policies.md
@@ -1,7 +1,7 @@
---
title: Create policies to enable applications
description: Learn how to create policies to enable the installation and execution of apps on Windows SE.
-ms.date: 06/19/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
diff --git a/education/windows/tutorial-deploy-apps-winse/deploy-apps.md b/education/windows/tutorial-deploy-apps-winse/deploy-apps.md
index bc3bd280042..62442e2058d 100644
--- a/education/windows/tutorial-deploy-apps-winse/deploy-apps.md
+++ b/education/windows/tutorial-deploy-apps-winse/deploy-apps.md
@@ -1,7 +1,7 @@
---
title: Applications deployment considerations
description: Learn how to deploy different types of applications to Windows 11 SE and some considerations before deploying them.
-ms.date: 05/23/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
diff --git a/education/windows/tutorial-deploy-apps-winse/deploy-policies.md b/education/windows/tutorial-deploy-apps-winse/deploy-policies.md
index 330d85b61ef..63f61438534 100644
--- a/education/windows/tutorial-deploy-apps-winse/deploy-policies.md
+++ b/education/windows/tutorial-deploy-apps-winse/deploy-policies.md
@@ -1,7 +1,7 @@
---
title: Deploy policies to enable applications
description: Learn how to deploy AppLocker policies to enable apps execution on Windows SE devices.
-ms.date: 05/23/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
diff --git a/education/windows/tutorial-deploy-apps-winse/index.md b/education/windows/tutorial-deploy-apps-winse/index.md
index ff7cce6a5fb..1c09685eed2 100644
--- a/education/windows/tutorial-deploy-apps-winse/index.md
+++ b/education/windows/tutorial-deploy-apps-winse/index.md
@@ -1,7 +1,7 @@
---
title: Deploy applications to Windows 11 SE with Intune
description: Learn how to deploy applications to Windows 11 SE with Intune and how to validate the apps.
-ms.date: 06/07/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
diff --git a/education/windows/tutorial-deploy-apps-winse/troubleshoot.md b/education/windows/tutorial-deploy-apps-winse/troubleshoot.md
index 631b12b06ed..38a3ee9d4c7 100644
--- a/education/windows/tutorial-deploy-apps-winse/troubleshoot.md
+++ b/education/windows/tutorial-deploy-apps-winse/troubleshoot.md
@@ -1,7 +1,7 @@
---
title: Troubleshoot app deployment issues in Windows SE
description: Troubleshoot common issues when deploying apps to Windows SE devices.
-ms.date: 06/19/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
@@ -45,10 +45,10 @@ Use the Event Viewer to see if a supplemental policy is deployed correctly. Thes
```
citool.exe -lp
```
-
+
- For the policy that allows managed installers to run, a policyID `C0DB889B-59C5-453C-B297-399C851934E4` and Friendly Name *[Win-EDU] Microsoft Apps Supplemental Policy - Prod* should be present, and have **Is Currently Enforced** showing as **true**
- For any additional policies that you deploy, check that a policy with a matching ID and Friendly Name is shown in the list and the **Is Currently Enforced** and **Is Authorized** properties are both showing as **true**
-
+
:::image type="content" source="images/troubleshoot-citool.png" alt-text="Screenshot of the output of citool.exe with the Win-EDU supplemental policy.":::
1. Check for **error events** with code **3077**: and reference [Understanding Application Control event IDs][WIN-1]
diff --git a/education/windows/tutorial-deploy-apps-winse/validate-apps.md b/education/windows/tutorial-deploy-apps-winse/validate-apps.md
index a3e128a92e4..211638de729 100644
--- a/education/windows/tutorial-deploy-apps-winse/validate-apps.md
+++ b/education/windows/tutorial-deploy-apps-winse/validate-apps.md
@@ -1,7 +1,7 @@
---
title: Validate the applications deployed to Windows SE devices
description: Learn how to validate the applications deployed to Windows SE devices via Intune.
-ms.date: 06/19/2023
+ms.date: 04/10/2024
ms.topic: tutorial
appliesto:
- ✅ Windows 11 SE, version 22H2 and later
@@ -65,11 +65,11 @@ To check the installation status of an app from the Intune portal:
1. Select **App > All apps**
1. Select the application you want to check
1. From the **Overview** page, you can verify the overall installation status
-
+
:::image type="content" source="./images/intune-app-install-overview.png" alt-text="Screenshot of the Microsoft Intune admin center - App installation details." lightbox="./images/intune-app-install-overview.png":::
1. From the **Device install status** page, you can verify the installation status for each device, and the status code that indicates the cause of the failure
-
+
:::image type="content" source="./images/intune-app-install-status.png" alt-text="Screenshot of the Microsoft Intune admin center - App installation status for each device." lightbox="./images/intune-app-install-status.png":::
> [!NOTE]
diff --git a/education/windows/tutorial-school-deployment/configure-device-apps.md b/education/windows/tutorial-school-deployment/configure-device-apps.md
deleted file mode 100644
index 25171ff770a..00000000000
--- a/education/windows/tutorial-school-deployment/configure-device-apps.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Configure applications with Microsoft Intune
-description: Learn how to configure applications with Microsoft Intune in preparation for device deployment.
-ms.date: 01/16/2024
-ms.topic: tutorial
----
-
-# Configure applications with Microsoft Intune
-
-With Intune for Education, school IT administrators have access to diverse applications to help students unlock their learning potential. This section discusses tools and resources for adding apps to Intune for Education.
-
-Applications can be assigned to groups:
-
-- If you target apps to a **group of users**, the apps will be installed on any managed devices that the users sign into
-- If you target apps to a **group of devices**, the apps will be installed on those devices and available to any user who signs in
-
-> [!div class="checklist"]
->In this section you will:
->
-> - Add apps to Intune for Education
-> - Assign apps to groups
-> - Review some considerations for Windows 11 SE devices
-
-## Add apps to Intune for Education
-
-Intune for Education supports the deployment of two types of Windows applications: **web apps** and **desktop apps**.
-
-:::image type="content" source="./images/intune-education-apps.png" alt-text="Intune for Education - Apps" lightbox="./images/intune-education-apps.png" border="true":::
-
-### Desktop apps
-
-The addition of desktop applications to Intune should be carried out by repackaging the apps, and defining the commands to silently install them. The process is described in the article [Add, assign, and monitor a Win32 app in Microsoft Intune][MEM-1].
-
-### Web apps
-
-To create web applications in Intune for Education:
-
-1. Sign in to the Intune for Education portal
-1. Select **Apps**
-1. Select **New app** > **New web app**
-1. Provide a URL for the web app, a name and, optionally, an icon and description
-1. Select **Save**
-
-For more information, see [Add web apps][INT-2].
-
-## Assign apps to groups
-
-To assign applications to a group of users or devices:
-
-1. Sign in to the Intune for Education portal
-1. Select **Groups** > Pick a group to manage
-1. Select **Apps**
-1. Select either **Web apps** or **Windows apps**
-1. Select the apps you want to assign to the group > Save
-
-## Considerations for Windows 11 SE
-
-Windows 11 SE prevents the installation and execution of third party applications with a technology called **Windows Defender Application Control** (WDAC).
-WDAC applies an *allowlist* policy, which ensures that unwanted apps don't run or get installed. However, it also prevents IT admins from deploying apps to Windows 11 SE devices, unless they're included in the E Mode policy.
-
-To learn more about which apps are supported in Windows 11 SE, and how to deploy them, see the tutorial [Deploy applications to Windows 11 SE with Intune][EDU-1].
-
-## Next steps
-
-With the applications configured, you can now deploy students' and teachers' devices.
-
-> [!div class="nextstepaction"]
-> [Next: Deploy devices >](enroll-overview.md)
-
-
-
-[EDU-1]: ../tutorial-deploy-apps-winse/index.md
-
-[MEM-1]: /mem/intune/apps/apps-win32-add
-
-[INT-1]: /intune-education/express-configuration-intune-edu
-[INT-2]: /intune-education/add-web-apps-edu
\ No newline at end of file
diff --git a/education/windows/tutorial-school-deployment/configure-device-settings.md b/education/windows/tutorial-school-deployment/configure-device-settings.md
deleted file mode 100644
index 5733d483e94..00000000000
--- a/education/windows/tutorial-school-deployment/configure-device-settings.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Configure and secure devices with Microsoft Intune
-description: Learn how to configure policies with Microsoft Intune in preparation for device deployment.
-ms.date: 01/16/2024
-ms.topic: tutorial
-ms.collection: essentials-manage
----
-
-# Configure and secure devices with Microsoft Intune
-
-With Intune for Education, you can configure settings for devices in the school, to ensure that they comply with specific policies.
-For example, you may need to secure your devices, ensuring that they are kept up to date. Or you may need to configure all the devices with the same look and feel.
-
-Settings can be assigned to groups:
-
-- If you target settings to a **group of users**, those settings will apply, regardless of what managed devices the targeted users sign in to
-- If you target settings to a **group of devices**, those settings will apply regardless of who is using the devices
-
-There are two ways to manage settings in Intune for Education:
-
-- **Express Configuration.** This option is used to configure a selection of settings that are commonly used in school environments
-- **Group settings.** This option is used to configure all settings that are offered by Intune for Education
-
-> [!NOTE]
-> Express Configuration is ideal when you are getting started. Settings are pre-configured to Microsoft-recommended values, but can be changed to fit your school's needs. It is recommended to use Express Configuration to initially set up your Windows devices.
-
-
-> [!div class="checklist"]
->In this section you will:
->
-> - Configure settings with Express Configuration
-> - Configure group settings
-> - Create Windows Update policies
-> - Configure security policies
-
-## Configure settings with Express Configuration
-
-With Express Configuration, you can get Intune for Education up and running in just a few steps. You can select a group of devices or users, select applications to distribute, and choose settings from the most commonly used in schools.
-
-> [!TIP]
-> To learn more, and practice step-by-step Express Configuration in Intune for Education, try this interactive demo.
-
-## Configure group settings
-
-Groups are used to manage users and devices with similar management needs, allowing you to apply changes to many devices or users at once. To review the available group settings:
-
-1. Sign in to the Intune for Education portal
-1. Select **Groups** > Pick a group to manage
-1. Select **Windows device settings**
-1. Expand the different categories and review information about individual settings
-
-Settings that are commonly configured for student devices include:
-
-- Wallpaper and lock screen background. See: [Lock screen and desktop][INT-7]
-- Wi-Fi connections. See: [Add Wi-Fi profiles][INT-8]
-- Enablement of the integrated testing and assessment solution *Take a Test*. See: [Add Take a Test profile][INT-9]
-
-For more information, see [Windows device settings in Intune for Education][INT-3].
-
-## Create Windows Update policies
-
-It is important to keep Windows devices up to date with the latest security updates. You can create Windows Update policies using Intune for Education.
-
-To create a Windows Update policy:
-
-1. Select **Groups** > Pick a group to manage
-1. Select **Windows device settings**
-1. Expand the category **Update and upgrade**
-1. Configure the required settings as needed
-
-For more information, see [Updates and upgrade][INT-6].
-
-> [!NOTE]
-> If you require a more complex Windows Update policy, you can create it in Microsoft Intune. For more information:
-> - [What is Windows Update for Business?][WIN-1]
-> - [Manage Windows software updates in Intune][MEM-1]
-
-## Configure security policies
-
-It is critical to ensure that the devices you manage are secured using the different security technologies available in Windows.
-Intune for Education provides different settings to secure devices.
-
-To create a security policy:
-
-1. Select **Groups** > Pick a group to manage
-1. Select **Windows device settings**
-1. Expand the category **Security**
-1. Configure the required settings as needed, including
- - Windows Defender
- - Windows Encryption
- - Windows SmartScreen
-
-For more information, see [Security][INT-4].
-
-> [!NOTE]
-> If you require more sophisticated security policies, you can create them in Microsoft Intune. For more information:
-> - [Antivirus][MEM-2]
-> - [Disk encryption][MEM-3]
-> - [Firewall][MEM-4]
-> - [Endpoint detection and response][MEM-5]
-> - [Attack surface reduction][MEM-6]
-> - [Account protection][MEM-7]
-
----
-
-## Next steps
-
-With the Intune service configured, you can configure policies and applications to deploy to your students' and teachers' devices.
-
-> [!div class="nextstepaction"]
-> [Next: Configure applications >](configure-device-apps.md)
-
-
-
-[EDU-1]: /education/windows/windows-11-se-overview
-
-[INT-2]: /intune-education/express-configuration-intune-edu
-[INT-3]: /intune-education/all-edu-settings-windows
-[INT-4]: /intune-education/all-edu-settings-windows#security
-[INT-6]: /intune-education/all-edu-settings-windows#updates-and-upgrade
-[INT-7]: /intune-education/all-edu-settings-windows#lock-screen-and-desktop
-[INT-8]: /intune-education/add-wi-fi-profile
-[INT-9]: /intune-education/take-a-test-profiles
-
-[WIN-1]: /windows/deployment/update/waas-manage-updates-wufb
-
-[MEM-1]: /mem/intune/protect/windows-update-for-business-configure
-[MEM-2]: /mem/intune/protect/endpoint-security-antivirus-policy
-[MEM-3]: /mem/intune/protect/encrypt-devices
-[MEM-4]: /mem/intune/protect/endpoint-security-firewall-policy
-[MEM-5]: /mem/intune/protect/endpoint-security-edr-policy
-[MEM-6]: /mem/intune/protect/endpoint-security-asr-policy
-[MEM-7]: /mem/intune/protect/endpoint-security-account-protection-policy
\ No newline at end of file
diff --git a/education/windows/tutorial-school-deployment/configure-devices-overview.md b/education/windows/tutorial-school-deployment/configure-devices-overview.md
deleted file mode 100644
index 27ad5f3a8d6..00000000000
--- a/education/windows/tutorial-school-deployment/configure-devices-overview.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Configure devices with Microsoft Intune
-description: Learn how to configure policies and applications in preparation for device deployment.
-ms.date: 11/09/2023
-ms.topic: tutorial
-ms.collection: essentials-manage
----
-
-# Configure settings and applications with Microsoft Intune
-
-Before distributing devices to your users, you must ensure that the devices will be configured with the required policies, settings, and applications as they get enrolled in Intune.
-Microsoft Intune uses Microsoft Entra groups to assign policies and applications to devices.
-With Microsoft Intune for Education, you can conveniently create groups and assign policies and applications to them.
-
-
-> [!div class="checklist"]
->In this section you will:
->
-> - Create groups
-> - Create and assign policies to groups
-> - Create and assign applications to groups
-
-## Create groups
-
-By organizing devices, students, classrooms, or learning curricula into groups, you can provide students with the resources and configurations they need.
-
-By default, Intune for Education creates two default groups: *All devices* and *All users*.
-Two additional groups are pre-created if you use **Microsoft School Data Sync (SDS)**: *All teachers* and *All students*. SDS can also be configured to automatically create and maintain groups of students and teachers for each school.
-
-:::image type="content" source="./images/intune-education-groups.png" alt-text="Intune for Education - Groups blade" border="true":::
-
-Beyond the defaults, groups can be customized to suit various needs. For example, if you have both *Windows 10* and *Windows 11 SE* devices in your school, you can create groups, such as *Windows 10 devices* and *Windows 11 SE devices*, to assign different policies and applications to.
-
-Two group types can be created:
-
-- **Assigned groups** are used when you want to manually add users or devices to a group
-- **Dynamic groups** reference rules that you create to assign students or devices to groups, which automate the membership's maintenance of those groups
-
-> [!TIP]
-> If you target applications and policies to a *device dynamic group*, they will be applied to the devices as soon as they are enrolled in Intune, before users signs in. This can be useful in bulk enrollment scenarios, where devices are enrolled without requiring users to sign in. Devices can be configured and prepared in advance, before distribution.
-
-For more information, see:
-
-- [Create groups in Intune for Education][EDU-1]
-- [Manually add or remove users and devices to an existing assigned group][EDU-2]
-- [Edit dynamic group rules to accommodate for new devices, locations, or school years][EDU-3]
-
-________________________________________________________
-
-## Next steps
-
-With the groups created, you can configure policies and applications to deploy to your groups.
-
-> [!div class="nextstepaction"]
-> [Next: Configure policies >](configure-device-settings.md)
-
-
-
-[EDU-1]: /intune-education/create-groups
-[EDU-2]: /intune-education/edit-groups-intune-for-edu
-[EDU-3]: /intune-education/edit-groups-intune-for-edu#edit-dynamic-group-rules
diff --git a/education/windows/tutorial-school-deployment/enroll-autopilot.md b/education/windows/tutorial-school-deployment/enroll-autopilot.md
deleted file mode 100644
index 23985289cf9..00000000000
--- a/education/windows/tutorial-school-deployment/enroll-autopilot.md
+++ /dev/null
@@ -1,148 +0,0 @@
----
-title: Enrollment in Intune with Windows Autopilot
-description: Learn how to join Microsoft Entra ID and enroll in Intune using Windows Autopilot.
-ms.date: 01/16/2024
-ms.topic: tutorial
----
-
-# Windows Autopilot
-
-Windows Autopilot is designed to simplify all parts of Windows devices lifecycle, from initial deployment through end of life. Using cloud-based services, Windows Autopilot can reduce the overall costs for deploying, managing, and retiring devices.
-
-Traditionally, IT pros spend a significant amount of time building and customizing images that will later be deployed to devices. Windows Autopilot introduces a new, simplified approach. Devices don't need to be reimaged, rather they can be deployed with the OEM image, and customized using cloud-based services.
-
-From the user's perspective, it only takes a few simple operations to make their device ready to use. The only interaction required from the end user is to set their language and regional settings, connect to a network, and verify their credentials. Everything beyond that is automated.
-
-## Prerequisites
-
-Before setting up Windows Autopilot, consider these prerequisites:
-
-- **Software requirements.** Ensure your school and devices meet the [software, networking, licensing, and configuration requirements][WIN-1] for Windows Autopilot
-- **Devices ordered and registered.** Ensure your school IT administrator or Microsoft partner has ordered the devices from an original equipment manufacturer (OEM) and registered them for the Autopilot deployment service. To connect with a partner, you can use the [Microsoft Partner Center][MSFT-1] and work with them to register your devices
-- **Networking requirements.** Ensure students know to connect to the school network during OOBE setup. For more information on managing devices behind firewalls and proxy servers, see [Network endpoints for Microsoft Intune][MEM-1]
-
-> [!NOTE]
-> Where not explicitly specified, both HTTPS (443) and HTTP (80) must be accessible. If you are auto-enrolling your devices into Microsoft Intune or deploying Microsoft Office, follow the networking guidelines for [Microsoft Intune][INT-1] and [Microsoft 365][M365-1].
-
-## Register devices to Windows Autopilot
-
-Before deployment, devices must be registered in the Windows Autopilot service. Each device's unique hardware identity (known as a *hardware hash*) must be uploaded to the Autopilot service. In this way, the Autopilot service can recognize which tenant devices belong to, and which OOBE experience it should present. There are three main ways to register devices to Autopilot:
-
-- **OEM registration process.** When you purchase devices from an OEM or Reseller, that company can automatically register devices to Windows Autopilot and associate them to your tenant. Before this registration can happen, a *Global Administrator* must grant the OEM/Reseller permissions to register devices. For more information, see [OEM registration][MEM-2]
- > [!NOTE]
- > For **Microsoft Surface registration**, collect the details shown in this [documentation table][SURF-1] and follow the instruction to submit the request form to Microsoft Support.
-- **Cloud Solution Provider (CSP) registration process.** As with OEMs, CSP partners must be granted permission to register devices for a school. For more information, see [Partner registration][MEM-5]
- > [!TIP]
- > Try the Microsoft Partner Center clickable demo, which provides detailed steps to establish a partner relationship and register devices.
-- **Manual registration.** To manually register a device, you must first capture its hardware hash. Once this process has been completed, the hardware hash can be uploaded to the Windows Autopilot service using [Microsoft Intune][MEM-6]
- > [!IMPORTANT]
- > **Windows 11 SE** devices do not support the use of Windows PowerShell or Microsoft Configuration Manager to capture hardware hashes. Hardware hashes can only be captured manually. We recommend working with an OEM, partner, or device reseller to register devices.
-
-## Create groups for Autopilot devices
-
-**Windows Autopilot deployment profiles** determine the Autopilot *deployment mode* and define the out-of-box experience of your devices. A device group is required to assign a Windows Autopilot deployment profile to the devices.
-For this task, it's recommended to create dynamic device groups using Autopilot attributes.
-
-Here are the steps for creating a dynamic group for the devices that have an assigned Autopilot group tag:
-
-1. Sign in to the Intune for Education portal
-1. Select **Groups** > **Create group**
-1. Specify a **Group name** and select **Dynamic**
-1. Under **Rules**, select **I want to manage: Devices** and use the clause **Where: Device group tag starts with**, specifying the required tag value
-1. Select **Create group**
- :::image type="content" source="./images/intune-education-autopilot-group.png" alt-text="Intune for Education - creation of a dynamic group for Autopilot devices" border="true":::
-
-More advanced dynamic membership rules can be created from Microsoft Intune admin center. For more information, see [Create an Autopilot device group using Intune][MEM-3].
-
-> [!TIP]
-> You can use these dynamic groups not only to assign Autopilot profiles, but also to target applications and settings.
-
-## Create Autopilot deployment profiles
-
-For Autopilot devices to offer a customized OOBE experience, you must create **Windows Autopilot deployment profiles** and assign them to a group containing the devices.
-A deployment profile is a collection of settings that determine the behavior of the device during OOBE. Among other settings, a deployment profile specifies a **deployment mode**, which can either be:
-
-1. **User-driven:** devices with this profile are associated with the user enrolling the device. User credentials are required to complete the Microsoft Entra join process during OOBE
-1. **Self-deploying:** devices with this profile aren't associated with the user enrolling the device. User credentials aren't required to complete the Microsoft Entra join process. Rather, the device is joined automatically and, for this reason, specific hardware requirements must be met to use this mode
-
-To create an Autopilot deployment profile:
-
-1. Sign in to the Intune for Education portal
-1. Select **Groups** > Select a group from the list
-1. Select **Windows device settings**
-1. Expand the **Enrolment** category
-1. From **Configure Autopilot deployment profile for device** select **User-driven**
-1. Ensure that **User account type** is configured as **Standard**
-1. Select **Save**
-
-While Intune for Education offers simple options for Autopilot configurations, more advanced deployment profiles can be created from Microsoft Intune admin center. For more information, see [Windows Autopilot deployment profiles][MEM-4].
-
-### Configure an Enrollment Status Page
-
-An Enrollment Status Page (ESP) is a greeting page displayed to users while enrolling or signing in for the first time to Windows devices. The ESP displays provisioning progress, showing applications and profiles installation status.
-
-:::image type="content" source="./images/win11-oobe-esp.gif" alt-text="Windows OOBE - enrollment status page animation." border="false":::
-
-> [!NOTE]
-> Some Windows Autopilot deployment profiles **require** the ESP to be configured.
-
-To deploy the ESP to devices, you need to create an ESP profile in Microsoft Intune.
-
-> [!TIP]
-> While testing the deployment process, you can configure the ESP to:
-> - allow the reset of the devices in case the installation fails
-> - allow the use of the device if installation error occurs
->
-> This enables you to troubleshoot the installation process in case any issues arise and to easily reset the OS. You can turn these settings off once you are done testing.
-
-For more information, see [Set up the Enrollment Status Page][MEM-3].
-
-> [!CAUTION]
-> The Enrollment Status Page (ESP) is compatible with Windows 11 SE. However, due to the E Mode policy, devices may not complete the enrollment. For more information, see [Enrollment Status Page][EDU-3].
-
-### Autopilot end-user experience
-
-Once configuration is complete and devices are distributed, students and teachers are able to complete the out-of-box experience with Autopilot. They can set up their devices at home, at school, or wherever there's a reliable Internet connection.
-When a Windows device is turned on for the first time, the end-user experience with Windows Autopilot is as follows:
-
-1. Identify the language and region
-1. Select the keyboard layout and decide on the option for a second keyboard layout
-1. Connect to the internet: if connecting through Wi-Fi, the user will be prompted to connect to a wireless network. If the device is connected through an ethernet cable, Windows will skip this step
-1. Apply updates: the device will look for and apply required updates
-1. Windows will detect if the device has an Autopilot profile assigned to it. If so, it will proceed with the customized OOBE experience. If the Autopilot profile specifies a naming convention for the device, the device will be renamed, and a reboot will occur
-1. The user authenticates to Microsoft Entra ID, using the school account
-1. The device joins Microsoft Entra ID, enrolls in Intune and all the settings and applications are configured
-
-> [!NOTE]
-> Some of these steps may be skipped, depending on the Autopilot profile configuration and if the device is using a wired connection.
-
-:::image type="content" source="./images/win11-login-screen.png" alt-text="Windows 11 login screen" border="false":::
-
-________________________________________________________
-## Next steps
-
-With the devices joined to Microsoft Entra tenant and managed by Intune, you can use Intune to maintain them and report on their status.
-
-> [!div class="nextstepaction"]
-> [Next: Manage devices >](manage-overview.md)
-
-
-
-[MEM-1]: /mem/intune/fundamentals/intune-endpoints
-[MEM-2]: /mem/autopilot/oem-registration
-[MEM-3]: /mem/autopilot/enrollment-autopilot#create-an-autopilot-device-group-using-intune
-[MEM-4]: /mem/autopilot/profiles
-[MEM-5]: /mem/autopilot/partner-registration
-[MEM-6]: /mem/autopilot/add-devices
-
-[WIN-1]: /windows/deployment/windows-autopilot/windows-autopilot-requirements
-
-[MSFT-1]: https://partner.microsoft.com/
-
-[INT-1]: /intune/network-bandwidth-use
-
-[M365-1]: https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2
-
-[EDU-3]: ../tutorial-deploy-apps-winse/considerations.md#enrollment-status-page
-
-[SURF-1]: /surface/surface-autopilot-registration-support
diff --git a/education/windows/tutorial-school-deployment/enroll-entra-join.md b/education/windows/tutorial-school-deployment/enroll-entra-join.md
deleted file mode 100644
index e599fca7ac4..00000000000
--- a/education/windows/tutorial-school-deployment/enroll-entra-join.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Enrollment in Intune with standard out-of-box experience (OOBE)
-description: Learn how to join devices to Microsoft Entra ID from OOBE and automatically get them enrolled in Intune.
-ms.date: 11/09/2023
-ms.topic: tutorial
----
-
-# Automatic Intune enrollment via Microsoft Entra join
-
-If you're setting up a Windows device individually, you can use the out-of-box experience to join it to your school's Microsoft Entra tenant, and automatically enroll it in Intune.
-With this process, no advance preparation is needed:
-
-1. Follow the on-screen prompts for region selection, keyboard selection, and network connection
-1. Wait for updates. If any updates are available, they'll be installed at this time
- :::image type="content" source="./images/win11-oobe-updates.png" alt-text="Windows 11 OOBE - updates page" border="true":::
-1. When prompted, select **Set up for work or school** and authenticate using your school's Microsoft Entra account
- :::image type="content" source="./images/win11-oobe-auth.png" alt-text="Windows 11 OOBE - authentication page" border="true":::
-1. The device will join Microsoft Entra ID and automatically enroll in Intune. All settings defined in Intune will be applied to the device
-
-> [!IMPORTANT]
-> If you configured enrollment restrictions in Intune blocking personal Windows devices, this process will not complete. You will need to use a different enrollment method, or ensure that the devices are registered in Autopilot.
-
-:::image type="content" source="./images/win11-login-screen.png" alt-text="Windows 11 login screen" border="false":::
-
----
-
-## Next steps
-
-With the devices joined to Microsoft Entra tenant and managed by Intune, you can use Intune to maintain them and report on their status.
-
-> [!div class="nextstepaction"]
-> [Next: Manage devices >](manage-overview.md)
diff --git a/education/windows/tutorial-school-deployment/enroll-overview.md b/education/windows/tutorial-school-deployment/enroll-overview.md
deleted file mode 100644
index 8410be0db99..00000000000
--- a/education/windows/tutorial-school-deployment/enroll-overview.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Device enrollment overview
-description: Learn about the different options to enroll Windows devices in Microsoft Intune
-ms.date: 11/09/2023
-ms.topic: overview
----
-
-# Device enrollment overview
-
-There are three main methods for joining Windows devices to Microsoft Entra ID and getting them enrolled and managed by Intune:
-
-- **Automatic Intune enrollment via Microsoft Entra join** happens when a user first turns on a device that is in out-of-box experience (OOBE), and selects the option to join Microsoft Entra ID. In this scenario, the user can customize certain Windows functionalities before reaching the desktop, and becomes a local administrator of the device. This option isn't an ideal enrollment method for education devices
-- **Bulk enrollment with provisioning packages.** Provisioning packages are files that can be used to set up Windows devices, and can include information to connect to Wi-Fi networks and to join a Microsoft Entra tenant. Provisioning packages can be created using either **Set Up School PCs** or **Windows Configuration Designer** applications. These files can be applied during or after the out-of-box experience
-- **Enrollment via Windows Autopilot.** Windows Autopilot is a collection of cloud services to configure the out-of-box experience, enabling light-touch or zero-touch deployment scenarios. Windows Autopilot simplifies the Windows device lifecycle, from initial deployment to end of life, for OEMs, resellers, IT administrators and end users
-
-## Choose the enrollment method
-
-**Windows Autopilot** and the **Set up School PCs** app are usually the most efficient options for school environments.
-This [table][INT-1] describes the ideal scenarios for using either option. It's recommended to review the table when planning your enrollment and deployment strategies.
-
-:::image type="content" source="./images/enroll.png" alt-text="The device lifecycle for Intune-managed devices - enrollment" border="false":::
-
-Select one of the following options to learn the next steps about the enrollment method you chose:
-> [!div class="op_single_selector"]
-> - [Automatic Intune enrollment via Microsoft Entra join](enroll-entra-join.md)
-> - [Bulk enrollment with provisioning packages](enroll-package.md)
-> - [Enroll devices with Windows Autopilot](enroll-autopilot.md)
-
-
-
-[INT-1]: /intune-education/add-devices-windows#when-to-use-set-up-school-pcs-vs-windows-autopilot
diff --git a/education/windows/tutorial-school-deployment/enroll-package.md b/education/windows/tutorial-school-deployment/enroll-package.md
deleted file mode 100644
index 22f7c70443b..00000000000
--- a/education/windows/tutorial-school-deployment/enroll-package.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Enrollment of Windows devices with provisioning packages
-description: Learn about how to enroll Windows devices with provisioning packages using SUSPCs and Windows Configuration Designer.
-ms.date: 11/09/2023
-ms.topic: tutorial
----
-
-# Enrollment with provisioning packages
-
-Enrolling devices with provisioning packages is an efficient way to deploy a large number of Windows devices. Some of the benefits of provisioning packages are:
-
-- There are no particular hardware dependencies on the devices to complete the enrollment process
-- Devices don't need to be registered in advance
-- Enrollment is a simple task: just open a provisioning package and the process is automated
-
-You can create provisioning packages using either **Set Up School PCs** or **Windows Configuration Designer** applications, which are described in the following sections.
-
-## Set up School PCs
-
-With Set up School PCs, you can create a package containing the most common device configurations that students need, and enroll devices in Intune. The package is saved on a USB stick, which can then be plugged into devices during OOBE. Applications and settings will be automatically applied to the devices, including the Microsoft Entra join and Intune enrollment process.
-
-### Create a provisioning package
-
-The Set Up School PCs app guides you through configuration choices for school-owned devices.
-
-:::image type="content" source="./images/supcs-win11se.png" alt-text="Configure device settings in Set Up School PCs app" border="false":::
-
-> [!CAUTION]
-> If you are creating a provisioning package for **Windows 11 SE** devices, ensure to select the correct *OS version* in the *Configure device settings* page.
-
-Set Up School PCs will configure many settings, allowing you to optimize devices for shared use and other scenarios.
-
-For more information on prerequisites, configuration, and recommendations, see [Use the Set Up School PCs app][EDU-1].
-
-> [!TIP]
-> To learn more and practice with Set up School PCs, try the Set Up School PCs demo, which provides detailed steps to create a provisioning package and deploy a device.
-## Windows Configuration Designer
-
-Windows Configuration Designer is especially useful in scenarios where a school needs to provision packages for both bring-you-own devices and school-owned devices. Differently from Set Up School PCs, Windows Configuration Designer doesn't offer a guided experience, and allows granular customizations, including the possibility to embed scripts in the package.
-
-:::image type="content" source="./images/wcd.png" alt-text="Set up device page in Windows Configuration Designer" border="false":::
-
-For more information, see [Install Windows Configuration Designer][WIN-1], which provides details about the app, its provisioning process, and considerations for its use.
-
-## Enroll devices with the provisioning package
-
-To provision Windows devices with provisioning packages, insert the USB stick containing the package during the out-of-box experience. The devices will read the content of the package, join Microsoft Entra ID and automatically enroll in Intune.
-All settings defined in the package and in Intune will be applied to the device, and the device will be ready to use.
-
-:::image type="content" source="./images/win11-oobe-ppkg.gif" alt-text="Windows 11 OOBE - enrollment with provisioning package animation." border="false":::
-
----
-
-## Next steps
-
-With the devices joined to Microsoft Entra tenant and managed by Intune, you can use Intune to maintain them and report on their status.
-
-> [!div class="nextstepaction"]
-> [Next: Manage devices >](manage-overview.md)
-
-
-
-[EDU-1]: /education/windows/use-set-up-school-pcs-app
-
-[WIN-1]: /windows/configuration/provisioning-packages/provisioning-install-icd
diff --git a/education/windows/tutorial-school-deployment/images/advanced-support.png b/education/windows/tutorial-school-deployment/images/advanced-support.png
deleted file mode 100644
index d7655d1616a..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/advanced-support.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/device-lifecycle.png b/education/windows/tutorial-school-deployment/images/device-lifecycle.png
deleted file mode 100644
index ab14cdb9f07..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/device-lifecycle.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/dfci-profile-expanded.png b/education/windows/tutorial-school-deployment/images/dfci-profile-expanded.png
deleted file mode 100644
index 3386f7673a3..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/dfci-profile-expanded.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/dfci-profile.png b/education/windows/tutorial-school-deployment/images/dfci-profile.png
deleted file mode 100644
index d77dc06f3dd..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/dfci-profile.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/enroll.png b/education/windows/tutorial-school-deployment/images/enroll.png
deleted file mode 100644
index 352cda95093..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/enroll.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/enrollment-restrictions.png b/education/windows/tutorial-school-deployment/images/enrollment-restrictions.png
deleted file mode 100644
index 69b22745a6e..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/enrollment-restrictions.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/entra-assign-licenses.png b/education/windows/tutorial-school-deployment/images/entra-assign-licenses.png
deleted file mode 100644
index 3f031053d59..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/entra-assign-licenses.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/entra-branding.png b/education/windows/tutorial-school-deployment/images/entra-branding.png
deleted file mode 100644
index 7201c7386da..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/entra-branding.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/entra-device-settings.png b/education/windows/tutorial-school-deployment/images/entra-device-settings.png
deleted file mode 100644
index ef18b7391ff..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/entra-device-settings.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/entra-tenant-name.png b/education/windows/tutorial-school-deployment/images/entra-tenant-name.png
deleted file mode 100644
index 4cf21148d16..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/entra-tenant-name.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/intune-diagnostics.png b/education/windows/tutorial-school-deployment/images/intune-diagnostics.png
deleted file mode 100644
index 20b05ad9d7a..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/intune-diagnostics.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/intune-education-apps.png b/education/windows/tutorial-school-deployment/images/intune-education-apps.png
deleted file mode 100644
index ca344cf5cfa..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/intune-education-apps.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/intune-education-autopilot-group.png b/education/windows/tutorial-school-deployment/images/intune-education-autopilot-group.png
deleted file mode 100644
index 75543684cae..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/intune-education-autopilot-group.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/intune-education-groups.png b/education/windows/tutorial-school-deployment/images/intune-education-groups.png
deleted file mode 100644
index 87f4546e88b..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/intune-education-groups.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/intune-education-portal.png b/education/windows/tutorial-school-deployment/images/intune-education-portal.png
deleted file mode 100644
index 6bcc9f9375d..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/intune-education-portal.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/inventory-reporting.png b/education/windows/tutorial-school-deployment/images/inventory-reporting.png
deleted file mode 100644
index 39c904e2058..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/inventory-reporting.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/m365-admin-center.png b/education/windows/tutorial-school-deployment/images/m365-admin-center.png
deleted file mode 100644
index d471b441dd2..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/m365-admin-center.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/protect-manage.png b/education/windows/tutorial-school-deployment/images/protect-manage.png
deleted file mode 100644
index 7ee7040a46b..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/protect-manage.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/remote-actions.png b/education/windows/tutorial-school-deployment/images/remote-actions.png
deleted file mode 100644
index cfbd12f2da0..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/remote-actions.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/retire.png b/education/windows/tutorial-school-deployment/images/retire.png
deleted file mode 100644
index c079cfeaac5..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/retire.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/supcs-win11se.png b/education/windows/tutorial-school-deployment/images/supcs-win11se.png
deleted file mode 100644
index 700ff6d87fd..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/supcs-win11se.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/surface-management-portal-expanded.png b/education/windows/tutorial-school-deployment/images/surface-management-portal-expanded.png
deleted file mode 100644
index 339bd909045..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/surface-management-portal-expanded.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/surface-management-portal.png b/education/windows/tutorial-school-deployment/images/surface-management-portal.png
deleted file mode 100644
index a1b7dd37ab5..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/surface-management-portal.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/wcd.png b/education/windows/tutorial-school-deployment/images/wcd.png
deleted file mode 100644
index fba5be741f9..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/wcd.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/whfb-disable.png b/education/windows/tutorial-school-deployment/images/whfb-disable.png
deleted file mode 100644
index 97177965e30..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/whfb-disable.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-autopilot-reset.png b/education/windows/tutorial-school-deployment/images/win11-autopilot-reset.png
deleted file mode 100644
index 0ec380619ef..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-autopilot-reset.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-login-screen.png b/education/windows/tutorial-school-deployment/images/win11-login-screen.png
deleted file mode 100644
index 438dda11bcd..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-login-screen.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-oobe-auth.png b/education/windows/tutorial-school-deployment/images/win11-oobe-auth.png
deleted file mode 100644
index 5ebb6a9f14a..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-oobe-auth.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-oobe-esp.gif b/education/windows/tutorial-school-deployment/images/win11-oobe-esp.gif
deleted file mode 100644
index fa2e4c3aeb7..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-oobe-esp.gif and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-oobe-ppkg.gif b/education/windows/tutorial-school-deployment/images/win11-oobe-ppkg.gif
deleted file mode 100644
index 2defd5c1ce8..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-oobe-ppkg.gif and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-oobe-updates.png b/education/windows/tutorial-school-deployment/images/win11-oobe-updates.png
deleted file mode 100644
index 51bbc39c9f1..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-oobe-updates.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/images/win11-wipe.png b/education/windows/tutorial-school-deployment/images/win11-wipe.png
deleted file mode 100644
index 027afae1721..00000000000
Binary files a/education/windows/tutorial-school-deployment/images/win11-wipe.png and /dev/null differ
diff --git a/education/windows/tutorial-school-deployment/index.md b/education/windows/tutorial-school-deployment/index.md
deleted file mode 100644
index c72273b7aa0..00000000000
--- a/education/windows/tutorial-school-deployment/index.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Introduction to the tutorial deploy and manage Windows devices in a school
-description: Introduction to deployment and management of Windows devices in education environments.
-ms.date: 11/09/2023
-ms.topic: tutorial
-ms.collection: essentials-get-started
----
-
-# Tutorial: deploy and manage Windows devices in a school
-
-This guide introduces the tools and services available from Microsoft to deploy, configure and manage Windows devices in an education environment.
-
-## Audience and user requirements
-
-This tutorial is intended for education professionals responsible for deploying and managing Windows devices, including:
-
-- School leaders
-- IT administrators
-- Teachers
-- Microsoft partners
-
-This content provides a comprehensive path for schools to deploy and manage new Windows devices with Microsoft Intune. It includes step-by-step information how to manage devices throughout their lifecycle, and specific guidance for **Windows 11 SE** and **Surface devices**.
-
-> [!NOTE]
-> Depending on your school setup scenario, you may not need to implement all steps.
-
-## Device lifecycle management
-
-Historically, school IT administrators and educators have struggled to find an easy-to-use, flexible, and secure way to manage the lifecycle of the devices in their schools. In response, Microsoft has developed integrated suites of products for streamlined, cost-effective device lifecycle management.
-
-Microsoft 365 Education provides tools and services that enable simplified management of all devices through Microsoft Intune services. With Microsoft's solutions, IT administrators have the flexibility to support diverse scenarios, including school-owned devices and bring-your-own devices.
-Microsoft Intune services include:
-
-- [Microsoft Intune][MEM-1]
-- [Microsoft Intune for Education][INT-1]
-- [Configuration Manager][MEM-2]
-- [Desktop Analytics][MEM-3]
-- [Windows Autopilot][MEM-4]
-- [Surface Management Portal][MEM-5]
-
-These services are part of the Microsoft 365 stack to help secure access, protect data, and manage risk.
-
-## Why Intune for Education?
-
-Windows devices can be managed with Intune for Education, enabling simplified management of multiple devices from a single point.
-From enrollment, through configuration and protection, to resetting, Intune for Education helps school IT administrators manage and optimize the devices throughout their lifecycle:
-
-:::image type="content" source="./images/device-lifecycle.png" alt-text="The device lifecycle for Intune-managed devices" border="false":::
-
-- **Enroll:** to enable remote device management, devices must be enrolled in Intune with an account in your Microsoft Entra tenant. Some enrollment methods require an IT administrator to initiate enrollment, while others require students to complete the initial device setup process. This document discusses the facets of various device enrollment methodologies
-- **Configure:** once the devices are enrolled in Intune, applications and settings will be applied, as defined by the IT administrator
-- **Protect and manage:** in addition to its configuration capabilities, Intune for Education helps protect devices from unauthorized access or malicious attacks. For example, adding an extra layer of authentication with Windows Hello can make devices more secure. Policies are available that let you control settings for Windows Firewall, Endpoint Protection, and software updates
-- **Retire:** when it's time to repurpose a device, Intune for Education offers several options, including resetting the device, removing it from management, or wiping school data. In this document, we cover different device return and exchange scenarios
-
-## Four pillars of modern device management
-
-In the remainder of this document, we'll discuss the key concepts and benefits of modern device management with Microsoft 365 solutions for education. The guidance is organized around the four main pillars of modern device management:
-
-- **Identity management:** setting up and configuring the identity system, with Microsoft 365 Education and Microsoft Entra ID, as the foundation for user identity and authentication
-- **Initial setup:** setting up the Intune for Education environment for managing devices, including configuring settings, deploying applications, and defining updates cadence
-- **Device enrollment:** Setting up Windows devices for deployment and enrolling them in Intune for Education
-- **Device reset:** Resetting managed devices with Intune for Education
-
----
-
-## Next steps
-
-Let's begin with the creation and configuration of your Microsoft Entra tenant and Intune environment.
-
-> [!div class="nextstepaction"]
-> [Next: Set up Microsoft Entra ID >](set-up-microsoft-entra-id.md)
-
-
-
-[MEM-1]: /mem/intune/fundamentals/what-is-intune
-[MEM-2]: /mem/configmgr/core/understand/introduction
-[MEM-3]: /mem/configmgr/desktop-analytics/overview
-[MEM-4]: /mem/autopilot/windows-autopilot
-[MEM-5]: /mem/autopilot/dfci-management
-
-[INT-1]: /intune-education/what-is-intune-for-education
diff --git a/education/windows/tutorial-school-deployment/manage-overview.md b/education/windows/tutorial-school-deployment/manage-overview.md
deleted file mode 100644
index 0a51b174b9a..00000000000
--- a/education/windows/tutorial-school-deployment/manage-overview.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Manage devices with Microsoft Intune
-description: Overview of device management capabilities in Intune for Education, including remote actions, remote assistance and inventory/reporting.
-ms.date: 11/09/2023
-ms.topic: tutorial
----
-
-# Manage devices with Microsoft Intune
-
-Microsoft Intune offers a streamlined remote device management experience throughout the school year. IT administrators can optimize device settings, deploy new applications, updates, ensuring that security and privacy are maintained.
-
-:::image type="content" source="./images/protect-manage.png" alt-text="The device lifecycle for Intune-managed devices - protect and manage devices" border="false":::
-
-## Remote device management
-
-With Intune for Education, there are several ways to manage students' devices. Groups can be created to organize devices and students, to facilitate remote management. You can determine which applications students have access to, and fine tune device settings and restrictions. You can also monitor which devices students sign in to, and troubleshoot devices remotely.
-
-### Remote actions
-
-Intune fo Education allows you to perform actions on devices without having to sign in to the devices. For example, you can send a command to a device to restart or to turn off, or you can locate a device.
-
-:::image type="content" source="./images/remote-actions.png" alt-text="Remote actions available in Intune for Education when selecting a Windows device" lightbox="./images/remote-actions.png" border="true":::
-
-With bulk actions, remote actions can be performed on multiple devices at once.
-
-To learn more about remote actions in Intune for Education, see [Remote actions][EDU-1].
-
-## Remote assistance
-
-With devices managed by Intune for Education, you can remotely assist students and teachers that are having issues with their devices.
-
-For more information, see [Remote assistance for managed devices - Intune for Education][EDU-2].
-
-## Device inventory and reporting
-
-With Intune for Education, it's possible view and report on current devices, applications, settings, and overall health. You can also download reports to review or share offline.
-
-Here are the steps for generating reports in Intune for Education:
-
-1. Sign in to the Intune for Education portal
-1. Select **Reports**
-1. Select between one of the report types:
- - Device inventory
- - Device actions
- - Application inventory
- - Settings errors
- - Windows Defender
- - Autopilot deployment
-1. If needed, use the search box to find specific devices, applications, and settings
-1. To download a report, select **Download**. The report will download as a comma-separated value (CSV) file, which you can view and modify in a spreadsheet app like Microsoft Excel.
- :::image type="content" source="./images/inventory-reporting.png" alt-text="Reporting options available in Intune for Education when selecting the reports blade" border="true":::
-
-To learn more about reports in Intune for Education, see [Reports in Intune for Education][EDU-3].
-
-
-
-[EDU-1]: /intune-education/edu-device-remote-actions
-[EDU-2]: /intune-education/remote-assist-mobile-devices
-[EDU-3]: /intune-education/what-are-reports
diff --git a/education/windows/tutorial-school-deployment/manage-surface-devices.md b/education/windows/tutorial-school-deployment/manage-surface-devices.md
deleted file mode 100644
index 028dc739c75..00000000000
--- a/education/windows/tutorial-school-deployment/manage-surface-devices.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Management functionalities for Surface devices
-description: Learn about the management capabilities offered to Surface devices, including firmware management and the Surface Management Portal.
-ms.date: 11/09/2023
-ms.topic: tutorial
-appliesto:
- - ✅ Surface devices
----
-
-# Management functionalities for Surface devices
-
-Microsoft Surface devices offer advanced management functionalities, including the possibility to manage firmware settings and a web portal designed for them.
-
-## Manage device firmware for Surface devices
-
-Surface devices use a Unified Extensible Firmware Interface (UEFI) setting that allows you to enable or disable built-in hardware components, protect UEFI settings from being changed, and adjust device boot configuration. With [Device Firmware Configuration Interface profiles built into Intune][INT-1], Surface UEFI management extends the modern management capabilities to the hardware level. Windows can pass management commands from Intune to UEFI for Autopilot-deployed devices.
-
-DFCI supports zero-touch provisioning, eliminates BIOS passwords, and provides control of security settings for boot options, cameras and microphones, built-in peripherals, and more. For more information, see [Manage DFCI on Surface devices][SURF-1] and [Manage DFCI with Windows Autopilot][MEM-1], which includes a list of requirements to use DFCI.
-
-:::image type="content" source="./images/dfci-profile.png" alt-text="Creation of a DFCI profile from Microsoft Intune" lightbox="./images/dfci-profile-expanded.png" border="true":::
-
-## Microsoft Surface Management Portal
-
-Located in the Microsoft Intune admin center, the Microsoft Surface Management Portal enables you to self-serve, manage, and monitor your school's Intune-managed Surface devices at scale. Get insights into device compliance, support activity, warranty coverage, and more.
-
-When Surface devices are enrolled in cloud management and users sign in for the first time, information automatically flows into the Surface Management Portal, giving you a single pane of glass for Surface-specific administration activities.
-
-To access and use the Surface Management Portal:
-
-1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431)
-1. Select **All services** > **Surface Management Portal**
- :::image type="content" source="./images/surface-management-portal.png" alt-text="Surface Management Portal within Microsoft Intune" lightbox="./images/surface-management-portal-expanded.png" border="true":::
-1. To obtain insights for all your Surface devices, select **Monitor**
- - Devices that are out of compliance or not registered, have critically low storage, require updates, or are currently inactive, are listed here
-1. To obtain details on each insights category, select **View report**
- - This dashboard displays diagnostic information that you can customize and export
-1. To obtain the device's warranty information, select **Device warranty and coverage**
-1. To review a list of support requests and their status, select **Support requests**
-
-
-
-[INT-1]: /intune/configuration/device-firmware-configuration-interface-windows
-[MEM-1]: /mem/autopilot/dfci-management
-[SURF-1]: /surface/surface-manage-dfci-guide
diff --git a/education/windows/tutorial-school-deployment/reset-wipe.md b/education/windows/tutorial-school-deployment/reset-wipe.md
deleted file mode 100644
index 9646537bace..00000000000
--- a/education/windows/tutorial-school-deployment/reset-wipe.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Reset and wipe Windows devices
-description: Learn about the reset and wipe options for Windows devices using Intune for Education, including scenarios when to delete devices.
-ms.date: 11/09/2023
-ms.topic: tutorial
----
-
-# Device reset options
-
-There are different scenarios that require a device to be reset, for example:
-
-- The device isn't responding to commands
-- The device is lost or stolen
-- It's the end of the life of the device
-- It's the end of the school year and you want to prepare the device for a new school year
-- The device has hardware problems and you want to send it to the service center
-
-:::image type="content" source="./images/retire.png" alt-text="The device lifecycle for Intune-managed devices - retirement" border="false":::
-
-Intune for Education provides two device reset functionalities that enable IT administrators to remotely execute them:
-
-- **Factory reset** (also known as **wipe**) is used to wipe all data and settings from the device, returning it to the default factory settings
-- **Autopilot reset** is used to return the device to a fully configured or known IT-approved state
-
-## Factory reset (wipe)
-
-A factory reset, or a wipe, reverts a device to the original settings when it was purchased. All settings, applications and data installed on the device after purchase are removed. The device is also removed from Intune management.
-
-Once the wipe is completed, the device will be in out-of-box experience.
-
-Here are the steps to perform a factory reset from Intune for Education:
-
-1. Sign in to the Intune for Education portal
-1. Select **Devices**
-1. Select the device you want to reset > **Factory reset**
-1. Select **Factory reset** to confirm the action
-
-:::image type="content" source="./images/win11-wipe.png" alt-text="Three screenshots showing the device being wiped, ending up in OOBE" lightbox="./images/win11-wipe.png" border="false":::
-
-Consider using factory reset in the following example scenarios:
-
-- The device isn't working properly, and you want to reset it without reimaging it
-- It's the end of school year and you want to prepare the device for a new school year
-- You need to reassign the device to a different student, and you want to reset the device to its original settings
-- You're returning a device to the service center, and you want to remove all data and settings from the device
-
-> [!TIP]
-> Consider that once the device is wiped, the new user will go through OOBE. This option may be ideal if the device is also registered in Autopilot to make the OOBE experience seamless, or if you plan to use a provisioning package to re-enroll the device.
-
-## Autopilot Reset
-
-Autopilot Reset is ideal when all data on a device needs to be wiped, but the device remains enrolled in your tenant.
-
-Once the Autopilot reset action is completed, the device will ask to chose region and keyboard layout, then it will display the sign-in screen.
-
-Here are the steps to perform an Autopilot reset from Intune for Education:
-
-1. Sign in to the Intune for Education portal
-1. Select **Devices**
-1. Select the device you want to reset > **Autopilot reset**
-1. Select **Autopilot reset** to confirm the action
-
-:::image type="content" source="./images/win11-autopilot-reset.png" alt-text="Three screenshots showing the device being wiped, ending up in the login screen" border="false":::
-
-Consider using Autopilot reset in the following example scenarios:
-
-- The device isn't working properly, and you want to reset it without reimaging it
-- It's the end of school year and you want to prepare the device for a new school year
-- You need to reassign the device to a different student, and you want to reset the device to without requiring the student to go through OOBE
-
-> [!TIP]
-> Consider that the end user will **not** go through OOBE, and the association of the user to the device in Intune doesn't change. For this reason, this option may be ideal for devices that have been enrolled in Intune as *shared devices* (for example, a device that was enrolled with a provisioning package or using Autopilot self-deploying mode).
-
-## Wiping and deleting a device
-
-There are scenarios that require a device to be deleted from your tenant, for example:
-
-- The device is lost or stolen
-- It's the end of the life of the device
-- The device has been replaced with a new device or has its motherboard replaced
-
-> [!IMPORTANT]
-> The following actions should only be performed for devices that are no longer going to be used in your tenant.
-
- To completely remove a device, you need to perform the following actions:
-
-1. If possible, perform a **factory reset (wipe)** of the device. If the device can't be wiped, delete the device from Intune using [these steps][MEM-1]
-1. If the device is registered in Autopilot, delete the Autopilot object using [these steps][MEM-2]
-1. Delete the device from Microsoft Entra ID using [these steps][MEM-3]
-
-## Autopilot considerations for a motherboard replacement scenario
-
-Repairing Autopilot-enrolled devices can be complex, as OEM requirements must be balanced with Autopilot requirements. If a motherboard replacement is needed on an Autopilot device, it's suggested the following process:
-
-1. Deregister the device from Autopilot
-1. Replace the motherboard
-1. Capture a new device ID (4K HH)
-1. Re-register the device with Autopilot
- > [!IMPORTANT]
- > For DFCI management, the device must be re-registered by a partner or OEM. Self-registration of devices is not supported with DFCI management.
-1. Reset the device
-1. Return the device
-
-For more information, see [Autopilot motherboard replacement scenario guidance][MEM-4].
-
-
-
-[MEM-1]: /mem/intune/remote-actions/devices-wipe#delete-devices-from-the-intune-portal
-[MEM-2]: /mem/intune/remote-actions/devices-wipe#delete-devices-from-the-intune-portal
-[MEM-3]: /mem/intune/remote-actions/devices-wipe#delete-devices-from-the-azure-active-directory-portal
-[MEM-4]: /mem/autopilot/autopilot-mbr
diff --git a/education/windows/tutorial-school-deployment/set-up-microsoft-entra-id.md b/education/windows/tutorial-school-deployment/set-up-microsoft-entra-id.md
deleted file mode 100644
index 845d66a892d..00000000000
--- a/education/windows/tutorial-school-deployment/set-up-microsoft-entra-id.md
+++ /dev/null
@@ -1,173 +0,0 @@
----
-title: Set up Microsoft Entra ID
-description: Learn how to create and prepare your Microsoft Entra tenant for an education environment.
-ms.date: 01/16/2024
-ms.topic: tutorial
-appliesto:
----
-
-# Set up Microsoft Entra ID
-
-The Microsoft platform for education simplifies the management of Windows devices with Intune for Education and Microsoft 365 Education. The first, fundamental step, is to configure the identity infrastructure to manage user access and permissions for your school.
-
-Microsoft Entra ID, which is included with the Microsoft 365 Education subscription, provides authentication and authorization to any Microsoft cloud services. Identity objects are defined in Microsoft Entra ID for human identities, like students and teachers, as well as non-human identities, like devices, services, and applications. Once users get Microsoft 365 licenses assigned, they'll be able to consume services and access resources within the tenant. With Microsoft 365 Education, you can manage identities for your teachers and students, assign licenses to devices and users, and create groups for the classrooms.
-
-> [!div class="checklist"]
->In this section you will:
->
-> - Set up a Microsoft 365 Education tenant
-> - Add users, create groups, and assign licenses
-> - Configure school branding
-> - Enable bulk enrollment
-
-## Create a Microsoft 365 tenant
-
-If you don't already have a Microsoft 365 tenant, you'll need to create one.
-
-For more information, see [Create your Office 365 tenant account][M365-1]
-
-> [!TIP]
-> To learn more, and practice how to configure the Microsoft 365 tenant for your school, try this interactive demo.
-### Explore the Microsoft 365 admin center
-
-The **Microsoft 365 admin center** is the hub for all administrative consoles for the Microsoft 365 cloud. To access the Microsoft Entra admin center, sign in with the same global administrator account when you [created the Microsoft 365 tenant](#create-a-microsoft-365-tenant).
-
-From the Microsoft 365 admin center, you can access different administrative dashboards: Microsoft Entra ID, Microsoft Intune, Intune for Education, and others:
-
-:::image type="content" source="./images/m365-admin-center.png" alt-text="*All admin centers* page in *Microsoft 365 admin center*" lightbox="./images/m365-admin-center.png" border="true":::
-
-For more information, see [Overview of the Microsoft 365 admin center][M365-2].
-
-> [!NOTE]
-> Setting up your school's basic cloud infrastructure does not require you to complete the rest of the Microsoft 365 setup. For this reason, we will skip directly to adding students and teachers as users in the Microsoft 365 tenant.
-
-## Add users, create groups, and assign licenses
-
-With the Microsoft 365 tenant in place, it's time to add users, create groups, and assign licenses. All students and teachers need a user account before they can sign in and access the different Microsoft 365 services. There are multiple ways to do this, including using School Data Sync (SDS), synchronizing an on-premises Active Directory, manually, or a combination of the above.
-
-> [!NOTE]
-> Synchronizing your Student Information System (SIS) with School Data Sync is the preferred way to create students and teachers as users in a Microsoft 365 Education tenant. However, if you want to integrate an on-premises directory and synchronize accounts to the cloud, skip to [Microsoft Entra Connect Sync](#microsoft-entra-connect-sync) below.
-
-### School Data Sync
-
-School Data Sync (SDS) imports and synchronizes SIS data to create classes in Microsoft 365, such as Microsoft 365 groups and class teams in Microsoft Teams. SDS can be used to create new, cloud-only, identities or to evolve existing identities. Users evolve into *students* or *teachers* and are associated with a *grade*, *school*, and other education-specific attributes.
-
-For more information, see [Overview of School Data Sync][SDS-1].
-
-> [!TIP]
-> To learn more and practice with School Data Sync, follow the Microsoft School Data Sync demo, which provides detailed steps to access, configure, and deploy School Data Sync in your Microsoft 365 Education tenant.
-
-> [!NOTE]
-> You can perform a test deployment by cloning or downloading sample SDS CSV school data from the [O365-EDU-Tools GitHub site](https://github.com/OfficeDev/O365-EDU-Tools).
->
-> Remember that you should typically deploy test SDS data (users, groups, and so on) in a separate test tenant, not your school production environment.
-
-### Microsoft Entra Connect Sync
-
-To integrate an on-premises directory with Microsoft Entra ID, you can use **Microsoft Entra Connect** to synchronize users, groups, and other objects. Microsoft Entra Connect lets you configure the authentication method appropriate for your school, including:
-
-- [Password hash synchronization][AAD-1]
-- [Pass-through authentication][AAD-2]
-- [Federated authentication][AAD-3]
-
-For more information, see [Set up directory synchronization for Microsoft 365][O365-1].
-
-### Create users manually
-
-In addition to the above methods, you can manually add users and groups, and assign licenses through the Microsoft 365 admin center.
-
-There are two options for adding users manually, either individually or in bulk:
-
-1. To add students and teachers as users in Microsoft 365 Education *individually*:
- - Sign in to the Microsoft Entra admin center
- - Select **Microsoft Entra ID** > **Users** > **All users** > **New user** > **Create new user**
- For more information, see [Add users and assign licenses at the same time][M365-3].
-1. To add *multiple* users to Microsoft 365 Education:
- - Sign in to the Microsoft Entra admin center
- - Select **Microsoft Entra ID** > **Users** > **All users** > **Bulk operations** > **Bulk create**
-
-For more information, see [Add multiple users in the Microsoft 365 admin center][M365-4].
-
-### Create groups
-
-Creating groups is important to simplify multiple tasks, like assigning licenses, delegating administration, deploy settings, applications or to distribute assignments to students. To create groups:
-
-1. Sign in to the Microsoft Entra admin center
-1. Select **Microsoft Entra ID** > **Groups** > **All groups** > **New group**
-1. On the **New group** page, select **Group type** > **Security**
-1. Provide a group name and add members, as needed
-1. Select **Next**
-
-For more information, see [Create a group in the Microsoft 365 admin center][M365-5].
-
-### Assign licenses
-
-The recommended way to assign licenses is through group-based licensing. With this method, Microsoft Entra ID ensures that licenses are assigned to all members of the group. Any new members who join the group are assigned the appropriate licenses, and when members leave, their licenses are removed.
-
-To assign a license to a group:
-
-1. Sign in to the Microsoft Entra admin center
-1. Select **Microsoft Entra ID** > **Show More** > **Billing** > **Licenses**
-1. Select the required products that you want to assign licenses for > **Assign**
-1. Add the groups to which the licenses should be assigned
-
- :::image type="content" source="images/entra-assign-licenses.png" alt-text="Assign licenses from Microsoft Entra admin center." lightbox="images/entra-assign-licenses.png":::
-
-For more information, see [Group-based licensing using Microsoft Entra admin center][AAD-4].
-
-## Configure school branding
-
-Configuring your school branding enables a more familiar Autopilot experience to students and teachers. With a custom school branding, you can define a custom logo and a welcome message, which will appear during the Windows out-of-box experience.
-
-To configure your school's branding:
-
-1. Sign in to the Microsoft Entra admin center
-1. Select **Microsoft Entra ID** > **Show More** > **User experiences** > **Company branding**
-1. You can specify brand settings like background image, logo, username hint and a sign-in page text
- :::image type="content" source="images/entra-branding.png" alt-text="Configure Microsoft Entra ID branding from Microsoft Entra admin center." lightbox="images/entra-branding.png":::
-1. To adjust the school tenant's name displayed during OOBE, select **Microsoft Entra ID** > **Overview** > **Properties**
-1. In the **Name** field, enter the school district or organization's name > **Save**
- :::image type="content" alt-text="Configure Microsoft Entra tenant name from Microsoft Entra admin center." source="images/entra-tenant-name.png" lightbox="images/entra-tenant-name.png":::
-
-For more information, see [Add branding to your directory][AAD-5].
-
-## Enable bulk enrollment
-
-If you decide to enroll Windows devices using provisioning packages instead of Windows Autopilot, you must ensure that the provisioning packages can join Windows devices to the Microsoft Entra tenant.
-
-To allow provisioning packages to complete the Microsoft Entra join process:
-
-1. Sign in to the Microsoft Entra admin center
-1. Select **Microsoft Entra ID** > **Devices** > **Device Settings**
-1. Under **Users may join devices to Microsoft Entra ID**, select **All**
- > [!NOTE]
- > If it is required that only specific users can join devices to Microsoft Entra ID, select **Selected**. Ensure that the user account that will create provisioning packages is included in the list of users.
-1. Select Save
- :::image type="content" source="images/entra-device-settings.png" alt-text="Configure device settings from Microsoft Entra admin center." lightbox="images/entra-device-settings.png":::
-
----
-
-## Next steps
-
-With users and groups created, and licensed for Microsoft 365 Education, you can now configure Microsoft Intune.
-
-> [!div class="nextstepaction"]
-> [Next: Set up Microsoft Intune >](set-up-microsoft-intune.md)
-
-
-
-[AAD-1]: /azure/active-directory/hybrid/whatis-phs
-[AAD-2]: /azure/active-directory/hybrid/how-to-connect-pta
-[AAD-3]: /azure/active-directory/hybrid/how-to-connect-fed-whatis
-[AAD-4]: /azure/active-directory/enterprise-users/licensing-groups-assign
-[AAD-5]: /azure/active-directory/fundamentals/customize-branding
-
-[M365-1]: /microsoft-365/education/deploy/create-your-office-365-tenant
-[M365-2]: /microsoft-365/admin/admin-overview/admin-center-overview
-[M365-3]: /microsoft-365/admin/add-users/add-users
-[M365-4]: /microsoft-365/enterprise/add-several-users-at-the-same-time
-[M365-5]: /microsoft-365/admin/create-groups/create-groups
-
-[O365-1]: /office365/enterprise/set-up-directory-synchronization
-
-[SDS-1]: /schooldatasync/overview-of-school-data-sync
diff --git a/education/windows/tutorial-school-deployment/set-up-microsoft-intune.md b/education/windows/tutorial-school-deployment/set-up-microsoft-intune.md
deleted file mode 100644
index 1ee9608b0cf..00000000000
--- a/education/windows/tutorial-school-deployment/set-up-microsoft-intune.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Set up device management
-description: Learn how to configure the Intune service and set up the environment for education.
-ms.date: 01/16/2024
-ms.topic: tutorial
-appliesto:
----
-
-# Set up Microsoft Intune
-
-Without the proper tools and resources, managing hundreds or thousands of devices in a school environment can be a complex and time-consuming task. Microsoft Intune is a collection of services that simplifies the management of devices at scale.
-
-The Microsoft Intune service can be managed in different ways, and one of them is **Intune for Education**, a web portal designed for education environments.
-
-:::image type="content" source="./images/intune-education-portal.png" alt-text="Intune for Education dashboard" lightbox="./images/intune-education-portal.png" border="true":::
-
-**Intune for Education** supports the entire device lifecycle, from the enrollment phase through retirement. IT administrators can start managing classroom devices with bulk enrollment options and a streamlined deployment. At the end of the school year, IT admins can reset devices, ensuring they're ready for the next year.
-
-For more information, see [Intune for Education documentation][INT-1].
-
-> [!div class="checklist"]
->In this section you will:
->
-> - Review Intune's licensing prerequisites
-> - Configure the Intune service for education devices
-
-## Prerequisites
-
-Before configuring settings with Intune for Education, consider the following prerequisites:
-
-- **Intune subscription.** Microsoft Intune is licensed in three ways:
- - As a standalone service
- - As part of [Enterprise Mobility + Security][MSFT-1]
- - As part of a [Microsoft 365 Education subscription][MSFT-2]
-- **Device platform.** Intune for Education can manage devices running a supported version of Windows 10, Windows 11, Windows 11 SE, iOS, and iPad OS
-
-For more information, see [Intune licensing][MEM-1] and [this comparison sheet][MSFT-3], which includes a table detailing the *Microsoft Modern Work Plan for Education*.
-
-## Configure the Intune service for education devices
-
-The Intune service can be configured in different ways, depending on the needs of your school. In this section, you'll configure the Intune service using settings commonly implemented by K-12 school districts.
-
-### Configure enrollment restrictions
-
-With enrollment restrictions, you can prevent certain types of devices from being enrolled and therefore managed by Intune. For example, you can prevent the enrollment of devices that are not owned by the school.
-
-To block personally owned Windows devices from enrolling:
-
-1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
-1. Select **Devices** > **Enroll devices** > **Enrollment device platform restrictions**
-1. Select the **Windows restrictions** tab
-1. Select **Create restriction**
-1. On the **Basics** page, provide a name for the restriction and, optionally, a description > **Next**
-1. On the **Platform settings** page, in the **Personally owned devices** field, select **Block** > **Next**
- :::image type="content" source="./images/enrollment-restrictions.png" alt-text="This screenshot is of the device enrollment restriction page in Microsoft Intune admin center." lightbox="./images/enrollment-restrictions.png":::
-1. Optionally, on the **Scope tags** page, add scope tags > **Next**
-1. On the **Assignments** page, select **Add groups**, and then use the search box to find and choose groups to which you want to apply the restriction > **Next**
-1. On the **Review + create** page, select **Create** to save the restriction
-
-For more information, see [Create a device platform restriction][MEM-2].
-
-### Disable Windows Hello for Business
-
-Windows Hello for Business is a biometric authentication feature that allows users to sign in to their devices using a PIN, password, or fingerprint. Windows Hello for Business is enabled by default on Windows devices, and to set it up, users must perform for multi-factor authentication (MFA). As a result, this feature may not be ideal for students, who may not have MFA enabled.
-It's suggested to disable Windows Hello for Business on Windows devices at the tenant level, and enabling it only for devices that need it, for example for teachers and staff devices.
-To disable Windows Hello for Business at the tenant level:
-
-1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
-1. Select **Devices** > **Windows** > **Windows Enrollment**
-1. Select **Windows Hello for Business**
-1. Ensure that **Configure Windows Hello for Business** is set to **disabled**
-1. Select **Save**
-
-:::image type="content" source="./images/whfb-disable.png" alt-text="Disablement of Windows Hello for Business from Microsoft Intune admin center." lightbox="./images/whfb-disable.png":::
-
-For more information how to enable Windows Hello for Business on specific devices, see [Create a Windows Hello for Business policy][MEM-4].
-
----
-
-## Next steps
-
-With the Intune service configured, you can configure policies and applications in preparation to the deployment of students' and teachers' devices.
-
-> [!div class="nextstepaction"]
-> [Next: Configure devices >](configure-devices-overview.md)
-
-
-
-[MEM-1]: /mem/intune/fundamentals/licenses
-[MEM-2]: /mem/intune/enrollment/enrollment-restrictions-set
-[MEM-4]: /mem/intune/protect/windows-hello#create-a-windows-hello-for-business-policy
-
-[INT-1]: /intune-education/what-is-intune-for-education
-
-[MSFT-1]: https://www.microsoft.com/microsoft-365/enterprise-mobility-security
-[MSFT-2]: https://www.microsoft.com/licensing/product-licensing/microsoft-365-education
-[MSFT-3]: https://edudownloads.azureedge.net/msdownloads/Microsoft-Modern-Work-Plan-Comparison-Education_11-2021.pdf
\ No newline at end of file
diff --git a/education/windows/tutorial-school-deployment/toc.yml b/education/windows/tutorial-school-deployment/toc.yml
deleted file mode 100644
index 8abc013f688..00000000000
--- a/education/windows/tutorial-school-deployment/toc.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-items:
- - name: Introduction
- href: index.md
- - name: 1. Prepare your tenant
- items:
- - name: Set up Microsoft Entra ID
- href: set-up-microsoft-entra-id.md
- - name: Set up Microsoft Intune
- href: set-up-microsoft-intune.md
- - name: 2. Configure settings and applications
- items:
- - name: Overview
- href: configure-devices-overview.md
- - name: Configure policies
- href: configure-device-settings.md
- - name: Configure applications
- href: configure-device-apps.md
- - name: 3. Deploy devices
- items:
- - name: Overview
- href: enroll-overview.md
- - name: Enroll devices via Microsoft Entra join
- href: enroll-entra-join.md
- - name: Enroll devices with provisioning packages
- href: enroll-package.md
- - name: Enroll devices with Windows Autopilot
- href: enroll-autopilot.md
- - name: 4. Manage devices
- items:
- - name: Overview
- href: manage-overview.md
- - name: Management functionalities for Surface devices
- href: manage-surface-devices.md
- - name: Reset and wipe devices
- href: reset-wipe.md
- - name: 5. Troubleshoot and get help
- href: troubleshoot-overview.md
-
diff --git a/education/windows/tutorial-school-deployment/troubleshoot-overview.md b/education/windows/tutorial-school-deployment/troubleshoot-overview.md
deleted file mode 100644
index 0d59f1af56a..00000000000
--- a/education/windows/tutorial-school-deployment/troubleshoot-overview.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Troubleshoot Windows devices
-description: Learn how to troubleshoot Windows devices from Intune and contact Microsoft Support for issues related to Intune and other services.
-ms.date: 11/09/2023
-ms.topic: tutorial
----
-
-# Troubleshoot Windows devices
-
-Microsoft Intune provides many tools that can help you troubleshoot Windows devices.
-Here's a collection of resources to help you troubleshoot Windows devices managed by Intune:
-
-- [Troubleshooting device enrollment in Intune][MEM-2]
-- [Troubleshooting Windows Autopilot][MEM-9]
-- [Troubleshoot Windows Wi-Fi profiles][MEM-6]
-- [Troubleshooting policies and profiles in Microsoft Intune][MEM-5]
-- [Troubleshooting BitLocker with the Intune encryption report][MEM-4]
-- [Troubleshooting CSP custom settings][MEM-8]
-- [Troubleshooting Win32 app installations with Intune][MEM-7]
-- [Troubleshooting device actions in Intune][MEM-3]
-- [**Collect diagnostics**][MEM-10] is a remote action that lets you collect and download Windows device logs without interrupting the user
- :::image type="content" source="./images/intune-diagnostics.png" alt-text="Intune for Education dashboard" lightbox="./images/intune-diagnostics.png" border="true":::
-
-## How to contact Microsoft Support
-
-Microsoft provides global technical, pre-sales, billing, and subscription support for cloud-based device management services. This support includes Microsoft Intune, Configuration Manager, Windows 365, and Microsoft Managed Desktop.
-
-Follow these steps to obtain support in Microsoft Intune provides many tools that can help you troubleshoot Windows devices:
-
-- Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431)
-- Select **Troubleshooting + support** > **Help and support**
- :::image type="content" source="images/advanced-support.png" alt-text="Screenshot that shows how to obtain support from Microsoft Intune." lightbox="images/advanced-support.png":::
-- Select the required support scenario: Configuration Manager, Intune, Co-management, or Windows 365
-- Above **How can we help?**, select one of three icons to open different panes: *Find solutions*, *Contact support*, or *Service requests*
-- In the **Find solutions** pane, use the text box to specify a few details about your issue. The console may offer suggestions based on what you've entered. Depending on the presence of specific keywords, the console provides help like:
- - Run diagnostics: start automated tests and investigations of your tenant from the console to reveal known issues. When you run a diagnostic, you may receive mitigation steps to help with resolution
- - View insights: find links to documentation that provides context and background specific to the product area or actions you've described
- - Recommended articles: browse suggested troubleshooting topics and other content related to your issue
-- If needed, use the *Contact support* pane to file an online support ticket
- > [!IMPORTANT]
- > When opening a case, be sure to include as many details as possible in the *Description* field. Such information includes: timestamp and date, device ID, device model, serial number, OS version, and any other details relevant to the issue.
-- To review your case history, select the **Service requests** pane. Active cases are at the top of the list, with closed issues also available for review
-
-For more information, see [Microsoft Intune support page][MEM-1]
-
-
-[MEM-1]: /mem/get-support
-[MEM-2]: /troubleshoot/mem/intune/troubleshoot-device-enrollment-in-intune
-[MEM-3]: /troubleshoot/mem/intune/troubleshoot-device-actions
-[MEM-4]: /troubleshoot/mem/intune/troubleshoot-bitlocker-admin-center
-[MEM-5]: /troubleshoot/mem/intune/troubleshoot-policies-in-microsoft-intune
-[MEM-6]: /troubleshoot/mem/intune/troubleshoot-wi-fi-profiles#troubleshoot-windows-wi-fi-profiles
-[MEM-7]: /troubleshoot/mem/intune/troubleshoot-win32-app-install
-[MEM-8]: /troubleshoot/mem/intune/troubleshoot-csp-custom-settings
-[MEM-9]: /mem/autopilot/troubleshooting
-[MEM-10]: /mem/intune/remote-actions/collect-diagnostics
diff --git a/education/windows/use-set-up-school-pcs-app.md b/education/windows/use-set-up-school-pcs-app.md
index d6b1fa3e62c..b7d2153dced 100644
--- a/education/windows/use-set-up-school-pcs-app.md
+++ b/education/windows/use-set-up-school-pcs-app.md
@@ -7,7 +7,7 @@ appliesto:
- ✅ Windows 10
---
-# Use the Set up School PCs app
+# Use the Set up School PCs app
IT administrators and technical teachers can use the **Set up School PCs** app to quickly set up Windows devices for students. The app configures devices with the apps and features students need, and it removes the ones they don't need. During setup, if licensed in your tenant, the app enrolls each student device in Microsoft Intune. You can then manage all the settings the app configures through Intune.
@@ -16,20 +16,20 @@ With Set up School PCs you can:
- Joins student devices to your organization's Microsoft Entra tenant
- Enable the optional Autopilot Reset feature, to return devices to a fully configured or known IT-approved state
- Use Windows Update and maintenance hours to keep student devices up-to-date, without interfering with class time
-- Lock down student devices to prevent activity that aren't beneficial to their education
+- Lock down student devices to prevent activity that aren't beneficial to their education
-This article describes how to use the Set up School PCs app. To learn more about the app's functionality, review the [Technical reference for the Set up School PCs app](set-up-school-pcs-technical.md).
+This article describes how to use the Set up School PCs app. To learn more about the app's functionality, review the [Technical reference for the Set up School PCs app](set-up-school-pcs-technical.md).
## Requirements
Before you begin, make sure that your devices and your school's network are configured with the following requirements:
- Microsoft Entra ID and Microsoft 365 licenses
-- [Latest Set up School PCs app](https://apps.microsoft.com/detail/9NBLGGH4LS40)
+- [Latest Set up School PCs app](https://apps.microsoft.com/detail/9NBLGGH4LS40)
- A NTFS-formatted USB drive that is at least 1 GB
- Student devices must either:
- Be within range of the Wi-Fi network that you configured in the app
- - Have a wired Ethernet connection when you set them up
+ - Have a wired Ethernet connection when you set them up
### Prepare existing PC account for new setup
@@ -46,7 +46,7 @@ Alternatively, you can also select **Start** > **Power** icon. Hold down Sh
1. Select **Troubleshoot** > **Reset this PC**
1. Select **Remove everything**
-1. If the option appears, select **Only the drive where Windows is installed**
+1. If the option appears, select **Only the drive where Windows is installed**
1. Select **Just remove my files**
1. Select **Reset**
@@ -58,20 +58,20 @@ This section offers recommendations to prepare you for the best possible setup e
We recommend you run the IT administrator or technical teacher's device on the same Windows build as the student devices.
-### Student devices must meet OS requirements for the app
+### Student devices must meet OS requirements for the app
-Check the OS requirements in the Set up School PCs app. We recommend using the latest Set up School PCs app along with the latest Windows images on the student devices.
+Check the OS requirements in the Set up School PCs app. We recommend using the latest Set up School PCs app along with the latest Windows images on the student devices.
To check the app's OS requirements, go to the Microsoft Store and locate the Set up School PCs app. In the app's description, go to **System Requirements** > **OS**.
-### Use app on a PC that is connected to your school's network
+### Use app on a PC that is connected to your school's network
We recommend that you run the Set up School PCs app on a computer that's connected to your school's network. That way the app can gather accurate information about your school's wireless networks and cloud subscriptions. If it's not connected, you need to enter the information manually.
->[!NOTE]
+>[!NOTE]
>Don't use the **Set up Schools PCs** app for devices that must connect to enterprise or open Wi-Fi networds that require the user to accept Terms of Use.
-### Run app on an open network or network that requires a basic password
+### Run app on an open network or network that requires a basic password
Don't use Set up School PCs over a certificate-based network, or one where you have to enter credentials in a browser. If you need to set up many devices over Wi-Fi, make sure that your network configuration can support it.
@@ -87,57 +87,57 @@ We recommend that you:
To set up more than one PC at the same time, save the provisioning package to additional USB drives. Then plug the USBs in at the same time during setup.
-### Limit changes to school-optimized settings
+### Limit changes to school-optimized settings
-We strongly recommend that you avoid changing preset policies. Changes can slow down setup, performance, and the time it takes to sign in.
+We strongly recommend that you avoid changing preset policies. Changes can slow down setup, performance, and the time it takes to sign in.
-## Create the provisioning package
+## Create the provisioning package
The **Set up School PCs** app guides you through the configuration choices for the student PCs. To begin, open the app on your device and select **Get started**.
-
+
### Package name
-Type a unique name to help distinguish your school's provisioning packages. The name appears:
+Type a unique name to help distinguish your school's provisioning packages. The name appears:
- On the local package folder
- In your tenant's Microsoft Entra account in the Azure portal
-A package expiration date is also attached to the end of each package. For example, *Set_Up_School_PCs (Expires 1-1-2024)*. The expiration date is 180 days after you create your package.
+A package expiration date is also attached to the end of each package. For example, *Set_Up_School_PCs (Expires 1-1-2024)*. The expiration date is 180 days after you create your package.
- 
+ 
-After you select **Next**, you can no longer change the name in the app. To create a package with a different name, reopen the Set up School PCs app.
+After you select **Next**, you can no longer change the name in the app. To create a package with a different name, reopen the Set up School PCs app.
-To change an existing package's name, right-click the package folder on your device and select **Rename**. This action doesn't change the name in Microsoft Entra ID. If you have Global Admin permissions, you can go to Microsoft Entra ID in the Azure portal, and rename the package there.
+To change an existing package's name, right-click the package folder on your device and select **Rename**. This action doesn't change the name in Microsoft Entra ID. You can access to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [User Administrator](/entra/identity/role-based-access-control/permissions-reference#user-administrator), and rename the package there.
-### Sign in
+### Sign in
1. Select how you want to sign in
- 1. (Recommended) To enable student device to automatically connect and authenticate to Microsoft Entra ID, and management services like Microsoft Intune, select **Sign-in**. Then go to step 3
+ 1. (Recommended) To enable student device to automatically connect and authenticate to Microsoft Entra ID, and management services like Microsoft Intune, select **Sign-in**. Then go to step 3
1. To complete setup without signing in, select **Continue without account**. Student devices won't connect to your school's cloud services and their management will be more difficult later. Continue to [Wireless network](#wireless-network)
-1. In the new window, select the account you want to use throughout setup.
+1. In the new window, select the account you want to use throughout setup.
- 
+ 
- To add an account not listed:
- 1. Select **Work or school account** > **Continue**.
- 1. Type in the account username and select **Next**.
- 1. Verify the user account and password, if prompted.
+ To add an account not listed:
+ 1. Select **Work or school account** > **Continue**.
+ 1. Type in the account username and select **Next**.
+ 1. Verify the user account and password, if prompted.
1. Select **Accept** to allow Set up School PCs to access your account throughout setup
1. When your account name appears on the page, select **Next**
- 
+ 
### Wireless network
-Add and save the wireless network profile that you want student devices to connect to. Only skip Wi-Fi setup if you have an Ethernet connection.
+Add and save the wireless network profile that you want student devices to connect to. Only skip Wi-Fi setup if you have an Ethernet connection.
-Select your organization's Wi-Fi network from the list of available wireless networks, or select **Add a wireless network** to manually configure it. Then select **Next**
+Select your organization's Wi-Fi network from the list of available wireless networks, or select **Add a wireless network** to manually configure it. Then select **Next**
- 
+ 
### Device names
@@ -147,17 +147,17 @@ To make sure all device names are unique, Set up School PCs automatically append
To keep the default name for your devices, select **Continue with existing names**.
- 
+ 
### Settings
Select more settings to include in the provisioning package. To begin, select the operating system on your student PCs.
-
+
Setting selections vary based on the OS version you select.
-
+
The following table describes each setting and lists the applicable Windows 10 versions. To find out if a setting is available in your version of Windows 10, look for an *X* in the setting row and in the version column.
@@ -172,20 +172,20 @@ The following table describes each setting and lists the applicable Windows 10 v
After you've made your selections, select **Next**.
-### Time zone
+### Time zone
> [!WARNING]
> If you are using the Autounattend.xml file to reimage your school PCs, do not specify a time zone in the file. If you set the time zone in the file *and* in this app, you will encounter an error.
-Choose the time zone where your school's devices are used. This setting ensures that all PCs are provisioned in the same time zone. When you're done, select **Next**.
+Choose the time zone where your school's devices are used. This setting ensures that all PCs are provisioned in the same time zone. When you're done, select **Next**.
-
+
### Product key
Optionally, type in a 25-digit product key to upgrade or change the edition of Windows on your student devices. If you don't have a product key, select **Continue without change**.
-
+
### Take a Test
@@ -195,7 +195,7 @@ Set up the Take a Test app to give online quizzes and high-stakes assessments. D
-1. Select from the advanced settings. Available settings include:
+1. Select from the advanced settings. Available settings include:
- Allow keyboard auto-suggestions: Allows app to suggest words as the student types on the device's keyboard
- Allow teachers to monitor online tests: Enables screen capture in the Take a Test app
1. Enter the URL where the test is hosted. When students log in to the Take a Test account, they'll be able to select or enter the link to view the assessment
@@ -203,11 +203,11 @@ Set up the Take a Test app to give online quizzes and high-stakes assessments. D
### Personalization
-Upload custom images to replace the student devices' default desktop and lock screen backgrounds. Select **Browse** to search for an image file on your computer. Accepted image formats are jpg, jpeg, and png.
+Upload custom images to replace the student devices' default desktop and lock screen backgrounds. Select **Browse** to search for an image file on your computer. Accepted image formats are jpg, jpeg, and png.
-If you don't want to upload custom images or use the images that appear in the app, select **Continue without personalization**. This option doesn't apply any customizations, and instead uses the devices' default or preset images.
+If you don't want to upload custom images or use the images that appear in the app, select **Continue without personalization**. This option doesn't apply any customizations, and instead uses the devices' default or preset images.
-
+
### Summary
@@ -216,7 +216,7 @@ Review all of the settings for accuracy and completeness
1. To make changes now, select any page along the left side of the window
2. When finished, select **Accept**
-
+
> [!NOTE]
> To make changes to a saved package, you have to start over.
@@ -230,34 +230,34 @@ Review all of the settings for accuracy and completeness
1. When the package is ready, you see the filename and package expiration date. You can also select **Add a USB** to save the same provisioning package to another USB drive. When you're done, remove the USB drive and select **Next**
-
+
## Run package - Get PCs ready
Complete each step on the **Get PCs ready** page to prepare student devices for set-up. Then select **Next**.
-
+
## Run package - Install package on PC
The provisioning package on your USB drive is named SetupSchoolPCs_<*devicename*>(Expires <*expiration date*>.ppkg. A provisioning package applies settings to Windows without reimaging the device.
-When used in context of the Set up School PCs app, the word *package* refers to your provisioning package. The word *provisioning* refers to the act of installing the package on the student device. This section describes how to apply the settings to a device in your school.
+When used in context of the Set up School PCs app, the word *package* refers to your provisioning package. The word *provisioning* refers to the act of installing the package on the student device. This section describes how to apply the settings to a device in your school.
> [!IMPORTANT]
-> The devices must have a new or reset Windows image and must not already have been through first-run setup experience (which is referred to as *OOBE*). For instructions about how to reset a devices's image, see [Prepare existing PC account for new setup](use-set-up-school-pcs-app.md#prepare-existing-pc-account-for-new-setup).
+> The devices must have a new or reset Windows image and must not already have been through first-run setup experience (which is referred to as *OOBE*). For instructions about how to reset a devices's image, see [Prepare existing PC account for new setup](use-set-up-school-pcs-app.md#prepare-existing-pc-account-for-new-setup).
1. Start with the student device turned off or with the device on the first-run setup screen. If the device is past the account setup screen, reset the device to start over. To reset the it, go to **Settings** > **Update & security** > **Recovery** > **Reset this PC**
-
+
1. Insert the USB drive. Windows automatically recognizes and installs the package
1. When you receive the message that it's okay to remove the USB drive, remove it from the device. If there are more devices to set up, insert the USB drive into the next one
- 
+ 
1. If you didn't set up the package with Microsoft Entra join, continue the Windows device setup experience. If you did configure the package with Microsoft Entra join, the device is ready for use and no further configurations are required
diff --git a/education/windows/windows-11-se-overview.md b/education/windows/windows-11-se-overview.md
index eec8f909f16..e5fd11df2bf 100644
--- a/education/windows/windows-11-se-overview.md
+++ b/education/windows/windows-11-se-overview.md
@@ -102,10 +102,10 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `ContentKeeper Cloud` | 9.01.45 | `Win32` | `ContentKeeper Technologies` |
| `DigiExam` | 14.1.0 | `Win32` | `Digiexam` |
| `Digital Secure testing browser` | 15.0.0 | `Win32` | `Digiexam` |
-| `Dolphin Guide Connect` | 1.25 | `Win32` | `Dolphin Guide Connect` |
-| `Dragon Professional Individual` | 15.00.100 | `Win32` | `Nuance Communications` |
+| `Dolphin Guide Connect` | 1.27 | `Win32` | `Dolphin Guide Connect` |
+| `Dragon Professional Individual` | 16.00.200.121 | `Win32` | `Nuance Communications` |
| `DRC INSIGHT Online Assessments` | 14.0.0.0 | `Store` | `Data recognition Corporation` |
-| `Duo from Cisco` | 3.0.0 | `Win32` | `Cisco` |
+| `Duo from Cisco` | 6.3.0 | `Win32` | `Cisco` |
| `Dyknow` | 7.9.13.7 | `Win32` | `Dyknow` |
| `e-Speaking Voice and Speech recognition` | 4.4.0.11 | `Win32` | `e-speaking` |
| `EasyReader` | 10.0.4.498 | `Win32` | `Dolphin Computer Access` |
@@ -114,7 +114,7 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `ESET Endpoint Security` | 10.1.2046.0 | `Win32` | `ESET` |
| `ESET Remote Administrator Agent` | 10.0.1126.0 | `Win32` | `ESET` |
| `eTests` | 4.0.25 | `Win32` | `CASAS` |
-| `Exam Writepad` | 23.2.4.2338 | `Win32` | `Sheldnet` |
+| `Exam Writepad` | 24.4.1.1200 | `Win32` | `Sheldnet` |
| `FirstVoices Keyboard` | 15.0.270 | `Win32` | `SIL International` |
| `FortiClient` | 7.2.0.4034+ | `Win32` | `Fortinet` |
| `Free NaturalReader` | 16.1.2 | `Win32` | `Natural Soft` |
@@ -126,8 +126,10 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `Immunet` | 7.5.8.21178 | `Win32` | `Immunet` |
| `Impero Backdrop Client` | 5.0.151 | `Win32` | `Impero Software` |
| `IMT Lazarus` | 2.86.0 | `Win32` | `IMTLazarus` |
+| `Inprint` | 3.7.6 | `Win32` | `Inprint` |
| `Inspiration 10` | 10.11 | `Win32` | `TechEdology Ltd` |
-| `JAWS for Windows` | 2023.2307.37 | `Win32` | `Freedom Scientific` |
+| `Instashare 2` | 1.3.13.0 | `Win32` | `BenQ` |
+| `JAWS for Windows` | 2024.2312.53 | `Win32` | `Freedom Scientific` |
| `Kite Student Portal` | 9.0.0.0 | `Win32` | `Dynamic Learning Maps` |
| `Keyman` | 16.0.142 | `Win32` | `SIL International` |
| `Kortext` | 2.3.433.0 | `Store` | `Kortext` |
@@ -155,7 +157,7 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `NetSupport School` | 14.00.0012 | `Win32` | `NetSupport` |
| `NextUp Talker` | 1.0.49 | `Win32` | `NextUp Technologies` |
| `Netsweeper Workstation Agent` | 4.50.54.54 | `Win32` | `Netsweeper` |
-| `NonVisual Desktop Access` | 2023.1. | `Win32` | `NV Access` |
+| `NonVisual Desktop Access` | 2023.3 | `Win32` | `NV Access` |
| `NWEA Secure Testing Browser` | 5.4.387.0 | `Win32` | `NWEA` |
| `PC Talker Neo` | 2209 | `Win32` | `Kochi System Development` |
| `PC Talker Neo Plus` | 2209 | `Win32` | `Kochi System Development` |
@@ -166,18 +168,19 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `ReadAndWriteForWindows` | 12.0.78 | `Win32` | `Texthelp Ltd.` |
| `Remote Desktop client (MSRDC)` | 1.2.4487.0 | `Win32` | `Microsoft` |
| `Remote Help` | 5.0.1311.0 | `Win32` | `Microsoft` |
-| `Respondus Lockdown Browser` | 2.0.9.03 | `Win32` | `Respondus` |
+| `Respondus Lockdown Browser` | 2.1.1.05 | `Win32` | `Respondus` |
| `Safe Exam Browser` | 3.5.0.544 | `Win32` | `Safe Exam Browser` |
-|`SchoolYear` | 3.5.4 | `Win32` |`SchoolYear` |
+|`SchoolYear` | 3.7.10 | `Win32` |`SchoolYear` |
|`School Manager` | 3.6.10-1149 | `Win32` |`Linewize` |
|`Schoolnet Secure Tester` | 2.1.0 | `Win32` |`School Net` |
|`Scratch` | 3.0 | `Win32` |`MIT` |
| `Senso.Cloud` |2021.11.15.0 | `Win32` | `Senso.Cloud` |
| `Skoolnext` | 2.19 | `Win32` | `Skool.net` |
| `Smoothwall Monitor` | 2.9.2 | `Win32` | `Smoothwall Ltd` |
-| `SuperNova Magnifier & Screen Reader` | 22.03 | `Win32` | `Dolphin Computer Access` |
+| `SuperNova Magnifier & Screen Reader` | 22.04 | `Win32` | `Dolphin Computer Access` |
| `SuperNova Magnifier & Speech` | 21.03 | `Win32` | `Dolphin Computer Access` |
-|`TX Secure Browser` | 15.0.0 | `Win32` | `Cambium Development` |
+| `Snapplify` | 6.9.7 | `Win32` | `Snapplify` |
+|`TX Secure Browser` | 16.0.0 | `Win32` | `Cambium Development` |
| `VitalSourceBookShelf` | 10.2.26.0 | `Win32` | `VitalSource Technologies Inc` |
|`WA Secure Browser` | 16.0.0 | `Win32` | `Cambium Development` |
| `Winbird` | 19 | `Win32` | `Winbird Co., Ltd.` |
@@ -185,8 +188,8 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `Windows SEB` | 3.4.0 | `Win32` | `Illinois Stateboard of Education` |
| `Windows Notepad` | 12.0.78 | `Store` | `Microsoft Corporation` |
| `Zoom` | 5.12.8 (10232) | `Win32` | `Zoom` |
-| `ZoomText Fusion` | 2023.2307.7.400 | `Win32` | `Freedom Scientific` |
-| `ZoomText Magnifier/Reader` | 2023.2307.29.400 | `Win32` | `Freedom Scientific` |
+| `ZoomText Fusion` | 2024.2403.1.400 | `Win32` | `Freedom Scientific` |
+| `ZoomText Magnifier/Reader` | 2024.2402.66.400 | `Win32` | `Freedom Scientific` |
## Add your own applications
@@ -224,4 +227,4 @@ For more information on Intune requirements for adding education apps, see [Conf
[EDUWIN-1]: /education/windows/tutorial-school-deployment/configure-device-apps
[EDUWIN-2]: /education/windows/tutorial-school-deployment/
-[WIN-1]: /windows/whats-new/windows-11-requirements
\ No newline at end of file
+[WIN-1]: /windows/whats-new/windows-11-requirements
diff --git a/education/windows/windows-11-se-settings-list.md b/education/windows/windows-11-se-settings-list.md
index bea07c4d0bc..1c973e20350 100644
--- a/education/windows/windows-11-se-settings-list.md
+++ b/education/windows/windows-11-se-settings-list.md
@@ -2,7 +2,7 @@
title: Windows 11 SE settings list
description: Windows 11 SE automatically configures settings in the operating system. Learn more about the settings you can control and manage, and the settings you can't change.
ms.topic: reference
-ms.date: 08/18/2023
+ms.date: 05/06/2024
appliesto:
- ✅ Windows 11 SE
ms.collection:
diff --git a/includes/configure/intune-custom-settings-1.md b/includes/configure/intune-custom-settings-1.md
index 05f77b08434..d804757446e 100644
--- a/includes/configure/intune-custom-settings-1.md
+++ b/includes/configure/intune-custom-settings-1.md
@@ -6,11 +6,4 @@ ms.topic: include
ms.service: windows-client
---
-To configure devices with Microsoft Intune, use a custom policy:
-
-1. Go to the Microsoft Intune admin center
-2. Select **Devices > Configuration profiles > Create profile**
-3. Select **Platform > Windows 10 and later** and **Profile type > Templates > Custom**
-4. Select **Create**
-5. Specify a **Name** and, optionally, a **Description > Next**
-6. Add the following settings:
\ No newline at end of file
+To configure devices with Microsoft Intune, [create a custom policy](/mem/intune/configuration/custom-settings-windows-10) and use the following settings:
\ No newline at end of file
diff --git a/includes/configure/intune-custom-settings-2.md b/includes/configure/intune-custom-settings-2.md
index 92dc4bf22d1..66b5ceae1d1 100644
--- a/includes/configure/intune-custom-settings-2.md
+++ b/includes/configure/intune-custom-settings-2.md
@@ -6,7 +6,4 @@ ms.topic: include
ms.service: windows-client
---
-7. Select **Next**
-8. Assign the policy to a security group that contains as members the devices or users that you want to configure > **Next**
-9. Under **Applicability Rules**, select **Next**
-10. Review the policy configuration and select **Create**
\ No newline at end of file
+Assign the policy to a group that contains as members the devices or users that you want to configure.
\ No newline at end of file
diff --git a/includes/configure/intune-custom-settings-info.md b/includes/configure/intune-custom-settings-info.md
deleted file mode 100644
index fc2277cecb3..00000000000
--- a/includes/configure/intune-custom-settings-info.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-author: paolomatarazzo
-ms.author: paoloma
-ms.date: 08/15/2023
-ms.topic: include
-ms.service: windows-client
----
-
-For more information about how to create custom settings using Intune, see [Use custom settings for Windows devices in Intune](/mem/intune/configuration/custom-settings-windows-10).
\ No newline at end of file
diff --git a/includes/configure/powershell-wmi-bridge-1.md b/includes/configure/powershell-wmi-bridge-1.md
new file mode 100644
index 00000000000..84c8a0bb24c
--- /dev/null
+++ b/includes/configure/powershell-wmi-bridge-1.md
@@ -0,0 +1,18 @@
+---
+author: paolomatarazzo
+ms.author: paoloma
+ms.date: 09/12/2023
+ms.topic: include
+ms.prod: windows-client
+---
+
+Configure your devices using PowerShell scripts via the [MDM Bridge WMI Provider](/windows/win32/dmwmibridgeprov/mdm-bridge-wmi-provider-portal).
+
+> [!IMPORTANT]
+> For all device settings, the WMI Bridge client must be executed as SYSTEM (LocalSystem) account.
+
+To test the PowerShell script, you can:
+
+1. [Download the psexec tool](/sysinternals/downloads/psexec)
+1. Open an elevated command prompt and run: `psexec.exe -i -s powershell.exe`
+1. Run the script in the PowerShell session
diff --git a/includes/configure/powershell-wmi-bridge-2.md b/includes/configure/powershell-wmi-bridge-2.md
new file mode 100644
index 00000000000..55db82674df
--- /dev/null
+++ b/includes/configure/powershell-wmi-bridge-2.md
@@ -0,0 +1,9 @@
+---
+author: paolomatarazzo
+ms.author: paoloma
+ms.date: 09/12/2023
+ms.topic: include
+ms.prod: windows-client
+---
+
+For more information, see [Use PowerShell scripting with the WMI Bridge Provider](/windows/client-management/mdm/using-powershell-scripting-with-the-wmi-bridge-provider).
diff --git a/includes/licensing/account-lockout-policy.md b/includes/licensing/account-lockout-policy.md
deleted file mode 100644
index 3ca26ae6ea7..00000000000
--- a/includes/licensing/account-lockout-policy.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-author: paolomatarazzo
-ms.author: paoloma
-ms.date: 09/18/2023
-ms.topic: include
----
-
-## Windows edition and licensing requirements
-
-The following table lists the Windows editions that support Account Lockout Policy:
-
-|Windows Pro|Windows Enterprise|Windows Pro Education/SE|Windows Education|
-|:---:|:---:|:---:|:---:|
-|Yes|Yes|Yes|Yes|
-
-Account Lockout Policy license entitlements are granted by the following licenses:
-
-|Windows Pro/Pro Education/SE|Windows Enterprise E3|Windows Enterprise E5|Windows Education A3|Windows Education A5|
-|:---:|:---:|:---:|:---:|:---:|
-|Yes|Yes|Yes|Yes|Yes|
-
-For more information about Windows licensing, see [Windows licensing overview](/windows/whats-new/windows-licensing).
diff --git a/includes/licensing/assigned-access-kiosk-mode.md b/includes/licensing/assigned-access-kiosk-mode.md
deleted file mode 100644
index f14704f4824..00000000000
--- a/includes/licensing/assigned-access-kiosk-mode.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-author: paolomatarazzo
-ms.author: paoloma
-ms.date: 09/18/2023
-ms.topic: include
----
-
-## Windows edition and licensing requirements
-
-The following table lists the Windows editions that support Assigned Access (kiosk mode):
-
-|Windows Pro|Windows Enterprise|Windows Pro Education/SE|Windows Education|
-|:---:|:---:|:---:|:---:|
-|Yes|Yes|Yes|Yes|
-
-Assigned Access (kiosk mode) license entitlements are granted by the following licenses:
-
-|Windows Pro/Pro Education/SE|Windows Enterprise E3|Windows Enterprise E5|Windows Education A3|Windows Education A5|
-|:---:|:---:|:---:|:---:|:---:|
-|Yes|Yes|Yes|Yes|Yes|
-
-For more information about Windows licensing, see [Windows licensing overview](/windows/whats-new/windows-licensing).
diff --git a/includes/licensing/assigned-access.md b/includes/licensing/assigned-access.md
new file mode 100644
index 00000000000..3a980896b0e
--- /dev/null
+++ b/includes/licensing/assigned-access.md
@@ -0,0 +1,32 @@
+---
+author: paolomatarazzo
+ms.author: paoloma
+ms.date: 09/18/2023
+ms.topic: include
+---
+
+
+
+## Windows edition requirements
+
+The following table lists the Windows editions that support Assigned Access:
+
+|Edition|Assigned Access support|
+|:---|:---:|
+|Education|✅|
+|Enterprise |✅|
+|Enterprise LTSC|✅|
+|IoT Enterprise | ✅|
+|IoT Enterprise LTSC|✅|
+|Pro Education|✅|
+|Pro|✅|
+
+
\ No newline at end of file
diff --git a/includes/licensing/shell-launcher.md b/includes/licensing/shell-launcher.md
new file mode 100644
index 00000000000..b44ad3f92b2
--- /dev/null
+++ b/includes/licensing/shell-launcher.md
@@ -0,0 +1,33 @@
+---
+author: paolomatarazzo
+ms.author: paoloma
+ms.date: 09/18/2023
+ms.topic: include
+---
+
+
+
+## Windows edition requirements
+
+The following table lists the Windows editions that support Shell Launcher:
+
+|Edition|Shell Launcher support|
+|:---|:---:|
+|Education|✅|
+|Enterprise |✅|
+|Enterprise LTSC|✅|
+|IoT Enterprise | ✅|
+|IoT Enterprise LTSC|✅|
+|Pro Education|❌|
+|Pro|❌|
+
+
\ No newline at end of file
diff --git a/includes/licensing/windows-security-policy-settings-and-auditing.md b/includes/licensing/windows-security-policy-settings-and-auditing.md
deleted file mode 100644
index 07f612b6ae9..00000000000
--- a/includes/licensing/windows-security-policy-settings-and-auditing.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-author: paolomatarazzo
-ms.author: paoloma
-ms.date: 09/18/2023
-ms.topic: include
----
-
-## Windows edition and licensing requirements
-
-The following table lists the Windows editions that support Windows security policy settings and auditing:
-
-|Windows Pro|Windows Enterprise|Windows Pro Education/SE|Windows Education|
-|:---:|:---:|:---:|:---:|
-|Yes|Yes|Yes|Yes|
-
-Windows security policy settings and auditing license entitlements are granted by the following licenses:
-
-|Windows Pro/Pro Education/SE|Windows Enterprise E3|Windows Enterprise E5|Windows Education A3|Windows Education A5|
-|:---:|:---:|:---:|:---:|:---:|
-|Yes|Yes|Yes|Yes|Yes|
-
-For more information about Windows licensing, see [Windows licensing overview](/windows/whats-new/windows-licensing).
diff --git a/store-for-business/includes/store-for-business-content-updates.md b/store-for-business/includes/store-for-business-content-updates.md
deleted file mode 100644
index 000c3669c06..00000000000
--- a/store-for-business/includes/store-for-business-content-updates.md
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
-
-## Week of July 10, 2023
-
-
-| Published On |Topic title | Change |
-|------|------------|--------|
-| 7/14/2023 | [Microsoft Store for Business and Education release history](/microsoft-store/release-history-microsoft-store-business-education) | modified |
-| 7/14/2023 | [Whats new in Microsoft Store for Business and Education](/microsoft-store/whats-new-microsoft-store-business-education) | modified |
-| 7/14/2023 | [Prerequisites for Microsoft Store for Business and Education (Windows 10)](/microsoft-store/prerequisites-microsoft-store-for-business) | modified |
-
-
-## Week of June 26, 2023
-
-
-| Published On |Topic title | Change |
-|------|------------|--------|
-| 6/29/2023 | [Microsoft Store for Business and Education release history](/microsoft-store/release-history-microsoft-store-business-education) | modified |
-| 6/29/2023 | [Whats new in Microsoft Store for Business and Education](/microsoft-store/whats-new-microsoft-store-business-education) | modified |
diff --git a/store-for-business/prerequisites-microsoft-store-for-business.md b/store-for-business/prerequisites-microsoft-store-for-business.md
index 1d519c7d261..ac4b271b5dc 100644
--- a/store-for-business/prerequisites-microsoft-store-for-business.md
+++ b/store-for-business/prerequisites-microsoft-store-for-business.md
@@ -65,11 +65,10 @@ If your organization restricts computers on your network from connecting to the
- `account.live.com`
- `clientconfig.passport.net`
- `windowsphone.com`
-- `\*.wns.windows.com`
-- `\*.microsoft.com`
-- `\*.s-microsoft.com`
+- `*.wns.windows.com`
+- `*.microsoft.com`
+- `*.s-microsoft.com`
- `www.msftncsi.com` (prior to Windows 10, version 1607)
-- `www.msftconnecttest.com/connecttest.txt` (replaces `www.msftncsi.com`
- starting with Windows 10, version 1607)
+- `www.msftconnecttest.com/connecttest.txt` (replaces `www.msftncsi.com` starting with Windows 10, version 1607)
Store for Business requires Microsoft Windows HTTP Services (WinHTTP) to install, or update apps.
diff --git a/store-for-business/whats-new-microsoft-store-business-education.md b/store-for-business/whats-new-microsoft-store-business-education.md
index 964efc7788c..4af32aae838 100644
--- a/store-for-business/whats-new-microsoft-store-business-education.md
+++ b/store-for-business/whats-new-microsoft-store-business-education.md
@@ -8,18 +8,20 @@ ms.author: cmcatee
author: cmcatee-MSFT
manager: scotv
ms.topic: conceptual
-ms.date: 01/11/2024
+ms.date: 06/21/2024
ms.reviewer:
---
# What's new in Microsoft Store for Business and Education
-> [!IMPORTANT]
->
-> - The retirement of Microsoft Store for Business and Microsoft Store for Education has been postponed. We will update this notice when a new retirement date is announced. You can continue to use the current capabilities of free apps until that time. For more information about this change, see [Update to Intune integration with the Microsoft Store on Windows](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/update-to-endpoint-manager-integration-with-the-microsoft-store/ba-p/3585077) and [FAQ: Supporting Microsoft Store experiences on managed devices](https://techcommunity.microsoft.com/t5/windows-management/faq-supporting-microsoft-store-experiences-on-managed-devices/m-p/3585286).
-
## Latest updates for Store for Business and Education
+**June 2024**
+
+The Microsoft Store for Business and Microsoft Store for Education portals will retire on August 15, 2024. For more information about this change, see [Update to Intune integration with the Microsoft Store on Windows](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/update-to-intune-integration-with-the-microsoft-store-on-windows/ba-p/3585077) and [FAQ: Supporting Microsoft Store experiences on managed devices](https://techcommunity.microsoft.com/t5/windows-management/faq-supporting-microsoft-store-experiences-on-managed-devices/m-p/3585286). If you are using offline licensing, you can use the [WinGet Download command](/windows/package-manager/winget/download) to continue to access offline apps and license files.
+
+## Previous releases and updates
+
**January 2024**
**Removal of private store capability from Microsoft Store for Business and Education**
@@ -28,8 +30,6 @@ The private store tab and associated functionality was removed from the Microsof
We recommend customers use the [Private app repository, Windows Package Manager, and Company Portal app](/windows/application-management/private-app-repository-mdm-company-portal-windows-11) to provide a private app repository within their organization.
-## Previous releases and updates
-
[May 2023](release-history-microsoft-store-business-education.md#may-2023)
- Tab removed from Microsoft Store apps on Windows 10 PCs.
diff --git a/windows/application-management/add-apps-and-features.md b/windows/application-management/add-apps-and-features.md
deleted file mode 100644
index 534e26d4268..00000000000
--- a/windows/application-management/add-apps-and-features.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: Add or hide Windows features
-description: Learn how to add Windows optional features using the Apps & features page in the Settings app. Also see the group policy objects (GPO) and MDM policies that show or hide Apps and Windows Features in the Settings app. Use Windows PowerShell to show or hide specific features in Windows Features.
-author: aczechowski
-ms.author: aaroncz
-manager: aaroncz
-ms.date: 08/18/2023
-ms.topic: how-to
-ms.service: windows-client
-ms.subservice: itpro-apps
-ms.localizationpriority: medium
-ms.collection: tier2
-appliesto:
- - ✅ Windows 11
- - ✅ Windows 10
----
-
-# Add or hide Windows features
-
-Windows includes optional features that aren't installed by default, but you can add later. These features are called [Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities), and can be installed at any time. Some of these features are language resources like language packs or handwriting support. On organization-owned devices, you can control access to these other features. You can use group policy or mobile device management (MDM) policies to hide the UI from users, or use Windows PowerShell to enable or disable specific features.
-
-## Use the Windows Settings app to add or uninstall features
-
-### Windows 11
-
-1. Open the Start menu and search for **Settings**.
-
-1. In the Settings app, search for "optional" and select **Optional features**.
-
- > [!TIP]
- > You can also use the following shortcut to open it directly: [`ms-settings:optionalfeatures`](ms-settings:optionalfeatures).
-
-1. To add a feature:
-
- 1. Select **View features** next to "Add an optional feature."
-
- 1. Find the feature you want to add, like **XPS Viewer**. Select the box to add it. You can select multiple features.
-
- 1. Select **Next**. Review the list of features you selected, and then select **Install** to add the selected features.
-
-1. To uninstall a feature:
-
- 1. Search for it in the list of **Installed features**.
-
- 1. Expand the section, and select **Uninstall**.
-
-### Windows 10
-
-1. In the Search bar, search for "apps" and select **Apps and features**.
-
-1. Select **Optional features** > **Add a feature**.
-
-1. Select the feature you want to add, like **XPS Viewer**, and then select **Install.**
-
-When the installation completes, the feature is listed in **Apps & features**. In **Apps & features** > **Optional features** > **More Windows features**, there are more features that you and your users can install.
-
-To uninstall a feature, open the **Settings** app. Select the feature, and then select **Uninstall**.
-
-## Use group policy or MDM policies to hide Windows features
-
-By default, the OS might show Windows features and allow users to install and uninstall these optional apps and features. To hide Windows features on your user devices, you can use group policy or an MDM provider like Microsoft Intune.
-
-### Group policy
-
-If you use group policy, use the `User Configuration\Administrative Template\Control Panel\Programs\Hide "Windows Features"` policy. By default, this policy may be set to **Not configured**, which means users can add or remove features. When this setting is **Enabled**, the settings page to add optional features is hidden on the device.
-
-You can't use group policy to disable specific Windows features, such as XPS Viewer. If you want to disable specific features, use [Windows PowerShell](#use-windows-powershell-to-disable-specific-features).
-
-If you want to hide the entire **Apps** feature in the Settings app, use the `User Configuration\Administrative Template\Control Panel\Programs\Hide "Programs and Features" page` policy.
-
-### MDM
-
-Using Microsoft Intune, you can use [administrative templates](/mem/intune/configuration/administrative-templates-windows) or the [settings catalog](/mem/intune/configuration/settings-catalog) to hide Windows features.
-
-If you want to hide the entire **Apps** feature in the Settings app, you can use a configuration policy on Intune enrolled devices. For more information on the settings you can configure, see [Control Panel and Settings device restrictions in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#control-panel-and-settings).
-
-## Use Windows PowerShell to disable specific features
-
-To disable specific features, use the Windows PowerShell [Disable-WindowsOptionalFeature](/powershell/module/dism/disable-windowsoptionalfeature) cmdlet.
-
-> [!NOTE]
-> There isn't a group policy that disables specific Windows features.
-
-To automate disabling specific features, create a scheduled task to run a PowerShell script. For more information about Windows task scheduler, see [Task Scheduler for developers](/windows/win32/taskschd/task-scheduler-start-page).
-
-Microsoft Intune can also run PowerShell scripts. For more information, see [Use PowerShell scripts on Windows client devices in Intune](/mem/intune/apps/intune-management-extension).
-
-To enable specific features, use the [Enable-WindowsOptionalFeature](/powershell/module/dism/enable-windowsoptionalfeature) cmdlet.
-
-Another useful PowerShell cmdlet is [Get-WindowsOptionalFeature](/powershell/module/dism/get-windowsoptionalfeature). Use this cmdlet to view information about optional features in the current OS or a mounted image. This cmdlet returns the current state of features, and whether a restart may be required when the state changes.
-
-## Related articles
-
-- [Features on Demand overview](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities)
-
-- [Available Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-non-language-fod)
-
-- [Language and region Features on Demand (FOD)](/windows-hardware/manufacture/desktop/features-on-demand-language-fod)
diff --git a/windows/application-management/app-v/appv-about-appv.md b/windows/application-management/app-v/appv-about-appv.md
deleted file mode 100644
index 94c799e8af2..00000000000
--- a/windows/application-management/app-v/appv-about-appv.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: What's new in App-V for Windows 10, version 1703 and earlier (Windows 10)
-description: Information about what's new in App-V for Windows 10, version 1703 and earlier.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# What's new in App-V for Windows 10, version 1703 and earlier
-
->Applies to: Windows 10, version 1703 and earlier
-
-Microsoft Application Virtualization (App-V) for Windows 10 delivers Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service in real time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
-
-## What's new in App-V Windows 10, version 1703
-
-### Auto-sequence and update your App-V packages singly or as a batch
-
-Previous versions of the App-V Sequencer required manual sequencing and updating of app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining prerequisite environment provisioning, automating app installation, and expediting package updating setup.
-
-Using the automatic sequencer to package your apps gives you the following benefits:
-
-* **Automatic virtual machine (VM) sequencing environment provisioning**. To learn more, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md).
-* **Package batch-sequencing**. This benefit denotes that multiple apps can be sequenced at the same time, in a single group. To learn more, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
-* **Package batch-updating**. This benefit denotes that multiple apps can be updated at the same time, in a single group. To learn more, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
-
-### Updates to the App-V project template
-
-Starting with Windows 10, version 1703, you can now save an App-V project template (.appvt) file as part of a sequenced App-V package. This file will automatically load every time you open the package for edits or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. To learn more, see [Create and apply an App-V project template to a sequenced App-V package](../app-v/appv-create-and-use-a-project-template.md).
-
-### Automatically clean up unpublished App-V packages from the App-V client
-
-Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up more storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically clean up your unpublished packages after a device restart. To learn more, see [Automatically clean up unpublished packages on the App-V client](../app-v/appv-auto-clean-unpublished-packages.md).
-
-## What's new in App-V in Windows 10, version 1607
-
-### App-V is now a feature in Windows 10
-
-With Windows 10, version 1607 and later releases, App-V is now included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
-
-To learn more about earlier versions of App-V, see [MDOP Information Experience](/microsoft-desktop-optimization-pack/index).
-
-The changes in App-V for Windows 10, version 1607 impact existing implementations of App-V in the following ways:
-
-* The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
-* In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
-
- > [!NOTE]
- >If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release.
-
-For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](../app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](../app-v/appv-migrating-to-appv-from-a-previous-version.md).
-
->[!IMPORTANT]
->You can only upgrade your existing App-V installation to Windows 10, version 1607 if it's version 5.0 SP2 or higher. If you're using an older version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you can upgrade to Windows 10, version 1607.
-
-## Support for System Center
-
-App-V supports System Center 2016 and Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](/previous-versions/system-center/system-center-2012-R2/jj822982(v=technet.10)) to learn more about how to integrate your App-V environment with Configuration Manager.
-
-## Related articles
-
-* [Release Notes for App-V for Windows 10, version 1607](../app-v/appv-release-notes-for-appv-for-windows.md)
-* [Release Notes for App-V for Windows 10, version 1703](../app-v/appv-release-notes-for-appv-for-windows-1703.md)
diff --git a/windows/application-management/app-v/appv-add-or-remove-an-administrator-with-the-management-console.md b/windows/application-management/app-v/appv-add-or-remove-an-administrator-with-the-management-console.md
deleted file mode 100644
index 21175a8da7b..00000000000
--- a/windows/application-management/app-v/appv-add-or-remove-an-administrator-with-the-management-console.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: How to Add or Remove an Administrator by Using the Management Console (Windows 10/11)
-description: Add or remove an administrator on the Microsoft Application Virtualization (App-V) server by using the Management Console.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to add or remove an administrator by using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
-
-## Add an administrator using the Management Console
-
-1. Open the Microsoft Application Virtualization (App-V) Management Console and select **Administrators** in the navigation pane. The navigation pane will display a list of Access Directory (AD) users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
-2. To add a new administrator, select **Add Administrator**. Enter the name of the administrator that you want to add in the **Active Directory Name** field. Make sure to also provide the associated user account domain name. For example, **Domain** \\ **UserName**.
-3. Select the account you want to add and select **Add**. The new account should now appear in the list of server administrators.
-
-## Remove an administrator using the Management Console
-
-1. Open the Microsoft Application Virtualization (App-V) Management Console and select **Administrators** in the navigation pane. The navigation pane displays a list of AD users and groups that currently have administrative access to the Microsoft Application Virtualization (App-V) server.
-2. Right-click the account to be removed from the list of administrators and select **Remove**.
-
-
-
-
-
-## Related articles
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-add-or-upgrade-packages-with-the-management-console.md b/windows/application-management/app-v/appv-add-or-upgrade-packages-with-the-management-console.md
deleted file mode 100644
index ee6544a1815..00000000000
--- a/windows/application-management/app-v/appv-add-or-upgrade-packages-with-the-management-console.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: How to Add or Upgrade Packages by Using the Management Console (Windows 10/11)
-description: Add or upgrade packages on the Microsoft Application Virtualization (App-V) server by using the Management Console.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to add or upgrade packages by using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can use the following procedure to add or upgrade a package to the App-V Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
-
-## Add a package to the Management Console
-
-1. Select the **Packages** tab in the navigation pane of the Management Console display.
-
- The console displays the list of packages that have been added to the server along with status information about each package. When a package is selected, detailed information about the package is displayed in the **PACKAGES** pane.
-
- Select the **Ungrouped** drop-down list box and specify how the packages are to be displayed in the console. You can also click the associated column header to sort the packages.
-
-2. Select **Add or Upgrade Packages** to specify which package you want to add.
-
-3. Enter the full path to the package that you want to add. Use the UNC or HTTP path format, for example **\\\\servername\\sharename\\foldername\\packagename.appv** or **http://server.1234/file.appv**, and then select **Add**.
-
- >[!IMPORTANT]
- >You must select a package with the **.appv** file name extension.
-
-4. The page displays the status message **Adding <Packagename>**. Select **IMPORT STATUS** to check the status of a package that you have imported.
-
- Select **OK** to add the package and close the **Add Package** page. If there was an error during the import, select **Detail** on the **Package Import** page for more information. The newly added package is now available in the **PACKAGES** pane.
-
-5. Select **Close** to close the **Add or Upgrade Packages** page.
-
-
-
-
-
-## Related articles
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-administering-appv-with-powershell.md b/windows/application-management/app-v/appv-administering-appv-with-powershell.md
deleted file mode 100644
index 9260eaa1592..00000000000
--- a/windows/application-management/app-v/appv-administering-appv-with-powershell.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Administering App-V by using Windows PowerShell (Windows 10/11)
-description: Administer App-V by using Windows PowerShell and learn where to find more information about PowerShell for App-V.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Administering App-V by using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Microsoft Application Virtualization (App-V) supports Windows PowerShell cmdlets that give administrators a quick and easy way to manage App-V. The following sections will tell you more about how to use Windows PowerShell with App-V.
-
-## How to administer App-V with Windows PowerShell
-
-The following table lists articles that will tell you more about how to use PowerShell for App-V.
-
-|Name|Description|
-|---|---|
-|[How to load the Windows PowerShell cmdlets for App-V and get cmdlet help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)|Describes how to install the Windows PowerShell cmdlets and find cmdlet help and examples.|
-|[How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)|Describes how to manage the client package lifecycle on a stand-alone computer with Windows PowerShell.|
-|[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)|Describes how to manage connection groups with Windows PowerShell.|
-|[How to modify client configuration by using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)|Describes how to modify the client with Windows PowerShell.|
-|[How to apply the user configuration file by using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)|Describes how to apply a user configuration file with Windows PowerShell.|
-|[How to apply the deployment configuration file by using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)|Describes how to apply a deployment configuration file with Windows PowerShell.|
-|[How to sequence a package by using Windows PowerShell](appv-sequence-a-package-with-powershell.md)|Describes how to create a new package with Windows PowerShell.|
-|[How to create a package accelerator by using Windows PowerShell](appv-create-a-package-accelerator-with-powershell.md)|Describes how to create a package accelerator with Windows PowerShell. You can use package accelerators to automatically sequence large, complex applications.|
-|[How to enable reporting on the App-V client by using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)|Describes how to enable the computer running the App-V Client to send reporting information.|
-|[How to install the App-V databases and convert the associated security identifiers by using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)|Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.|
-|[How to configure the client to receive package and connection groups updates from the publishing server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)|Describes how to use Windows PowerShell to configure a client after you have deployed the App-V management and publishing servers and added the required packages and connection groups.|
-
->[!IMPORTANT]
->Make sure that any script you execute with your App-V packages matches the execution policy that you have configured for Windows PowerShell.
-
-## Windows PowerShell error handling
-
-The following table describes Windows PowerShell error handling for App-V.
-
-|Event|Action|
-|---|---|
-|Using the **RollbackOnError** attribute with embedded scripts|When you use the **RollbackOnError** attribute with embedded scripts, the attribute is ignored for the following events: - Removing a package - Unpublishing a package - Terminating a virtual environment - Terminating a process|
-|Package name contains **$**|If a package name contains the character \$\, you must use a single-quote ( **'** ). For example: ```Add-AppvClientPackage 'Contoso$App.appv'```|
-
-
-
-
-
-## Related articles
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-administering-virtual-applications-with-the-management-console.md b/windows/application-management/app-v/appv-administering-virtual-applications-with-the-management-console.md
deleted file mode 100644
index 3ae0ecc41f1..00000000000
--- a/windows/application-management/app-v/appv-administering-virtual-applications-with-the-management-console.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Administering App-V Virtual Applications by using the Management Console (Windows 10/11)
-description: Administering App-V Virtual Applications by using the Management Console
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Administering App-V Virtual Applications by using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the Microsoft Application Virtualization (App-V) management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers running the App-V client. One or more management servers typically share a common data store for configuration and package information.
-
-The management server uses Active Directory Domain Services (AD DS) groups to manage user authorization and has SQL Server installed to manage the database and data store.
-
-Because the management servers stream applications to end users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs. The management server consists of the following components:
-
-- The **management server** manages packages and connection groups.
-- The **publishing server** deploys packages to computers running the App-V Client.
-- The **management database** manages the package access publishes the server’s synchronization with the management server.
-
-## Management Console tasks
-
-Here are some articles that can show you how to perform the most common tasks that the App-V Management Console is used for:
-
-- [How to connect to the Management Console](appv-connect-to-the-management-console.md)
-- [How to add or upgrade packages by using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md)
-- [How to configure access to packages by using the Management Console](appv-configure-access-to-packages-with-the-management-console.md)
-- [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md)
-- [How to delete a package in the Management Console](appv-delete-a-package-with-the-management-console.md)
-- [How to add or remove an administrator by using the Management Console](appv-add-or-remove-an-administrator-with-the-management-console.md)
-- [How to register and unregister a publishing server by using the Management Console](appv-register-and-unregister-a-publishing-server-with-the-management-console.md)
-- [How to create a custom configuration file by using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md)
-- [How to transfer access and configurations to another version of a package by using the Management Console](appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md)
-- [How to customize virtual application extensions for a specific AD group by using the Management Console](appv-customize-virtual-application-extensions-with-the-management-console.md)
-- [How to view and configure applications and default virtual application extensions by using the Management Console](appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md)
-
-The main elements of the App-V Management Console are:
-
-|Management Console tab|Description|
-|---|---|
-|Packages tab|Use the **Packages** tab to add or upgrade packages.|
-|Connection Groups tab|Use the **Connection Groups** tab to manage connection groups.|
-|Servers tab|Use the **Servers** tab to register a new server.|
-|Administrators tab|Use the **Administrators** tab to register, add, or remove administrators in your App-V environment.|
-
->[!IMPORTANT]
->The browser you're using to open the Web Management Console must have JavaScript enabled.
-
-
-
-
-
-## Other resources for this App-V deployment
-
-- [Application Virtualization (App-V) overview](appv-for-windows.md)
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-allow-administrators-to-enable-connection-groups.md b/windows/application-management/app-v/appv-allow-administrators-to-enable-connection-groups.md
deleted file mode 100644
index 24ab5d46a1a..00000000000
--- a/windows/application-management/app-v/appv-allow-administrators-to-enable-connection-groups.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Only Allow Admins to Enable Connection Groups (Windows 10/11)
-description: Configure the App-V client so that only administrators, not users, can enable or disable connection groups.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to allow only administrators to enable connection groups
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can configure the App-V client so that only administrators, not users, can enable or disable connection groups. In earlier versions of App-V, there was no way to restrict access to disabling connection groups to users.
-
->[!NOTE]
->This feature is supported starting in App-V 5.0 SP3.
-
-Use one of the following methods to allow only administrators to enable or disable connection groups.
-
-|Method|Steps|
-|---|---|
-|Group Policy setting|Enable the “Require publish as administrator” Group Policy setting, which is located in the following Group Policy Object node:
**Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Publishing**|
-|Windows PowerShell cmdlet|Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter.
Parameter values: - **0** – False - **1** – True
Example: ```Set-AppvClientConfiguration -RequirePublishAsAdmin 1```|
-
-
-
-
-
-## Related articles
-
-- [Managing Connection Groups](appv-managing-connection-groups.md)
diff --git a/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md b/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md
deleted file mode 100644
index 363bf2e7ec8..00000000000
--- a/windows/application-management/app-v/appv-application-publishing-and-client-interaction.md
+++ /dev/null
@@ -1,899 +0,0 @@
----
-title: Application Publishing and Client Interaction (Windows 10/11)
-description: Learn technical information about common App-V Client operations and their integration with the local operating system.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Application publishing and client interaction
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This article provides technical information about common App-V Client operations and their integration with the local operating system.
-
-## App-V package files created by the Sequencer
-
-The Sequencer creates App-V packages and produces a virtualized application. The sequencing process creates the following files:
-
-|File|Description|
-|---|---|
-|.appv|- The primary package file, which contains captured assets and state information from the sequencing process. - Architecture of the package file, publishing information, and registry in a tokenized form that can be reapplied to a machine and to a specific user upon delivery.|
-|.MSI|Executable deployment wrapper that you can use to deploy .appv files manually or by using a third-party deployment platform.|
-|_DeploymentConfig.XML|File used to customize the default publishing parameters for all applications in a package that is deployed globally to all users on a computer that is running the App-V Client.|
-|_UserConfig.XML|File used to customize the publishing parameters for all applications in a package that is a deployed to a specific user on a computer that is running the App-V Client.|
-|Report.xml|Summary of messages resulting from the sequencing process, including omitted drivers, files, and registry locations.|
-|.CAB|Optional: Package accelerator file used to automatically rebuild a previously sequenced virtual application package.|
-|.appvt|Optional: Sequencer template file used to retain commonly reused Sequencer settings.|
-
-To learn more about sequencing, see [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
-
-## What’s in the appv file?
-
-The appv file is a container that stores XML and non-XML files together in a single entity. This file is built from the AppX format, which is based on the Open Packaging Conventions (OPC) standard.
-
-To view the appv file contents, make a copy of the package, and then rename the copied file to a .zip extension.
-
-The appv file contains the following folder and files, which are used when creating and publishing a virtual application:
-
-| Name | Type | Description |
-|---|---|---|
-| Root | File folder | Directory that contains the file system for the virtualized application captured during sequencing. |
-| [Content_Types].xml | XML File | List of the core content types in the appv file (for example, DLL, EXE, BIN). |
-| AppxBlockMap.xml | XML File | Layout of the appv file, which uses File, Block, and BlockMap elements that enable location and validation of files in the App-V package.|
-| AppxManifest.xml | XML File | Metadata for the package that contains the required information for adding, publishing, and launching the package. Includes extension points (file type associations and shortcuts) and the names and GUIDs associated with the package.|
-| FilesystemMetadata.xml | XML File | List of the files captured during sequencing, including attributes (such as directories, files, opaque directories, empty directories, and long and short names). |
-| PackageHistory.xml | XML File | Information about the sequencing computer (operating system version, Internet Explorer version, .Net Framework version) and process (upgrade, package version).|
-| Registry.dat | DAT File | Registry keys and values captured during the sequencing process for the package.|
-| StreamMap.xml | XML File | List of files for the primary and publishing feature block. The publishing feature block contains the ICO files and required portions of files (EXE and DLL) for publishing the package. When present, the primary feature block includes files that have been optimized for streaming during the sequencing process.|
-
-## App-V Client data storage locations
-
-The App-V Client performs tasks to keep virtual applications running properly and working like locally installed applications. The process of opening and running virtual applications requires mapping from the virtual file system and registry to ensure the application has the required components of a traditional application expected by users. This section describes the assets that are required to run virtual applications and lists the location where App-V stores the assets.
-
-| Name | Location | Description |
-|---|---|---|
-| Package Store | %ProgramData%\App-V| Default location for read-only package files.|
-| Machine Catalog | %ProgramData%\Microsoft\AppV\Client\Catalog| Contains per-machine configuration documents.|
-| User Catalog | %AppData%\Microsoft\AppV\Client\Catalog| Contains per-user configuration documents.|
-| Shortcut Backups | %AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups| Stores previous integration points that enable restore on package unpublish.|
-| Copy on Write (COW) Roaming | %AppData%\Microsoft\AppV\Client\VFS| Writeable roaming location for package modification.|
-| Copy on Write (COW) Local | %LocalAppData%\Microsoft\AppV\Client\VFS| Writeable non-roaming location for package modification.|
-| Machine Registry | HKLM\Software\Microsoft\AppV| Contains package state information, including VReg for machine or globally published packages (Machine hive).|
-| User Registry | HKCU\Software\Microsoft\AppV| Contains user package state information including VReg.|
-| User Registry Classes | HKCU\Software\Classes\AppV| Contains more user package state information.|
-
-More details for the table are provided in the section below and throughout the document.
-
-### Package store
-
-The App-V Client manages the applications assets mounted in the package store. This default storage location is %ProgramData%\App-V, but you can configure it during or after setup by using the **Set-AppVClientConfiguration** Windows PowerShell cmdlet, which modifies the local registry (**PackageInstallationRoot** value under the HKLM\Software\Microsoft\AppV\Client\Streaming key). The package store must be located at a local path on the client operating system. The individual packages are stored in the package store in subdirectories named after the Package GUID and Version GUID.
-
-The following is an example of a path to a specific application:
-
-```syntax
-C:\ProgramData\App-V\PackGUID\VersionGUID
-```
-
-To change the default location of the package store during setup, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
-
-### Shared Content Store
-
-If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). In VDI environments where local storage can be limited, it's important to use as little disk space as possible. You can minimize disk space usage by streaming applications from a high-performance network location (such as a SAN). For more information, see [Shared Content Store in Microsoft App-V 5.0 - Behind the Scenes](/archive/blogs/appv/shared-content-store-in-microsoft-app-v-5-0-behind-the-scenes).
-
->[!NOTE]
->The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client.
-
-### Package catalogs
-
-The App-V Client manages the following file-based locations:
-
-- **Catalogs (user and machine).**
-- **Registry locations**—depends on how the package is targeted for publishing. There's a Catalog (data store) for the computer, and a catalog for each individual user. The Machine catalog stores global information applicable to all users or any specific user, and the User catalog stores information applicable to a specific user. The catalog is a collection of Dynamic Configurations and manifest files; there's discrete data for both file and registry per package version.
-
-### Machine catalog
-
-The locations described in this table can be found in the %programdata%\Microsoft\AppV\Client\Catalog\ folder.
-
-| | Location |
-|:---|:---|
-|**Description**|Stores package documents that are available to users on the machine when packages are added and published. However, if a package is “global” at publishing time, the integrations are available to all users. If a package is non-global, the integrations are published only for specific users, but there are still global resources that are modified and visible to anyone on the client computer (such as when the package directory is in a shared disk location). If a package is available to a user on the computer (global or non-global), the manifest is stored in the Machine Catalog. When a package is published globally, there's a Dynamic Configuration file, stored in the Machine Catalog; therefore, the determination of whether a package is global is defined according to whether there's a policy file (UserDeploymentConfiguration file) in the Machine Catalog.|
-|**Default storage location**|%programdata%\Microsoft\AppV\Client\Catalog\ This location isn't the same as the Package Store location. The Package Store is the golden or pristine copy of the package files.|
-|**Files in the machine catalog**|- Manifest.xml - DeploymentConfiguration.xml - UserManifest.xml (Globally Published Package) - UserDeploymentConfiguration.xml (Globally Published Package)|
-|**Additional machine catalog location, used when the package is part of a connection group**|The following location is in addition to the specific package location mentioned previously as the default storage location: %programdata%\Microsoft\AppV\Client\Catalog\PackageGroups\ConGroupGUID\ConGroupVerGUID|
-|**Additional files in the machine catalog when the package is part of a connection group**|- PackageGroupDescriptor.xml - UserPackageGroupDescriptor.xml (globally published Connection Group)|
-
-### User catalog
-
-The locations described in this table can be found in the appdata\roaming\Microsoft\AppV\Client\Catalog\ folder.
-
-|| Location |
-|:---|:---|
-|**Description**|Created during the publishing process. Contains information used for publishing the package, and for making sure that a package is provisioned to a specific user at launch. Created in a roaming location and includes user-specific publishing information. When a package is published for a user, the policy file is stored in the User Catalog. At the same time, a copy of the manifest is also stored in the User Catalog. When a package entitlement is removed for a user, the relevant package files are removed from the User Catalog. Looking at the user catalog, an administrator can view the presence of a Dynamic Configuration file, which indicates that the package is entitled for that user. For roaming users, the User Catalog needs to be in a roaming or shared location to preserve the legacy App-V behavior of targeting users by default. Entitlement and policy are tied to a user, not a computer, so they should roam with the user once they're provisioned.|
-|**Default storage location**|appdata\roaming\Microsoft\AppV\Client\Catalog\Packages\PkgGUID\VerGUID|
-|**Files in the user catalog**|- UserManifest.xml - DynamicConfiguration.xml or UserDeploymentConfiguration.xml|
-|**Additional user catalog location, used when the package is part of a connection group**|The following location is in addition to the specific package location mentioned above: appdata\roaming\Microsoft\AppV\Client\Catalog\PackageGroups\PkgGroupGUID\PkgGroupVerGUID|
-|**Additional file in the machine catalog when the package is part of a connection group**|UserPackageGroupDescriptor.xml|
-
-### Shortcut backups
-
-During the publishing process, the App-V Client backs up any shortcuts and integration points to %AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups. This backup lets integration points restore to the previous versions when the package is unpublished.
-
-### Copy on Write files
-
-The Package Store contains a pristine copy of the package files that have been streamed from the publishing server. During normal operation of an App-V application, the user or service may require changes to the files. However, these changes aren't made in the package store to preserve your ability to repair the application, which removes these changes. These locations, called Copy on Write (COW), support both roaming and non-roaming locations. The location where the modifications are stored depends where the application has been programmed to write changes to in a native experience.
-
-### COW roaming
-
-The COW Roaming location described above stores changes to files and directories that are targeted to the typical %AppData% location or \\Users\\*<username>*\\AppData\\Roaming location. These directories and files are then roamed based on the operating system settings.
-
-### COW local
-
-The COW Local location is similar to the roaming location, but the directories and files aren't roamed to other computers, even if roaming support has been configured. The COW Local location described above stores changes applicable to typical windows and not the %AppData% location. The directories listed will vary but there will be two locations for any typical Windows locations (for example, Common AppData and Common AppDataS). The **S** signifies the restricted location when the virtual service requests the change as a different elevated user from the signed-in users. The non-**S** location stores user-based changes.
-
-## Package registry
-
-Before an application can access the package registry data, the App-V Client must make the package registry data available to the applications. The App-V Client uses the real registry as a backing store for all registry data.
-
-When a new package is added to the App-V Client, a copy of the REGISTRY.DAT file from the package is created at %ProgramData%\Microsoft\AppV\Client\VREG\{Version GUID}.dat. The name of the file is the version GUID with the .DAT extension. The reason this copy is made is to ensure that the actual hive file in the package is never in use, which would prevent the removal of the package at a later time.
-
-**Registry.dat from Package Store** > **%ProgramData%\Microsoft\AppV\Client\Vreg\\{VersionGUID}.dat**
-
-When the first application from the package is launched on the client, the client stages or copies the contents out of the hive file, re-creating the package registry data in an alternate location under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Packages\PackageGuid\Versions\VersionGUID\REGISTRY. The staged registry data has two distinct types of machine data and user data. Machine data is shared across all users on the machine. User data is staged for each user to a user-specific location HKCU\Software\Microsoft\AppV\Client\Packages\PackageGUID\Registry\User. The machine data is ultimately removed at package removal time, and the user data is removed on a user unpublish operation.
-
-### Package registry staging vs. connection group registry staging
-
-When connection groups are present, the previous process of staging the registry holds true, but instead of having one hive file to process, there are more than one. The files are processed in the order in which they appear in the connection group XML, with the first writer winning any conflicts.
-
-The staged registry persists the same way as in the single package case. Staged user registry data remains for the connection group until it's disabled; staged machine registry data is removed on connection group removal.
-
-### Virtual registry
-
-The purpose of the virtual registry (VREG) is to provide a single merged view of the package registry and the native registry to applications. It also provides copy-on-write (COW) functionality—that is, any changes made to the registry from the context of a virtual process are made to a separate COW location. This functionality means that the VREG must combine up to three separate registry locations into a single view based on the populated locations in the **registry COW** > **package** > **native**. When a request is made for a registry data it will locate in order until it finds the data it was requesting. Meaning if there's a value stored in a COW location it will not proceed to other locations, however, if there's no data in the COW location it will proceed to the Package and then Native location until it finds the appropriate data.
-
-### Registry locations
-
-There are two package registry locations and two connection group locations where the App-V Client stores registry information, depending on whether the Package is published individually or as part of a connection group. There are three COW locations for packages and three for connection groups, which are created and managed by the VREG. Settings for packages and connection groups aren't shared:
-
-#### Single Package VReg
-
-The registries in the following table are located in the Registry\Client\Packages\PkgGUID\ folder.
-
-|Location|Description|
-|---|---|
-|COW|- Machine Registry\Client\Packages\PkgGUID\REGISTRY (Only elevate process can write) - User Registry\Client\Packages\PkgGUID\REGISTRY (User Roaming anything written under HKCU except Software\Classes - User Registry Classes\Client\Packages\PkgGUID\REGISTRY (HKCU\Software\Classes writes and HKLM for non-elevated process)|
-|Package|- Machine Registry\Client\Packages\PkgGUID\Versions\VerGuid\Registry\Machine - User Registry Classes\Client\Packages\PkgGUID\Versions\VerGUID\Registry|
-|Native|- Native application registry location|
-
-#### Connection Group VReg
-
-The registries in the following table are located in the Machine Registry\Client\PackageGroups\GrpGUID\ and User Registry Classes\Client\PackageGroups\GrpGUID\ folders.
-
-|Location|Description|
-|---|---|
-|COW|- Machine Registry\Client\PackageGroups\GrpGUID\REGISTRY (only elevate process can write) - User Registry\Client\PackageGroups\GrpGUID\REGISTRY (Anything written to HKCU except Software\Classes) - User Registry Classes\Client\PackageGroups\GrpGUID\REGISTRY|
-|Package|- Machine Registry\Client\PackageGroups\GrpGUID\Versions\VerGUID\REGISTRY - User Registry Classes\Client\PackageGroups\GrpGUID\Versions\VerGUID\REGISTRY|
-|Native|- Native application registry location|
-
-There are two COW locations for HKLM: elevated and non-elevated processes. Elevated processes always write HKLM changes to the secure COW under HKLM. Non-elevated processes always write HKLM changes to the non-secure COW under HKCU\\Software\\Classes. When an application reads changes from HKLM, elevated processes will read changes from the secure COW under HKLM. Non-elevated reads from both, favoring the changes made in the unsecure COW first.
-
-### Pass-through keys
-
-An administrator can use pass-through keys to configure certain keys to only be read from the native registry, bypassing the Package and COW locations. Pass-through locations are global to the machine (not package-specific) and can be configured by adding the path to the key, which should be treated as pass-through to the **REG\_MULTI\_SZ** value called **PassThroughPaths** of the key HKLM\Software\Microsoft\AppV\Subsystem\VirtualRegistry. Any key that appears under this multi-string value (and their children) will be treated as pass-through.
-
-The following locations are configured as pass-through locations by default:
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WINEVT
-
-- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\services\\eventlog\\Application
-
-- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Autologger
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Policies
-
-The purpose of pass-through keys is to ensure that a virtual application doesn't write registry data in the VReg that is required for non-virtual applications for successful operation or integration. The Policies key ensures that Group Policy-based settings set by the administrator are utilized and not per package settings. The AppModel key is required for integration with Windows Modern UI-based applications. Administers ideally shouldn't modify any of the default pass-through keys, but in some instances, the admin may need to add more pass-through keys to adjust application behavior.
-
-## App-V package store behavior
-
-App-V manages the Package Store, which is the location where the expanded asset files from the appv file are stored. By default, this location is stored at %ProgramData%\\App-V, and is limited in terms of storage capabilities only by free disk space. The package store is organized by the GUIDs for the package and version as mentioned in the previous section.
-
-### Add packages
-
-App-V Packages are staged upon addition to the computer with the App-V Client. The App-V Client provides on-demand staging. When publishing or manually entering the **Add-AppVClientPackage** cmdlet, the data structure is built in the package store (C:\\programdata\\App-V\\{PkgGUID}\\{VerGUID}). The package files identified in the publishing block defined in the StreamMap.xml file are added to the system, and the top level folders and child files are staged to ensure proper application assets exist at launch.
-
-### Mounting packages
-
-Packages can be explicitly loaded by entering the **Mount-AppVClientPackage** PowerShell cmdlet or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store.
-
-### Streaming packages
-
-The App-V Client can be configured to change the default behavior of streaming. All streaming policies are stored under the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Streaming. Policies are set by entering the **Set-AppvClientConfiguration** PowerShell cmdlet. The following policies apply to streaming:
-
-|Policy|Description|
-|---|---|
-|AllowHighCostLaunch|Allows streaming over 3G and cellular networks|
-|AutoLoad|Specifies the Background Load setting: 0 – Disabled 1 – Previously Used Packages only 2 – All Packages|
-|PackageInstallationRoot|The root folder for the package store in the local machine|
-|PackageSourceRoot|The root override where packages should be streamed from|
-|SharedContentStoreMode|Enables the use of Shared Content Store for VDI scenarios|
-
-These settings affect the behavior of streaming App-V package assets to the client. By default, App-V only downloads the assets required after downloading the initial publishing and primary feature blocks. There are three specific behaviors in streaming packages that are important to understand:
-
-- Background Streaming
-- Optimized Streaming
-- Stream Faults
-
-### Background streaming
-
-The Windows PowerShell cmdlet **Get-AppvClientConfiguration** can be used to determine the current mode for background streaming with the AutoLoad setting and modified with either the **Set-AppvClientConfiguration** cmdlet or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can either be disabled altogether (value=0) or enabled for all packages (value=2), regardless of whether they've been launched.
-
-### Optimized streaming
-
-App-V packages can be configured with a primary feature block during sequencing. This setting allows the sequencing engineer to monitor launch files for a specific application, or applications, and mark the blocks of data in the App-V package for streaming at first launch of any application in the package.
-
-### Stream faults
-
-After the initial stream of any publishing data and the primary feature block, requests for more files perform stream faults. These blocks of data are downloaded to the package store on an as-needed basis. This flexibility allows a user to download only a small part of the package, typically enough to launch the package and run normal tasks. All other blocks are downloaded when a user initiates an operation that requires data not currently in the package store.
-
-### Package upgrades
-
-App-V Packages require updating throughout the lifecycle of the application. App-V Package upgrades are like the package publish operation, as each version will be created in its own PackageRoot location: %ProgramData%\App-V\{PkgGUID}\{newVerGUID}. The upgrade operation is optimized by creating hard links to identical and streamed files from other versions of the same package.
-
-### Package removal
-
-The App-V Client's behavior when packages are removed depends on the package removal method. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but the package store location and COW locations remain. When the **Remove-AppVClientPackge** Windows PowerShell cmdlet is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server doesn't perform a Remove operation. Neither operation will remove the Package Store package files.
-
-## Roaming registry and data
-
-App-V is able to provide a near-native experience when roaming, depending on how the application being used is written. By default, App-V roams AppData that is stored in the roaming location, based on the roaming configuration of the operating system. Other locations for storage of file-based data don't roam from computer to computer, since they're in locations that aren't roamed.
-
-### Roaming requirements and user catalog data storage
-
-App-V stores data, which represents the state of the user’s catalog, in the form of:
-
-- Files under %appdata%\\Microsoft\\AppV\\Client\\Catalog
-- Registry settings under HKEY_CURRENT_USER\Software\Microsoft\AppV\Client\Packages
-
-Together, these files and registry settings represent the user’s catalog, so either both must be roamed, or neither must be roamed for a given user. App-V doesn't support roaming %AppData%, but not roaming the user’s profile (registry), or vice versa.
-
->[!NOTE]
->The **Repair-AppvClientPackage** cmdlet doesn't repair the publishing state of packages where the user’s App-V state under HKEY_CURRENT_USER is missing or mismatched with the data in %appdata%.
-
-### Registry-based data
-
-App-V registry roaming falls into two scenarios, as shown in the following table.
-
-|Scenario|Description|
-|---|---|
-|Applications that are run as standard users|When a standard user launches an App-V application, both HKLM and HKCU for App-V applications are stored in the HKCU hive on the machine. This scenario presents two distinct paths:
- HKLM's location is HKCU\SOFTWARE\Classes\AppV\Client\Packages\\{PkgGUID}\REGISTRY\MACHINE\SOFTWARE - HKCU's location is HKCU\SOFTWARE\Microsoft\AppV\Client\Packages\\{PkgGUID}\REGISTRY\USER\\{UserSID}\SOFTWARE
The locations are enabled for roaming based on the operating system settings.|
-|Applications that are run with elevation|When an application is launched with elevation:
- HKLM data is stored in the HKLM hive on the local computer - HKCU data is stored in the User Registry location
In this scenario, these settings aren't roamed with normal operating system roaming configurations, and the resulting registry keys and values are stored in the following locations:
- HKLM's location is HKLM\SOFTWARE\Microsoft\AppV\Client\Packages\\{PkgGUID}\\{UserSID}\REGISTRY\MACHINE\SOFTWARE - HKCU's location is HKCU\SOFTWARE\Microsoft\AppV\Client\Packages\\{PkgGUID}\\Registry\User\\{UserSID}\SOFTWARE|
-
-### App-V and folder redirection
-
-App-V supports folder redirection of the roaming AppData folder (%AppData%). When the virtual environment is started, the roaming AppData state from the user’s roaming AppData directory is copied to the local cache. Conversely, when the virtual environment is shut down, the local cache that is associated with a specific user’s roaming AppData is transferred to the actual location of that user’s roaming AppData directory.
-
-A typical package has several locations mapped in the user’s backing store for settings in both AppData\\Local and AppData\\Roaming. These locations are the Copy on Write locations that are stored per user in the user’s profile, and that are used to store changes made to the package VFS directories and to protect the default package VFS.
-
-The following table shows local and roaming locations when folder redirection hasn't been implemented.
-
-| VFS directory in package | Mapped location of backing store |
-|---|---|
-| ProgramFilesX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\ProgramFilesX86 |
-| SystemX86 | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\SystemX86 |
-| Windows | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\Windows |
-| appv\_ROOT | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\appv_ROOT|
-| AppData | C:\Users\username\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\AppData |
-
-The following table shows local and roaming locations when folder redirection has been implemented for %AppData% and the location has been redirected (typically to a network location).
-
-| VFS directory in package | Mapped location of backing store |
-|---|---|
-| ProgramFilesX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\ProgramFilesX86 |
-| SystemX86 | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\SystemX86 |
-| Windows | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\Windows |
-| appv_ROOT | C:\Users\Local\AppData\Local\Microsoft\AppV\Client\VFS\\<GUID>\appv\_ROOT |
-| AppData | \\Fileserver\users\Local\roaming\Microsoft\AppV\Client\VFS\\<GUID>\AppData |
-
-The current App-V Client VFS driver can't write to network locations, so the App-V Client detects the presence of folder redirection and copies the data on the local drive during publishing and when the virtual environment starts. After the user closes the App-V application and the App-V Client closes the virtual environment, the local storage of the VFS AppData is copied back to the network, enabling roaming to more machines, where the process will be repeated. Here's what happens during the process:
-
-1. During publishing or virtual environment startup, the App-V Client detects the location of the AppData directory.
-2. If the roaming AppData path is local or no AppData\\Roaming location is mapped, nothing happens.
-3. If the roaming AppData path isn't local, the VFS AppData directory is mapped to the local AppData directory.
-
-This process solves the problem of a non-local %AppData% that isn't supported by the App-V Client VFS driver. However, the data stored in this new location isn't roamed with folder redirection. All changes during the running of the application happen to the local AppData location and must be copied to the redirected location. The process does the following things:
-
-1. Shuts down the App-V application, which also shuts down the virtual environment.
-2. Compresses the local cache of the roaming AppData location and store it in a .zip file.
-3. Uses the time stamp at the end of the .zip packaging process to name the file.
-4. Records the time stamp in the HKEY\_CURRENT\_USER\\Software\\Microsoft\\AppV\\Client\\Packages\\<GUID>\\AppDataTime registry as the last known AppData time stamp.
-5. Calls the folder redirection process to evaluate and initiate the .zip file uploaded to the roaming AppData directory.
-
-The time stamp is used to determine a “last writer wins” scenario if there's a conflict and is used to optimize the download of the data when the App-V application is published, or the virtual environment is started. Folder redirection will make the data available from any other clients covered by the supporting policy and will initiate the process of storing the AppData\\Roaming data to the local AppData location on the client. Here's what happens during the process:
-
-1. The user starts an application, which also starts the virtual environment.
-2. The application’s virtual environment checks for the most recent time stamped .zip file, if present.
-3. The virtual environment checks the registry for the last known uploaded time stamp, if present.
-4. The virtual environment downloads the most recent .zip file unless the local last known upload time stamp is greater than or equal to the time stamp from the .zip file.
-5. If the local last known upload time stamp is earlier than that of the most recent .zip file in the roaming AppData location, the virtual environment extracts the .zip file to the local temp directory in the user’s profile.
-6. After the .zip file is successfully extracted, the local cache of the roaming AppData directory is renamed and the new data moved into place.
-7. The renamed directory is deleted and the application opens with the most recently saved roaming AppData data.
-
-This process completes the successful roaming of application settings that are present in AppData\\Roaming locations. The only other condition that must be addressed is a package repair operation. The process does the following things:
-
-1. During repair, detects if the path to the user’s roaming AppData directory isn't local.
-2. Maps the non-local roaming AppData path targets, recreating the expected roaming and local AppData locations.
-3. Deletes the time stamp stored in the registry, if present.
-
-This process will recreate both the local and network locations for AppData and remove the registry record of the time stamp.
-
-## App-V Client application lifecycle management
-
-In an App-V Full Infrastructure, after applications are sequenced, they're managed and published to users or computers through the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are input as PowerShell commands on the computer running the App-V Client.
-
-This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Microsoft Configuration Manager, see [Deploy App-V virtual applications with Configuration Manager](/mem/configmgr/apps/get-started/deploying-app-v-virtual-applications).
-
-The App-V application lifecycle tasks are triggered at user sign in (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured (after the client is enabled) with Windows PowerShell commands. See [App-V Client Configuration Settings: Windows PowerShell](appv-client-configuration-settings.md#app-v-client-configuration-settings-windows-powershell).
-
-### Publishing refresh
-
-The publishing refresh process comprises several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process when the user signs in, the machine turns on, and at scheduled intervals. The client configuration during setup listed in the previous section is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following Windows PowerShell cmdlets:
-
-- **Add-AppVPublishingServer** configures the client with an App-V Publishing Server that provides App-V packages.
-- **Set-AppVPublishingServer** modifies the current settings for the App-V Publishing Server.
-- **Set-AppVClientConfiguration** modifies the currents settings for the App-V Client.
-- **Sync-AppVPublishingServer** initiates an App-V Publishing Refresh process manually. This process is also utilized in the scheduled tasks created during configuration of the publishing server.
-
-The following sections will elaborate what goes on during the publishing refresh process.
-
-#### Adding an App-V package
-
-Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the **Add-AppVClientPackage** cmdlet in Windows PowerShell, except the publishing refresh add process contacts the configured publishing server and passes a high-level list of applications back to the client to pull more detailed information, rather than just doing a single package add operation.
-
-The process then configures the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following steps are a detailed workflow of the process, assuming the package is configured for Fault Streaming.
-
-#### How to add an App-V package
-
-1. Initiate installation manually through Windows PowerShell or Task Sequence initiation of the Publishing Refresh process.
-
- 1. The App-V Client makes an HTTP connection and requests a list of applications based on the target. The Publishing refresh process supports targeting machines or users.
-
- 2. The App-V Publishing Server uses the identity of the initiating target, user or machine, and queries the database for a list of entitled applications. The list of applications is provided as an XML response, which the client uses to send more requests to the server for more information on a per-package basis.
-
-2. The Publishing Agent on the App-V Client will evaluate any connection groups that are unpublished or disabled, since package version updates that are part of the connection group can't be processed.
-
-3. Configure the packages by identifying the **Add** or **Update** operations.
-
- 1. The App-V Client utilizes the AppX API from Windows and accesses the appv file from the publishing server.
-
- 2. The package file is opened and the **AppXManifest.xml** and **StreamMap.xml** files are downloaded to the Package Store.
-
- 3. Completely stream publishing block data defined in the **StreamMap.xml** file. Publishing block data is stored in Package Store\\PkgGUID\\VerGUID\\Root.
-
- - Icons: Targets of extension points.
- - Portable Executable Headers (PE Headers): Targets of extension points that contain the base information about the image need on disk, accessed directly or through file types.
- - Scripts: Download scripts directory for use throughout the publishing process.
-
- 4. Populate the Package store by performing the following sub-steps:
-
- 1. Create sparse files on disk that represent the extracted package for any directories listed.
-
- 2. Stage top-level files and directories under root.
-
- All other files are created when the directory is listed as sparse on disk and streamed on demand.
-
- 5. Create the machine catalog entries. Create the **Manifest.xml** and **DeploymentConfiguration.xml** files from the package files (if no **DeploymentConfiguration.xml** file in the package a placeholder is created).
-
- 6. Create location of the package store in the registry **HKLM\\Software\\Microsoft\\AppV\\Client\\Packages\\PkgGUID\\Versions\\VerGUID\\Catalog**.
-
- 7. Create the **Registry.dat** file from the package store to **%ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat**.
-
- 8. Register the package with the App-V Kernel Mode Driver at **HKLM\\Microsoft\\Software\\AppV\\MAV**.
-
- 9. Invoke scripting from the **AppxManifest.xml** or **DeploymentConfig.xml** file for Package Add timing.
-
-4. Configure Connection Groups by adding and enabling or disabling.
-
-5. Remove objects that aren't published to the target (user or machine).
-
- > [!NOTE]
- >This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).
-
-6. Invoke background load mounting based on client configuration.
-
-7. Packages that already have publishing information for the machine or user are immediately restored.
-
- > [!NOTE]
- >This condition occurs as a product of removal without unpublishing with background addition of the package.
-
-This process completes an App-V package add for the publishing refresh process. The next step is publishing the package to a specific target (machine or user).
-
-
-
-**Package add file and registry data**
-
-#### Publishing an App-V package
-
-During the Publishing Refresh operation, the specific publishing operation, **Publish-AppVClientPackage**, adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.
-
-#### How to publish an App-V package
-
-1. Package entries are added to the user catalog
-
- 1. User targeted packages: the **UserDeploymentConfiguration.xml** and **UserManifest.xml** files are placed on the machine in the User Catalog.
-
- 2. Machine targeted (global) packages: the **UserDeploymentConfiguration.xml** is placed in the Machine Catalog.
-
-2. Register the package with the kernel mode driver for the user at **HKLM\\Software\\Microsoft\\AppV\\MAV**.
-
-3. Perform integration tasks.
-
- 1. Create extension points.
-
- 2. Store backup information in the user’s registry and roaming profile (Shortcut Backups).
-
- > [!NOTE]
- >This enables restore extension points if the package is unpublished.
-
- 3. Run scripts targeted for publishing timing.
-
-Publishing an App-V Package that is part of a Connection Group is similar to the above process. For connection groups, the path that stores the specific catalog information includes PackageGroups as a child of the Catalog Directory. Review the Machine and User Catalog information in the preceding sections for details.
-
-
-
-**Package add file and registry data—global**
-
-### Application launch
-
-After the Publishing Refresh process, the user launches and then relaunches an App-V application. The App-V Client checks the path to the user catalog for files created during publishing. After establishing rights to launch the package, the App-V Client creates a virtual environment, begins streaming any necessary data, and applies the appropriate manifest and deployment configuration files during virtual environment creation. Once the virtual environment created and configured for the specific package and application, the application starts. This might seem like a lot, but the process in action is fast, and is optimized to minimize network traffic.
-
-#### How to launch App-V applications
-
-1. User launches the application by selecting a shortcut or file type invocation.
-
-2. The App-V Client verifies existence in the User Catalog for the following files
-
- - **UserDeploymentConfiguration.xml**
- - **UserManifest.xml**
-
-3. If the files are present, the application is entitled for that specific user and the application will start the process for launch. There's no network traffic at this point.
-
-4. Next, the App-V Client checks that the path for the package registered for the App-V Client service is found in the registry.
-
-5. Upon finding the path to the package store, the virtual environment is created.
-
- If this process execution is the first launch, the Primary Feature Block downloads if present.
-
-6. After downloading, the App-V Client service consumes the manifest and deployment configuration files to configure the virtual environment and all App-V subsystems are loaded.
-
-7. The Application launches. For any missing files in the package store (sparse files), App-V will stream fault the files on an as-needed basis.
-
- 
-
- **Package add file and registry data—stream**
-
-### Upgrading an App-V package
-
-The current version of App-V's package upgrade process differs from the older versions in its storage optimization. App-V supports multiple versions of the same package on a machine entitled to different users. Package versions can be added at any time, as the package store and catalogs are updated with the new resources. During an upgrade in the new version, only new files are added to the new version store location, and hard links are created for unchanged files. Such results reduce overall storage by only presenting the file on one disk location, then projecting it into all folders with a file location entry on the disk.
-
-#### How to upgrade an App-V package
-
-1. The App-V Client performs a Publishing Refresh and discovers a newer version of an App-V Package.
-
-2. Package entries are added to the appropriate catalog for the new version.
-
- 1. User targeted packages: the **UserDeploymentConfiguration.xml** and **UserManifest.xml** files are placed on the machine in the user catalog at **appdata\\roaming\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID**.
-
- 2. Machine targeted (global) packages: the **UserDeploymentConfiguration.xml** is placed in the machine catalog at **%programdata%\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID**.
-
-3. Register the package with the kernel mode driver for the user at **HKLM\\Software\\Microsoft\\AppV\\MAV**.
-
-4. Perform integration tasks.
-
- 1. Integrate extensions points (EP) from the Manifest and Dynamic Configuration files.
-
- 2. File based EP data is stored in the AppData folder utilizing Junction Points from the package store.
-
- 3. Version 1 EPs already exist when a new version becomes available.
-
- 4. The extension points are switched to the Version 2 location in machine or user catalogs for any newer or updated extension points.
-
-5. Run scripts targeted for publishing timing.
-
-6. Install Side-by-Side assemblies as required.
-
-### Upgrading an in-use App-V package
-
-If you try to upgrade a package that is currently in use, the upgrade task is placed in a pending state. The upgrade will run later, according to the following rules:
-
-| Task type | Applicable rule |
-|---|---|
-| User-based tasks, such as publishing a package to a user | The pending task will be performed after the user signs out and then signs back in. |
-| Globally based tasks, such as enabling a connection group globally | The pending task will be performed when the computer is shut down and then restarted. |
-
-When a task is placed in a pending state, the App-V Client also generates a registry key for the pending task, as follows:
-
-| User-based or globally based task | Where the registry key is generated |
-|---|---|
-| User-based tasks | HKEY\_CURRENT\_USER\Software\Microsoft\AppV\Client\PendingTasks |
-| Globally based tasks | HKEY\_LOCAL\_MACHINE\Software\Microsoft\AppV\Client\PendingTasks |
-
-The following operations must be completed before users can use the newer version of the package:
-
-| Task | Details |
-|---|---|
-| Add the package to the computer | This task is computer-specific and you can perform it at any time by completing the steps in [How to add an App-V package](#how-to-add-an-app-v-package). |
-| Publish the package | See the Package Publishing section above for steps. This process requires that you update extension points on the system. You can't complete this task while the application is in use. |
-
-Use the following example scenarios as a guide for updating packages.
-
-| Scenario | Requirements |
-|---|---|
-| App-V package isn't in use when you try to upgrade | None of the following components of the package can be in use: virtual application, COM server, or shell extensions.
The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and ran. |
-| App-V package is in use when the administrator publishes a newer version of the package | The App-V Client sets the operation to "pending," which means that it's queued and will be carried out later when the package isn't in use.
If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur.
If the package has shell extensions, which are permanently loaded by Windows Explorer, the user won't be able to sign in. Users must sign off and then sign back in to initiate the App-V package upgrade.|
-
-### Global vs. user publishing
-
-App-V Packages can be published in one of two ways; as user, which entitles an App-V package to a specific user or group of users, or as global, which entitles the App-V package to the entire machine for all users of the machine. Once a package upgrade has been pended and the App-V package isn't in use, consider the two types of publishing:
-
-- Global publishing is when the application is published to a machine; all users on that machine can use it. The upgrade will happen when the App-V Client Service starts, which effectively means a machine restart.
-- User publishing is when the application is published to a user. If there are multiple users on the machine, the application can be published to a subset of the users. The upgrade will happen when the user signs in or when it's published again (periodically, ConfigMgr Policy refresh and evaluation, or an App-V periodic publishing/refresh, or explicitly through Windows PowerShell commands).
-
-### Removing an App-V package
-
-Removing App-V applications in a Full Infrastructure is an unpublish operation and doesn't perform a package removal. The process is the same as the publish process above, but instead of adding the removal process reverses the changes that have been made for App-V Packages.
-
-### Repairing an App-V package
-
-The repair operation is easy to do but may affect many locations on the machine. The previously mentioned Copy on Write (COW) locations are removed, and extension points are deintegrated and then reintegrated. Before repairing, please review where the COW data placement locations are registered in the registry. To perform a Repair operation, all you need to do is initiate it from the App-V Client Console or through the **Repair-AppVClientPackage** PowerShell cmdlet. After that, the operation is completed automatically.
-
-## Integration of App-V packages
-
-The App-V Client and package architecture provides specific integration with the local operating system during the addition and publishing of packages. Three files define the integration or extension points for an App-V Package:
-
-- AppXManifest.xml is stored inside of the package with fallback copies stored in the package store and the user profile. Contains the options created during the sequencing process.
-- DeploymentConfig.xml provides configuration information of computer- and user-based integration extension points.
-- UserConfig.xml is a subset of the Deploymentconfig.xml file that only provides user-based configurations and only targets user-based extension points.
-
-### Rules of integration
-
-When App-V applications are published to a computer with the App-V Client, some specific actions take place as described in the following list:
-
-- Global Publishing: Shortcuts are stored in the All Users profile location and other extension points are stored in the registry in the HKLM hive.
-- User Publishing: Shortcuts are stored in the current user account profile and other extension points are stored in the registry in the HKCU hive.
-- Backup and Restore: Existing native application data and registry (such as FTA registrations) are backed up during publishing.
-
- 1. App-V packages are given ownership based on the last integrated package where the ownership is passed to the newest published App-V application.
- 2. Ownership transfers from one App-V package to another when the owning App-V package is unpublished. This transfer won't initiate a restore of the data or registry.
- 3. Restore the backed-up data when the last package is unpublished or removed on a per-extension point basis.
-
-### Extension points
-
-The App-V publishing files (manifest and dynamic configuration) provide several extension points to integrate the application with the local operating system. These extension points perform typical application installation tasks, such as placing shortcuts, creating file type associations, and registering components. As these are virtualized applications that aren't installed in the same manner a traditional application, there are some differences. The following is a list of extension points covered in this section:
-
-- Shortcuts
-- File type associations
-- Shell extensions
-- COM
-- Software clients
-- Application capabilities
-- URL Protocol handler
-- AppPath
-- Virtual application
-
-### Shortcuts
-
-The shortcut is one of the basic elements of integration with the OS and is the interface for direct user launch of an App-V application. During the publishing and unpublishing of App-V applications.
-
-From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section as shown in the following example:
-
-```XML
-
-
- [{Common Desktop}]\Adobe Reader.lnk
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\SC_Reader.ico
-
-
- 1
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
-
-
-```
-
-As mentioned previously, the App-V shortcuts are placed by default in the user’s profile based on the refresh operation. Global refresh places shortcuts in the All Users profile and user refresh stores them in the specific user’s profile. The actual executable is stored in the Package Store. The location of the ICO file is a tokenized location in the App-V package.
-
-### File type associations
-
-Users can use file type invocations or open a file with a registered extension (.docx) to start an App-V application because the App-V Client manages the local operating system File Type Associations during publishing. File type associations are present in the manifest and dynamic configuration files, as shown in the following example:
-
-```XML
-
-
-
- .xdp
- AcroExch.XDPDoc
- application/vnd.adobe.xdp+xml
-
-
- AcroExch.XDPDoc
- Adobe Acrobat XML Data Package File
- 65536
- [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\XDPFile_8.ico
-
- Read
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Open
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"
-
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Printto
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" /t "%1" "%2" "%3" "%4"
-
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Read
- Open with Adobe Reader
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"
-
-
-
-
-
-```
-
->[!NOTE]
->In this example:
->- `.xdp` is the extension
->- `AcroExch.XDPDoc` is the ProgId value (which points to the adjoining ProgId)
->- `"[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"` is the command line, which points to the application executable
-
-### Shell extensions
-
-Shell extensions are embedded in the package automatically during the sequencing process. When the package is published globally, the shell extension gives users the same functionality as if the application were locally installed. The application requires no extra setup or configuration on the client to enable the shell extension functionality.
-
-#### Requirements for using shell extensions
-
-- Packages that contain embedded shell extensions must be published globally.
-- The “bitness” of the application, Sequencer, and App-V Client must match, or the shell extensions won’t work. The following example configuration fulfills the matching requirement:
- - The version of the application is 64-bit.
- - The Sequencer is running on a 64-bit computer.
- - The package is being delivered to a 64-bit App-V Client computer.
-
-The following table displays the supported shell extensions.
-
-| Handler | Description |
-|---|---|
-| Context menu handler | Adds menu items to the context menu. it's called before the context menu is displayed. |
-| Drag-and-drop handler | Controls the action upon right-click drag-and-drop and modifies the context menu that appears. |
-| Drop target handler | Controls the action after a data object is dragged-and-dropped over a drop target, such as a file.|
-| Data object handler| Controls the action after a file is copied to the clipboard or dragged-and-dropped over a drop target. It can provide more clipboard formats to the drop target.|
-| Property sheet handler| Replaces or adds pages to the property sheet dialog box of an object.|
-| Infotip handler| Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse-hover.|
-| Column handler| Allows creating and displaying custom columns in Windows Explorer *Details view*. It can be used to extend sorting and grouping.|
-| Preview handler| Enables a preview of a file to be displayed in the Windows Explorer Preview Pane.|
-
-### COM
-
-The App-V Client supports publishing applications with support for COM integration and virtualization. COM integration allows the App-V Client to register COM objects on the local operating system and virtualization of the objects. For the purposes of this document, the integration of COM objects requires more details.
-
-App-V supports registering COM objects from the package to the local operating system with two process types: Out-of-process and In-process. Registering COM objects is accomplished with one or a combination of multiple modes of operation for a specific App-V package that includes Off, Isolated, and Integrated. Integrated mode is configured for either the Out-of-process or In-process type. Configuration of COM modes and types is accomplished with dynamic configuration files (deploymentconfig.xml or userconfig.xml).
-
-For details on App-V integration, see [Microsoft Application Virtualization 5.0 Integration](/archive/blogs/appv/microsoft-application-virtualization-5-0-integration).
-
-### Software clients and application capabilities
-
-App-V supports specific software clients and application capabilities extension points to register virtualized applications with the operating system's software client. This specific support means users can select default programs for operations like email, instant messaging, and using the media player. This operation is performed in the control panel with **Set Program Access** and **Computer Defaults**, and is configured during sequencing in the manifest or dynamic configuration files. Application capabilities are only supported when the App-V applications are published globally.
-
-The following example illustrates a software client registration of an App-V-based mail client.
-
-```XML
-
-
-
-
-
-
- Mozilla Thunderbird
- Mozilla Thunderbird
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0
-
-
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /SetAsDefaultAppGlobal
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /HideShortcuts
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /ShowShortcuts
-
- 1
-
-
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe
- "[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -mail
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll
-
- Thunderbird URL
- 2
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe
- "[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -osint -compose "%1"
-
-
-
-
-
-
-
-```
-
->[!NOTE]
->In this example:
->- `` is the overall Software Clients setting to integrate Email clients.
->- `` is the flag to set a particular Email client as the default Email client.
->- `[{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll` is the MAPI dll registration.
-
-### URL Protocol handler
-
-Virtual applications don't always specifically utilize file type invocation. For, example, in an application that supports embedding a mailto: link inside a document or web page, the user selects the link expecting to access their registered mail client. App-V supports URL Protocol handlers that can be registered on a per-package basis with the local operating system. During sequencing, the URL Protocol handlers are automatically added to the package.
-
-For situations where there's more than one application that could register the specific URL Protocol handler, the dynamic configuration files can be utilized to modify the behavior and suppress or disable this feature for an application that shouldn't be the primary application launched.
-
-### AppPath
-
-The AppPath extension point supports calling App-V applications directly from the operating system. Administrators can provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable from either the Run or Start Screen, depending on the operating system. It therefore avoids modifying the system path environment variable on all systems, as it's accomplished during publishing.
-
-The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For more information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](/archive/blogs/virtualworld/app-paths-a-virtual-application-extension-in-app-v-5-0).
-
-### Virtual application
-
-This subsystem provides a list of applications captured during sequencing which is consumed by other App-V components. Integration of extension points belonging to a specific application can be disabled using dynamic configuration files. For example, if a package contains two applications, you can disable all extension points belonging to one application to only allow integration of extension points for the other application.
-
-### Extension point rules
-
-The previously described extension points are integrated into the operating system based on how the packages have been published. Global publishing places extension points in public machine locations, where user publishing places extension points in user locations. For example, a shortcut created on the desktop and published globally will result in the file data for the shortcut (%Public%\\Desktop) and the registry data (HKLM\\Software\\Classes). The same shortcut would have file data (%UserProfile%\\Desktop) and registry data (HKCU\\Software\\Classes).
-
-Extension points aren't all published the same way, where some extension points will require global publishing and others require sequencing on the specific operating system and architecture where they're delivered. Below is a table that describes these two key rules.
-
-|Virtual Extension|Requires target OS sequencing|Requires global publishing|
-|---|:---:|:---:|
-|Shortcut|||
-|File Type Association|||
-|URL Protocols|X||
-|AppPaths|X||
-|COM Mode|||
-|Software Client|X||
-|Application Capabilities|X|X|
-|Context Menu Handler|X|X|
-|Drag-and-drop Handler|X||
-|Data Object Handler|X||
-|Property Sheet Handler|X||
-|Infotip Handler|X||
-|Column Handler|X||
-|Shell Extensions|X||
-|Browser Helper Object|X|X|
-|Active X Object|X|X|
-
-## Dynamic configuration processing
-
-Deploying App-V packages to a single machine or user is simple. However, as organizations deploy App-V applications across business lines and geographic and political boundaries, it becomes impossible to sequence all applications with the same settings. App-V was designed to overcome this problem by capturing specific settings and configurations during sequencing in the Manifest file while also supporting modification with Dynamic Configuration files.
-
-App-V dynamic configuration lets you specify a package policy at either the machine or user levels. Sequencing engineers can use Dynamic Configuration files to modify the configuration of a package post-sequencing to address the needs of individual groups of users or machines. In some instances, it may be necessary to modify the application to provide proper functionality within the App-V environment. For example, you may need to modify the \_\*config.xml files to allow certain actions to be performed at a specified time while executing the application, like disabling a mailto extension to prevent a virtualized application from overwriting that extension from another application.
-
-App-V packages contain the Manifest file inside of the App-V Package file, which is representative of sequencing operations and is the policy of choice unless Dynamic Configuration files are assigned to a specific package. Post-sequencing, the Dynamic Configuration files can be modified to allow an application to be published to different desktops or users with different extension points. The two Dynamic Configuration files are the Dynamic Deployment Configuration (DDC) and Dynamic User Configuration (DUC) files. This section focuses on the combination of the manifest and dynamic configuration files.
-
-### Examples of dynamic configuration files
-
-The following example shows the combination of the Manifest, Deployment Configuration, and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is to show the combination of the files only, not to be a complete description of the specific categories available in each file. For more information, download the [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760).
-
-#### Manifest
-
-```XML
-
-
- [{Common Programs}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM exe.O.ico
-
-
-```
-
-#### Deployment Configuration
-
-```XML
-
-
-
-
-
-
-
-
-
-
-```
-
-#### User Configuration
-
-```XML
-
-
-
-
- [{Desktop}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM exe.O.ico
-
-
-
-
-
-
-
- [{Desktop}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM.exe.O.ico
-
-
- [{Common Programs}]\7-Zip\7-Zip File Manager.Ink
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot)]\7zFM.exe.O.ico
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-## Side-by-side assemblies
-
-App-V supports automatic packaging of side-by-side assemblies during sequencing and deployment on the client during virtual application publishing. App-V also supports capturing side-by-side assemblies during sequencing for assemblies not present on the sequencing machine. For assemblies consisting of Visual C++ (Version 8 and newer) or MSXML run-time, the Sequencer will automatically detect and capture these dependencies even if they weren't installed during monitoring.
-
-The side-by-side assemblies feature removes the limitations of previous versions of App-V, where the App-V Sequencer didn't capture assemblies already present on the sequencing workstation, and privatized the assemblies, which limited it to a bit version per package. This behavior resulted in App-V applications being deployed to clients missing the required side-by-side assemblies, which led to application launch failures. This failure forced the packaging process to document and ensure that all assemblies required for packages were locally installed on the user’s client operating system. This task was both a management and implementation challenge due to the number of assemblies and the lack of application documentation for the required dependencies.
-
-Side-by-side assembly support in App-V has the following features:
-
-- Automatic captures of side-by-side assembly during sequencing, regardless of whether the assembly was already installed on the sequencing workstation.
-- The App-V Client automatically installs required side-by-side assemblies to the client computer at publishing time if they aren't already installed.
-- The Sequencer reports the VC run-time dependency in Sequencer reporting mechanism.
-- The Sequencer allows opting to not package assemblies already installed on the Sequencer, supporting scenarios where the assemblies have previously been installed on the target computers.
-
-### Automatic publishing of side-by-side assemblies
-
-During publishing of an App-V package with side-by-side assemblies, the App-V Client will check for the presence of the assembly on the machine. If it doesn't detect an assembly, the client will deploy the assembly to the machine. Packages that are part of connection groups will rely on the side-by-side assembly installations in the base packages, as the connection groups don't contain any information about assembly installation.
-
->[!NOTE]
->Unpublishing or removing a package with an assembly doesn't remove the assemblies for that package.
-
-## Client logging
-
-The App-V Client logs information to the Windows Event log in standard ETW format. The specific App-V events can be found in the event viewer under **Applications and Services Logs\\Microsoft\\AppV\\Client**.
-
-There're three specific categories of events recorded:
-
-- **Admin** logs events for configurations applied to the App-V Client and also contains the primary warnings and errors.
-- **Operational** logs the general App-V execution and usage of individual components, creating an audit log of the App-V Client's completed App-V operations.
-- **Virtual Application** logs virtual application launches and use of virtualization subsystems.
diff --git a/windows/application-management/app-v/appv-apply-the-deployment-configuration-file-with-powershell.md b/windows/application-management/app-v/appv-apply-the-deployment-configuration-file-with-powershell.md
deleted file mode 100644
index 310cac63128..00000000000
--- a/windows/application-management/app-v/appv-apply-the-deployment-configuration-file-with-powershell.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Apply deployment config file via Windows PowerShell (Windows 10/11)
-description: How to apply the deployment configuration file by using Windows PowerShell for Windows 10/11.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/15/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to apply the deployment configuration file by using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-When you add or set a package to a computer running the App-V client before it's been published, a dynamic deployment configuration file is applied to it. The dynamic deployment configuration file configures the default settings for the package that all users share on the computer running the App-V client. This section will tell you how to use a deployment configuration file.
-
-## Apply the deployment configuration file with Windows PowerShell
-
-> [!NOTE]
-> The following example cmdlet uses the following two file paths for the package and configuration files:
->
-> * C:\\Packages\\Contoso\\MyApp.appv
-> * C:\\Packages\\Contoso\\DynamicConfigurations\\deploymentconfig.xml
->
-> If your package and configuration files use different file paths than the example, feel free to replace them as needed.
-
-To specify a new default set of configurations for all users who will run the package on a specific computer, in a Windows PowerShell console, enter the following cmdlet:
-
-```PowerShell
-Add-AppVClientPackage -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
-```
-
->[!NOTE]
->This command captures the resulting object into $pkg. If the package is already present on the computer, you can use the **Set-AppVclientPackage** cmdlet to apply the deployment configuration document:
->
-> ```PowerShell
-> Set-AppVClientPackage -Name Myapp -Path C:\Packages\Contoso\MyApp.appv -DynamicDeploymentConfiguration C:\Packages\Contoso\DynamicConfigurations\deploymentconfig.xml
-> ```
-
-
-
-
-
-## Related articles
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-apply-the-user-configuration-file-with-powershell.md b/windows/application-management/app-v/appv-apply-the-user-configuration-file-with-powershell.md
deleted file mode 100644
index cb64552879e..00000000000
--- a/windows/application-management/app-v/appv-apply-the-user-configuration-file-with-powershell.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to apply the user configuration file by using Windows PowerShell (Windows 10/11)
-description: How to apply the user configuration file by using Windows PowerShell (Windows 10/11).
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/15/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to apply the user configuration file by using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-When you publish a package to a specific user, you'll also need to specify a dynamic user configuration file to tell that package how to run.
-
-## Apply a user configuration file
-
-Here's how to specify a user-specific configuration file:
-
-> [!NOTE]
-> The following example cmdlets use this example file path for its package:
->
-> * C:\\Packages\\Contoso\\MyApp.appv.
->
-> If your package file uses a different file path than the example, feel free to replace it as needed.
-
-1. Enter the following cmdlet in Windows PowerShell to add the package to the computer:
-
- ```PowerShell
- Add-AppVClientPackage C:\Packages\Contoso\MyApp.appv
- ```
-2. Enter the following cmdlet to publish the package to the user and specify the updated the dynamic user configuration file:
-
- ```PowerShell
- Publish-AppVClientPackage $pkg -DynamicUserConfigurationPath C:\Packages\Contoso\config.xml
- ```
-
-
-
-
-
-## Related articles
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-auto-batch-sequencing.md b/windows/application-management/app-v/appv-auto-batch-sequencing.md
deleted file mode 100644
index 415ade7895a..00000000000
--- a/windows/application-management/app-v/appv-auto-batch-sequencing.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
-description: How to automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package.
-
-Starting with Windows 10 version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This automatic customization load is applicable to all of the sequencing scenarios:
-
-- Using the **New-BatchAppVSequencerPackages** cmdlet
-- Using the App-V Sequencer interface
-- Using the **New-AppVSequencerPackage** cmdlet
-
->[!NOTE]
->If you're trying to update multiple apps at the same time, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
-
-### Sequence multiple apps with a PowerShell cmdlet
-
-Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations.
-
-#### Create your ConfigFile for use by the PowerShell cmdlet
-
-1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad.
-
-2. Add the following required XML info for each app:
-
- - ``````. The name of the app you're adding to the package.
- - ``````. The file path to the folder with the app installer.
- - ``````. The file name for the app executable. This file will typically be an .exe or .msi file.
- - ``````. The command-line options required for the app installation.
- - ``````. The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
- - ``````. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based sequencing, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
- - ``````. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
-
- **Example:**
-
- ```XML
-
-
-
- Skype for Windows
- D:\Install\New\SkypeforWindows
- SkypeSetup.exe
- /S
- 20
- True
- True
-
-
- Power BI
- D:\Install\New\MicrosoftPowerBI
- PBIDesktop.msi
- /S
- 20
- True
- True
-
-
-
- ```
-3. Save your completed file, using the name **ConfigFile**.
-
-#### Start the App-V Sequencer interface and app installation process
-
-Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing:
-
-```PowerShell
-New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath
-```
-
-Where `````` is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and `````` is the full path to where the sequenced packages should be copied.
-
-The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After the sequencing and package creation for the first app on the VM is completed, the package is copied from the VM to the Host computer, specified in the *OutputPath* parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
-
-### Review the log files
-
-There are three types of log files that occur when you sequence multiple apps at the same time:
-
-- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the sequencing activities for each app, such as "Copying installer to VM," "Scheduling sequencing task," and so on. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
-- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
-- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters.
-
-### Related articles
-
-- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
-- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
-- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
-- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
-- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
-- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
-- [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
diff --git a/windows/application-management/app-v/appv-auto-batch-updating.md b/windows/application-management/app-v/appv-auto-batch-updating.md
deleted file mode 100644
index 4b2246bee42..00000000000
--- a/windows/application-management/app-v/appv-auto-batch-updating.md
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
-description: How to automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Updating multiple apps at the same time follows a similar process to the one used for [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However, when updating, you'll also have to pass your previously created app package files to the App-V Sequencer cmdlet.
-
-Starting with Windows 10 version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
-
->[!NOTE]
->If you're trying to sequence multiple apps at the same time, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
-
-## Update multiple apps with a PowerShell cmdlet
-
-Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations.
-
-### Create your ConfigFile for use by the PowerShell cmdlet
-
-1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad.
-
-2. Add the following XML info for each app:
-
- - ``````. The name of the app you're adding to the package.
- - ``````. The file path to the folder with the app installer.
- - ``````. The file name for the app executable. This file will typically be an .exe or .msi file.
- - ``````. The command-line options required for the app installation.
- - ``````. The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
- - ``````. The maximum amount of time, in minutes, that the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
- - ``````. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
- - ``````. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
-
- **Example:**
- ```XML
-
-
-
- Skype for Windows Update
- D:\Install\Update\SkypeforWindows
- SkypeSetup.exe
- /S
- C:\App-V_Package\Microsoft_Apps\skypeupdate.appv
- 20
- true
- true
-
-
- Microsoft Power BI Update
- D:\Install\Update\PowerBI
- PBIDesktop.msi
- /S
- C:\App-V_Package\MS_Apps\powerbiupdate.appv
- 20
- true
- true
-
-
- ```
-
-3. Save your completed file under the name **ConfigFile**.
-
-### Start the App-V Sequencer interface and app installation process
-
-- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating:
-
- ```PowerShell
- New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath
- ```
- Where `````` is the name of the virtual machine (VM) with the App-V Sequencer installed that you'll run the batch updating on, and `````` is the full path to where the updated packages should be copied.
-
- The cmdlet creates a "clean" checkpoint on the VM. After the checkpoint is created, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM. This copy-operation opens a new session of the VM (through VMConnect), allowing app updates to begin from the command-line. After the update and package creation for the first app on the VM is completed, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
-
-## Update multiple apps with the App-V Sequencer interface
-
-Updating multiple apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM.
-
-### Create your ConfigFile for use by the App-V Sequencer interface
-
-1. Determine the apps that need to be updated and then open a text editor, such as Notepad.
-
-2. Add the following XML info for each app:
-
- - ``````. The name of the app you're adding to the package.
- - ``````. The file path to the folder with the app installer.
- - ``````. The file name for the app executable. This file will typically be an .exe or .msi file.
- - ``````. The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
- - ``````. The maximum amount of time, in minutes, the cmdlet should wait for updating to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
- - ``````. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to use cmdlet-based updating, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
- - ``````. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
-
- **Example:**
-
- ```XML
-
-
-
- Skype for Windows Update
- D:\Install\Update\SkypeforWindows
- SkypeSetup.exe
- /S
- C:\App-V_Package\Microsoft_Apps\skypeupdate.appv
- 20
- false
- true
-
-
- Microsoft Power BI Update
- D:\Install\Update\PowerBI
- PBIDesktop.msi
- /S
- C:\App-V_Package\MS_Apps\powerbiupdate.appv
- 20
- false
- true
-
-
- ```
-
-### Start the App-V Sequencer interface and app installation process
-
-- Open PowerShell as an admin on the Host computer and run the following commands to start the batch updating:
-
- ```PowerShell
- New-BatchAppVSequencerPackages –ConfigFile –VMName -OutputPath
- ```
- Where `````` is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and `````` is the full path to where the updated packages should be copied.
-
- This cmdlet creates a "clean" checkpoint on the VM. After the checkpoint is created, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM. This opens a new session of the VM (through VMConnect) and app updating begins from the command-line. After the updating and package creation for the first app on the VM is completed, the package is copied from the VM to the Host computer specified in the *OutputPath* parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted to a "clean" checkpoint and turned off.
-
-### Review the log files
-
-There are three types of log files that occur when you sequence multiple apps at the same time:
-
-- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about updating activities for each app, such as "Copying installer to VM," "Scheduling updating task," and so on. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
-- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
-- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the **NewAppVSequencerPackage** cmdlet, including the allowed parameters.
-
-### Related articles
-
-- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
-- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
-- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
-- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
-- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
-- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
-- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
diff --git a/windows/application-management/app-v/appv-auto-clean-unpublished-packages.md b/windows/application-management/app-v/appv-auto-clean-unpublished-packages.md
deleted file mode 100644
index d56ea57fc80..00000000000
--- a/windows/application-management/app-v/appv-auto-clean-unpublished-packages.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Auto-remove unpublished packages on App-V client (Windows 10/11)
-description: How to automatically clean up any unpublished packages on your App-V client devices.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/15/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Automatically clean up unpublished packages on the App-V client
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-If you wanted to free up additional storage space in previous versions of App-V, you would have had to manually remove your unpublished packages from your client devices. Starting with Windows 10 version 1703, use PowerShell or Group Policy settings to automatically clean up your unpublished packages after restarting your device.
-
-## Clean up with PowerShell cmdlets
-
-You can enter PowerShell cmdlets to turn on the **AutoCleanupEnabled** setting, which will automatically clean up your unpublished App-V packages from your App-V client devices.
-
-### Turn on the AutoCleanupEnabled option
-
-1. Open PowerShell as an admin and enter the following cmdlet to turn on the automatic package cleanup functionality:
-
- ```PowerShell
- Set-AppvClientConfiguration -AutoCleanupEnabled 1
- ```
-
- After running the cmdlet, you should see the following info on the PowerShell screen:
-
- |Name|Value|SetbyGroupPolicy|
- |---|---|---|
- |AutoCleanupEnabled|1|False|
-
-1. Run the following cmdlet to check if the configuration has the cleanup setting turned on.
-
- ```PowerShell
- Get-AppvClientConfiguration
- ```
- If the **AutoCleanupEnabled** option shows a value of **1** in the configuration list, that means the setting is turned on.
-
-## Clean up with Group Policy settings
-
-Using Group Policy, you can turn on the **Enable automatic cleanup of unused App-V packages** setting to automatically clean up your unpublished App-V packages from your App-V client devices.
-
-### Turn on the Enable automatic cleanup of unused App-V packages setting
-
-1. Open your Group Policy editor and select the **Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused App-V packages** setting.
-
-2. Select **Enabled**, then select **OK**.
-
- After your Group Policy updates and you reset the client, the setting will clean up any unpublished App-V packages on the App-V client.
-
-
-
-
-
-## Related articles
-
-- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
-- [Deploying App-V for Windows client](appv-deploying-appv.md)
-- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
diff --git a/windows/application-management/app-v/appv-auto-provision-a-vm.md b/windows/application-management/app-v/appv-auto-provision-a-vm.md
deleted file mode 100644
index 50e6dd4a877..00000000000
--- a/windows/application-management/app-v/appv-auto-provision-a-vm.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
-description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Starting with Windows 10 version 1703, the `New-AppVSequencerVM` and `Connect-AppvSequencerVM` Windows PowerShell cmdlets are available, which automatically create your sequencing environment for you, including provisioning your virtual machine.
-
-## Automatic VM provisioning of the sequencing environment
-
-You have two options for provisioning a VM for auto-sequencing:
-
-1. Using a Virtual Hard Disk (VHD)
-2. Updating an existing VM
-
-You can only choose one option.
-
->[!NOTE]
->We have reduced the number of environmental checks performed by the App-V Sequencer, narrowing down the list of apps that need to be disabled or turned off for a clean sequencing experience. We've also suppressed antivirus and other similar app warnings.
-
-### Provision a new VM with a VHD file
-
-Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer.
-
-#### Create a VHD file
-
-For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://www.powershellgallery.com/packages/Convert-WindowsImage/10.0) command-line tool.
-
-#### Create a VHD file with the Convert-WindowsImage command-line tool
-
-1. Open PowerShell as an admin and run the **Convert-WindowsImage** tool, using the following commands:
-
- ```ps1
- Convert-WindowsImage -SourcePath "" -VHDFormat "VHD" -VHDPartitionStyle "MBR"
- ```
- Where `````` is the full path to your ISO image.
-
->[!IMPORTANT]
->You must specify the *VHDPartitionStyle* as **MBR**. If you use the default value, **GPT**, will cause a boot failure in your VHD image.
-
-#### Provision your VM with your VHD file
-
-After you have a VHD file, you must provision your VM for auto-sequencing.
-
-1. On the Host device, install the Windows client and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
-2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server).
-3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters:
-
- ```PowerShell
- New-AppVSequencerVM -VMName "" -ADKPath "" -VHDPath "" -VMMemory "" -VMSwitch ""
- ```
-
- This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start.
-
-### Provision an existing VM for auto-sequencing
-
-If your apps require custom prerequisites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM.
-
-#### Connect to your existing VM
-
-- Open PowerShell as an admin and run the following commands on your existing VM:
-
- - **Set the network category of your connection profile on the VM to _Private_:**
-
- ```PowerShell
- Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private
- ```
-
- - **Enable firewall rules for _Remote Desktop_ and _Windows Remote Management_:**
-
- ```PowerShell
- Enable-NetFirewallRule -DisplayGroup “Remote Desktop”
- Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”
- ```
-
- - **Set the VM to receive remote commands without a confirmation prompt:**
-
- ```PowerShell
- Enable-PSRemoting –Force
- ```
-
-#### Provision an existing VM
-
-1. On the Host device, install the Windows client and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
-
-2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters:
-
- ```ps1
- Connect-AppvSequencerVM -VMName ""
- ```
-
- Where `````` is the name of the VM as shown in the Hyper-V Manager tool.
-
-This command connects to an existing Hyper-V VM using the provided VM name for auto-sequencing.
-
-### Review the provisioning log files
-
-The two types of provisioning log files, located at %temp%\AutoSequencer\Logs, are:
-
-- **New-AppVSequencerVM-.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on.
-- **Connect-AppvSequencerVM-report-.txt**. Includes info about the connections made to the VM, showing whether there were any failures.
-
-### Next steps
-
-After provisioning your sequencing environment, you must sequence your apps, either as a group or individually. For more info about sequencing your apps, see the following articles
-
-- [Manually sequence a single new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
-- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
-- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
-
-After you sequence your packages, you can automatically clean up any unpublished packages on the App-V client. To learn more, see [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md).
-
-### Related articles
-
-- [Download the **Convert-WindowsImage** tool](https://www.powershellgallery.com/packages/Convert-WindowsImage/10.0)
-- [Download the Windows ADK](/windows-hardware/get-started/adk-install)
-- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
-- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
diff --git a/windows/application-management/app-v/appv-available-mdm-settings.md b/windows/application-management/app-v/appv-available-mdm-settings.md
deleted file mode 100644
index 32afb3de6ba..00000000000
--- a/windows/application-management/app-v/appv-available-mdm-settings.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Available Mobile Device Management (MDM) settings for App-V (Windows 10/11)
-description: Learn the available Mobile Device Management (MDM) settings you can use to configure App-V on Windows 10.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/15/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Available Mobile Device Management (MDM) settings for App-V
-
-Starting with Windows 10 version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](/windows/client-management/mdm/enterpriseappvmanagement-csp) page.
-
-|Policy name|Supported versions|URI full path|Data type|Values|
-|---|---|---|---|---|
-|Name|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //Name|String|Read-only data, provided by your App-V packages.|
-|Version|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //Version|String|Read-only data, provided by your App-V packages.|
-|Publisher|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //Publisher|String|Read-only data, provided by your App-V packages.|
-|InstallLocation|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //InstallLocation|String|Read-only data, provided by your App-V packages.|
-|InstallDate|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //InstallDate|String|Read-only data, provided by your App-V packages.|
-|Users|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //Users|String|Read-only data, provided by your App-V packages.|
-|AppVPackageID|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //AppVPackageID|String|Read-only data, provided by your App-V packages.|
-|AppVVersionID|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //AppVVersionID|String|Read-only data, provided by your App-V packages.|
-|AppVPackageUri|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPackageManagement// //AppVPackageUri|String|Read-only data, provided by your App-V packages.|
-|LastError|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/LastError|String|Read-only data, provided by your App-V packages.|
-|LastErrorDescription|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/LastErrorDescription|String|- **0**: No errors returned during publish. - **1**: Unpublish groups failed during publish. - **2**: Publish no-group packages failed during publish. - **3**: Publish group packages failed during publish. - **4**: Unpublish packages failed during publish. - **5**: New policy write failed during publish. - **6**: Multiple non-fatal errors occurred during publish.|
-|SyncStatusDescription|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncStatusDescription|String|- **0**: App-V publishing is idle. - **1**: App-V connection groups publish in progress. - **2**: App-V packages (non-connection group) publish in progress. - **3**: App-V packages (connection group) publish in progress. - **4**: App-V packages unpublish in progress.|
-|SyncProgress|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncProgress|String|- **0**: App-V Sync is idle. - **1**: App-V Sync is initializing. - **2**: App-V Sync is in progress. - **3**: App-V Sync is complete. - **4**: App-V Sync requires device reboot.|
-|PublishXML|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
-|Policy|Windows 10/11|./Vendor/MSFT/EnterpriseAppVManagement/ AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
diff --git a/windows/application-management/app-v/appv-capacity-planning.md b/windows/application-management/app-v/appv-capacity-planning.md
deleted file mode 100644
index 5d052067c57..00000000000
--- a/windows/application-management/app-v/appv-capacity-planning.md
+++ /dev/null
@@ -1,198 +0,0 @@
----
-title: App-V Capacity Planning (Windows 10/11)
-description: Use these recommendations as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# App-V Capacity Planning
-
->Applies to: Windows Server 2016
-
-The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
-
->[!IMPORTANT]
->Use the information in this section only as a general guide for planning your App-V deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
-
-## Determine the project scope
-
-Before you design the App-V infrastructure, determining which applications will be available virtually, and also identify the target users and their locations. This information will determine what type of App-V infrastructure your project should implement. You should base your decisions about your project's scope on your organization's specific needs.
-
-|Task|More information|
-|----|----------------|
-|Determine application scope|The App-V infrastructure can be set up in different ways depending on which applications you want to virtualize. This customization in set up means your first task is to define which applications you want to virtualize.|
-|Determine location scope|"Location scope" refers to the physical locations where you plan to run the virtualized applications (for example, enterprise-wide or a specific geographic location). It can also refer to the user population that will run the virtual applications (for example, a single department). You should obtain a network map that includes the connection paths, the available bandwidth for each location, the number of users using virtualized applications, and the WAN link speed.|
-
-## Determine which App-V infrastructure is required
-
-You can also manage your App-V environment using an electronic software distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information, see [How to deploy App-V packages using electronic software distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
-
-* **Standalone model**—The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V in Standalone mode only needs the sequencer and the client; no extra components are required. Applications are prepared for virtualization using a process called sequencing. For more information, see [Planning for the App-V Sequencer and Client deployment](appv-planning-for-sequencer-and-client-deployment.md). The standalone model is recommended for the following scenarios:
-
- * When there are disconnected remote users who can't connect to the App-V infrastructure.
- * When you're running a software management system, such as Configuration Manager.
- * When network bandwidth limitations inhibit electronic software distribution.
-* **Full infrastructure model**—The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V full infrastructure model consists of one or more App-V management servers that can be used to publish applications to all clients. Publishing places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about how to install the management server, see [Planning for App-V Server deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
-
- * When you want to use the Management Server to publish the application to target computers.
- * For rapid provisioning of applications to target computers.
- * When you want to use App-V reporting.
-
->[!IMPORTANT]
->The App-V full infrastructure model requires Microsoft SQL Server to store configuration data. For more information, see [App-V supported configurations](appv-supported-configurations.md).
-
-## End-to-end server sizing guidance
-
-The following section describes end-to-end App-V sizing and planning. For more specific information, refer to the subsequent sections.
-
->[!NOTE]
->Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
-
-* 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time (<3 seconds).
-* A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time (<5 seconds).
-
-## App-V Management Server capacity planning recommendations
-
-The App-V publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V management server supported configurations, see [App-V supported configurations](appv-supported-configurations.md).
-
->[!NOTE]
->The default refresh time on the App-V publishing server is ten minutes.
-
-When multiple simultaneous publishing servers contact a single management server for package metadata refreshes, the following three factors will influence the publishing server's round-trip response time:
-
-1. The number of publishing servers making simultaneous requests.
-2. The number of connection groups configured on the management server.
-3. The number of access groups configured on the management server.
-
-The following table describes each factor that impacts round-trip time in more detail.
-
->[!NOTE]
->Round trip response time is the time taken by the computer running the App-V publishing server to receive a successful package metadata update from the management server.
-
-|Factors impacting round-trip response time|Description|
-|------------------------------------------|-----------|
-|The number of publishing servers simultaneously requesting package metadata refreshes.|A single management server can respond to up to 320 publishing servers simultaneously requesting publishing metadata. For example, in a case with 30 publishing servers simultaneously requesting publishing metadata, the round-trip response time is about 40 seconds, while for less than 50 servers it's less than 5 seconds. From 50 to 320 publishing servers, response team increases linearly (approximately 2×).|
-|The number of connection groups configured on the management server.|For up to 100 connection groups, there's no significant change in the round-trip response time on the publishing server. For 100–400 connection groups, there's a minor linear increase in the round-trip response time.|
-|The number of access groups configured on the management server.|For up to 40 access groups, there's a linear (approximately 3×) increase in the round-trip response time on the publishing server.|
-
-The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V management server.
-
-|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization|
-|---|---|---|---|---|---|---|---|
-|Publishing servers contact management server for publishing metadata at same time|Number of publishing servers.|0 0 0 0 0 0|1 1 1 1 1 1|50 100 200 300 315 320|LAN|5 10 19 32 30 37|17 17 17 15 17 15|
-|Publishing metadata contains connection groups|Number of connection groups|10 20 100 150 300 400|1 1 1 1 1 1|100 100 100 100 100 100|LAN|10 11 11 16 22 25|17 19 22 19 20 20|
-|Publishing metadata contains access groups|Number of access groups|0 0 0 0|1 10 20 40|100 100 100 100|LAN|10 43 153 535|17 26 24 24|
-
-The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example, transactions/sec is approximately 30, batch requests approximately 200, and user connects approximately six.
-
-Through a geographically distributed deployment, where the management server and publishing servers utilize a slow link network between them, the round-trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
-
-|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization (in %)|
-|---|---|---|---|---|---|---|---|
-|Network connection between the publishing server and management server|1.5 Mbps Slow link Network|0 0|1 1|50 100|1.5 Mbps Cable DSL|4 5|1 2|
-|Network connection between the publishing server and management server|LAN/WiFi Network|0 0|1 1|100 200|WiFi|11 20|15 17|
-
-Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
-
-## App-V Reporting Server capacity planning recommendations
-
-App-V clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V client. For more information about the App-V Reporting Server's supported configurations, see [App-V supported configurations](appv-supported-configurations.md).
-
->[!NOTE]
->Round-trip response time is the time taken by the computer running the App-V client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
-
-|Scenario|Summary|
-|---|---|
-|Multiple App-V clients send reporting information to the reporting server simultaneously.|Round-trip response time from the reporting server is 2.6 seconds for 500 clients. Round-trip response time from the reporting server is 5.65 seconds for 1000 clients. Round-trip response time increases linearly depending on number of clients.|
-|Requests per second processed by the reporting server.|A single reporting server and a single database can process a maximum of 139 requests per second. The average is 121 requests/second. With the help of two reporting servers that report to the same Microsoft SQL Server database, the average requests/second, like a single reporting server, is about 127, with a max of 278 requests/second. A single reporting server can process 500 concurrent/active connections. A single reporting server can process a maximum 1,500 concurrent connections.|
-|Reporting database.|Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second. Throughput and response time are independent of database size.|
-
-### Calculating random delay
-
-The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
-
-*Random delay = 4 × number of clients/average requests per second*.
-
-Example: Random delay for 500 clients with 120 requests per second is *4 × 500/120 = about 17 minutes*.
-
-## App-V publishing server capacity planning recommendations
-
-Computers running the App-V client connect to the App-V publishing server to send a publishing refresh request and receive a response. Round trip response time is measured on the computer running the App-V client, while processor time is measured on the publishing server. For more information about App-V Publishing Server supported configurations, see [App-V supported configurations](appv-supported-configurations.md).
-
-> [!IMPORTANT]
-> The following list displays the main factors to consider when setting up the App-V publishing server:
-> * The number of clients connecting simultaneously to a single publishing server.
-> * The number of packages in each refresh.
-> * The available network bandwidth in your environment between the client and the App-V publishing server.
-
-|Scenario|Summary|
-|---|---|
-|Multiple App-V clients connect to a single publishing server simultaneously.|A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously. For 5,000–10,000 clients, the publishing server requires a minimum quad core. For 10,000–20,000 clients, the publishing server should have dual quad cores for more efficient response times. A publishing server with a quad core can refresh up to 10,000 packages within three seconds. (Supports 10,000 simultaneous clients.)|
-|Number of packages in each refresh.|Increasing number of packages will increase response time by about 40% (up to 1,000 packages).|
-|Network between the App-V client and the publishing server.|Across a slow network (1.5-Mbps bandwidth), there's a 97% increase in response time compared to LAN (up to 1,000 users).|
-
->[!NOTE]
->The publishing server CPU usage is always high during the time interval when it must process simultaneous requests (>90% in most cases). The publishing server can handle about 1,500 client requests in one second.
-
-|Scenario|Variation|Number of App-V clients|Number of packages|Processor configuration on publishing server|Network connection type|App-V client round-trip time (in seconds)|Publishing server CPU utilization (in %)|
-|---|---|---|---|---|---|---|---|
-|App-V client sends publishing refresh request and receives response, each request containing 120 packages|Number of clients|100 1,000 5,000 10,000|120 120 120 120|Dual Core Dual Core Quad Core Quad Core|LAN|1 2 2 3|100 99 89 77|
-|Multiple packages in each refresh.|Number of packages|1,000 1,000|500 1,000|Quad Core|LAN|2 3|92 91|
-|Network between client and publishing server.|1.5 Mbps Slow link network|100 500 1,000|120 120 120|Quad Core|1.5-Mbps intra-continental network|3 10 (0.2% failure rate) 7 (1% failure rate)||
-
-## App-V streaming capacity planning recommendations
-
-Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package.
-
-> [!IMPORTANT]
-> The following list identifies the main factors to consider when setting up the App-V streaming server:
-> * The number of clients streaming application packages simultaneously from a single streaming server.
-> * The size of the package being streamed.
-> * The available network bandwidth in your environment between the client and the streaming server.
-
-|Scenario|Summary|
-|---|---|
-|Multiple App-V clients stream applications from a single streaming server simultaneously.|If the number of clients simultaneously streaming from the same server increases, there's a linear relationship with the package download/streaming time.|
-|Size of the package being streamed.|The package size has a significant impact on the streaming/download time only for larger packages with a size of about 1 GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.|
-|Network between the App-V client and the streaming server.|Across a slow network (1.5-Mbps bandwidth), there's a 70–80% increase in response time compared to LAN (up to 100 users).|
-
-The following table displays sample values for each of the factors in the previous list:
-
-|Scenario|Variation|Number of App-V clients|Size of each package|Network connection type|Round-trip time on the App-V client (in seconds)|
-|---|---|---|---|---|---|
-|Multiple App-V clients streaming virtual application packages from a streaming server.|Number of clients.|100 200 1,000 100 200 1,000|3.5 MB 3.5 MB 3.5 MB 5 MB 5 MB 5 MB|LAN|29 39 391 35 68 461|
-|Size of each package being streamed.|Size of each package.|100 200 100 200|21 MB 21 MB 109 MB 109 MB|LAN|33 83 100 160|
-|Network connection between client and App-V streaming server.|1.5 Mbps Slow link network.|100 100|3.5 MB 5 MB|1.5-Mbps intra-continental network|102 121|
-
-Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
-
->[!NOTE]
->The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions.
-
-For example, an average user can stream a 100-MB package in less than 2 minutes, when 100 simultaneous clients are streaming from the server. However, a package of size 1 GB could take up to 30 minutes. In most real-world environments, streaming demand isn't uniformly distributed, you'll need to understand the approximate peak streaming requirements present in your environment to properly size the number of required streaming servers.
-
-The number of clients a streaming server can support can be increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
-
-## Combining App-V server roles
-
-Discounting scaling and fault-tolerance requirements, the minimum number of servers that a location with Active Directory connectivity needs to function is 1. This server will host the management server, management server service, and Microsoft SQL Server roles. This coverage means that you can arrange server roles in any combination you like, as they don't conflict with one another.
-
-Notwithstanding scaling requirements, the minimum number of servers that a fault-tolerant implementation needs to function is four. The management server and Microsoft SQL Server roles support placement in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
-
-Although there are many fault-tolerance strategies and technologies you can use, not all are applicable to a given service. Additionally, if App-V roles are combined, the resulting incompatibilities could cause certain fault-tolerance options to stop working.
-
-
-
-
-
-## Related articles
-
-* [App-V supported configurations](appv-supported-configurations.md)
-* [Planning for high availability with App-V](appv-planning-for-high-availability-with-appv.md)
-* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
diff --git a/windows/application-management/app-v/appv-client-configuration-settings.md b/windows/application-management/app-v/appv-client-configuration-settings.md
deleted file mode 100644
index c7b029ac7a4..00000000000
--- a/windows/application-management/app-v/appv-client-configuration-settings.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: About Client Configuration Settings (Windows 10/11)
-description: Learn about the App-V client configuration settings and how to use Windows PowerShell to modify the client configuration settings.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# About Client Configuration Settings
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. Understanding how the register's format for data works can help you better understand the client, as you can configure many client actions by changing registry entries. This topic lists the App-V client configuration settings and explains their uses. You can use Windows PowerShell to modify the client configuration settings. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).
-
-You can use Group Policy to configure App-V client settings by navigating to the **Group Policy management console** at **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
-
-## App-V Client Configuration Settings: Windows PowerShell
-
-The following table provides information about App-V client configuration settings that can be configured through Windows PowerShell cmdlets:
-
-
-| Windows PowerShell cmdlet or cmdlets, **Option** Type | Description | Disabled policy state keys and values |
-|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-PackageInstallationRoot** String | Specifies directory where all new applications and updates will be installed. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-PackageSourceRoot** String | Overrides source location for downloading package content. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-AllowHighCostLaunch** True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows client machines connected by a metered network connection (for example, 4G). | 0 |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReestablishmentRetries** Integer (0–99) | Specifies the number of times to retry a dropped session. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReestablishmentInterval** Integer (0–3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-LocationProvider** String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-CertFilterForClientSsl** String | Specifies the path to a valid certificate in the certificate store. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-VerifyCertificateRevocationList** True (enabled); False (Disabled state) | Verifies Server certificate revocation status before streaming with HTTPS. | 0 |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-SharedContentStoreMode** True (enabled); False (Disabled state) | Specifies that streamed package contents will not be saved to the local hard disk. | 0 |
-| Set-AppvPublishingServer
**-Name** String | Displays the name of publishing server. | Policy value not written (same as Not Configured) |
-| Set-AppvPublishingServer
**-URL** String | Displays the URL of publishing server. | Policy value not written (same as Not Configured) |
-| Set-AppvPublishingServer
**-UserRefreshOnLogon** True (enabled); False (Disabled state) | Triggers a user publishing refresh on sign in. (Boolean) Word count (with spaces): 60 | False |
-| Set-AppvPublishingServer
**-UserRefreshInterval** Word count (with spaces): 85 Integer (0–744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | 0 |
-| Set-AppvPublishingServer
**-UserRefreshIntervalUnit** 0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-MigrationMode** True (enabled state); False (Disabled state) | Migration mode allows the App-V client to modify shortcuts and FTAs for packages created by a previous version of App-V. | |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-EnablePackageScripts** True (enabled); False (Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | |
-| Set-AppvClientConfiguration
**-RoamingFileExclusions** String | Specifies the file paths relative to %userprofile% that don't roam with a user's profile. For example, ```/ROAMINGFILEEXCLUSIONS='desktop;my pictures'``` | |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-RoamingRegistryExclusions** String | Specifies the registry paths that don't roam with a user profile. For example, ```/ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients``` | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-IntegrationRootUser** String | Specifies the location to create symbolic links associated with the current version of a per-user published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links won't be used when you publish the package. For example, ```%localappdata%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-IntegrationRootGlobal** String | Specifies the location to create symbolic links associated with the current version of a globally published package. All virtual application extensions, such as shortcuts and file type associations, will point to this path. If you don't specify a path, symbolic links won't be used when you publish the package. For example, ```%allusersprofile%\\Microsoft\\AppV\\Client\\Integration```. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-VirtualizableExtensions** String | A comma-delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command-line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a locally installed application inside a virtual environment with virtualized applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Policy value not written |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingEnabled** True (enabled); False (Disabled state) | Returns information to a reporting server. | False |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingServerURL** String | Specifies the location on the reporting server where client information is saved. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingDataCacheLimit** Integer \[0–1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingDataBlockSize** Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This limit can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingStartTime** Integer (0–23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0–23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22. **Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingInterval** Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ReportingRandomDelay** Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This method can help to prevent collisions on the server. | Policy value not written (same as Not Configured) |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
-EnableDynamicVirtualization 1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-EnablePublishingRefreshUI** 1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | |
-| Sync-AppvPublishingServer
**-HidePublishingRefreshUI** 1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | |
-| Set-AppvClientConfiguration, Set-AppvPublishingServer
**-ProcessesUsingVirtualComponents** String | Specifies a list of process paths (that may contain wildcards) that are candidates for using dynamic virtualization (such as supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Empty string. |
-
-## App-V client configuration settings: registry keys
-
-The following table provides information about App-V client configuration settings that can be configured through the registry:
-
-
-| **Setting name** Type | Registry key value | Disabled policy state keys and values |
-|--------------------------------------------------------------------------------|-------------------------------------------------------------------------|---------------------------------------------------|
-| **PackageInstallationRoot** String | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
-| **PackageSourceRoot** String | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
-| **AllowHighCostLaunch** True (Enabled); False (Disabled state) | Streaming\\AllowHighCostLaunch | 0 |
-| **ReestablishmentRetries** Integer (0–99) | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
-| **ReestablishmentInterval** Integer (0–3600) | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
-| **LocationProvider** String | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
-| **CertFilterForClientSsl** String | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
-| **VerifyCertificateRevocationList** True (Enabled); False (Disabled state) | Streaming\\VerifyCertificateRevocationList | 0 |
-| **SharedContentStoreMode** True (Enabled); False (Disabled state) | Streaming\\SharedContentStoreMode | 0 |
-| **Name** String | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
-| **URL** String | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
-| **GlobalRefreshEnabled** True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalEnabled | False |
-| **GlobalRefreshOnLogon** True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
-| **GlobalRefreshInterval** Integer (0–744) | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
-| **GlobalRefreshIntervalUnit** 0 for hour, 1 for day | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
-| **UserRefreshEnabled** True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserEnabled | False |
-| **UserRefreshOnLogon** True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
-| **UserRefreshInterval** Word count (with spaces): 85; Integer (0–744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
-| **UserRefreshIntervalUnit** 0 for hour, 1 for day | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
-| **MigrationMode** True(Enabled state); False (Disabled state) | Coexistence\\MigrationMode | |
-| **EnablePackageScripts** True (Enabled); False (Disabled state) | \\Scripting\\EnablePackageScripts | |
-| **RoamingFileExclusions** String | | |
-| **RoamingRegistryExclusions** String | Integration\\RoamingRegistryExclusions | Policy value not written (same as Not Configured) |
-| **IntegrationRootUser** String | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
-| **IntegrationRootGlobal** String | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
-| **VirtualizableExtensions** String | Integration\\VirtualizableExtensions | Policy value not written |
-| **ReportingEnabled** True (Enabled); False (Disabled state) | Reporting\\EnableReporting | False |
-| **ReportingServerURL** String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
-| **ReportingDataCacheLimit** Integer \[0–1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
-| **ReportingDataBlockSize** Integer \[1024–Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
-| **ReportingStartTime** Integer (0–23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
-| **ReportingInterval** Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
-| **ReportingRandomDelay** Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
-| EnableDynamicVirtualization 1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
-| **EnablePublishingRefreshUI** 1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
-| **HidePublishingRefreshUI** 1 (Enabled), 0 (Disabled) | | |
-| **ProcessesUsingVirtualComponents** String | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
-
-## Related topics
-
-* [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
diff --git a/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md b/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md
deleted file mode 100644
index 23f43e8cb3a..00000000000
--- a/windows/application-management/app-v/appv-configure-access-to-packages-with-the-management-console.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: How to configure access to packages by using the Management Console (Windows 10/11)
-description: How to configure access to packages by using the App-V Management Console.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to configure access to packages by using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
-
-Use the following procedure to configure access to virtualized packages.
-
-## Grant access to an App-V package
-
-1. Find the package you want to configure:
-
- 1. Open the App-V Management console.
-
- 1. Right-click the package to be configured, then select **Edit active directory access** to display the **AD Access** page. Alternatively, select the package and select **Edit** in the **AD Access** pane.
-
-2. Provision a security group for the package:
-
- 1. Go to the **Find valid Active Directory names and grant access** page.
-
- 1. Using the format **mydomain** \\ **groupname**, enter the name or part of the name of an Active Directory group object, then select **Check**.
-
- > [!NOTE]
- > Ensure that you provide an associated domain name for the group that you are searching for.
-
-3. Grant access to the package by first selecting the desired group, then selecting **Grant Access**. The newly added group is displayed in the **AD entities with access** pane.
-
-4. Select **Close** to accept the default configuration settings and close the AD Access page.
-
- To customize configurations for a specific group, select the **Assigned configurations** drop-down menu, then select **Custom**. To make changes to your custom configurations, select **Edit**. After you grant access, select **Close**.
-
-## Remove access to an App-V package
-
-1. Find the package you want to configure:
-
- 1. Open the App-V Management console.
-
- 1. To display the **AD Access** page, right-click the package to be configured, then select **Edit active directory access**. Alternatively, select the package, then select **Edit** in the **AD Access** pane.
-
-2. Select the group you want to remove, then select **Delete**.
-
-3. Select **Close**.
-
-
-
-
-
-## Related articles
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-configure-connection-groups-to-ignore-the-package-version.md b/windows/application-management/app-v/appv-configure-connection-groups-to-ignore-the-package-version.md
deleted file mode 100644
index 9524c2d4474..00000000000
--- a/windows/application-management/app-v/appv-configure-connection-groups-to-ignore-the-package-version.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: How to make a connection group ignore the package version (Windows 10/11)
-description: Learn how to make a connection group ignore the package version with the App-V Server Management Console.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to make a connection group ignore the package version
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can use Application Virtualization (App-V) to configure a connection group to use any version of a package, simplifying package upgrades and reducing the number of connection groups you need to create.
-
-You can also configure a connection group to accept any version of a package, so that you can upgrade the package without having to disable the connection group.
-
-- If the connection group has access to multiple versions of a package, App-V will use the latest version.
-
-- If the connection group contains an optional package with an incorrect version, App-V ignores the package and won't block the connection group's virtual environment from being created.
-
-- If the connection group contains a non-optional package that has an incorrect version, App-V won't be able to create the connection group's virtual environment.
-
-## Make a connection group ignore the package version with the App-V Server Management Console
-
-1. In the Management Console, select **Connection Groups**.
-
-2. Select the correct connection group from the Connection Groups library.
-
-3. Select **Edit** in the Connected Packages pane.
-
-4. Select the **Use Any Version** check box next to the package name, then select **Apply**.
-
-For more about adding or upgrading packages, see [How to add or upgrade packages by using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md).
-
-## Make a connection group ignore the package version from the App-V client on a stand-alone computer
-
-1. Create the connection group XML document.
-
-2. Set the **Package** tag attribute **VersionID** to an asterisk (*) to upgrade the package.
-
-3. Enter the following cmdlet (including the path to the connection group XML document) to add the connection group:
-
- ```PowerShell
- Add-AppvClientConnectionGroup
- ```
-
- For more information about how to use the **Add-AppvClientConnectionGroup** cmdlet, see [**Add-AppvClientConnectionGroup**](/powershell/module/appvclient/add-appvclientconnectiongroup).
-
-4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:
-
- - [**Remove-AppvClientPackage**](/powershell/module/appvclient/remove-appvclientpackage)
- - [**Add-AppvClientPackage**](/powershell/module/appvclient/add-appvclientpackage)
- - [**Publish-AppvClientPackage**](/powershell/module/appvclient/publish-appvclientpackage)
-
-For more information, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).
-
-
-
-
-
-## Related articles
-
-- [Managing connection groups](appv-managing-connection-groups.md)
diff --git a/windows/application-management/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md b/windows/application-management/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
deleted file mode 100644
index c8e45c8af10..00000000000
--- a/windows/application-management/app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: How to configure the client to receive package and connection groups updates from the publishing server (Windows 10/11)
-description: How to configure the client to receive package and connection groups updates from the publishing server.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/25/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to configure the client to receive package and connection groups updates from the publishing server
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-The App-V publishing server's single-point management and high scalability lets you deploy packages and connection groups and keep them up to date.
-
-This article will tell you how to configure the App-V client to receive updates from the publishing server.
-
->[!NOTE]
->The following example has the management server installed on a computer named **MyMgmtSrv**, and the publishing server installed on a computer named **MyPubSrv**. If the computers you'll be configuring the App-V client on have different names, you should replace the example's names with your computer's names.
-
-## Configure the App-V client to receive updates from the publishing server
-
-1. Deploy the App-V management and publishing servers, and add the required packages and connection groups. For more information about adding packages and connection groups, see [How to add or upgrade packages by using the Management Console](appv-add-or-upgrade-packages-with-the-management-console.md) and [How to create a connection group](appv-create-a-connection-group.md).
-2. To open the management console, open a web browser and enter the following URL: `https://MyMgmtSrv/AppvManagement/Console.html`. Import, publish, and entitle all packages and connection groups that your users will need.
-3. On the computer running the App-V client, open an elevated Windows PowerShell command prompt, and run the following command:
-
- ```PowerShell
- Add-AppvPublishingServer -Name ABC -URL https://MyPubSrv/AppvPublishing
- ```
-
- This command will configure the specified publishing server. You should see output similar to the following:
-
- ```PowerShell
- Id : 1
- SetByGroupPolicy : False
- Name : ABC
- URL : https://MyPubSrv/AppvPublishing
- GlobalRefreshEnabled : False
- GlobalRefreshOnLogon : False
- GlobalRefreshInterval : 0
- GlobalRefreshIntervalUnit : Day
- UserRefreshEnabled : True
- UserRefreshOnLogon : True
- UserRefreshInterval : 0
- UserRefreshIntervalUnit : Day
- ```
-
-4. On the computer running the App-V client, open a Windows PowerShell command prompt and enter the following cmdlet:
-
- ```PowerShell
- Sync-AppvPublishingServer -ServerId 1
- ```
-
- This cmdlet will query the publishing server for which packages and connection groups need to be added or removed for this particular client based on your configured entitlements for the packages and connection groups on the management server.
-
-
-
-
-
-## Related article
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-connect-to-the-management-console.md b/windows/application-management/app-v/appv-connect-to-the-management-console.md
deleted file mode 100644
index 50ed9fd433b..00000000000
--- a/windows/application-management/app-v/appv-connect-to-the-management-console.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: How to connect to the Management Console (Windows 10/11)
-description: In this article, learn the procedure for connecting to the App-V Management Console through your web browser.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/25/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to connect to the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to connect to the App-V Management Console.
-
-## Connect to the App-V Management Console
-
-1. Open your web browser and enter the address for the App-V Management server. For example, **https://\<_management server name_\>:\<_management service port number_\>/console.html**.
-
-2. To view different sections of the console, select your desired section in the navigation pane.
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-connection-group-file.md b/windows/application-management/app-v/appv-connection-group-file.md
deleted file mode 100644
index bfad2cc36f6..00000000000
--- a/windows/application-management/app-v/appv-connection-group-file.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: About the connection group file (Windows 10/11)
-description: A summary of what the connection group file is and how to configure it.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/25/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# About the connection group file
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-## Connection group file overview
-
-### What is a connection group?
-
-A connection group is an App-V feature that can group packages together to create a virtual environment where applications within that package group can interact with each other.
-
-For example, let's say you want to use plug-ins with Microsoft Office. You can create one package that contains the plug-ins and another package that contains Office, and then add both packages to the same connection group to enable Office to use those plug-ins.
-
-### How a connection group file works
-
-When you apply an App-V connection group file, all packages specified in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) connection group file to configure existing App-V connection groups.
-
-An example file path for a package file would be %APPDATA%\Microsoft\AppV\Client\Catalog\PackageGroups\{6CCC7575-162E-4152-9407-ED411DA138F4}\{4D1E16E1-8EF8-41ED-92D5-8910A8527F96}.
-
-## Structure of the connection group XML file
-
-This section will tell you more about the components of the connection group XML file.
-
-### Parameters that define the connection group
-
-The following table describes the parameters in the XML file that define the connection group itself, not the packages.
-
-|Field|Description|
-|-----|-----------|
-|Schema name|Name of the schema.If you want to use the “optional packages” and “use any version” features described in this table, you must specify the following schema in the XML file:`xmlns="https://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"`|
-|AppConnectionGroupId|Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.You can create a new GUID by entering **[Guid]::NewGuid()**.|
-|VersionId|Version GUID identifier for this version of the connection group.When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.|
-|DisplayName|Display name of the connection group.|
-|Priority|Optional priority field for the connection group.A value of **0** indicates the highest priority.If a priority is required but has not been configured, the package will fail because it can't determine the correct connection group to use.|
-
-### 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.
-
-|Field|Description|
-|---|---|
-|PackageId|Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.|
-|VersionId|Unique GUID identifier for the version of the package. If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted.|
-|IsOptional|Parameter that enables you to make a package optional within the connection group. Valid entries are:- “**true**”—package is optional in the connection group- “**false**”—package is required in the connection group|
-
-### App-V example connection group XML file
-
-The following example connection group XML file shows examples of the fields listed in the previous tables.
-
-```XML
-
-
-
-
-
-
-```
-
-## Configuring the priority of packages in a connection group
-
-Package precedence is configured using the package list order. The first package in the document has the highest precedence. Subsequent packages in the list have descending priority.
-
-Package precedence is the resolution for otherwise inevitable resource collisions during virtual environment initialization. For example, if two packages that are opening in the same virtual environment define the same registry DWORD value, the package with the highest precedence determines the value that is set.
-
-You can use the connection group file to configure each connection group by using the following methods:
-
-- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, select the connection group and then select **Edit**.
-
- > [!NOTE]
- >A package only requires priority if it's associated with more than one connection group.
-- Specify package precedence within the connection group.
-
-The priority field is required when a running virtual application initiates from a native application request, such as Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
-
-If a virtual application is opened using another virtual application, the client will use the original virtual application's virtual environment. The priority field is not used in this case.
-
-The following is an example of priority configuration:
-
-The virtual application Microsoft Outlook is running in virtual environment **XYZ**. When you open an attached Microsoft Word document, a virtualized version Microsoft Word opens in the virtual environment **XYZ**, regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.
-
-## Supported virtual application connection configurations
-
-App-V supports the following application connection configurations.
-
-- **An .exe file and plug-in (.dll)**. For example, you might want to distribute Microsoft Office to all users, but only distribute a Microsoft Excel plug-in to a small subset of those users.
-
- Enable the connection group for the appropriate users. Update each package individually as required.
-
-- **An .exe file and a middleware application**. This is for cases where you have an application that requires a middleware application, or several applications that all depend on the same middleware runtime version.
-
- All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime. You can optionally combine multiple middleware applications into a single connection group.
-
- |Example|Example description|
- |---|---|
- |Virtual application connection group for the financial division|- Middleware application 1- Middleware application 2- Middleware application 3- Middleware application runtime|
- |Virtual application connection group for HR division|- Middleware application 5- Middleware application 6- Middleware application runtime|
-
-- **An. exe file and an .exe file**. This is for cases where you have an application that relies on another application, but you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.
-
- For example, if you are deploying Microsoft Lync 2010, you can use three packages:
-
- - Microsoft Office 2010
- - Microsoft Communicator 2007
- - Microsoft Lync 2010
-
- You can manage the deployment with the following connection groups:
-
- - Microsoft Office 2010 and Microsoft Communicator 2007
- - Microsoft Office 2010 and Microsoft Lync 2010
-
- After deployment, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package or keep and maintain them as separate packages and deploy them with a connection group.
-
-
-
-
-
-## Related articles
-
-- [Managing connection groups](appv-managing-connection-groups.md)
diff --git a/windows/application-management/app-v/appv-connection-group-virtual-environment.md b/windows/application-management/app-v/appv-connection-group-virtual-environment.md
deleted file mode 100644
index d84704a33ff..00000000000
--- a/windows/application-management/app-v/appv-connection-group-virtual-environment.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: About the connection group virtual environment (Windows 10/11)
-description: Learn how the connection group virtual environment works and how package priority is determined.
-author: aczechowski
-ms.service: windows-client
-ms.date: 06/25/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# About the connection group virtual environment
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-## How package priority is determined
-
-The virtual environment and its current state are associated with the connection group, not with the individual packages. If you remove an App-V package from the connection group, the state that existed as part of the connection group won't migrate with the package.
-
-If the same package is a part of two different connection groups, you have to indicate which connection group App-V should use. For example, you might have two packages in a connection group wherein each defines the same registry DWORD value.
-
-The connection group that is used is based on the order in which a package appears inside the **AppConnectionGroup** XML document:
-
-- The first package has the highest precedence.
-- The second package has the second highest precedence.
-
-Consider the following example section:
-
-```XML
-
-
-
-
-
-```
-
-Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package.
-
-For this example, the DWORD value definition would be as shown below:
-
-- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
-- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
-
-Since Package 1 appears first, the AppConnectionGroup's virtual environment will have the single DWORD value of 5 (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5). This result means that the virtual applications in Package 1, Package 2, and Package 3 will all see the value 5 when they query for HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region.
-
-Other virtual environment resources are resolved in a similar way, but usually collisions occur in the registry.
-
-## Merging identical package paths into one virtual directory in connection groups
-
-If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group's virtual environment. Merging these paths allows an application in one package to access files that are in a different package.
-
-When you remove a package from a connection group, the removed package's applications can no longer access files from packages in the connection group it was removed from.
-
-App-V looks up a file’s name in the connection group in the order App-V packages are listed in the connection group manifest file.
-
-The following example shows the order and relationship of a file name lookup in a connection group for **Package A** and **Package B**.
-
-|Package A|Package B|
-|---|---|
-|C:\Windows\System32|C:\Windows\System32|
-|C:\AppTest|C:\AppTest|
-
-When a virtualized application tries to find a specific file, App-V will search for a matching file path in Package A. If it doesn't find a matching path in Package A, it will then search Package B using the following mapping rules:
-
-- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, App-V will use the first matching file.
-- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, App-V will use the first matching file.
-
-
-
-
-
-## Related articles
-
-- [Managing Connection Groups](appv-managing-connection-groups.md)
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
deleted file mode 100644
index e12fd39cb00..00000000000
--- a/windows/application-management/app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: How to convert a package created in a previous version of App-V (Windows 10/11)
-description: Use the package converter utility to convert a virtual application package created in a previous version of App-V.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to convert a package created in a previous version of App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-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.
-
-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.
-
-## 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/11, the App-V for Windows client 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.)
-
-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 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).
-
-2. You can enter the following cmdlets to check or convert packages:
-
- - **Test-AppvLegacyPackage**—This cmdlet checks packages. It will return information about any failures with the package such as missing **.sft** files, an invalid source, **.osd** file errors, or invalid package version. This cmdlet won't 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**—This cmdlet converts packages from legacy versions to updated versions. To convert an existing package, enter the following cmdlet:
-
- ```PowerShell
- ConvertFrom-AppvLegacyPackage C:\contentStore C:\convertedPackages
- ```
-
- 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 client virtual application package file will be saved. By default, if you don't specify a new name, the old package name will be used.
-
- Additionally, the package converter optimizes performance of packages in App-V for Windows client by setting the package to stream fault the App-V package. This definition of setting 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 enter cmdlets like this example:
-
- ```PowerShell
- dir C:\contentStore\myPackage | Test-AppvLegacyPackage
- ```
-
- 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 that 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 feature 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.
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
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
deleted file mode 100644
index e602397d30f..00000000000
--- a/windows/application-management/app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: How to create a connection croup with user-published and globally published packages (Windows 10/11)
-description: How to create a connection croup with user-published and globally published packages.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to create a connection croup with user-published and globally published packages
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-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)
-
-## 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.
-- 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 globally published package that's listed as non-optional in a user-published connection group that also appears in other packages, running **Unpublish-AppvClientPackage <package> -global** cmdlet can unpublish the package from every connection group containing that package. Tracking connection groups can help you avoid unintentionally unpublishing non-optional packages.
-
-## How to use Windows PowerShell cmdlets to create user-entitled connection groups
-
-1. Add and publish packages by using the following commands:
-
- ```PowerShell
- Add-AppvClientPackage
- Add-AppvClientPackage
- Publish-AppvClientPackage -PackageId -VersionId -Global
- 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).
-
-3. Add and publish the connection group by using the following commands:
-
- ```PowerShell
- Add-AppvClientConnectionGroup
- Enable-AppvClientConnectionGroup -GroupId -VersionId
- ```
-
-## How to use the App-V Server to create user-entitled connection groups
-
-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.
-
-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.
-
-
-
-
-
-## Related articles
-
-- [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
deleted file mode 100644
index a78ae6f6cde..00000000000
--- a/windows/application-management/app-v/appv-create-a-connection-group.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: How to create a connection group (Windows 10/11)
-description: Learn how to create a connection group with the App-V Management Console and where to find information about managing connection groups.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to create a connection group
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-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).
-
-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.
-
-## Create a connection group
-
-1. In the App-V Management Console, select **CONNECTION GROUPS** to display the Connection Groups library.
-
-2. Select **ADD CONNECTION GROUP** to create a new connection group.
-
-3. In the **New Connection Group** pane, enter a description for the group.
-
-4. Select **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, then select the arrow to add the application.
-
- 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.
-
-6. After adding all the applications and configuring Active Directory access, select **Apply**.
-
-
-
-
-
-## Related articles
-
-- [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
deleted file mode 100644
index ead8b2f6624..00000000000
--- a/windows/application-management/app-v/appv-create-a-custom-configuration-file-with-the-management-console.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: How to create a custom configuration file by using the App-V Management Console (Windows 10/11)
-description: How to create a custom configuration file by using the App-V Management Console.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to create a custom configuration file by using the App-V Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.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.
-
-## Create a dynamic user configuration file
-
-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 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 file name and select **Save**. Now you can edit the file to configure a package for a user.
-
- > [!NOTE]
- > If you want to export a configuration while running on Windows Server, make sure to disable the IE Enhanced Security Configuration setting. If this setting is enalbed and set to block downloads, you won't be able to download anything from the App-V Server.
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
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
deleted file mode 100644
index cbe79ac2df5..00000000000
--- a/windows/application-management/app-v/appv-create-a-package-accelerator-with-powershell.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: How to create a package accelerator by using Windows PowerShell (Windows 10/11)
-description: Learn how to create an App-v Package Accelerator by using Windows PowerShell. App-V Package Accelerators automatically sequence large, complex applications.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to create a package accelerator by using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-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
-
-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. Ensure there's the App-V 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.
-
- 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 App-V package.
- - *Path* specifies the output directory for the package.
-
- The following example cmdlet shows how you can create a package accelerator with the App-V package and the installation media:
-
- ```PowerShell
- New-AppvPackageAccelerator -InputPackagePath -Installer -Path
- ```
-
- 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.
-
-
-
-
-
-## Related articles
-
-- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
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
deleted file mode 100644
index e1500e38076..00000000000
--- a/windows/application-management/app-v/appv-create-a-package-accelerator.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: How to create a package accelerator (Windows 10/11)
-description: Learn how to create App-V Package Accelerators to automatically generate new virtual application packages.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to create a package accelerator
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-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).
-
-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:
-> - 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
-
-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, select **Tools** > **Create Accelerator**.
-
-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.
-
- Select **Next**.
-
-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, 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 by the **Installation Files** page. If the files displayed aren't 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. 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 more 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've confirmed the information displayed, 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.
-
-11. On the **Completion** page, select **Close**.
-
- >[!IMPORTANT]
- >You should always digitally sign the package accelerator to ensure that it is secure and can be verified by a publisher during application.
-
-
-
-
-
-## Related articles
-
-- [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)
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
deleted file mode 100644
index 2ee8100f3ea..00000000000
--- a/windows/application-management/app-v/appv-create-a-virtual-application-package-package-accelerator.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: How to create a virtual application package using an App-V Package Accelerator (Windows 10/11)
-description: How to create a virtual application package using an App-V Package Accelerator.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to create a virtual application package using an App-V Package Accelerator
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-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.
-
-## Create a virtual application package with an App-V Package Accelerator
-
-1. Make sure you've copied the required package accelerator locally to the computer running the App-V Sequencer. Also make sure to copy all required installation files for the package to a local folder on the computer running 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 Sequencer, go to **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
-
-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, 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 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, select **Export** and specify the location where the file should be saved, and then select **Next**.
-
-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, select **Make New Folder**, browse to the folder that contains the installation files, then select **Next**.
-
- > [!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 you to install an application before you apply the package accelerator and you have already installed the required application, select **I have installed all applications**, 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 you choose will identify 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 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 the package size exceeds 4 GB.
-
-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 contained within the package, select **Configure Software**. **Configure Software** will let you configure any associated tasks required to run the application on the target computers. For example, you can configure any associated license agreements.
-
- The following items can be configured using the Sequencer as part of this step:
-
- - **Load Package** loads files associated with the package. It can take several seconds to an hour to decode the package.
- - **Run Each Program** optionally runs programs contained within the package. This step can help you complete associated license or configuration tasks that must be completed before deploying and running 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, then close the applications. It can take several minutes for all programs to run. Select **Next**.
- - **Save Package** saves the package.
- - **Primary Feature Block** optimizes the package for streaming by rebuilding the primary feature block.
-
- If you don't want to configure the applications, select **Skip this step**, then select **Next**.
-
-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, 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).
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-create-and-use-a-project-template.md b/windows/application-management/app-v/appv-create-and-use-a-project-template.md
deleted file mode 100644
index a37682809cf..00000000000
--- a/windows/application-management/app-v/appv-create-and-use-a-project-template.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Create and apply an App-V project template to a sequenced App-V package (Windows 10/11)
-description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Create and apply an App-V project template to a sequenced App-V package
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can use an App-V Project Template (.appvt) file to save commonly applied settings associated with an existing virtual application package. You can then apply these settings whenever you create new virtual application packages in your environment, streamlining the package creation process. App-V Project Templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V Project Templates can be applied to multiple applications. To learn more about package accelerators, see [How to create a package accelerator](appv-create-a-package-accelerator.md).
-
->[!IMPORTANT]
->Starting with Windows 10 version 1703, running the **New-AppvSequencerPackage** or the **Update-AppvSequencerPackage** cmdlets will automatically capture and store your customizations as an App-V Project Template. If you want to make changes to this package later, you can automatically load your customizations from this template file. If you have an auto-saved template and you attempt to load another template through the *TemplateFilePath* parameter, the customization value from the parameter will override the auto-saved template.
-
-## Create a project template
-
-You must first create and save a project template, including a virtual app package with settings to be used by the template.
-
-1. On the device running the App-V Sequencer, select **Start**, select **All Programs**, select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
-
- > [!NOTE]
- >If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure.
-
-2. On the **File** menu, select **Open**, select **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V Project Template, and then select **Edit** to change any of the settings or info included in the file.
-
-3. On the **File** menu, select **Save As Template**, review the settings associated with the new template, select **OK**, name your new template, and then select **Save**.
-
- The new App-V Project Template is saved in the folder you specified.
-
-## Apply a project template
-
-After creating the template, you can apply it to all of your new virtual app packages, automatically including all of the settings.
-
->[!IMPORTANT]
->Virtual app packages don't support using both a project template and a package accelerator at the same time.
-
-1. On the device running the App-V Sequencer, select **Start** > **All Programs** > **Microsoft Application Virtualization** > **Microsoft Application Virtualization Sequencer**.
-
-2. On the **File** menu, select **New From Template**, browse to your newly created project template and select **Open**.
-
-3. Create your new virtual app package. The settings saved with your template are automatically applied.
-
-### Related articles
-
-- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
-- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
-- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
-- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
-- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
-- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
diff --git a/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md b/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md
deleted file mode 100644
index ef0e7deee18..00000000000
--- a/windows/application-management/app-v/appv-creating-and-managing-virtualized-applications.md
+++ /dev/null
@@ -1,156 +0,0 @@
----
-title: Creating and managing App-V virtualized applications (Windows 10/11)
-description: Create and manage App-V virtualized applications to monitor and record the installation process for an application to be run as a virtualized application.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# Creating and managing App-V virtualized applications
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-After you've properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
-
-For more information about configuring the App-V sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](https://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V%205.0%20Sequencing%20Guide.docx).
-
->[!NOTE]
->The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
-
-## Sequencing an application
-
-You can use the App-V Sequencer to perform the following tasks:
-
-- Create virtual packages that can be deployed to computers running the App-V client.
-- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
-- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
-
- > [!NOTE]
- >You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client.
-
-- Convert existing virtual packages.
-
-The sequencer uses the **%TMP% \\ Scratch** or **%TEMP% \\ Scratch** directory and the **Temp** directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
-
-When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V package.
-
-- **.msi file**. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
-- **Report.xml file**. In this file, the sequencer saves all issues, warnings, and errors that were discovered during sequencing. It displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
-- **.appv file**. This file is the virtual application file.
-- **Deployment configuration file**. The deployment configuration file determines how the virtual application will be deployed to target computers.
-- **User configuration file**. The user configuration file determines how the virtual application will run on target computers.
-
->[!IMPORTANT]
->You must configure the %TMP% and %TEMP% folders that the package converter uses to be a secure location and directory. A secure location is only accessible by an administrator. Additionally, when you sequence the package, you should either save the package to a secure location or make sure that no other user is allowed to log in during the conversion and monitoring process.
-
-The **Options** dialog box in the sequencer console contains the following tabs:
-
-- **General**. Use this tab to enable Microsoft Updates to run during sequencing. Select **Append Package Version to Filename** to configure the sequence to add a version number to the virtualized package that is being sequenced. Select **Always trust the source of Package Accelerators** to create virtualized packages using a package accelerator without being prompted for authorization.
-
- >[!IMPORTANT]
- >Package Accelerators created using App-V 4.6 are not supported by App-V.
-
-- **Parse Items**. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the **Package Files** tab in **Advanced Editing**.
-- **Exclusion Items**. Use this tab to specify which folders and directories shouldn't be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click **New** and specify the location and the associated **Mapping Type**. This option is required for some packages.
-
-App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the service will be included in the sequenced virtual package as long as it's installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then after installation, the application must be run while the sequencer is monitoring for the Windows Service to be included in the package. Only services running under the Local System account are supported. Services configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
-
-- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
-- [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
-- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
-
-## App-V shell extension support
-
-App-V supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
-
-Shell extensions are automatically embedded in the package during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
-
-### Requirements for using shell extensions
-
-- Packages that contain embedded shell extensions must be published globally. The application requires no extra setup or configuration on the client to enable the shell extension functionality.
-- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
- - The version of the application is 64-bit.
- - The Sequencer is running on a 64-bit computer.
- - The package is being delivered to a 64-bit App-V client computer.
-
-The following table lists the supported shell extensions:
-
-|Handler|Description|
-|---|---|
-|Context menu handler|Adds menu items to the context menu. It's called before the context menu is displayed.|
-|Drag-and-drop handler|Controls the action where right-click, drag and drop, and modifies the context menu that appears.|
-|Drop target handler|Controls the action after a data object is dragged and dropped over a drop target such as a file.|
-|Data object handler|Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide more clipboard formats to the drop target.|
-|Property sheet handler|Replaces or adds pages to the property sheet dialog box of an object.|
-|Infotip handler|Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover.|
-|Column handler|Allows creating and displaying custom columns in **Windows Explorer Details view**. It can be used to extend sorting and grouping.|
-|Preview handler|Enables a preview of a file to be displayed in the Windows Explorer Preview pane.|
-
-## Copy on Write (CoW) file extension support
-
-Copy on write (CoW) file extensions allow App-V to dynamically write to specific locations contained in the virtual package while it's being used.
-
-The following list shows the file types that can exist in a virtual package under the VFS directory, since App-V 5.1, but which can't be updated on the computer running the App-V client. All other files and directories can be modified.
-
-- .com
-- .exe
-- .dll
-- .ocx
-
-## Modifying an existing virtual application package
-
-You can use the sequencer to modify an existing package. The computer on which you do this modification should match the chip architecture of the computer you used to create the application. For example, if you initially sequenced a package using a computer running a 64-bit operating system, you should modify the package using a computer running a 64-bit operating system.
-
-For more information, see [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md).
-
-## Creating a project template
-
-An App-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you can't use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
-
-A template can specify and store multiple settings as follows:
-
-- **Advanced Monitoring Options**. Enables Microsoft Update to run during monitoring. Saves allow local interaction option settings
-- **General Options**. Enables the use of **Windows Installer**, **Append Package Version to Filename**.
-- **Exclusion Items.** Contains the Exclusion pattern list.
-
-Starting with Windows 10 version 1703, running the **new-appvsequencerpackage** or **update-appvsequencepackage** cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
-
->[!IMPORTANT]
->If you attempt to load another template through the *_TemplateFilePath_* parameter while already having an auto-saved template, the customization value from the parameter will override the auto-saved template.
-
-For more information, see [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md).
-
-## Creating a package accelerator
-
->[!NOTE]
->Package accelerators created using a previous version of App-V must be recreated using App-V.
-
-You can use App-V package accelerators to automatically generate a new virtual application package. After you've successfully created a package accelerator, you can reuse and share the package accelerator.
-
-In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
-
-After you've successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
-
-For more information, see the following articles:
-
-- [How to Create a Package Accelerator](appv-create-a-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)
-
-## Sequencer error reporting
-
-The App-V Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
-
-You can also find additional information about sequencing errors using the Windows Event Viewer.
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-customize-virtual-application-extensions-with-the-management-console.md b/windows/application-management/app-v/appv-customize-virtual-application-extensions-with-the-management-console.md
deleted file mode 100644
index bbb9594d7c6..00000000000
--- a/windows/application-management/app-v/appv-customize-virtual-application-extensions-with-the-management-console.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: How to customize virtual application extensions for a specific AD group by using the Management Console (Windows 10/11)
-description: How to customize virtual application extensions for a specific AD group by using the Management Console.
-author: aczechowski
-ms.service: windows-client
-ms.date: 07/10/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to customize virtual applications extensions for a specific AD group by using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
-
-## Customize virtual applications extensions for an AD group
-
-1. To view the package that you want to configure, open the App-V Management Console. To view the configuration assigned to a given user group, select the package, then right-click the package name and select **Edit active directory access**. Alternatively, select the package and select **EDIT** in the **AD ACCESS** pane.
-
-2. To customize an AD group, you can find the group from the list of **AD Entities with Access**. Then, using the drop-down box in the **Assigned Configuration** pane, select **Custom**, and then select **EDIT**.
-
-3. To disable all extensions for a given application, clear **ENABLE**.
-
- To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane, and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane and select **Remove Shortcut**. To edit an existing shortcut, right-click the application and select **Edit Shortcut**.
-
-4. To view any other application extensions, select **Advanced**, and select **Export Configuration**. Enter a filename and select **Save**. You can view all application extensions that are associated with the package using the configuration file.
-
-5. To edit additional application extensions, modify the configuration file and select **Import and Overwrite this Configuration**. Select the modified file and select **Open**. In the dialog, select **Overwrite** to complete the process.
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-delete-a-connection-group.md b/windows/application-management/app-v/appv-delete-a-connection-group.md
deleted file mode 100644
index 88af78ee9ff..00000000000
--- a/windows/application-management/app-v/appv-delete-a-connection-group.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: How to delete a connection group (Windows 10/11)
-description: Learn how to delete an existing App-V connection group in the App-V Management Console and where to find information about managing connection groups.
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to delete a connection group
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to delete an existing App-V connection group.
-
-## Delete a connection group
-
-1. Open the App-V Management Console and select **CONNECTION GROUPS**.
-
-2. Right-click the connection group to be removed and select **delete**.
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
-- [Managing connection groups](appv-managing-connection-groups.md)
diff --git a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md b/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md
deleted file mode 100644
index 2bd65704c0a..00000000000
--- a/windows/application-management/app-v/appv-delete-a-package-with-the-management-console.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: How to delete a package in the Management Console (Windows 10/11)
-description: Learn how to delete a package in the App-V Management Console and where to find information about operations for App-V.
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to delete a package in the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to delete an App-V package.
-
-## Delete a package in the Management Console
-
-1. To view the package you want to delete, open the App-V Management Console and select **Packages**. Select the package to be removed.
-
-2. Select or right-click the package, then select **Delete** to remove the package.
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-deploy-appv-databases-with-sql-scripts.md b/windows/application-management/app-v/appv-deploy-appv-databases-with-sql-scripts.md
deleted file mode 100644
index af21f7aff47..00000000000
--- a/windows/application-management/app-v/appv-deploy-appv-databases-with-sql-scripts.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: How to Deploy the App-V Databases by Using SQL Scripts (Windows 10/11)
-description: Learn how to use SQL scripts to install the App-V databases and upgrade the App-V databases to a later version.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to deploy the App-V databases by using SQL scripts
-
->Applies to: Windows Server 2016
-
-Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
-
-* Install the App-V databases
-* Upgrade the App-V databases to a later version
-
->[!NOTE]
->If you have already deployed an App-V 5.0 SP3 database or later, the SQL scripts are not required to upgrade to App-V for Windows.
-
-## How to install the App-V databases by using SQL scripts
-
-1. Before you install the database scripts, review and keep a copy of the App-V license terms. By running the database scripts, you are agreeing to the license terms. If you do not accept them, you should not use this software.
-
-2. Copy **appv\_server\_setup.exe** from the App-V release media to a temporary location.
-
-3. From a command prompt, run **appv\_server\_setup.exe** and specify a temporary location for extracting the database scripts.
-
- ```sql
- appv\_server\_setup.exe /layout c:\\__
- ```
-
-4. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate **readme.txt** file for instructions:
-
- | Database | Location of readme.txt file to use|
- |---|---|
- | Management database | ManagementDatabase subfolder |
- | Reporting database | ReportingDatabase subfolder |
-
->[!CAUTION]
->The readme.txt file in the ManagementDatabase subfolder is out of date. The information in the updated readme files below is the most current and should supersede the readme information provided in the **DatabaseScripts** folders.
-
->[!IMPORTANT]
-> The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
-
-### Updated management database README file content
-
-```syntax
-***********************************************************************************************************
-Before you install and use the Application Virtualization Database Scripts, you must:
-
-- Review the license terms.
-- Print and retain a copy of the license terms for your records.
-
-By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
-***********************************************************************************************************
-
-Steps to install "AppVManagement" schema in SQL SERVER.
-
-## PREREQUISITES:
-
- 1. Review the installation package. The following files MUST exist:
-
- SQL files
- ---------
- Database.sql
- CreateTables.sql
- CreateStoredProcs.sql
- UpdateTables.sql
- Permissions.sql
-
- 2. Ensure the target SQL Server instance and SQL Server Agent service are running.
-
- 3. If you are not running the scripts directly on the server, ensure the
- necessary SQL Server client software is installed and available from
- the specified location. Specifically, the "osql" command must be supported for these scripts to run.
-
-## PREPARATION:
-
- 1. Review the database.sql file and modify as necessary. Although the
- defaults are likely sufficient, it is suggested that the following
- settings be reviewed:
-
- DATABASE - ensure name is satisfactory - default is "AppVManagement".
-
- 2. Review the Permissions.sql file and provide all the necessary account information
- for setting up read and write access on the database. Note: Default settings in the file will not work.
-
-## INSTALLATION:
-
- 1. Run the database.sql against the "master" database. Your user
- credential must have the ability to create databases.
- This script will create the database.
-
- 2. Run the following scripts against the "AppVManagement" database using the
- same account as above in order.
-
- CreateTables.sql
- CreateStoredProcs.sql
- UpdateTables.sql
- Permissions.sql
-
-```
-
-### Updated reporting database README file content
-
-```syntax
-***********************************************************************************************************
-Before you install and use the Application Virtualization Database Scripts, you must:
-
-- Review the license terms.
-- Print and retain a copy of the license terms for your records.
-
-By running the App-V you agree to such license terms. If you do not accept them, do not use the software.
-***********************************************************************************************************
-
-Steps to install "AppVReporting" schema in SQL SERVER.
-
-## PREREQUISITES:
-
- 1. Review the installation package. The following files MUST exist:
-
- SQL files
- ---------
- Database.sql
- UpgradeDatabase.sql
- CreateTables.sql
- CreateReportingStoredProcs.sql
- CreateStoredProcs.sql
- CreateViews.sql
- Permissions.sql
- ScheduleReportingJob.sql
-
- 2. Ensure the target SQL Server instance and SQL Server Agent service are running.
-
- 3. If you are not running the scripts directly on the server, ensure the
- necessary SQL Server client software is installed and executable from
- the location you have chosen. Specifically, the "osql" command must be supported for these scripts to run.
-
-## PREPARATION:
-
- 1. Review the database.sql file and modify as necessary. Although the
- defaults are likely sufficient, it is suggested that the following
- settings be reviewed:
-
- DATABASE - ensure name is satisfactory - default is "AppVReporting".
-
- 2. Review the Permissions.sql file and provide all the necessary account information
- for setting up read and write access on the database. Note: Default settings
- in the file will not work.
-
- 3. Review the ScheduleReportingJob.sql file and make sure that the stored proc schedule
- time is acceptable. The default stored proc schedule time is at 12.01 AM (line 84).
- If this time is not suitable, you can change this to a more suitable time. The time is in the format HHMMSS.
-
-## INSTALLATION:
-
- 1. Run the database.sql against the "master" database. Your user
- credential must have the ability to create databases.
- This script will create the database.
-
- 2. If upgrading the database, run UpgradeDatabase.sql This will upgrade database schema.
-
- 2. Run the following scripts against the "AppVReporting" database using the
- same account as above in order.
-
- CreateTables.sql
- CreateReportingStoredProcs.sql
- CreateStoredProcs.sql
- CreateViews.sql
- Permissions.sql
- ScheduleReportingJob.sql
-```
-
-
-
-
-
-## Related articles
-
-* [Deploying the App-V Server](appv-deploying-the-appv-server.md)
-* [How to deploy the App-V Server](appv-deploy-the-appv-server.md)
diff --git a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md
deleted file mode 100644
index a0856627909..00000000000
--- a/windows/application-management/app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to deploy App-V packages using electronic software distribution (Windows 10/11)
-description: Learn how to use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to deploy App-V packages using electronic software distribution
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
-
-For component requirements and options for using an ESD to deploy App-V packages, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
-
-Use one of the following methods to publish packages to App-V client computers with an ESD:
-
-- Use the functionality in a third-party ESD.
-- Install the application on the target client computer with the associated Windows Installer (.msi) file that's created when you initially sequence the application. The .msi file contains the associated App-V package file information used to configure a package and copies the required package files to the client.
-- Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).
-
-| Method | Description |
-|---|---|
-| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.|
-| Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. |
-| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using Windows PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|
-
-## Deploy App-V packages with an ESD
-
-1. Install the App-V Sequencer on a computer in your environment. For more information about installing the sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md).
-
-2. Use the App-V Sequencer to create a virtual application. To learn more about creating virtual applications, see [Creating and managing App-V virtualized applications](appv-creating-and-managing-virtualized-applications.md).
-
-3. After you create the virtual application, deploy the package by using your ESD solution.
-
-
-
-
-
-## Related articles
-
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md b/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md
deleted file mode 100644
index d0e531b2343..00000000000
--- a/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md
+++ /dev/null
@@ -1,526 +0,0 @@
----
-title: How to Deploy the App-V Server Using a Script (Windows 10/11)
-description: 'Learn how to deploy the App-V server by using a script (appv_server_setup.exe) from the command line.'
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to deploy the App-V server using a script
-
->Applies to: Windows Server 2016
-
-In order to complete the **appv_server_setup.exe** server setup successfully using the command line, you must specify and combine multiple parameters.
-
-## To install the App-V server using a script
-
-Use the following lists and tables for more information about installing the App-V server using the command line.
-
-The information in the following lists and tables can also be accessed through the command line by entering the following command: ```appv\_server\_setup.exe /?```.
-
-## How to use common parameters to install the Management server and Management database on a local machine
-
-The following examples will show you how to install the Management server and database on a local machine.
-
-### Parameters for a default instance of Microsoft SQL Server for a new installation on a local machine
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */MANAGEMENT_SERVER*
-* */MANAGEMENT_ADMINACCOUNT*
-* */MANAGEMENT_WEBSITE_NAME*
-* */MANAGEMENT_WEBSITE_PORT*
-* */DB_PREDEPLOY_MANAGEMENT*
-* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
-* */MANAGEMENT_DB_NAME*
-
-### Parameters for a custom instance of Microsoft SQL Server for a new installation on a local machine
-
-To use a custom instance of Microsoft SQL Server, use the following parameters:
-
-* */MANAGEMENT_SERVER*
-* */MANAGEMENT_ADMINACCOUNT*
-* */MANAGEMENT_WEBSITE_NAME*
-* */MANAGEMENT_WEBSITE_PORT*
-* */DB_PREDEPLOY_MANAGEMENT*
-* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
-* */MANAGEMENT_DB_NAME*
-
-### Example parameters for using a custom instance of Microsoft SQL Server for a new installation on a local machine
-
-```SQL
-/appv_server_setup.exe /QUIET
-/MANAGEMENT_SERVER
-/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
-/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
-/MANAGEMENT_WEBSITE_PORT="8080"
-/DB_PREDEPLOY_MANAGEMENT
-/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/MANAGEMENT_DB_NAME="AppVManagement"
-```
-
-## How to use common parameters to install the Management server using an existing Management database on a local machine
-
-The following examples will show you how to install the Management server on a local machine with an existing Management database.
-
-### Default instance of Microsoft SQL Server for installation with an existing Management database on a local machine
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */MANAGEMENT_SERVER*
-* */MANAGEMENT_ADMINACCOUNT*
-* */MANAGEMENT_WEBSITE_NAME*
-* */MANAGEMENT_WEBSITE_PORT*
-* */EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL*
-* */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
-* */EXISTING_MANAGEMENT_DB_NAME*
-
-### Custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */MANAGEMENT_SERVER*
-* */MANAGEMENT_ADMINACCOUNT*
-* */MANAGEMENT_WEBSITE_NAME*
-* */MANAGEMENT_WEBSITE_PORT*
-* */EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL*
-* */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
-* */EXISTING_MANAGEMENT_DB_NAME*
-
-### Example parameters for using a custom instance of Microsoft SQL Server for installation with an existing Management database on a local machine
-
-```SQL
-/appv_server_setup.exe /QUIET
-/MANAGEMENT_SERVER
-/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
-/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
-/MANAGEMENT_WEBSITE_PORT="8080"
-/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL
-/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName"
-/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement"
-```
-
-## How to install the Management server with an existing Management database on a remote machine
-
-### Default instance of Microsoft SQL Server with an existing Management database on a remote machine
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */MANAGEMENT_SERVER*
-* */MANAGEMENT_ADMINACCOUNT*
-* */MANAGEMENT_WEBSITE_NAME*
-* */MANAGEMENT_WEBSITE_PORT*
-* */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME*
-* */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
-* */EXISTING_MANAGEMENT_DB_NAME*
-
-### Custom instance of Microsoft SQL Server with an existing Management database on a remote machine
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */MANAGEMENT_SERVER*
-* */MANAGEMENT_ADMINACCOUNT*
-* */MANAGEMENT_WEBSITE_NAME*
-* */MANAGEMENT_WEBSITE_PORT*
-* */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME*
-* */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
-* */EXISTING_MANAGEMENT_DB_NAME*
-
-### Example for using a custom instance of Microsoft SQL Server with an existing Management database on a remote machine
-
-```SQL
-/appv_server_setup.exe /QUIET
-/MANAGEMENT_SERVER
-/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
-/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
-/MANAGEMENT_WEBSITE_PORT="8080"
-/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="SqlServermachine.domainName"
-/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName"
-/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement"
-```
-
-## Installing the Management database and the Management Server on the same computer
-
-The following examples will show you how to install the Management server and database on the same computer.
-
-### Default instance of Microsoft SQL Server for installation on the same computer
-
-To use the default instance of Microsoft SQL Server, use these parameters:
-
-* */DB_PREDEPLOY_MANAGEMENT*
-* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
-* */MANAGEMENT_DB_NAME*
-* */MANAGEMENT_SERVER_MACHINE_USE_LOCAL*
-* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Custom instance of Microsoft SQL Server for installation on the same computer
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */DB_PREDEPLOY_MANAGEMENT*
-* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
-* */MANAGEMENT_DB_NAME*
-* */MANAGEMENT_SERVER_MACHINE_USE_LOCAL*
-* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Example for using a custom instance of Microsoft SQL Server for installation on the same computer
-
-```SQL
-/appv_server_setup.exe /QUIET
-/DB_PREDEPLOY_MANAGEMENT
-/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/MANAGEMENT_DB_NAME="AppVManagement"
-/MANAGEMENT_SERVER_MACHINE_USE_LOCAL
-/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
-```
-
-## Installing the Management database on a different computer than the Management server
-
-The following examples will show you how to install the Management database and server on different computers.
-
-### Default instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */DB_PREDEPLOY_MANAGEMENT*
-* */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
-* */MANAGEMENT_DB_NAME*
-* */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT*
-* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */DB_PREDEPLOY_MANAGEMENT*
-* */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
-* */MANAGEMENT_DB_NAME*
-* */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT*
-* */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Example for using a custom instance of Microsoft SQL Server for installing the Management database on a different computer than the Management server
-
-```SQL
-/appv_server_setup.exe /QUIET
-/DB_PREDEPLOY_MANAGEMENT
-/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/MANAGEMENT_DB_NAME="AppVManagement"
-/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
-/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
-```
-
-## Installing the Publishing server
-
-The following examples will show you how to install the Publishing server.
-
-### Default instance of Microsoft SQL Server for installing the Publishing server
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */PUBLISHING_SERVER*
-* */PUBLISHING_MGT_SERVER*
-* */PUBLISHING_WEBSITE_NAME*
-* */PUBLISHING_WEBSITE_PORT*
-
-### Example for installing the Publishing server
-
-```SQL
-/appv_server_setup.exe /QUIET
-/PUBLISHING_SERVER
-/PUBLISHING_MGT_SERVER="http://ManagementServerName:ManagementPort"
-/PUBLISHING_WEBSITE_NAME="Microsoft AppV Publishing Service"
-/PUBLISHING_WEBSITE_PORT="8081"
-```
-
-## Installing the Reporting server and Reporting database on a local machine
-
-The following examples will show you how to install the Reporting server and database on a local machine.
-
-### Default instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */REPORTING_SERVER*
-* */REPORTING_WEBSITE_NAME*
-* */REPORTING_WEBSITE_PORT*
-* */DB_PREDEPLOY_REPORTING*
-* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
-* */REPORTING_DB_NAME*
-
-### Custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */REPORTING_SERVER*
-* */REPORTING_ADMINACCOUNT*
-* */REPORTING_WEBSITE_NAME*
-* */REPORTING_WEBSITE_PORT*
-* */DB_PREDEPLOY_REPORTING*
-* */REPORTING_DB_CUSTOM_SQLINSTANCE*
-* */REPORTING_DB_NAME*
-
-### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server and Reporting database on a local machine
-
-```SQL
-/appv_server_setup.exe /QUIET
-/REPORTING_SERVER
-/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
-/REPORTING_WEBSITE_PORT="8082"
-/DB_PREDEPLOY_REPORTING
-/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/REPORTING_DB_NAME="AppVReporting"
-```
-
-## Installing the Reporting server using an existing Reporting database on a local machine
-
-The following examples will show you how to install the reporting machine on a local machine with an existing Reporting database.
-
-### Default instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */REPORTING_SERVER*
-* */REPORTING_WEBSITE_NAME*
-* */REPORTING_WEBSITE_PORT*
-* */EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL*
-* */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
-* */EXISTING_REPORTING_DB_NAME*
-
-### Custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */REPORTING_SERVER*
-* */REPORTING_ADMINACCOUNT*
-* */REPORTING_WEBSITE_NAME*
-* */REPORTING_WEBSITE_PORT*
-* */EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL*
-* */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE*
-* */EXISTING_REPORTING_DB_NAME*
-
-### Example for using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a local machine
-
-```SQL
-/appv_server_setup.exe /QUIET
-/REPORTING_SERVER
-/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
-/REPORTING_WEBSITE_PORT="8082"
-/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL
-/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/EXITING_REPORTING_DB_NAME="AppVReporting"
-```
-
-## Installing the Reporting server using an existing Reporting database on a remote machine
-
-The following examples will show you how to install the Reporting server and on a remote machine with an existing database.
-
-### Default instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */REPORTING_SERVER*
-* */REPORTING_WEBSITE_NAME*
-* */REPORTING_WEBSITE_PORT*
-* */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME*
-* */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
-* */EXISTING_REPORTING_DB_NAME*
-
-### Custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */REPORTING_SERVER*
-* */REPORTING_ADMINACCOUNT*
-* */REPORTING_WEBSITE_NAME*
-* */REPORTING_WEBSITE_PORT*
-* */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME*
-* */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE*
-* */EXISTING_REPORTING_DB_NAME*
-
-### Example using a custom instance of Microsoft SQL Server for installing the Reporting server using an existing Reporting database on a remote machine
-
-```SQL
-/appv_server_setup.exe /QUIET
-/REPORTING_SERVER
-/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
-/REPORTING_WEBSITE_PORT="8082"
-/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="SqlServerMachine.DomainName"
-/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/EXITING_REPORTING_DB_NAME="AppVReporting"
-```
-
-## Installing the Reporting database on the same computer as the Reporting server
-
-The following examples will show you how to install the Reporting database and server on the same computer.
-
-### Default instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */DB_PREDEPLOY_REPORTING*
-* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
-* */REPORTING_DB_NAME*
-* */REPORTING_SERVER_MACHINE_USE_LOCAL*
-* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */DB_PREDEPLOY_REPORTING*
-* */REPORTING_DB_CUSTOM_SQLINSTANCE*
-* */REPORTING_DB_NAME*
-* */REPORTING_SERVER_MACHINE_USE_LOCAL*
-* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on the same computer as the Reporting server
-
-```SQL
-/appv_server_setup.exe /QUIET
-/DB_PREDEPLOY_REPORTING
-/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/REPORTING_DB_NAME="AppVReporting"
-/REPORTING_SERVER_MACHINE_USE_LOCAL
-/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
-```
-
-## Installing the Reporting database on a different computer than the Reporting server
-
-The following examples will show you how to install the Reporting database and server on different computers.
-
-### Default instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
-
-To use the default instance of Microsoft SQL Server, use the following parameters:
-
-* */DB_PREDEPLOY_REPORTING*
-* */REPORTING_DB_SQLINSTANCE_USE_DEFAULT*
-* */REPORTING_DB_NAME*
-* */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT*
-* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
-
-To use a custom instance of Microsoft SQL Server, use these parameters:
-
-* */DB_PREDEPLOY_REPORTING*
-* */REPORTING_DB_CUSTOM_SQLINSTANCE*
-* */REPORTING_DB_NAME*
-* */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT*
-* */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT*
-
-### Example for using a custom instance of Microsoft SQL Server for installing the Reporting database on a different computer than the Reporting server
-
-```SQL
-/appv_server_setup.exe /QUIET
-/DB_PREDEPLOY_REPORTING
-/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
-/REPORTING_DB_NAME="AppVReporting"
-/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
-/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount"
-```
-
-## Parameter definitions
-
-* [General parameters](#parameter-definitions-for-general-parameters)
-* [Management Server installation parameters](#parameter-definitions-for-management-server-installation-parameters)
-* [Management Server Database parameters](#parameter-definitions-for-the-management-server-database)
-* [Publishing Server installation parameters](#parameter-definitions-for-publishing-server-installation-parameters)
-* [Reporting Server parameters](#parameter-definitions-for-reporting-server)
-* [Parameters for using an existing Reporting Server database](#parameters-for-using-an-existing-reporting-server-database)
-* [Reporting Server database installation parameters](#parameter-definitions-for-reporting-server-database-installation)
-* [Parameters for using an existing Management Server database](#parameters-for-using-an-existing-management-server-database)
-
-### Parameter definitions for general parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| */QUIET* | Specifies silent install. |
-| */UNINSTALL* | Specifies an uninstall. |
-| */LAYOUT* | Specifies layout action. This extracts the MSIs and script files to a folder without installing the actual product. No value is expected. |
-| */LAYOUTDIR* | Specifies the layout directory with a string. For example, ```/LAYOUTDIR="C:\Application Virtualization Server"```. |
-| */INSTALLDIR* | Specifies the installation directory with a string. For example, ```/INSTALLDIR="C:\Program Files\Application Virtualization\Server"```. |
-| */MUOPTIN* | Enables Microsoft Update. No value is expected. |
-| */ACCEPTEULA* | Accepts the license agreement. This is required for an unattended installation. For example, ```/ACCEPTEULA``` or ```/ACCEPTEULA=1```. |
-
-### Parameter definitions for Management Server installation parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| */MANAGEMENT_SERVER* | Specifies that the management server will be installed. No value is expected. |
-| */MANAGEMENT_ADMINACCOUNT* | Specifies the account that will be allowed administrator access to the management server. This account can be an individual user account or a group. For example, ```/MANAGEMENT_ADMINACCOUNT="mydomain\admin"```. If **/MANAGEMENT_SERVER** isn't specified, this parameter will be ignored.|
-| */MANAGEMENT_WEBSITE_NAME* | Specifies name of the website that will be created for the management service. For example, ```/MANAGEMENT_WEBSITE_NAME="Microsoft App-V Management Service"``` |
-| */MANAGEMENT_WEBSITE_PORT* | Specifies the port number that will be used by the management service will use. For example, ```/MANAGEMENT_WEBSITE_PORT=82```. |
-
-### Parameter definitions for the Management Server Database
-
-| Parameter | Description |
-|-----------|-------------|
-| */DB\_PREDEPLOY\_MANAGEMENT* | Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected. |
-| */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance should be used. No value is expected. |
-| */MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used to create a new database. For example, ```/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this parameter will be ignored. |
-| */MANAGEMENT_DB_NAME* | Specifies the name of the new management database that should be created. For example, ```/MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. |
-| */MANAGEMENT_SERVER_MACHINE_USE_LOCAL* | Indicates if the management server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. |
-| */MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT* | Specifies the machine account of the remote machine that the management server will be installed on. For example, ```/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="domain\computername"```. |
-| */MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT* | Indicates the Administrator account that will be used to install the management server. For example, ```/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT ="domain\alias"```. |
-
-### Parameter definitions for Publishing Server installation parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| */PUBLISHING_SERVER* | Specifies that the publishing server will be installed. No value is expected. |
-| */PUBLISHING_MGT_SERVER* | Specifies the URL to Management Service the Publishing server will connect to. For example, ```http://;```. If **/PUBLISHING_SERVER** isn't used, this parameter will be ignored. |
-| */PUBLISHING_WEBSITE_NAME* | Specifies name of the website that will be created for the publishing service. For example, ```/PUBLISHING_WEBSITE_NAME="Microsoft App-V Publishing Service"```. |
-| */PUBLISHING_WEBSITE_PORT* | Specifies the port number used by the publishing service. For example, ```/PUBLISHING_WEBSITE_PORT=83```. |
-
-### Parameter definitions for Reporting Server
-
-| Parameter | Description |
-|-----------|-------------|
-| */REPORTING_SERVER* | Specifies that the Reporting Server will be installed. No value is expected. |
-| */REPORTING_WEBSITE_NAME* | Specifies name of the website that will be created for the Reporting Service. For example, ```/REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"```. |
-| */REPORTING_WEBSITE_PORT* | Specifies the port number that the Reporting Service will use. For example, ```/REPORTING_WEBSITE_PORT=82```. |
-
-### Parameters for using an existing Reporting Server database
-
-| Parameter | Description |
-|-----------|-------------|
-| */EXISTING\_REPORTING\_DB_SQL_SERVER_USE_LOCAL* | Indicates that the Microsoft SQL Server is installed on the local server. This is a switch parameter, so no value is expected. |
-| */EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME* | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. |
-| */EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance is to be used. This is a switch parameter, so no value is expected. |
-| */EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. |
-| */EXISTING_REPORTING_DB_NAME* | Specifies the name of the existing Reporting database that should be used. Takes a string. For example, ```/EXISTING_REPORTING_DB_NAME="AppVReporting"```. |
-
-### Parameter definitions for Reporting Server database installation
-
-| Parameter | Description |
-|-----------|-------------|
-| */DB\_PREDEPLOY\_REPORTING* | Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected. |
-| */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. |
-| */REPORTING_DB_NAME* | Specifies the name of the new Reporting database that should be created. Takes a string. For example, ```/REPORTING_DB_NAME="AppVMgmtDB"```. |
-| */REPORTING_SERVER_MACHINE_USE_LOCAL* | Indicates that the Reporting server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. |
-| */REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT* | Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. For example, ```/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"```. |
-| */REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT* | Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. For example, ```/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"```. |
-
-### Parameters for using an existing Management Server database
-
-| Parameter | Description |
-|-----------|-------------|
-| */EXISTING\_MANAGEMENT\_DB_SQL_SERVER_USE_LOCAL* | Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. |
-| */EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME* | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. For example, ```/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="mycomputer1"```. |
-| */EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this variable will be ignored. |
-| */EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that will be used. For example, ```/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE="AppVManagement"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. |
-| */EXISTING_MANAGEMENT_DB_NAME* | Specifies the name of the existing management database that should be used. For example, ```/EXISTING_MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. |
-
-
-
-
-
-## Related articles
-
-* [Deploying the App-V Server](appv-deploying-the-appv-server.md)
diff --git a/windows/application-management/app-v/appv-deploy-the-appv-server.md b/windows/application-management/app-v/appv-deploy-the-appv-server.md
deleted file mode 100644
index ccd4d5e8c22..00000000000
--- a/windows/application-management/app-v/appv-deploy-the-appv-server.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: How to Deploy the App-V Server (Windows 10/11)
-description: Use these instructions to deploy the Application Virtualization (App-V) Server in App-V for Windows 10/11.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to Deploy the App-V Server (new installation)
-
->Applies to: Windows Server 2016
-
-## Before you start
-
->[!IMPORTANT]
->If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
-
-* Ensure that you’ve installed required software. See [App-V prerequisites](appv-prerequisites.md).
-* Review the server section of [App-V security considerations](appv-security-considerations.md).
-* Specify a port where each component will be hosted.
-* Add firewall rules to allow incoming requests to access the specified ports.
-* If you use SQL scripts instead of the Windows Installer to set up the Management database or Reporting database, you must run the required SQL scripts before installing the Management Server or Reporting Server. See [How to deploy the App-V databases by using SQL scripts](appv-deploy-appv-databases-with-sql-scripts.md).
-
-## Installing the App-V server
-
-1. Download the App-V server components. All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
-
- * The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
- * The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
-
-2. Copy the App-V server installation files to the computer on which you want to install it.
-
-3. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**.
-
-4. Review and accept the license terms, and choose whether to enable Microsoft updates.
-
-5. On the **Feature Selection** page, select all components listed in the following table.
-
- | Component | Description |
- |---|---|
- | Management server | Provides overall management functionality for the App-V infrastructure. |
- | Management database | Facilitates database predeployments for App-V management. |
- | Publishing server | Provides hosting and streaming functionality for virtual applications. |
- | Reporting server | Provides App-V reporting services. |
- | Reporting database | Facilitates database predeployments for App-V reporting. |
-
-6. On the **Installation Location** page, accept the default location where the selected components will be installed, or change the location by typing a new path on the **Installation Location** line.
-
-7. On the initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below.
-
- | Method | What you need to do |
- |---|---|
- | You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, then specify the instance name. Use the format **INSTANCENAME**. The assumed installation location is the local computer. Not supported: A server name using the format **ServerName**\\**INSTANCE**.|
- | You are using a custom database name. | Select **Custom configuration** and type the database name. The database name must be unique, or the installation will fail.|
-
-8. On the **Configure** page, accept the default value, **Use this local computer**.
-
- > [!NOTE]
- > If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
-
-9. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below.
-
- | Method | What you need to do |
- |---|---|
- | You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, and type the name of the instance. Use the format **INSTANCENAME**. The assumed installation location is the local computer. Not supported: A server name using the format **ServerName**\\**INSTANCE**.|
- | You are using a custom database name. | Select **Custom configuration** and type the database name. The database name must be unique, or the installation will fail.|
-
-10. On the **Configure** page, accept the default value: **Use this local computer**.
-
- > [!NOTE]
- > If you're installing the Management server and Management database side-by-side, the appropriate options are selected by default and cannot be changed.
-
-11. On the **Configure** (Management Server Configuration) page, specify the following:
-
- | Item to configure | Description and examples |
- |---|---|
- | Specify AD group | Specify the AD group with sufficient permissions to manage the App-V environment. Example: MyDomain\MyUser
After installation, you can add users or groups on the management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use Domain local or Universal groups to perform this action.|
- |Website name | Specify the custom name that will be used to run the publishing service. If you do not have a custom name, you don't have to change it.|
- |Port binding | Specify a unique port number that will be used by App-V. Example: **12345** Ensure that the port specified is not being used by another website. |
-
-12. On the **Configure Publishing Server Configuration** page, specify the following:
-
- | Item to configure | Description and examples |
- |---|---|
- | Specify the management service URL | Example: http://localhost:12345 |
- | Website name | Specify the custom website name that will be used to run the publishing service. If you do not have a custom name, do not make any changes. |
- | Port binding | Specify a unique port number that will be used by App-V. Example: 54321 Ensure that the port specified is not being used by another website. |
-
-13. On the **Reporting Server** page, specify the following:
-
- | Item to configure | Description and examples |
- |---|---|
- | Website name | Specify the custom name that will be used to run the Reporting Service. If you do not have a custom name, do not make any changes. |
- | Port binding | Specify a unique port number that will be used by App-V. Example: 55555 Ensure that the port specified is not being used by another website.|
-
-14. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page.
-
-15. To verify that the setup completed successfully, open a web browser, and type the following URL with the bracketed variables adjusted according to your specifications in the earlier steps:
-
- `http://:/console.html`
-
- Example: `http://localhost:12345/console.html`. If the installation succeeded, the App-V Management console will display with no errors.
-
-## Related articles
-
-* [Deploying App-V](appv-deploying-appv.md)
-* [How to install the management and reporting databases on separate computers from the management and reporting services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
-* [How to install the publishing server on a remote computer](appv-install-the-publishing-server-on-a-remote-computer.md)
-* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md)
diff --git a/windows/application-management/app-v/appv-deploying-appv.md b/windows/application-management/app-v/appv-deploying-appv.md
deleted file mode 100644
index 57ec0897716..00000000000
--- a/windows/application-management/app-v/appv-deploying-appv.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Deploying App-V (Windows 10/11)
-description: App-V supports several different deployment options. Learn how to complete App-V deployment at different stages in your App-V deployment.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying App-V for Windows client
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-App-V supports several different deployment options. Review this article for information about the tasks that you must complete at different stages in your deployment.
-
-## App-V Deployment Information
-
-* [Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)
-
- This section describes how to install the App-V sequencer used to virtualize applications, and how to enable the App-V client that runs on target computers to facilitate virtualized packages.
-* [Deploying the App-V server](appv-deploying-the-appv-server.md)
-
- This section provides information about installing the App-V management, publishing, database, and reporting severs.
-* [App-V deployment checklist](appv-deployment-checklist.md)
-
- This section provides a deployment checklist that can be used to assist with installing App-V.
-
-The following sections describe how to use App-V to deliver Microsoft Office as a virtualized application to computers in your organization.
-
-* [Deploying Microsoft Office 2016 by using App-V](appv-deploying-microsoft-office-2016-with-appv.md)
-* [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
-* [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
-
-## Other App-V deployment resources
-
-* [Application Virtualization (App-V) overview](appv-for-windows.md)
-* [Getting started with App-V](appv-getting-started.md)
-* [Planning for App-V](appv-planning-for-appv.md)
-* [Operations for App-V](appv-operations.md)
-* [Troubleshooting App-V](appv-troubleshooting.md)
-* [Technical reference for App-V](appv-technical-reference.md)
-
-
-
-
diff --git a/windows/application-management/app-v/appv-deploying-microsoft-office-2010-wth-appv.md b/windows/application-management/app-v/appv-deploying-microsoft-office-2010-wth-appv.md
deleted file mode 100644
index e68c95f2302..00000000000
--- a/windows/application-management/app-v/appv-deploying-microsoft-office-2010-wth-appv.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Deploying Microsoft Office 2010 by Using App-V
-description: Create Office 2010 packages for Microsoft Application Virtualization (App-V) using the App-V Sequencer or the App-V Package Accelerator.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying Microsoft Office 2010 by Using App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
-
-* Application Virtualization (App-V) Sequencer
-* Application Virtualization (App-V) Package Accelerator
-
-## App-V support for Office 2010
-
-The following table shows the App-V versions, methods of Office package creation, supported licensing, and supported deployments for Office 2010.
-
-|Supported item|Support level|
-|---|---|
-|Package creation|- Sequencing - Package Accelerator - Office Deployment Kit|
-|Supported licensing|Volume Licensing|
-|Supported deployments|- Desktop - Personal VDI - RDS|
-
-## Creating Office 2010 App-V using the sequencer
-
-Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V. For more information, see [How to Sequence a New Application with App-V 5.0](/microsoft-desktop-optimization-pack/appv-v5/how-to-sequence-a-new-application-with-app-v-50-beta-gb18030).
-
-## Deploying the Microsoft Office package for App-V
-
-You can deploy Office 2010 packages by using any of the following App-V deployment methods:
-
-* Microsoft Configuration Manager
-* App-V server
-* Stand-alone through Windows PowerShell commands
-
-## Office App-V package management and customization
-
-Office 2010 packages can be managed like any other App-V packages through known package management mechanisms. No special instructions are needed, for example, to add, publish, unpublish, or remove Office packages.
-
-## Microsoft Office integration with Windows
-
-The following table provides a full list of supported integration points for Office 2010.
-
-(POPULATE THE THIRD COLUMN)
-
-|Extension Point|Description|Office 2010|
-|---|---|---|
-|Lync meeting Join Plug-in for Firefox and Chrome|User can join Lync meetings from Firefox and Chrome||
-|Sent to OneNote Print Driver|User can print to OneNote|Yes|
-|OneNote Linked Notes|OneNote Linked Notes||
-|Send to OneNote Internet Explorer Add-In|User can send to OneNote from IE||
-|Firewall Exception for Lync and Outlook|Firewall Exception for Lync and Outlook||
-|MAPI Client|Native apps and add-ins can interact with virtual Outlook through MAPI||
-|SharePoint Plugin for Firefox|User can use SharePoint features in Firefox||
-|Mail Control Panel Applet|User gets the mail control panel applet in Outlook|Yes|
-|Primary Interop Assemblies|Support managed add-ins||
-|Office Document Cache Handler|Allows Document Cache for Office applications||
-|Outlook Protocol Search handler|User can search in Outlook|Yes|
-|Active X Controls: - Groove.SiteClient - PortalConnect.PersonalSite - SharePoint.openDocuments - SharePoint.ExportDatabase - SharePoint.SpreadSheetLauncher - SharePoint.StssyncHander - SharePoint.DragUploadCtl - SharePoint.DragDownloadCtl - Sharpoint.OpenXMLDocuments - Sharepoint.ClipboardCtl - WinProj.Activator - Name.NameCtrl - STSUPld.CopyCtl - CommunicatorMeetingJoinAx.JoinManager - LISTNET.Listnet - OneDrive Pro Browser Helper|Active X Control.
For more information about ActiveX controls, see the [ActiveX Control API Reference](/previous-versions/office/developer/sharepoint-2010/ms440037(v=office.14)).||
-|OneDrive Pro Icon Overlays|Windows explorer shell icon overlays when users look at folders OneDrive Pro folders||
-
-### Connection Groups
-
-* [Managing Connection Groups](appv-managing-connection-groups.md)
-
-### Dynamic Configuration
-
-* [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
diff --git a/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md b/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md
deleted file mode 100644
index 8b8c6ca547e..00000000000
--- a/windows/application-management/app-v/appv-deploying-microsoft-office-2013-with-appv.md
+++ /dev/null
@@ -1,430 +0,0 @@
----
-title: Deploying Microsoft Office 2013 by Using App-V (Windows 10/11)
-description: Use Application Virtualization (App-V) to deliver Microsoft Office 2013 as a virtualized application to computers in your organization.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying Microsoft Office 2013 by Using App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
-
-## What to know before you start
-
-Before you deploy Office 2013 with App-V, review the following planning information.
-
-### Supported Office versions and Office coexistence
-
-The following table will direct you to more information about which versions of Office App-V supports and how to run App-V with coexisting versions of Office.
-
-|Information to review|Description|
-|---|---|
-|[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#supported-versions-of-microsoft-office)|- Supported versions of Office - Supported deployment types like desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI - Office licensing options.|
-|[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#before-you-implement-office-coexistence)|Considerations for installing different versions of Office on the same computer.|
-
-### Packaging, publishing, and deployment requirements
-
-Before you deploy Office with App-V, review the following requirements.
-
-|Task|Requirement|
-|---|---|
-|Packaging|All Office applications you wish to deploy to users must be in a single package. In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation. If you're deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#deploying-visio-2013-and-project-2013-with-office).|
-|Publishing|You can only publish one Office package per client computer. You must publish the Office package globally, not to the user.|
-|Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
-
-### Excluding Office applications from a package
-
-The following table describes the recommended methods for excluding specific Office applications from a package.
-
-|Task|Details|
-|---|---|
-|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word. For more information, see [ExcludeApp element](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ad=US&rs=en-US&ui=en-US#excludeapp-element).|
-|Modify the **DeploymentConfig.xml** file|Modify the **DeploymentConfig.xml** file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client. For more information, see [Disabling Office 2013 applications](#disabling-office-2013-applications).|
-
-## Creating an Office 2013 package for App-V with the Office Deployment Tool
-
-Complete the following steps to create an Office 2013 package for App-V or later.
-
->[!IMPORTANT]
->In App-V and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
-
-### Review prerequisites for using the Office Deployment Tool
-
-Before you start, ensure that the computer on which you're installing the Office Deployment Tool has the following prerequisites fulfilled:
-
-|Prerequisite|Description|
-|---|---|
-|Prerequisite software|.NET Framework 4|
-|Supported operating systems|64-bit version of Windows 8 or later 64-bit version of Windows 7|
-
->[!NOTE]
->In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing.
-
-### Create Office 2013 App-V packages using Office Deployment Tool
-
-You create Office 2013 App-V packages with the Office Deployment Tool. The following instructions explain how to create an Office 2013 App-V package with Volume Licensing or Subscription Licensing.
-
-Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10/11 computers.
-
-### Download the Office Deployment Tool
-
-Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The App-V sequencer can't create or modify packages. To create a package:
-
-1. Download the [Office 2013 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778).
-2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
-
- Example: \\\\Server\\Office2013
-3. Check that a **setup.exe** and a **configuration.xml** file exist and are in the location you specified.
-
-### Download Office 2013 applications
-
-After you download the Office Deployment Tool, you can use it to get the latest Office 2013 applications. You can create the Office 2013 App-V package after getting all the Office applications.
-
-The XML file included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
-
-1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
-
- 1. Open the sample XML file in Notepad or your favorite text editor.
-
- 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following example denotes a configuration.xml file:
-
- ```XML
-
-
-
-
-
-
-
-
-
-
- ```
-
- > [!NOTE]
- >The configuration XML is a sample XML file. This file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
-
- The previous example of an XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. The Product ID of the applications won't affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications by specifying licensing in a later stage. For more information, see [Customizable attributes and elements of the XML file](#customizable-attributes-and-elements-of-the-xml-file), later in this topic.
-
- After editing the configuration.xml file to specify the desired product, languages, and also the location that the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
-2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2013 applications that will later be converted into an App-V package. An example command is:
-
- ```PowerShell
- \\server\Office2013\setup.exe /download \\server\Office2013\Customconfig.xml
- ```
-
- The following table describes each element of the command:
-
- |Element|Description|
- |---|---|
- |```\\server\Office2013```|This network share location is the one that contains the Office Deployment Tool and the custom Configuration.xml file, **Customconfig.xml**.|
- |```setup.exe```|This element is the Office Deployment Tool.|
- |```/download```|This element downloads the Office 2013 applications that you specify in the **Customconfig.xml** file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.|
- |```\\server\Office2013\Customconfig.xml```|This element passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After the download command is used, Office applications should be found in the location specified in the XML configuration file, which in this example is ```\\Server\Office2013```.|
-
-#### Customizable attributes and elements of the XML file
-
-|Input and description|Example|
-|---|---|
-|Add element: Specifies the products and languages to include in the package.|N/A|
-|OfficeClientEdition (attribute of Add element): Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if **OfficeClientEdition** isn't set to a valid value.|```OfficeClientEdition="32"``` ```OfficeClientEdition="64"```|
-|Product element: Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.|```Product ID="O365ProPlusRetail"``` ```Product ID="VisioProRetail"``` ```Product ID="ProjectProRetail"``` ```Product ID="ProPlusVolume"``` ```Product ID="ProjectProVolume"```|
-|Language element: Specifies the language supported in the applications.|```Language ID="en-us"```|
-|Version (attribute of Add element): Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).|```15.1.2.3```|
-|SourcePath (attribute of Add element): Specifies the location where the applications will be saved to.|```Sourcepath="\Server\Office2013”```|
-
-### Convert the Office applications into an App-V package
-
-After you download the Office 2013 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2013 App-V package. You'll need to make sure to have the right procedure depending on your licensing model.
-
-#### What you'll need to do
-
-* Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8, and Windows 10/11 computers.
-* Create an Office App-V package for either the Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, then modify the **Customconfig.xml** configuration file.
-
- The following table summarizes the values you need to enter in the **Customconfig.xml** file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
-
-|Product ID|Volume Licensing|Subscription Licensing|
-|---|---|---|
-|Office 2013|ProPlusVolume|O365ProPlusRetail|
-|Office 2013 with Visio 2013|ProPlusVolume VisioProVolume|O365ProPlusRetail VisioProRetail|
-|Office 2013 with Visio 2013 and Project 2013|ProPlusVolume VisioProVolume ProjectProVolume|O365ProPlusRetail VisioProRetail ProjectProRetail|
-
-#### How to convert the Office applications into an App-V package
-
-1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
-
- * **SourcePath**: Point to the Office applications downloaded earlier.
- * **ProductID**: Specify the type of licensing, as shown in the following examples:
- * Subscription Licensing:
- ```XML
-
-
-
-
-
-
-
-
-
-
- ```
- In this example, the following changes were made to create a package with Subscription licensing:
-
- * **SourcePath** is the path, which was changed to point to the Office applications that were downloaded earlier.
- * **Product ID** for Office was changed to `O365ProPlusRetail`.
- * **Product ID** for Visio was changed to `VisioProRetail`.
- * Volume Licensing
- ```XML
-
-
-
-
-
-
-
-
-
-
- ```
- In this example, the following changes were made to create a package with Volume licensing:
-
- * **SourcePath** is the source's path, which was changed to point to the Office applications that were downloaded earlier.
- * **Product ID** for Office was changed to `ProPlusVolume`.
- * **Product ID** for Visio was changed to `VisioProVolume`.
- * **ExcludeApp** (optional) lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
- * **PACKAGEGUID** (optional)—By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
-
- An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
-
- > [!NOTE]
- >Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
-2. Use the **/packager** command to convert the Office applications to an Office 2013 App-V package.
-
- For example:
-
- ```PowerShell
- \\server\Office2013\setup.exe /packager \\server\Office2013\Customconfig.xml \\server\share\Office2013AppV
- ```
-
- In the example:
-
- |Element|Description|
- |---|---|
- |```\\server\Office2013```|This network share location is the one that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is named **Customconfig.xml**.|
- |```setup.exe```|This element is the Office Deployment Tool.|
- |```/packager```|This element creates the Office 2013 App-V package with Volume Licensing as specified in the **Customconfig.xml** file.|
- |```\\server\Office2013\Customconfig.xml```|This element passes the configuration XML file, which in this example is named "Customconfig," that has been prepared for the packaging stage.|
- |```\\server\share\Office2013AppV```|This element specifies the location of the newly created Office App-V package.|
-
- After you run the **/packager** command, the following folders will appear in the directory where you specified the package should be saved:
-
- * **App-V Packages**, which contains an Office 2013 App-V package and two deployment configuration files.
- * **WorkingDir**
-
- > [!NOTE]
- >To troubleshoot any issues, see the log files in the %temp% directory (default).
-3. Verify that the Office 2013 App-V package works correctly:
-
- 1. Publish the Office 2013 App-V package that you created globally to a test computer and verify that the Office 2013 shortcuts appear.
- 2. Start a few Office 2013 applications, such as Excel or Word, to test that your package is working as expected.
-
-## Publishing the Office package for App-V
-
-Use the following information to publish an Office package.
-
-### Methods for publishing Office App-V packages
-
-Deploy the App-V package for Office 2013 by using the same methods you use for any other package:
-
-* Microsoft Configuration Manager
-* App-V Server
-* Stand-alone through Windows PowerShell commands
-
-### Publishing prerequisites and requirements
-
-|Prerequisite or requirement|Details|
-|---|---|
-|Enable Windows PowerShell scripting on the App-V clients.|To publish Office 2013 packages, you must run a script. Package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command: ```Set-AppvClientConfiguration –EnablePackageScripts 1```|
-|Publish the Office 2013 package globally.|Extension points in the Office App-V package require installation at the computer level. When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.|
-
-### How to publish an Office package
-
-Run the following command to publish an Office package globally, with the bracketed value replaced by the path to the App-V package:
-
-```PowerShell
-Add-AppvClientPackage | Publish-AppvClientPackage –global
-```
-
-* From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
-
-## Customizing and managing Office App-V packages
-
-To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
-
-* [Enabling Office plug-ins by using connection groups](#enabling-office-plug-ins-by-using-connection-groups)
-* [Disabling Office 2013 applications](#disabling-office-2013-applications)
-* [Disabling Office 2013 shortcuts](#disabling-office-2013-shortcuts)
-* [Managing Office 2013 package upgrades](#managing-office-2013-package-upgrades)
-* [Managing Office 2013 licensing upgrades](#managing-office-2013-licensing-upgrades)
-* [Deploying Visio 2013 and Project 2013 with Office](#deploying-visio-2013-and-project-2013-with-office)
-
-### Enabling Office plug-ins by using connection groups
-
-Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You can't use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
-
-#### To enable plug-ins for Office App-V packages
-
-1. Add a Connection Group through App-V Server, Microsoft Configuration Manager, or a Windows PowerShell cmdlet.
-2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It's a good idea to use Microsoft 365 Apps for enterprise (non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
-3. Create an App-V package that includes the desired plug-ins.
-4. Add a Connection Group through App-V Server, Configuration Manager, or a Windows PowerShell cmdlet.
-5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created.
-
- >[!IMPORTANT]
- >The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, then add the plug-in App-V package.
-6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package.
-7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2013 App-V package has.
-
- Since the Office 2013 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as **Integrated** and that both **InProcessEnabled** and **OutOfProcessEnabled** match the settings of the Office 2013 App-V package you published.
-8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
-9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the updated file.
-10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2013 App-V package is in use when the Connection Group is enabled. If that happens, you'll have to reboot to successfully enable the Connection Group.
-11. After you successfully publish both packages and enable the Connection Group, start the target Office 2013 application and verify that the plug-in you published and added to the Connection Group works as expected.
-
-### Disabling Office 2013 applications
-
-You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You don't have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you'll save the changes, add the Office 2013 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
-
->[!NOTE]
->To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool#excludeapp-element).
-
-#### To disable an Office 2013 application
-
-1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
-2. Search for the Office application you want to disable, for example, Access 2013.
-3. Change the value of "Enabled" from "true" to "false."
-4. Save the Deployment Configuration File.
-5. Add the Office 2013 App-V Package with the new Deployment Configuration File.
-
- ``` XML
-
-
- InfoPath Filler 2013
-
-
-
-
-
-
- Lync 2013
-
-
-
-
-
-
- Access 2013
-
-
-
-
- ```
-6. Re-add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
-
-### Disabling Office 2013 shortcuts
-
-You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
-
-1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
-2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
-
- ```XML
- Shortcuts
-
- -->
-
-
-
-
- [{Common Programs}]\Microsoft Office 2013\Access 2013.lnk
- [{AppvPackageRoot}])office15\MSACCESS.EXE
- [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
-
-
- Microsoft.Office.MSACCESS.EXE.15
- true
- Build a professional app quickly to manage data.
- l
- [{AppVPackageRoot}]\office15\MSACCESS.EXE
-
- ```
-3. Save the Deployment Configuration File.
-4. Republish Office 2013 App-V Package with new Deployment Configuration File.
-
-Many more settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
-
-### Managing Office 2013 package upgrades
-
-To upgrade an Office 2013 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2013 package, perform the following steps.
-
-#### How to upgrade a previously deployed Office 2013 package
-
-1. Create a new Office 2013 package through the Office Deployment Tool that uses the most recent Office 2013 application software. The most recent Office 2013 bits can always be obtained through the download stage of creating an Office 2013 App-V Package. The newly created Office 2013 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
-
- > [!NOTE]
- > Office App-V packages have two Version IDs:
- > * An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
- > * A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
-2. Globally publish the newly created Office 2013 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2013 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
-3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
-
-### Managing Office 2013 licensing upgrades
-
-If a new Office 2013 App-V Package has a different license than the Office 2013 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2013 and the new Office 2013 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
-
-#### How to upgrade an Office 2013 License
-
-1. Unpublish the already deployed Office 2013 Subscription Licensing App-V package.
-2. Remove the unpublished Office 2013 Subscription Licensing App-V package.
-3. Restart the computer.
-4. Add the new Office 2013 App-V Package Volume Licensing.
-5. Publish the added Office 2013 App-V Package with Volume Licensing.
-
-An Office 2013 App-V Package with your chosen licensing will be successfully deployed.
-
-### Deploying Visio 2013 and Project 2013 with Office
-
-This section describes the requirements and options for deploying Visio 2013 and Project 2013 with Office.
-
-* **To package and publish Visio 2013 and Project 2013 with Office**: Include Visio 2013 and Project 2013 in the same package with Office. If you aren’t deploying Office, you can create a package that contains Visio and/or Project.
-* **To deploy Visio 2013 and Project 2013 to specific users**: Use one of the following methods:
-
-|Goal|Method|
-|---|---|
-|Create two different packages and deploy each one to a different group of users|Create and deploy the following packages: A package that contains only Office—deploy to computers whose users need only Office. A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.|
-|Create just one package for the whole organization, or for users who share computers|Follow these steps: 1. Create a package that contains Office, Visio, and Project. 2. Deploy the package to all users. 3. Use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
-
-## Additional resources
-
-### Additional resources for Office 2013 App-V Packages
-
-* [Office 2013 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778)
-
-### Additional resources for Connection Groups
-
-* [Managing Connection Groups](appv-managing-connection-groups.md)
-* [Connection groups on the App-V team blog](/archive/blogs/gladiator/app-v-5-more-on-connection-groups)
-
-### Additional resources for Dynamic Configuration
-
-* [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
diff --git a/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md b/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md
deleted file mode 100644
index e76a52b47d5..00000000000
--- a/windows/application-management/app-v/appv-deploying-microsoft-office-2016-with-appv.md
+++ /dev/null
@@ -1,383 +0,0 @@
----
-title: Deploying Microsoft Office 2016 by using App-V (Windows 10/11)
-description: Use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying Microsoft Office 2016 by using App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the information in this article to use Application Virtualization (App-V) to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md).
-
-## What to know before you start
-
-Before you deploy Office 2016 with App-V, review the following planning information.
-
-### Supported Office versions and Office coexistence
-
-Use the following table to get information about supported versions of Office and running coexisting versions of Office.
-
-|Information to review|Description|
-|---|---|
-|[Supported versions of Microsoft Office](appv-planning-for-using-appv-with-office.md#supported-versions-of-microsoft-office)|Supported versions of Office and deployment types (for example, desktop, personal Virtual Desktop Infrastructure (VDI), and pooled VDI), and Office licensing options.|
-|[Planning for using App-V with coexisting versions of Office](appv-planning-for-using-appv-with-office.md#before-you-implement-office-coexistence)|Considerations for installing different versions of Office on the same computer.|
-
-### Packaging, publishing, and deployment requirements
-
-Before you deploy Office with App-V, review the following requirements.
-
-|Task|Requirement|
-|-----------|-------------------|
-| Packaging. | All Office applications that you deploy to users must be in a single package. In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation. If you're deploying Microsoft Visio 2016 and Microsoft Project 2016 at the same time as Office, you must put them all in the same package. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office). |
-| Publishing. | You can only publish one Office package per client computer. You must publish the Office package globally, not to the user. |
-| Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer with Remote Desktop Services. | You must enable [shared computer activation](/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). |
-
-### Excluding Office applications from a package
-
-The following table describes the recommended methods for excluding specific Office applications from a package.
-
-|Task|Details|
-|-------------|---------------|
-| Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool. | With this setting, you can exclude specific Office applications from the package that the Office Deployment Tool creates. For example, you can use this setting to create a package that contains only Microsoft Word. For more information, see [ExcludeApp element](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ad=US&rs=en-US&ui=en-US#excludeapp-element). |
-| Modify the DeploymentConfig.xml file | Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client. For more information, see [Disabling Office 2016 applications](#disabling-office-2016-applications). |
-
-## Creating an Office 2016 package for App-V with the Office Deployment Tool
-
-Complete the following steps to create an Office 2016 package for App-V.
-
->[!IMPORTANT]
->In App-V 5.0 and later, you must use the Office Deployment Tool to create a package. You can't use the Sequencer to create packages.
-
-### Review prerequisites for using the Office Deployment Tool
-
-The computer on which you're installing the Office Deployment Tool must have the following:
-
-| Prerequisite | Description |
-|----------------------|--------------------|
-| Prerequisite software | .NET Framework 4 |
-| Supported operating systems | 64-bit version of Windows 10/11 64-bit version of Windows 8 or 8.1 64-bit version of Windows 7 |
-
->[!NOTE]
->In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
-
-### Create Office 2016 App-V packages with the Office Deployment Tool
-
-You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with subscription licensing.
-
-Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10/11 computers.
-
-### Download the Office Deployment Tool
-
-Office 2016 App-V packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package can't be created or modified through the App-V sequencer. To begin package creation, follow these steps:
-
-1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
-
- >[!IMPORTANT]
- >You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.
-2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
-
- Example location: \\\\Server\\Office2016
-3. Check that the **setup.exe** and **configuration.xml** files exist and are in the location you specified.
-
-### Download Office 2016 applications
-
-After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.
-
-The XML file included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
-
-1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
- 1. Open the sample XML file in Notepad or your favorite text editor.
- 2. With the sample **configuration.xml** file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the **configuration.xml** file:
-
- ```XML
-
-
-
-
-
-
-
-
-
-
- ```
-
- > [!NOTE]
- >The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To uncomment these lines, remove the `````` from the end of the line.
-
- The previous example of an XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office2016 location where Office applications will be saved. The Product ID of the applications won't affect Office's final licensing. You can create Office 2016 App-V packages with various licensing from the same applications by specifying licensing in a later stage. The following table summarizes the XML file's customizable attributes and elements:
-
- | Input | Description | Example |
- |--------------|----------------------------|----------------|
- | Add element | Specifies which products and languages the package will include. | N/A |
- | **OfficeClientEdition** (attribute of **Add** element) | Specifies whether Office 2016 32-bit or 64-bit edition will be used. **OfficeClientEdition** must be set to a valid value for the operation to succeed. | `OfficeClientEdition="32"` `OfficeClientEdition="64"` |
- | Product element | Specifies the application. Project 2016 and Visio 2016 must be specified here as added products to include them in the applications. For more information about Product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](/office365/troubleshoot/installation/product-ids-supported-office-deployment-click-to-run). | `Product ID ="O365ProPlusRetail"` `Product ID ="VisioProRetail"` `Product ID ="ProjectProRetail"` |
- | Language element | Specifies which language the applications support. | `Language ID="en-us"` |
- | Version (attribute of **Add** element) | Optional. Specifies which build the package will use. Defaults to latest advertised build (as defined in v32.CAB at the Office source). | `16.1.2.3` |
- | SourcePath (attribute of **Add** element) | Specifies the location the applications will be saved to. | `Sourcepath = "\\Server\Office2016"` |
- | Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation. The default is **Deferred** for Microsoft 365 Apps for enterprise and **Current** for Visio Pro for Office 365 and Project Desktop Client. For more information about update channels, see [Overview of update channels for Microsoft 365 Apps for enterprise](/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"` `Channel="Deferred"` `Channel="FirstReleaseDeferred"` `Channel="FirstReleaseCurrent"` |
-
-After editing the **configuration.xml** file to specify the desired product, languages, and the location where the Office 2016 applications will be saved to, you can save the configuration file under a name of your choice, such as "Customconfig.xml."
-2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2016 applications that will later be converted into an App-V package. An example command is:
-
- `\\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml`
-
- The following table describes the example command's elements:
-
- | Element | Description |
- |-------------------------------|--------------------------------------|
- | ```\\server\Office2016``` | This network share location is the one that contains the Office Deployment Tool and the custom **Configuration.xml** file, which in this example is **Customconfig.xml**. |
- | ``Setup.exe`` | This element is the Office Deployment Tool. |
- | ```/download``` | Downloads the Office 2016 applications that you specify in the **Customconfig.xml** file. |
- | ```\\server\Office2016\Customconfig.xml```| This element passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After the download command is used, Office applications should be found in the location specified in the configuration file, which in this example is ```\\Server\Office2016```. |
-
-### Convert the Office applications into an App-V package
-
-After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.
-
-#### What you’ll need to do
-
-* Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10/11 computers.
-* Create an Office App-V package for either Subscription Licensing package by using the Office Deployment Tool, and then modify the **Customconfig.xml** configuration file.
-
- The following table summarizes the values you need to enter in the **Customconfig.xml** file. The steps in the sections that follow the table will specify the exact entries you need to make.
-
->[!NOTE]
->You can use the Office Deployment Tool to create App-V packages for Microsoft 365 Apps for enterprise. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
-
-| Product ID | Subscription licensing |
-|---|---|
-| Office 2016| O365ProPlusRetail |
-| Office 2016 with Visio 2016 | O365ProPlusRetail VisioProRetail |
-| Office 2016 with Visio 2016 and Project 2016 | O365ProPlusRetail VisioProRetail ProjectProRetail |
-
-#### How to convert the Office applications into an App-V package
-
-1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
-
- * **SourcePath**: Change to the location where you saved the Office applications you downloaded during setup.
- * **ProductID**: Specify the type of licensing, as shown in the following example:
-
- * Subscription Licensing:
- ```XML
-
-
-
-
-
-
-
-
-
-
- ```
- This example made the following changes to create this Subscription Licensing package:
-
- * **SourcePath** was changed to point to the Office applications that were downloaded earlier.
- * **Product ID** for Office was changed to `O365ProPlusRetail`.
- * **Product ID** for Visio was changed to `VisioProRetail`.
- * **ExcludeApp** (optional): Lets you specify Office programs that you don’t want included in the App-V package created by the Office Deployment Tool. For example, you can exclude Access.
- * **PACKAGEGUID** (optional): By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use **PACKAGEGUID** to specify a different package ID for each package, which allows you to publish multiple App-V packages created by the Office Deployment Tool, and then manage your published packages with the App-V Server.
-
- An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
-
- > [!NOTE]
- >Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
-2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
-
- An example packager command is:
-
- ```syntax
- \\server\Office2016\setup.exe /packager \\server\Office2016\Customconfig.xml \\server\share\Office2016AppV
- ```
-
- The following table describes each element used in the example command:
-
- | Element | Description |
- |-------------------------------|--------------------------------------|
- |```\\server\Office2016```|This network share location is the one that contains the Office Deployment Tool and the custom Configuration.xml file, which in this example is Customconfig.xml.|
- |```Setup.exe```|This element is the Office Deployment Tool.|
- |```/packager```|This command creates the Office 2016 App-V package with the license type specified in the Customconfig.xml file.|
- |```\\server\Office2016\Customconfig.xml```|This element passes the configuration XML file that has been prepared for the packaging stage. In this example, the file is Customconfig.xml.|
- |```\\server\share\Office2016AppV```|This element specifies the location of the newly created Office App-V package.|
-
- After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
-
- * **App-V Packages**—contains an Office 2016 App-V package and two deployment configuration files.
- * **WorkingDir**
-
- > [!NOTE]
- >To troubleshoot any issues, see the log files in the %temp% directory (default).
-3. Verify that the Office 2016 App-V package works correctly:
-
- 1. Publish the Office 2016 App-V package that you created globally to a test computer and verify that the Office 2016 shortcuts appear.
- 2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
-
-## Publishing the Office package for App-V
-
-Use the following information to publish an Office package.
-
-### Methods for publishing Office App-V packages
-
-Deploy the App-V package for Office 2016 by using the same methods as the other packages that you've already deployed:
-
-* Microsoft Configuration Manager
-* App-V Server
-* Stand-alone through Windows PowerShell commands
-
-### Publishing prerequisites and requirements
-
-| Prerequisite or requirement | Details |
-|---------------------------------------|--------------------|
-| Enable Windows PowerShell scripting on the App-V clients. | To publish Office 2016 packages, you must run a script. However, package scripts are disabled by default on App-V clients. To enable scripting, run the following Windows PowerShell command: `Set-AppvClientConfiguration -EnablePackageScripts 1` |
-| Publish the Office 2016 package globally. | Extension points in the Office App-V package require installation at the computer level. When you publish at the computer level, no prerequisite actions or redistributables are needed. The Office 2016 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages. |
-
-### How to publish an Office package
-
-Run the following command to publish an Office package globally:
-
-```PowerShell
-Add-AppvClientPackage | Publish-AppvClientPackage -global
-```
-
-* You can add permissions to a group of computers instead of just a user group through the Web Management Console on the App-V Server. This feature lets packages be published globally to the computers in the corresponding group.
-
-## Customizing and managing Office App-V packages
-
-To manage your Office App-V packages, use the same operations as you would for any other package, with a few exceptions as outlined in the following sections.
-
-* [Enabling Office plug-ins by using connection groups](#enabling-office-plug-ins-by-using-connection-groups)
-* [Disabling Office 2016 applications](#disabling-office-2016-applications)
-* [Disabling Office 2016 shortcuts](#disabling-office-2016-shortcuts)
-* [Managing Office 2016 package upgrades](#managing-office-2016-package-upgrades)
-* [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office)
-
-### Enabling Office plug-ins by using connection groups
-
-The following steps will tell you how to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that only contains the plug-ins (you can't use the Office Deployment Tool to create the plug-ins package). After that, create a connection group that contains the Office package and the plug-ins package.
-
-#### Enable plug-ins for Office App-V packages
-
-1. Add a Connection Group through App-V Server, Microsoft Configuration Manager, or a Windows PowerShell cmdlet.
-2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer that will be used to sequence the plug-in. We recommend that you use Microsoft 365 Apps for enterprise (non-virtual) on the sequencing computer when sequencing Office 2016 plug-ins.
-3. Create an App-V package that includes the plug-ins you want.
-4. Add a Connection Group through the App-V Server, Configuration Manager, or a Windows PowerShell cmdlet.
-5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.
-
- >[!IMPORTANT]
- >The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.
-6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match published Office 2016 App-V package's global settings.
-7. Verify that the plug-in package's Deployment Configuration file has the same settings as the Office 2016 App-V package.
-
- The Office 2016 App-V plug-in package's settings must match those of the operating system to allow for integration. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2016 App-V package you published.
-8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
-9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
-10. Ensure that the Connection Group you created on your desired computer is enabled. The Connection Group created will be shown as "pending" if the Office 2016 App-V package is being used while the Connection Group is enabled. If that happens, you'll have to reboot the computer to successfully enable the Connection Group.
-11. After you successfully publish both packages and enable the Connection Group, verify the plug-ins you published on the Connection Group work as expected.
-
-### Disabling Office 2016 applications
-
-You can also disable specific applications in your Office App-V package. For example, if you don't want to use Access, you can disable Access while leaving all other Office applications available. When you disable an application, the user will no longer see its shortcut icon. You don't need to re-sequence the application to disable it. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, just save the changes and add the Office 2016 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
-
->[!NOTE]
->To exclude specific Office applications when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
-
-#### Disable an Office 2016 application
-
-1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
-2. Search for the Office application you want to disable, for example, Access 2016.
-3. Change the value of **Enabled** to **false**.
-4. Save the Deployment Configuration File.
-5. Add the Office 2016 App-V Package with the new Deployment Configuration File.
-
- ```XML
-
-
- Lync 2016
-
-
-
-
-
-
- Access 2016
-
-
-
-
- ```
-6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
-
-### Disabling Office 2016 shortcuts
-
-You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
-
-#### Disable shortcuts for Office 2016 applications
-
-1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
-2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. The following example shows how to delete the Microsoft Access shortcuts while keeping the subsystems `` intact.
-
- ``` XML
- Shortcuts
-
- -->
-
-
-
-
- [{Common Programs}]\Microsoft Office 2016\Access 2016.lnk
- [{AppvPackageRoot}])office16\MSACCESS.EXE
- [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
-
-
- Microsoft.Office.MSACCESS.EXE.16
- true
- Build a professional app quickly to manage data.
- l
- [{AppVPackageRoot}]\office16\MSACCESS.EXE
-
- ```
-3. Save the Deployment Configuration File.
-4. Republish the Office 2016 App-V Package with the new Deployment Configuration File.
-
-Many more settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
-
-### Managing Office 2016 package upgrades
-
-To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the steps outlined in the following section.
-
-#### How to upgrade a previously deployed Office 2016 package
-
-1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
-
- > [!NOTE]
- >Office App-V packages have two Version IDs:
- >* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
- >* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
-2. Globally publish the newly created Office 2016 App-V Packages onto the computers you want to apply the new updates to. Since the new package has the same lineage as the older Office 2016 App-V Package, publishing will be fast, as publishing the new package with the updates only applies the new changes to the old package.
-3. Upgrades will be applied in the same manner of any globally published App-V packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
-
-### Deploying Visio 2016 and Project 2016 with Office
-
-The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.
-
-| Task | Details |
-|---------------------|---------------|
-| How do I package and publish Visio 2016 and Project 2016 with Office? | You must include Visio 2016 and Project 2016 in the same package with Office. If you're not deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic. |
-| How can I deploy Visio 2016 and Project 2016 to specific users? | Use one of the following methods: **To create two different packages and deploy each one to a different group of users**: Create and deploy the following packages: - A package that contains only Office—deploy to computers whose users need only Office. - A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.
**To create only one package for the whole organization, or to create a package intended for users who share computers**: 1. Create a package that contains Office, Visio, and Project. 2. Deploy the package to all users. 3. Use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project. |
-
-## Related articles
-
-* [Deploying App-V for Windows client](appv-deploying-appv.md)
-* [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
-* [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
-* [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
diff --git a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md
deleted file mode 100644
index f9ba5b9a574..00000000000
--- a/windows/application-management/app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Deploying App-V packages by using electronic software distribution (ESD)
-description: Deploying App-V packages by using electronic software distribution (ESD)
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying App-V packages by using electronic software distribution (ESD)
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can deploy App-V packages using an electronic software distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
-
-To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682125(v=technet.10)#BKMK_Appv)
-
-## How to deploy virtualized packages using an ESD
-
-To learn more about how to deploy virtualized packages using an ESD, see [How to deploy App-V packages using electronic software distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md).
-
-## How to enable only administrators to publish packages by using an ESD
-
-To learn how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD, see [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md).
-
-## Related articles
-
-- [App-V and Citrix integration](https://www.microsoft.com/download/details.aspx?id=40885)
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md b/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md
deleted file mode 100644
index d9f21502187..00000000000
--- a/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Deploying the App-V Sequencer and configuring the client (Windows 10/11)
-description: Learn how to deploy the App-V Sequencer and configure the client by using the ADMX template and Group Policy.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying the App-V Sequencer and configuring the client
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-The App-V Sequencer and client let administrators virtualize and run virtual applications.
-
-## Enable the client
-
-The App-V client is the component that runs a virtualized application on a target computer. The client lets users interact with icons and file types, starting virtualized applications. The client can also get the virtual application content from the management server.
-
->[!NOTE]
->Starting with Windows 10 version 1607, App-V is included with the operating system. You only need to enable it.
-
-[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
-
-## Client configuration settings
-
-The App-V client stores its configuration in the registry. Understanding the format used in the data registry can help you learn useful information about the client. For information about client settings that you can configure through Windows PowerShell or through the registry, see [About client configuration settings](appv-client-configuration-settings.md).
-
-## Configure the client by using the ADMX template and Group Policy
-
-You can use Group Policy to configure the client settings for the App-V client and the Remote Desktop Services client.
-
-To manage the ADMX template, perform the following steps on the computer that you'll use to manage Group Policy. This computer is typically the Domain Controller.
-
-1. Save the **.admx** file to the following directory: ```Windows\PolicyDefinitions```
-2. Save the **.adml** file to the following directory: ```Windows\PolicyDefinitions\```
-
-After you've completed the preceding steps, you can use Group Policy to configure the client settings by using the Group Policy Management Console under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
-
-## Understanding Shared Content Store mode for App-V clients
-
-App-V Shared Content Store (SCS) mode lets SCS App-V clients run virtualized applications without having to save any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V client are supported with SCS mode.
-
->[!IMPORTANT]
->If the App-V client is configured to run in the SCS mode, the location where the App-V packages are streamed from must be available, otherwise, the virtualized package will fail. Additionally, we do not recommend deployment of virtualized applications to computers that run the App-V client in the SCS mode across the internet.
-
-Additionally, the SCS isn't a physical location that contains virtualized packages. It's a mode that allows the App-V client to stream the required virtualized package data across the network.
-
-The SCS mode is helpful in the following scenarios:
-
-* Virtual desktop infrastructure (VDI) deployments
-* Remote Desktop Services deployments
-
-To use SCS in your environment, you must configure the App-V client to run in SCS mode, as it doesn't use SCS mode by default.
-
-There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V client in SCS mode. This pre-load operation can be rendered a successful one with Windows PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using Windows PowerShell commands. The package wouldn't stream across the network because it would be locally stored.
-
-### Configure the Group Policy setting for the SCS Mode for App-V clients
-
-Use the following steps to locate and configure the Group Policy setting for the SCS Mode for App-V clients.
-
-1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
-2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
-
-### Configure an individual client to use SCS mode
-
-To configure the App-V client to run in SCS mode, on the client, enter the following Windows PowerShell command:
-
-```PowerShell
-Set-AppvClientConfiguration -SharedContentStoreMode 1
-```
-
-## Deploy the Sequencer
-
-The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V client. The Sequencer helps provide a predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.
-
-For a list of changes in the App-V Sequencer, see [What's new in App-V](appv-about-appv.md).
-
-To deploy the sequencer, see [How to install the Sequencer](appv-install-the-sequencer.md).
-
-## App-V client and Sequencer logs
-
-You can use the App-V Sequencer log information to troubleshoot Sequencer installation and operational events while using App-V. The Sequencer-related log information can be reviewed with the **Event Viewer**. The following file path is the specific path for Sequencer-related events:
-
-**Event Viewer\Applications and Services Logs\Microsoft\App V**.
-
->[!NOTE]
->Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**.
-
-
-
diff --git a/windows/application-management/app-v/appv-deploying-the-appv-server.md b/windows/application-management/app-v/appv-deploying-the-appv-server.md
deleted file mode 100644
index 35e22a14003..00000000000
--- a/windows/application-management/app-v/appv-deploying-the-appv-server.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: Deploying the App-V Server (Windows 10/11)
-description: Learn how to deploy the Application Virtualization (App-V) Server in App-V for Windows 10/11 by using different deployment configurations described in this article.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Deploying the App-V server
-
->Applies to: Windows Server 2016
-
-You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V security considerations](appv-security-considerations.md).
-
->[!NOTE]
->If you plan to use the App-V server components in your deployment, note that the version number is still listed as App-V 5.x, as the App-V server components have not changed in App-V for Windows client.
-
-To learn more about deploying App-V for Windows client, read [What's new in App-V](appv-about-appv.md).
-
->[!IMPORTANT]
->Before installing and configuring the App-V servers, you must specify the port or ports where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports, as the installer does not modify firewall settings.
-
-## Download and install App-V server components
-
->[!NOTE]
->If you're already using App-V 5.x, you don't need to re-deploy the App-V server components, as they haven't changed since App-V 5.0 was released.
-
-App-V offers the following five server components, each of which serves a specific purpose in an App-V environment.
-
-* **Management server.** Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server.
-
- > [!NOTE]
- > If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you may want to take advantage of the reporting and streaming capabilities in App-V.
-
-* **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. For more information about the management database, see [How to deploy the App-V server](appv-deploy-the-appv-server.md).
-
-* **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. To learn how to configure the publishing server, see [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md).
-
-* **Reporting server.** Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. To learn more about App-V's reporting capabilities, see [About App-V reporting](appv-reporting.md).
-
-* **Reporting database.** Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. To learn more about the reporting database, see [How to deploy the App-V server](appv-deploy-the-appv-server.md).
-
-All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from either of the following locations:
-
-* The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from this site.
-* The [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx) if you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home).
-
-In large organizations, you might want to install more than one instance of the server components to get the following benefits.
-
-* Fault tolerance for situations when one of the servers is unavailable.
-* High availability to balance server requests. A network load balancer can also help you achieve this.
-* Scalability to support high loads. For example, you can install additional servers behind a network load balancer.
-
-## App-V standalone deployment
-
-The App-V standalone deployment's topology is good for small deployments or test environments. In this implementation type, all server components are installed on a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. However, because services and associated databases will compete for the computer's resources, it's not a good idea to use the standalone deployment for larger deployments.
-
-The following articles will give you more information about how to set up an App-V standalone deployment.
-
-* [How to deploy the App-V server](appv-deploy-the-appv-server.md)
-* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md)
-
-## App-V server distributed deployment
-
-The distributed deployment topology can support a large App-V client base, allowing you to more easily manage and scale your environment. When you use this type of deployment the App-V server components are deployed across multiple computers, based on your organization's structure and requirements.
-
-* [How to install the management and reporting databases on separate computers from the management and reporting services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
-* [How to install the management server on a standalone computer and connect it to the database](appv-install-the-management-server-on-a-standalone-computer.md)
-* [How to deploy the App-V server using a script](appv-deploy-the-appv-server-with-a-script.md)
-* [How to install the publishing server on a remote computer](appv-install-the-publishing-server-on-a-remote-computer.md)
-* [How to install the management server on a standalone computer and connect it to the database](appv-install-the-management-server-on-a-standalone-computer.md)
-
-## Using an Enterprise Software Distribution (ESD) solution and App-V
-
-You can also deploy packages with an ESD. Its full integration capabilities will vary depending on which ESD you use.
-
->[!NOTE]
->The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
-
-* [Deploying App-V packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
-
-## App-V Server logs
-
-You can use App-V server log information to help troubleshoot the server installation and operational events while using App-V. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
-
-**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**
-
-Associated setup logs are saved in the following directory:
-
-**%temp%**
-
-## App-V reporting
-
-App-V reporting allows App-V clients to collect data and then send it back to be stored in a central repository. You can use this information to get a better view of the virtual application usage within your organization. The following list displays some of the types of information the App-V client collects:
-
-* Information about the computer running the App-V client.
-* Information about virtualized packages on a specific computer running the App-V client.
-* Information about package open and shutdown for a specific user.
-
-The reporting information will be maintained until it is successfully sent to the reporting server database. After the data is in the database, you can use Microsoft SQL Server Reporting Services (SSRS) to generate any necessary reports.
-
-If you want to retrieve report information, you must use Microsoft SQL SSRS, which is available with Microsoft SQL. SSRS must be deployed separately to generate the associated reports, as it isn't automatically installed during App-V server installation.
-
-For more information, see [About App-V reporting](appv-reporting.md) and [How to enable reporting on the App-V client by using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
-
-## Other App-V server resources
-
-* [Deploying App-V](appv-deploying-appv.md)
-
-
-
-
diff --git a/windows/application-management/app-v/appv-deployment-checklist.md b/windows/application-management/app-v/appv-deployment-checklist.md
deleted file mode 100644
index 0b06042ae16..00000000000
--- a/windows/application-management/app-v/appv-deployment-checklist.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: App-V Deployment Checklist (Windows 10/11)
-description: Use the App-V deployment checklist to understand the recommended steps and items to consider when deploying App-V features.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# App-V Deployment Checklist
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This checklist outlines the recommended steps and items to consider when deploying App-V features. Use it to organize your priorities while you deploy App-V. You can copy this checklist into a spreadsheet program and customize it for your use.
-
-|Status|Task|References|Notes|
-|---|---|---|---|
-||Prepare the computing environment for App-V deployment during your planning phase.|[App-V planning checklist](appv-planning-checklist.md)||
-||Review App-V's supported configurations.|[App-V supported configurations](appv-supported-configurations.md)||
-||Run App-V Setup to deploy the required App-V features for your environment.|[How to install the sequencer](appv-install-the-sequencer.md) [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) [How to deploy the App-V server](appv-deploy-the-appv-server.md)||
-
->[!NOTE]
->Keep track of server names and associated URLs you create during installation. You'll need this information throughout the installation process.
-
-
-
-
-
-## Related articles
-
-* [Deploying App-V](appv-deploying-appv.md)
diff --git a/windows/application-management/app-v/appv-dynamic-configuration.md b/windows/application-management/app-v/appv-dynamic-configuration.md
deleted file mode 100644
index d6073f10c0b..00000000000
--- a/windows/application-management/app-v/appv-dynamic-configuration.md
+++ /dev/null
@@ -1,617 +0,0 @@
----
-title: About App-V Dynamic Configuration (Windows 10/11)
-description: Learn how to create or edit an existing Application Virtualization (App-V) dynamic configuration file.
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# About App-V dynamic configuration
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-You can use dynamic configuration to customize an App-V package for a user. This article will tell you how to create or edit an existing dynamic configuration file.
-
-When you edit the Dynamic Configuration file, it customizes how an App-V package will run for a user or group. Therefore, package customization is made more convenient by removing the need to resequence packages using the desired settings and provides a way to keep package content and custom settings independent.
-
-## Advanced: dynamic configuration
-
-Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no further customization). If you want to adjust these defaults for a particular user or group, you can create and edit the following files:
-
-- User Configuration file
-- Deployment Configuration file
-
-These .xml files specify package settings let you customize packages without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. These automatically generated configuration files reflect the package's default settings that were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This result provides you with a package-specific template to get started if any of the defaults must be changed.
-
->[!NOTE]
->The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements.
-
-## Dynamic Configuration file contents
-
-All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. The following list represents the relationship between these files in how they'll be read, from most to least precedence:
-
-- User Configuration .xml file
-- Deployment Configuration .xml file
-- Package Manifest
-
-The first item represents what will be read last. Therefore, its content takes precedence. All packages inherently contain and provide default settings from the Package Manifest, but it also has the least precedence. If you apply a Deployment Configuration .xml file with customized settings, it will override the Package Manifest's defaults. If you apply a User Configuration .xml file with customized settings prior to the override of the Package Manifest's defaults, it will override both the deployment configuration and the Package Manifest's defaults.
-
-There are two types of configuration files:
-
-- **User Configuration file (UserConfig)**: Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V client.
-- **Deployment Configuration file (DeploymentConfig)**: Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V client.
-
-You can use the UserConfig file to customize the settings for a package for a specific set of users on a computer or make changes that will be applied to local user locations such as HKCU. You can use the DeploymentConfig file to modify the default settings of a package for all users on a machine or make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the All Users folder.
-
-The UserConfig file provides configuration settings that you can apply to a single user without affecting any other users on a client:
-
-- Extensions that will be integrated into the native system per user: shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM.
-- Virtual Subsystems: Application Objects, Environment variables, Registry modifications, Services, and Fonts.
-- Scripts (user context only).
-
-The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the preceding UserConfig list:
-
-- All UserConfig settings from the preceding section in this topic
-- Extensions that can only be applied globally for all users
-- Virtual Subsystems that can be configured for global machine locations, such as the registry
-- Product Source URL
-- Scripts (Machine context only)
-- Controls to terminate child processes
-
-## File structure
-
-The structure of the App-V Dynamic Configuration file is explained in the following section.
-
-## Dynamic User Configuration file
-
-### Header
-
-An example of a Dynamic User Configuration file's header is:
-
-```xml
-
-
-```
-
-The **PackageId** is the same value that exists in the Manifest file.
-
-### Dynamic User Configuration file body
-
-The Dynamic User Configuration file's body can include all app extension points defined in the Manifest file, and the information to configure virtual applications. There are four subsections allowed in the body:
-
-**Applications**: All app-extensions contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored.
-
-```xml
-
-
-
-
-
-
- …
-
-```
-
-**Subsystems**: AppExtensions and other subsystems are arranged as subnodes under ``, as shown in the following example.
-
-```xml
-
-
- ..
-
- ..
-
-```
-
-Each subsystem can be enabled/disabled using the **Enabled** attribute. The following sections describe the various subsystems and usage samples.
-
-### Dynamic User Configuration file extensions
-
-Extension Subsystems control extensions. These subsystems are Shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM.
-
-Extension Subsystems can be enabled and disabled independently of the content. Therefore, if Shortcuts are enabled, the client will use the shortcuts contained within the manifest by default. Each Extension Subsystem can contain an `` node. If this child element is present, the client will ignore the content in the Manifest file for that subsystem and only use the content in the configuration file.
-
-### Examples of the shortcuts subsystem
-
-#### Example 1
-
-Content will be ignored if the user defined the following syntaxes in either the dynamic or deployment config file:
-
-```xml
-
-
-
-```
-
-#### Example 2
-
-Content in the manifest will be integrated during publishing if the user defined only the following syntax:
-
-```xml
-
- ``
-```
-
-#### Example 3
-
-All shortcuts in the manifest will be ignored and no shortcuts will be integrated if the user defines the following syntaxes:
-
-```xml
-
-
-
-```
-
-### Supported Extension Subsystems
-
-**Shortcuts**: This subsystem controls shortcuts that will be integrated into the local system. The following example has two shortcuts:
-
-```xml
-
-
-
-
-
- \[{Common Programs}\]\\Microsoft Contoso\\Microsoft ContosoApp Filler 2010.lnk
- \[{PackageRoot}\]\\Contoso\\ContosoApp.EXE
- \[{Windows}\]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\inficon.exe
-
-
- ContosoApp.Filler.3
- Fill out dynamic forms to gather and reuse information throughout the organization using Microsoft ContosoApp.
- 0
- 1
- \[{PackageRoot}\]\\Contoso\\ContosoApp.EXE
-
-
-
-
- \[{AppData}\]\\Microsoft\\Contoso\\Recent\\Templates.LNK
- \[{AppData}\]\\Microsoft\\Templates
-
-
-
-
-
- 0
- 1
-
-
-
-
-
-```
-
-**File Type Associations**: Associates file types with programs to open by default and to set up the context menu. (MIME types can also be set up with this subsystem.) An example of a FileType association is:
-
-```xml
-
-
-
-
-
- .docm
- contosowordpad.DocumentMacroEnabled.12
- document
- application/vnd.ms-contosowordpad.document.macroEnabled.12
-
- wincontosowordpad.exe
-
-
- contosowordpad.8
-
-
-
-
-
-
- true
-
-
-
-
-
-
-
- contosowordpad.DocumentMacroEnabled.12
- \[{Windows}\]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\contosowordpadicon.exe,15
- Blah Blah Blah
- \[{FOLDERID\_ProgramFilesX86}\]\\Microsoft Contoso 14\\res.dll,9182
- \[{FOLDERID\_ProgramFilesX86}\]\\Microsoft Contoso 14\\res.dll,1424
- 0
-
- Open
-
- {e56fa627-c35f-4a01-9e79-7d36aed8225a}
- Edit
- &Edit
- "\[{PackageRoot}\]\\Contoso\\WINcontosowordpad.EXE" /vu "%1"
-
-
- {e56fa627-c35f-4a01-9e79-7d36aed8225a}
- Open
- &Open
- "\[{PackageRoot}\]\\Contoso\\WINcontosowordpad.EXE" /n "%1"
-
-
- mscontosowordpad
- ShellSystem
- \[SHELLNOOP\]
- \[SetForeground\]\[ShellNewDatabase "%1"\]
-
-
-
-
-
-
-
-
-```
-
-**URL Protocols**: This subsystem controls the URL Protocols integrated into the local registry of the client machine. The following example illustrates the “mailto:” protocol.
-
-```xml
-
-
-
-
- mailto
-
- \[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE,-9403
- 2
-
-
-
-
-
-
-
- 2
-
-
- open
-
- \[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE
- open
- \[{ProgramFilesX86}\\Microsoft Contoso\\Contoso\\contosomail.EXE" -c OEP.Note /m "%1"
-
-
- 0
- 0
- 2
-
-
- contosomail
- ShellSystem
- \[SHELLNOOP\]
- \[SetForeground\]\[ShellNewDatabase "%1"\]
-
-
-
-
-
-
-
-
-```
-
-**Software Clients**: Allows the app to register as an email client, news reader, or media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases, you only need to enable and disable it. There's also a control that lets you enable or disable the email client only in case you want all the other clients to remain as they are.
-
-```xml
-
-
-
-```
-
-**AppPaths**: If an application, such as contoso.exe, is registered with an apppath name of “myapp”, this subsystem lets you open the app by entering “myapp” into the run menu.
-
-```xml
-
-
-
-
- \[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE
- contosomail.exe
- \[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE
-
- false
-
-
-
-
-
-```
-
-**COM**: Allows an Application to register Local COM servers. Mode can be Integration, Isolated or Off. When Isol.
-
-```xml
-
-```
-
-### Other settings for Dynamic User Configuration file
-
-In addition to Extensions, the following other subsystems can be enabled/disabled and edited.
-
-#### Virtual Kernel Objects
-
-```xml
-
-```xml
-
-**Virtual Registry**: use this if you want to set a registry in the Virtual Registry within HKCU.
-
-```xml
-
-
-
-
-
-
-
-
-
-```
-
-#### Virtual File System
-
-```xml
-
-```
-
-#### Virtual Fonts
-
-```xml
-
-```
-
-#### Virtual Environment Variables
-
-```xml
-
-
-
-
-
-
-
-
-
-```
-
-#### Virtual services
-
-```xml
-
-```
-
-#### UserScripts
-
-Scripts can be used to set up or alter the virtual environment and execute scripts on deployment or removal, before an application executes, or they can clean up the environment after the application terminates. Refer to a sample User Configuration file output by the sequencer to see a sample script. For more information about the various triggers you can use to set up scripts, see the [Scripts](appv-dynamic-configuration.md#scripts) section.
-
-## Dynamic Deployment Configuration file
-
-### Dynamic Deployment Configuration file header
-
-The header of a Deployment Configuration file should look something like this:
-
-```xml
-
-```
-
-The **PackageId** is the same value as the one that exists in the Manifest file.
-
-### Dynamic Deployment Configuration file body
-
-The body of the deployment configuration file includes two sections:
-
-- The User Configuration section allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest.
-- The Machine Configuration section contains information that can only be configured for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS.
-
-```xml
-
-
-..
-
-
-..
-
-..
-
-
-```
-
-User Configuration: For more information about this section, see [Dynamic User Configuration](#dynamic-user-configuration-file).
-
-Machine Configuration: The Machine Configuration section of the Deployment Configuration File configures information that can only be set for an entire machine, not a specific user on the computer, like the HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. This element can have the following four subsections.
-
-#### Subsystems
-
-AppExtensions and other subsystems are arranged as subnodes under ``:
-
-```xml
-
-
- ..
-
- ..
-
-```
-
-The following section describes the various subsystems and usage samples.
-
-#### Extensions
-
-Some subsystems (Extension Subsystems) control extensions that can only apply to all users. The subsystem is application capabilities. Because this subsystem can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The rules for User Configuration extension controls and settings also apply to the ones in Machine Configuration.
-
-#### Application Capabilities
-
-Application Capabilities extension is used by default programs in the Windows OS interface; it allows an application to register itself as capable of opening certain file extensions, as a contender for the Start menu's internet browser slot, and as capable of opening certain Windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI.
-
-```xml
-
-
-
-
- \[{PackageRoot}\]\\LitView\\LitViewBrowser.exe
-
- LitView Browser
- SOFTWARE\\LitView\\Browser\\Capabilities
-
-
-
- @\[{ProgramFilesX86}\]\\LitView\\LitViewBrowser.exe,-12345
- @\[{ProgramFilesX86}\]\\LitView\\LitViewBrowser.exe,-12346
- 0
- Lit View E-Mail Client
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-#### Other settings for Dynamic Deployment Configuration file
-
-You can edit other subsystems in addition to extensions:
-
-- Machine-wide Virtual Registry: Use this subsystem when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine.
-
-```xml
-
-
-
-
-
-
-
-
-
-```
-
-- Machine-wide Virtual Kernel Objects
-
-```xml
-
-
-
-
-
-```
-
-- ProductSourceURLOptOut: Indicates whether the URL for the package can be modified globally through PackageSourceRoot to support branch office scenarios. It's set to False by default. Changes to the value take effect on the next launch.
-
-```xml
-
- ..
-
- ..
-
-```
-
-- MachineScripts: The package can be configured to execute scripts upon deployment, publishing, or removal. To see an example script, see a sample deployment configuration file generated by the sequencer. The following section provides more information about the various triggers you can use to set up scripts.
-
-- TerminateChildProcess: You can use this subsystem to specify that an application executable's child processes will be terminated when the application.exe process is terminated.
-
-```xml
-
- ..
-
-
-
-
-
- ..
-
-```
-
-### Scripts
-
-The following table describes the various script events and the context under which they can be run.
-
-|Script execution time|Can be specified in Deployment Configuration|Can be specified in User Configuration|Can run in the package's virtual environment|Can be run in the context of a specific application|Runs in system/user context: (Deployment Configuration, User Configuration)|
-|---|:---:|:---:|:---:|:---:|:---:|
-|AddPackage|X||||(SYSTEM, N/A)|
-|PublishPackage|X|X|||(SYSTEM, User)|
-|UnpublishPackage|X|X|||(SYSTEM, User)|
-|RemovePackage|X||||(SYSTEM, N/A)|
-|StartProcess|X|X|X|X|(User, User)|
-|ExitProcess|X|X||X|(User, User)|
-|StartVirtualEnvironment|X|X|X||(User, User)|
-|TerminateVirtualEnvironment|X|X|||(User, User)|
-
-### Using multiple scripts on a single event trigger
-
-App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you convert from App-V 4.6 to App-V for Windows client. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is included in the App-V client.
-
-#### How to use multiple scripts on a single event trigger
-
-For each script that you want to run, pass that script as an argument to the ScriptRunner.exe application. The application will run each script separately, along with the arguments that you specify for each script. Use only one script (ScriptRunner.exe) per trigger.
-
->[!NOTE]
->We recommended you first run the multi-script line from a command prompt to make sure all arguments are built correctly before adding them to the deployment configuration file.
-
-#### Example script and parameter descriptions
-
-Using the following example file and table, modify the deployment or user configuration file to add the scripts that you want to run.
-
-```xml
-
-
- ScriptRunner.exe
-
- -appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10
- -appvscript script2.vbs arg1 arg2
- -appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 –rollbackonerror
-
-
-
-
-```
-
-|Parameter in the example file|Description|
-|---|---|
-|``|Name of the event trigger you're running a script for, such as when adding or publishing a package.|
-|`ScriptRunner.exe`|The script launcher application included in the App-V client.
Although ScriptRunner.exe is included in the App-V client, the App-V client's location must be in %path% or ScriptRunner won't run. `ScriptRunner.exe` is typically located in the C:\Program Files\Microsoft Application Virtualization\Client folder.|
-|`-appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10`
`-appvscript script2.vbs arg1 arg2`
`-appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 -rollbackonerror`|`-appvscript`—token that represents the actual script you want to run. `script1.exe`—name of the script you want to run. `arg1 arg2`—arguments for the script you want to run. `-appvscriptrunnerparameters`—token that represents the execution options for script1.exe. `-wait`—token that tells ScriptRunner to wait for execution of script1.exe to finish before proceeding to the next script. `-timeout=x`—token that informs ScriptRunner to stop running the current script after *x* number of seconds. All other specified scripts will still run. `-rollbackonerror`—token that tells ScriptRunner to stop running all scripts that haven't yet run and roll back an error to the App-V client.|
-|``|Waits for overall completion of ScriptRunner.exe.
Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.
If any individual script reported an error and rollbackonerror was set to True, then ScriptRunner should report the error to App-V client.|
-
-ScriptRunner will run any script whose file type is associated with an application installed on the computer. If the associated application is missing, or the script’s file type isn't associated with any of the computer's applications, the script won't run.
-
-### Create a Dynamic Configuration file using an App-V Manifest file
-
-You can create the Dynamic Configuration file using one of three methods: manually, using the App-V Management Console, or by sequencing a package, which will generate a package with two sample files.
-
-For more information about how to create the file using the App-V Management Console, see [How to create a Custom Configuration file by using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md).
-
-To create the file manually, you can combine the components listed in the previous sections into a single file. However, we recommend you use files generated by the sequencer instead of manually created ones.
-
-
-
-
-
-## Related topics
-
-- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
-- [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md b/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
deleted file mode 100644
index 39c355141c7..00000000000
--- a/windows/application-management/app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: How to enable only administrators to publish packages by using an ESD
-description: Learn how to enable only administrators to publish packages by bsing an electronic software delivery (ESD).
-author: aczechowski
-ms.service: windows-client
-ms.subservice: itpro-apps
-ms.date: 05/02/2022
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: how-to
----
-
-# How to enable only administrators to publish packages by using an ESD
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you couldn't prevent end users from performing these tasks.
-
-Here's how to enable only administrators to publish or unpublish packages:
-
-1. Navigate to the following Group Policy Object node:
-
- **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Publishing**.
-
-2. Enable the **Require publish as administrator** Group Policy setting.
-
- To instead use Windows PowerShell to set this item, see [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending).
-
-
-
-
diff --git a/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md b/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md
deleted file mode 100644
index 757e57fbf23..00000000000
--- a/windows/application-management/app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Enable Reporting on the App-V Client by Using Windows PowerShell (Windows 10/11)
-description: How to Enable Reporting on the App-V Client by Using Windows PowerShell
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to Enable Reporting on the App-V Client by Using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to configure the App-V for reporting.
-
-**To configure the computer running the App-V client for reporting**
-
-1. Enable the App-V client. For more information, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
-
-2. After you have enabled the App-V client, use the **Set-AppvClientConfiguration** cmdlet to configure appropriate Reporting Configuration settings:
-
-|Setting|Description|
-|--- |--- |
-|ReportingEnabled|Enables the client to return information to a reporting server. This setting is required for the client to collect the reporting data on the client.|
-|ReportingServerURL|Specifies the location on the reporting server where client information is saved. For example, https://<reportingservername>:<reportingportnumber>. **Note:** This is the port number that was assigned during the Reporting Server setup|
-|Reporting Start Time|This is set to schedule the client to automatically send the data to the server. This setting will indicate the hour at which the reporting data will start to send. It is in the 24 hour format and will take a number between 0-23.|
-|ReportingRandomDelay|Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and ReportingRandomDelay and will wait the specified duration before sending data.|
-|ReportingInterval|Specifies the retry interval that the client will use to resend data to the reporting server.|
-|ReportingDataCacheLimit|Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.|
-|ReportingDataBlockSize|Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over.|
-
-3. After the appropriate settings have been configured, the computer running the App-V client will automatically collect data and will send the data back to the reporting server.
-
- Additionally, administrators can manually send the data back in an on-demand manner using the **Send-AppvClientReport** cmdlet.
-
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-
-[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md b/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md
deleted file mode 100644
index 7622c5c8ddd..00000000000
--- a/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Enable the App-V in-box client (Windows 10/11)
-description: Learn how to enable the Microsoft Application Virtualization (App-V) in-box client installed with Windows 10/11.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Enable the App-V in-box client
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-The App-V client is the component that runs virtualized applications on user devices. Once you enable the client, users can interact with icons and file names to start virtualized applications. The client can also get virtual application content from the management server.
-
-Starting with Windows 10 version 1607, the App-V client is installed automatically. However, you'll still need to enable the client yourself to allow user devices to access and run virtual applications. You can set up the client with the Group Policy editor or with Windows PowerShell.
-
-Here's how to enable the App-V client with Group Policy:
-
-1. Open the device’s **Group Policy Editor**.
-2. Navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
-3. Run **Enables App-V Client**, then select **Enabled**.
-4. Restart the device.
-
-Here's how to enable the App-V client with Windows PowerShell:
-
-1. Open Windows PowerShell.
-2. Enter **Enable-Appv**, then select the Enter key.
-3. Restart the device.
-4. To verify that the App-V client is working, enter **Get-AppvStatus**, then select the Enter key.
-
-Check out these articles for more information about how to configure the App-V client:
-
-* [Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)
-* [How to modify client configuration by using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
-* [Using the client management console](appv-using-the-client-management-console.md)
-* [How to configure the client to receive package and connection group updates from the Publishing server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
-
-
-
diff --git a/windows/application-management/app-v/appv-evaluating-appv.md b/windows/application-management/app-v/appv-evaluating-appv.md
deleted file mode 100644
index dc3deee0f36..00000000000
--- a/windows/application-management/app-v/appv-evaluating-appv.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Evaluating App-V (Windows 10/11)
-description: Learn how to evaluate App-V for Windows 10/11 in a lab environment before deploying into a production environment.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Evaluating App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-> [!NOTE]
-> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
-
-Before you deploy App-V into a production environment, you should evaluate it in a lab environment. You can use the information in this article to set up App-V in a lab environment for evaluation purposes only.
-
-## Configure lab computers for App-V Evaluation
-
-Use the following links for information about setting up the App-V sequencer on a computer in your lab environment.
-
-### Installing the App-V Sequencer and Creating Packages
-
-Use the following links for information about setting up the App-V sequencer and creating packages in your lab environment.
-
-- [How to Install the Sequencer](appv-install-the-sequencer.md)
-
-- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
-
-### Configuring the App-V Server
-
-Use the following links for information about setting up the App-V server in your lab environment.
-
-- [How to Deploy the App-V server](appv-deploy-the-appv-server.md)
-
-- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
-
-### Enabling the App-V Client
-
-Use the following links for more information about creating and managing virtualized packages in your lab environment.
-
-- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
-
-- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
-
-
-## Related articles
-
-- [Getting Started with App-V](appv-getting-started.md)
diff --git a/windows/application-management/app-v/appv-for-windows.md b/windows/application-management/app-v/appv-for-windows.md
deleted file mode 100644
index b2ded1f2680..00000000000
--- a/windows/application-management/app-v/appv-for-windows.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Application Virtualization (App-V) (Windows 10/11)
-description: See various articles that can help you administer Application Virtualization (App-V) and its components.
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Application Virtualization (App-V) for Windows client overview
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-> [!NOTE]
-> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
-
-The articles in this section provide information and instructions to help you administer App-V and its components. This information is for system administrators who manage large installations with many servers and clients, and for support personnel who interact directly with the computers or users.
-
-[Getting started with App-V](appv-getting-started.md)
-
-- [What's new in App-V](appv-about-appv.md)
-- [Evaluating App-V](appv-evaluating-appv.md)
-- [High-level architecture for App-V](appv-high-level-architecture.md)
-
-[Planning for App-V](appv-planning-for-appv.md)
-
-- [Preparing your environment for App-V](appv-preparing-your-environment.md)
-- [App-V prerequisites](appv-prerequisites.md)
-- [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
-- [App-V supported configurations](appv-supported-configurations.md)
-- [App-V planning checklist](appv-planning-checklist.md)
-
-[Deploying App-V](appv-deploying-appv.md)
-
-- [Deploying the App-V Sequencer and configuring the client](appv-deploying-the-appv-sequencer-and-client.md)
-- [Deploying the App-V Server](appv-deploying-the-appv-server.md)
-- [App-V deployment checklist](appv-deployment-checklist.md)
-- [Deploying Microsoft Office 2016 by using App-V](appv-deploying-microsoft-office-2016-with-appv.md)
-- [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
-- [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
-
-[Operations for App-V](appv-operations.md)
-
-- [Creating and managing App-V virtualized applications](appv-creating-and-managing-virtualized-applications.md)
-- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
-- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
-- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
-- [Administering App-V Virtual Applications by using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
-- [Managing connection groups](appv-managing-connection-groups.md)
-- [Deploying App-V packages by using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
-- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
-- [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
-- [Migrating to App-V from a previous version](appv-migrating-to-appv-from-a-previous-version.md)
-- [Maintaining App-V](appv-maintaining-appv.md)
-- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
-
-[Troubleshooting App-V](appv-troubleshooting.md)
-
-[Technical reference for App-V](appv-technical-reference.md)
-
-- [Performance guidance for Application Virtualization](appv-performance-guidance.md)
-- [Application publishing and client interaction](appv-application-publishing-and-client-interaction.md)
-- [Viewing App-V Server publishing metadata](appv-viewing-appv-server-publishing-metadata.md)
-- [Running a locally installed application inside a virtual environment with virtualized applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
-
-
-
diff --git a/windows/application-management/app-v/appv-getting-started.md b/windows/application-management/app-v/appv-getting-started.md
deleted file mode 100644
index aab10ec1a45..00000000000
--- a/windows/application-management/app-v/appv-getting-started.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Getting Started with App-V (Windows 10/11)
-description: Get started with Microsoft Application Virtualization (App-V) for Windows 10/11. App-V for Windows client devices delivers Win32 applications to users as virtual applications.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Getting started with App-V for Windows client
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-> [!NOTE]
-> [!INCLUDE [Application Virtualization will be end of life in April 2026](../includes/app-v-end-life-statement.md)]
-
-Microsoft Application Virtualization (App-V) for Windows delivers Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service in real time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
-
-Starting with Windows 10 version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/WindowsForBusiness/windows-for-enterprise). If you're new to Windows client and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. To learn what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
-
-If you’re already using App-V, performing an in-place upgrade to Windows 10/11 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10/11, see [Upgrading to App-V for Windows from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md).
-
->[!IMPORTANT]
->You can upgrade your existing App-V installation to App-V for Windows from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade your existing App-V installation to App-V 5.0 SP2 before upgrading to App-V for Windows.
-
-To learn more about previous versions of App-V, see [MDOP information experience](/microsoft-desktop-optimization-pack/index).
-
-## Getting started with App-V for Windows (new installations)
-
-To start using App-V to deliver virtual applications to users, you’ll need to download, enable, and install server- and client-side components. The following table describes the App-V for Windows client components, what they do, and where to find them.
-
-
-
-| Component | What it does | Where to find it |
-|------------|--|------|
-| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For more information, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).
If you're already using App-V 5.x, you don't need to redeploy the App-V server components, as they haven't changed since App-V 5.0's release. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package that can be downloaded from the following locations:
If you have a Microsoft Developer Network (MSDN) subscription, use the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/subscriptions/downloads/default.aspx#FileId=65215) to download the MDOP ISO package.
If you're using [Windows client for Enterprise or Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home), download it from the [Volume Licensing Service Center](https://www.microsoft.com/licensing/default.aspx).
For more information about installing and using the server components, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).|
-| App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices, allowing users to interact with icons and file names to start virtualized applications. | Starting with Windows 10 version 1607, the App-V client is automatically installed.
To learn how to enable the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
-| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must run the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows client](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). |
-
-For more information about these components, see [High Level Architecture for App-V](appv-high-level-architecture.md).
-
-If you're new to App-V, it's a good idea to read the documentation thoroughly. Before deploying App-V in a production environment, you can ensure installation goes smoothly by validating your deployment plan in a test network environment. You might also consider taking a class about relevant technologies. To get started, see the [Microsoft Training Overview](https://www.microsoft.com/learning/default.aspx).
-
-## Getting started with App-V
-
-[What's new in App-V](appv-about-appv.md) provides a high-level overview of App-V and how it can be used in your organization?
-
-[Evaluating App-V](appv-evaluating-appv.md) provides information about how you can best evaluate App-V for use in your organization.
-
-[High Level Architecture for App-V](appv-high-level-architecture.md) provides a description of the App-V features and how they work together.
-
-## Other resources for this product
-
-* [Application Virtualization (App-V) overview](appv-for-windows.md)
-* [Planning for App-V](appv-planning-for-appv.md)
-* [Deploying App-V](appv-deploying-appv.md)
-* [Operations for App-V](appv-operations.md)
-* [Troubleshooting App-V](appv-troubleshooting.md)
-* [Technical reference for App-V](appv-technical-reference.md)
diff --git a/windows/application-management/app-v/appv-high-level-architecture.md b/windows/application-management/app-v/appv-high-level-architecture.md
deleted file mode 100644
index 1757dca790e..00000000000
--- a/windows/application-management/app-v/appv-high-level-architecture.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: High-level architecture for App-V (Windows 10/11)
-description: Use the information in this article to simplify your Microsoft Application Virtualization (App-V) deployment.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# High-level architecture for App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following information to simplify your Microsoft Application Virtualization (App-V) deployment.
-
-## Architecture overview
-
-A typical App-V implementation consists of the following elements.
-
-|Element|Description|
-|---|---|
-|App-V Management server|The App-V Management server provides overall management functionality for the App-V infrastructure. Additionally, you can install more than one instance of the management server in your environment, which provides the following benefits: **Fault tolerance and high availability**—installing and configuring the App-V Management server on two separate computers can help in situations when one of the servers is unavailable or offline. You can also help increase App-V availability by installing the Management server on multiple computers. In this scenario, consider using a network load balancer to keep server requests balanced. **Scalability**—you can add more management servers as necessary to support a high load. For example, you can install multiple servers behind a load balancer.|
-|App-V Publishing Server|The App-V publishing server provides functionality for virtual application hosting and streaming. The publishing server doesn't require a database connection and supports HTTP and HTTPS protocols. You can also help increase App-V availability by installing the Publishing server on multiple computers. You should also consider having a network load balancer to keep server requests balanced.|
-|App-V Reporting Server|The App-V Reporting server lets authorized users run and view existing App-V reports and unplanned reports for managing App-V infrastructure. The Reporting server requires a connection to the App-V reporting database. You can also help increase App-V availability by installing the Reporting server on multiple computers. You should also consider having a network load balancer to keep server requests balanced.|
-|App-V Client|The App-V client enables packages created using App-V to run on target computers.|
-
->[!NOTE]
->If you are using App-V with electronic software distribution (ESD), you aren't required to use the App-V Management server. However, you can still use App-V's reporting and streaming functionality.
-
-## Related articles
-
-- [Getting Started with App-V](appv-getting-started.md)
diff --git a/windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md b/windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
deleted file mode 100644
index 911023aae03..00000000000
--- a/windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell (Windows 10/11)
-description: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-
-# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell
-
-**Applies to**
-- Windows Server 2016
-
-Use the following Windows PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts.
-
-Before attempting this procedure, you should read and understand the information and examples displayed in the following list:
-
-- **.INPUTS** – The account or accounts used to convert to SID format. This item can be a single account name or an array of account names.
-
-- **.OUTPUTS** - A list of account names with the corresponding SID in standard and hexadecimal formats.
-
-- **Examples** -
-
- **.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List**.
-
- **$accountsArray = @("DOMAIN\\user\_account1", "DOMAIN\\machine\_account1$", "DOMAIN\_user\_account2")**
-
- **.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200**
-
- \#>
-
-**To convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs)**
-
-1. Copy the following script into a text editor and save it as a Windows PowerShell script file, for example **ConvertToSIDs.ps1**.
-
-2. To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
-
- ```powershell
- <#
- .SYNOPSIS
- This Windows PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats.
- .DESCRIPTION
- This is a Windows PowerShell script that converts any number of Active Directory (AD) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by SQL server when running SQL scripts.
- .INPUTS
- The account(s) to convert to SID format. This can be a single account name or an array of account names. Please see examples below.
- .OUTPUTS
- A list of account names with the corresponding SID in standard and hexadecimal formats
- .EXAMPLE
- .\ConvertToSID.ps1 DOMAIN\user_account1 DOMAIN\machine_account1$ DOMAIN\user_account2 | Format-List
- .EXAMPLE
- $accountsArray = @("DOMAIN\user_account1", "DOMAIN\machine_account1$", "DOMAIN_user_account2")
- .\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200
- #>
-
- function ConvertSIDToHexFormat
- {
- param([System.Security.Principal.SecurityIdentifier]$sidToConvert)
- $sb = New-Object System.Text.StringBuilder
- [int] $binLength = $sidToConvert.BinaryLength
- [Byte[]] $byteArray = New-Object Byte[] $binLength
- $sidToConvert.GetBinaryForm($byteArray, 0)
- foreach($byte in $byteArray)
- {
- $sb.Append($byte.ToString("X2")) |Out-Null
- }
- return $sb.ToString()
- }
- [string[]]$myArgs = $args
- if(($myArgs.Length -lt 1) -or ($myArgs[0].CompareTo("/?") -eq 0))
- {
- [string]::Format("{0}====== Description ======{0}{0}" +
- " Converts any number of user or machine account names to string and hexadecimal SIDs.{0}" +
- " Pass the account(s) as space separated command line parameters. (For example 'ConvertToSID.exe DOMAIN\\Account1 DOMAIN\\Account2 ...'){0}" +
- " The output is written to the console in the format 'Account name SID as string SID as hexadecimal'{0}" +
- " And can be written out to a file using standard Windows PowerShell redirection{0}" +
- " Please specify user accounts in the format 'DOMAIN\username'{0}" +
- " Please specify machine accounts in the format 'DOMAIN\machinename$'{0}" +
- " For more help content, please run 'Get-Help ConvertToSID.ps1'{0}" +
- "{0}====== Arguments ======{0}" +
- "{0} /? Show this help message", [Environment]::NewLine)
- {
- else
- {
- #If an array was passed in, try to split it
- if($myArgs.Length -eq 1)
- {
- $myArgs = $myArgs.Split(' ')
- }
-
- #Parse the arguments for account names
- foreach($accountName in $myArgs)
- {
- [string[]] $splitString = $accountName.Split('\') # We're looking for the format "DOMAIN\Account" so anything that does not match, we reject
- if($splitString.Length -ne 2)
- {
- $message = [string]::Format("{0} is not a valid account name. Expected format 'Domain\username' for user accounts or 'DOMAIN\machinename$' for machine accounts.", $accountName)
- Write-Error -Message $message
- continue
- }
- #Convert any account names to SIDs
- try
- {
- [System.Security.Principal.NTAccount] $account = New-Object System.Security.Principal.NTAccount($splitString[0], $splitString[1])
- [System.Security.Principal.SecurityIdentifier] $SID = [System.Security.Principal.SecurityIdentifier]($account.Translate([System.Security.Principal.SecurityIdentifier]))
- }
- catch [System.Security.Principal.IdentityNotMappedException]
- {
- $message = [string]::Format("Failed to translate account object '{0}' to a SID. Please verify that this is a valid user or machine account.", $account.ToString())
- Write-Error -Message $message
- continue
- }
-
- #Convert regular SID to binary format used by SQL
- $hexSIDString = ConvertSIDToHexFormat $SID
- $SIDs = New-Object PSObject
- $SIDs | Add-Member NoteProperty Account $accountName
- $SIDs | Add-Member NoteProperty SID $SID.ToString()
- $SIDs | Add-Member NoteProperty Hexadecimal $hexSIDString
-
- Write-Output $SIDs
- }
- }
- ```
-
-3. Run the script you saved in Step 1 of this procedure passing the accounts to convert as arguments.
-
- For example,
-
- **.\\ConvertToSID.ps1 DOMAIN\\user\_account1 DOMAIN\\machine\_account1$ DOMAIN\\user\_account2 | Format-List” or “$accountsArray = @("DOMAIN\\user\_account1", "DOMAIN\\machine\_account1$", "DOMAIN\_user\_account2")**
-
- **.\\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\\SIDs.txt -Width 200”**
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md
deleted file mode 100644
index ba5480496de..00000000000
--- a/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services (Windows 10/11)
-description: How to install the Management and Reporting Databases on separate computers from the Management and Reporting Services.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services
-
->Applies to: Windows Server 2016
-
-Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.
-
->[!NOTE]
->After you complete the deployment, the administrator installing the service will need the Microsoft SQL Server name, instance name and the database name to connect to these databases.
-
-## Installing the management database and the management server on separate computers
-
-1. Copy the App-V server installation files to the computer you want to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
-2. On the **Getting started** page, review and accept the license terms, then select **Next**.
-3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended).** To disable Microsoft updates, select **I don’t want to use Microsoft Update**, then select **Next**.
-4. On the **Feature selection** page, select the components you want to install by first selecting the **Management Server Database** checkbox, then selecting **Next**.
-5. On the **Installation location** page, accept the default location and select **Next**.
-6. On the initial **Create new management server database** page, accept the default selections if appropriate, then select **Next**.
- * If you are using a custom SQL Server instance, select **Use a custom instance** and enter the name of the instance.
- * If you are using a custom database name, select **Custom configuration** and enter the database name.
-7. On the next **Create new management server database** page, select **Use a remote computer**, then enter the remote machine account using the following format: ```Domain\MachineAccount```.
-
- > [!NOTE]
- >If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: ```Domain\AdministratorLoginName```. After that, select **Next**.
-8. To start the installation, select **Install**.
-
-## Installing the reporting database and the reporting server on separate computers
-
-1. Copy the App-V server installation files to the computer you want to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
-2. On the **Getting started** page, review and accept the license terms, then select **Next**.
-3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft Update, select **Use Microsoft Update when I check for updates (recommended)**. To disable Microsoft Update, select **I don’t want to use Microsoft Update**. After that, select **Next**.
-4. On the **Feature selection** page, select the components you want to install by first selecting the **Reporting Server Database** checkbox, then selecting **Next**.
-5. On the **Installation Location** page, accept the default location and select **Next**.
-6. On the initial **Create new management server database** page, accept the default selections if appropriate, then select **Next**.
- * If you're using a custom SQL Server instance, select **Use a custom instance** and enter the instance name.
- * If you're using a custom database name, select **Custom configuration** and enter the database name.
-7. On the next **Create new management server database** page, select **Use a remote computer**, and enter the remote machine account using the following format: ```Domain\MachineAccount```.
-
- > [!NOTE]
- >If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. After that, select **Next**.
-8. To start the installation, select **Install**.
-
-## Installing the management and reporting databases using App-V database scripts
-
-1. Copy the App-V server installation files to the computer on which you want to install it on.
-2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
-
- ```SQL
- appv\_server\_setup.exe /LAYOUT /LAYOUTDIR=”InstallationExtractionLocation”
- ```
-
-3. After the extraction has been completed, to access the App-V database scripts and instructions readme file:
-
- * The App-V Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**.
- * The App-V Reporting Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Reporting Database**.
-4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
-
- > [!NOTE]
- >For more information about modifying the required SIDs contained in the scripts, see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
-5. Run the scripts on the computer running Microsoft SQL Server.
-
-
-
-
-
-## Related articles
-
-* [Deploying App-V](appv-deploying-appv.md)
diff --git a/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md b/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md
deleted file mode 100644
index a9263f3cba7..00000000000
--- a/windows/application-management/app-v/appv-install-the-management-server-on-a-standalone-computer.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: How to install the Management Server on a Standalone Computer and Connect it to the Database (Windows 10/11)
-description: How to install the Management Server on a Standalone Computer and Connect it to the Database
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to install the Management Server on a Standalone Computer and Connect it to the Database
-
->Applies to: Windows Server 2016
-
-To install the management server on a standalone computer and connect it to the database, follow these steps.
-
-1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
-2. On the **Getting Started** page, review and accept the license terms, then select **Next**.
-3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft Update, select **Use Microsoft Update when I check for updates (recommended)**. To disable Microsoft Update, select **I don’t want to use Microsoft Update**, then select **Next**.
-4. On the **Feature Selection** page, select the **Management Server** checkbox, then select **Next**.
-5. On the **Installation Location** page, accept the default location, then select **Next**.
-6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, then enter the computer running Microsoft SQL's machine name, such as ```SqlServerMachine```.
-
- > [!NOTE]
- >If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance**, then enter the instance's name. Specify the **SQL Server Database name** that this management server will use, such as ```AppvManagement```.
-7. On the **Configure management server configuration** page, specify the following items:
- * The AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
- * The **Website Name** you want to use for the management service. Accept the default if you do not have a custom name.
- * For the **Port Binding**, specify a unique port number, such as **12345**.
-8. Select **Install**.
-9. To confirm that the setup has completed successfully, open a web browser and enter the following URL: https://managementserver:portnumber/Console. If the installation was successful, you should see the **Management Console** appear without any error messages or warnings displayed.
-
-
-
-
-
-## Related articles
-
-* [Deploying App-V](appv-deploying-appv.md)
diff --git a/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md b/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md
deleted file mode 100644
index b25c54796cf..00000000000
--- a/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Install the Publishing Server on a Remote Computer (Windows 10/11)
-description: Use the procedures in this article to install the Microsoft Application Virtualization (App-V) publishing server on a separate computer.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to install the publishing server on a remote computer
-
->Applies to: Windows Server 2016
-
-Use the following procedure to install the publishing server on a separate computer. Before you perform the following procedure, ensure the database and management server are available.
-
-## Installing the publishing server on a separate computer
-
-1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
-2. On the **Getting started** page, review and accept the license terms, then select **Next**.
-3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft updates, select **Use Microsoft Update when I check for updates (recommended)**. To disable Microsoft Update, select **I don’t want to use Microsoft Update**. Click **Next**.
-4. On the **Feature selection** page, select the **Publishing Server** checkbox, then select **Next**.
-5. On the **Installation location** page, accept the default location, then select **Next**.
-6. On the **Configure publishing server configuration** page, specify the following items:
-
- * The URL for the management service that the publishing server will connect to. For example, **http://ManagementServerName:12345**.
- * Specify the website name that you want to use for the publishing service. If you don't have a custom name, then use the default name.
- * For the **Port binding**, specify a unique port number that will be used by App-V. For example, **54321**.
-7. On the **Ready to install** page, select **Install**.
-8. After the installation is complete, the publishing server must be registered with the management server. In the App-V management console, use the following steps to register the server:
-
- 1. Open the App-V management server console.
- 2. In the left pane, select **Servers**, then select **Register New Server**.
- 3. Enter the server name and a description (if required), then select **Add**.
-9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle that package to an AD group, then publish it. Using an internet browser, open the following URL: https://publishingserver:pubport. If the server is running correctly, information like the following example should appear.
-
- ```xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ```
-
-
-
-
-
-## Related articles
-
-* [Deploying App-V](appv-deploying-appv.md)
diff --git a/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md
deleted file mode 100644
index 39075f56f33..00000000000
--- a/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to install the Reporting Server on a standalone computer and connect it to the database (Windows 10/11)
-description: How to install the App-V Reporting Server on a Standalone Computer and Connect it to the Database
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to install the reporting server on a standalone computer and connect it to the database
-
->Applies to: Windows Server 2016
-
-Use the following procedure to install the reporting server on a standalone computer and connect it to the database.
-
->[!IMPORTANT]
->Before performing the following procedure you should read and understand [About App-V reporting](appv-reporting.md).
-
-## Install the reporting server on a standalone computer and connect it to the database
-
-1. Copy the App-V server installation files to the computer you plan to install it on. To start the App-V server installation, run **appv\_server\_setup.exe** as an administrator, then select **Install**.
-2. On the **Getting started** page, review and accept the license terms, then select **Next**.
-3. On the **Use Microsoft Update to help keep your computer secure and up-to-date** page, to enable Microsoft Update, select **Use Microsoft Update when I check for updates (recommended)**. To disable Microsoft Update, select **I don’t want to use Microsoft Update**. Select **Next**.
-4. On the **Feature selection** page, select the **Reporting Server** checkbox, then select **Next**.
-5. On the **Installation location** page, accept the default location and select **Next**.
-6. On the **Configure existing reporting database** page, select **Use a remote SQL Server**, then enter the machine name of the computer running Microsoft SQL Server. For example, you can name your computer **SqlServerMachine**.
-
- > [!NOTE]
- >If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server instance, select **Use the default instance**. If you're using a custom Microsoft SQL Server instance, select **Use a custom instance**, then enter the name of your custom instance. Specify the **SQL Server Database name** that this reporting server will use; for example, you can name the server **AppvReporting**.
-7. On the **Configure reporting server configuration** page.
-
- * Specify the website name you want to use for the reporting service. Leave the default unchanged if you do not have a custom name.
- * For the **Port binding**, specify a unique, five-digit port number for App-V to use, such as **55555**. Make sure that the specified port isn't being used by another website.
-8. Select **Install**.
-
-
-
-
-
-## Related articles
-
-* [About App-V reporting](appv-reporting.md)
-* [Deploying App-V](appv-deploying-appv.md)
-* [How to enable reporting on the App-V client by using Windows PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)
diff --git a/windows/application-management/app-v/appv-install-the-sequencer.md b/windows/application-management/app-v/appv-install-the-sequencer.md
deleted file mode 100644
index 2f756b549e3..00000000000
--- a/windows/application-management/app-v/appv-install-the-sequencer.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Install the App-V Sequencer (Windows 10/11)
-description: Learn how to install the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Install the App-V Sequencer
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Those devices must be running the App-V client to allow users to interact with virtual applications.
-
-The App-V Sequencer is included in the Windows client Assessment and Deployment Kit (Windows ADK).
-
->[!NOTE]
->The computer that will run the sequencer must not have the App-V client enabled. As a best practice, choose a computer with the same hardware and software configurations as the computers that will run the virtual applications. The sequencing process is resource-intensive, so make sure the computer that will run the Sequencer has plenty of memory, a fast processor, and a fast hard drive.
-
-## How to install the App-V Sequencer
-
-1. Go to [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
-2. Select the **Get Windows ADK for Windows 10** button on the page to start the ADK installer. Make sure that **Microsoft Application Virtualization (App-V) Sequencer** is selected during the installation.
-
- 
-3. To open the Sequencer, go to the **Start** menu and select **Microsoft Application Virtualization (App-V) Sequencer**.
-
-See [Creating and managing virtual applications](appv-creating-and-managing-virtualized-applications.md) and the [Application Virtualization Sequencing Guide](https://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V%205.0%20Sequencing%20Guide.docx) for information about creating virtual applications with the Sequencer.
-
-## Command-line options for installing the sequencer
-
-You can also use the command line to install the App-V sequencer. The following list displays information about options for installing the sequencer using the command line and **appv\_sequencer\_setup.exe**:
-
-| Command | Description |
-|-------------------|------------------|
-| **/INSTALLDIR** | Specifies the installation directory. |
-| **/Log** | Specifies where the installation log will be saved. The default location is **%Temp%**. For example, **C:\\Logs\\log.log**. |
-| **/q** | Specifies a quiet or silent installation. |
-| **/Uninstall** | Specifies the removal of the sequencer. |
-| **/ACCEPTEULA** | Accepts the license agreement. This is required for an unattended installation. For example, **/ACCEPTEULA** or **/ACCEPTEULA=1**. |
-| **/LAYOUT** | Specifies the associated layout action. It also extracts the Windows Installer (.msi) and script files to a folder without installing App-V. No value is expected. |
-| **/LAYOUTDIR** | Specifies the layout directory. Requires a string value. For example, **/LAYOUTDIR=”C:\\Application Virtualization Client”**. |
-| **/?** or **/h** or **/help** | Displays associated help. |
-
-## To troubleshoot the App-V sequencer installation
-
-For more information regarding the sequencer installation, you can view the error log in the **%temp%** folder. To review the log files, click **Start**, type **%temp%**, and then look for the **appv\_ log**.
-
-
-
-
-
-## Related articles
-
-* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
diff --git a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md b/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
deleted file mode 100644
index 9ce856129da..00000000000
--- a/windows/application-management/app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help (Windows 10/11)
-description: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# How to load the Windows PowerShell cmdlets for App-V and get cmdlet help
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-## Requirements for using Windows PowerShell cmdlets
-
-This section will tell you what you'll need to use the PowerShell cmdlets.
-
-### How to let users access PowerShell cmdlets
-
-You can grant your users access to PowerShell cmdlets through one of the following methods:
-
-* While you're deploying and configuring the App-V server, specify an Active Directory group or individual user with permissions to manage the App-V environment. For more information, see [How to deploy the App-V Server](appv-deploy-the-appv-server.md).
-* After you've deployed the App-V server, you can use the App-V Management console to add an additional Active Directory group or user. For more information, see [How to add or remove an administrator by using the Management console](appv-add-or-remove-an-administrator-with-the-management-console.md).
-
-### Elevated command prompt
-
-You'll need an elevated command prompt to run the following cmdlets:
-
-* **Add-AppvClientPackage**
-* **Remove-AppvClientPackage**
-* **Set-AppvClientConfiguration**
-* **Add-AppvClientConnectionGroup**
-* **Remove-AppvClientConnectionGroup**
-* **Add-AppvPublishingServer**
-* **Remove-AppvPublishingServer**
-* **Send-AppvClientReport**
-* **Set-AppvClientMode**
-* **Set-AppvClientPackage**
-* **Set-AppvPublishingServer**
-
-### Other cmdlets
-
-The following cmdlets are ones that end-users can run unless you configure them to require an elevated command prompt.
-
-* **Publish-AppvClientPackage**
-* **Unpublish-AppvClientPackage**
-
-To configure these cmdlets to require an elevated command prompt, use one of the following methods:
-
-* Run the **Set-AppvClientConfiguration** cmdlet with the *-RequirePublishAsAdmin* parameter. For more information, see the following resources:
- * [How to manage connection groups on a stand-alone computer by using Windows PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)
- * [Understanding pending packages: UserPending and GlobalPending](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#about-pending-packages-userpending-and-globalpending)
-* Enable the **Require publish as administrator** Group Policy setting for App-V Clients. For more information, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md).
-
-## Loading the Windows PowerShell cmdlets
-
-To load the Windows PowerShell cmdlet modules:
-
-1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
-2. Enter one of the following cmdlets to load a list of usable cmdlets for the module you want:
-
-|App-v component|Cmdlet to enter|
-|---|---|
-|App-V Server|**Import-Module AppvServer**|
-|App-V Sequencer|**Import-Module AppvSequencer**|
-|App-V Client|**Import-Module AppvClient**|
-
-## Getting help for the Windows PowerShell cmdlets
-
-Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
-
-* As a downloadable module in PowerShell. To access the module, open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE) and enter one of the cmdlets from the following table.
-
-|App-v component|Cmdlet to enter|
-|---|---|
-|App-V Server|**Update-Help -Module AppvServer**|
-|App-V Sequencer|**Update-Help -Module AppvSequencer**|
-|App-V Client|**Update-Help -Module AppvClient**|
-
-* Online in the [Microsoft Desktop Optimization Pack](/powershell/mdop/get-started).
-
-## Displaying the help for a Windows PowerShell cmdlet
-
-To display help for a specific Windows PowerShell cmdlet:
-
-1. Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
-2. Enter **Get-Help** followed by the cmdlet you need help with. For example:
- ```PowerShell
- Get-Help Publish-AppvClientPackage
- ```
diff --git a/windows/application-management/app-v/appv-maintaining-appv.md b/windows/application-management/app-v/appv-maintaining-appv.md
deleted file mode 100644
index 0b04a038f50..00000000000
--- a/windows/application-management/app-v/appv-maintaining-appv.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Maintaining App-V (Windows 10/11)
-description: After you have deployed App-V for Windows 10/11, you can use the following information to maintain the App-V infrastructure.
-author: aczechowski
-ms.service: windows-client
-ms.date: 09/27/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Maintaining App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-After you have deployed App-V for Windows client, you can use the following information to maintain the App-V infrastructure.
-
-## Moving the App-V server
-
-The App-V server connects to the App-V database, which means you can install the management component and connect it to the App-V database on any computer on the network. For more information, see [How to move the App-V server to another computer](appv-move-the-appv-server-to-another-computer.md).
-
-## Determine if an App-V application is running virtualized
-
-Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace (PID stands for process ID). To find the process ID of the process you're currently using, enter the Windows API **GetCurrentProcessId()**.
-
-For example, let's say the process ID is 4052. If you can successfully open a named Event object called **AppVVirtual-4052** with the **OpenEvent()** API in the default read access namespace, then the application is virtual. If the **OpenEvent()** call fails, the application isn't virtual.
-
-Additionally, ISVs who want to explicitly virtualize or not virtualize calls on specific APIs with App-V 5.1 and later can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module to hint to a downstream component whether the call should be virtualized or not.
-
-
-
-
-
-## Other resources for maintaining App-V
-
-* [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
deleted file mode 100644
index 55a855d2ebc..00000000000
--- a/windows/application-management/app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
-title: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell (Windows 10/11)
-description: How to manage App-V packages running on a stand-alone computer by using Windows PowerShell.
-author: aczechowski
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.service: windows-client
-ms.date: 09/24/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-# How to manage App-V packages running on a stand-alone computer by using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-The following sections explain how to perform various management tasks on a stand-alone client computer with Windows PowerShell cmdlets.
-
-## Return a list of packages
-
-Enter the **Get-AppvClientPackage** cmdlet to return a list of packages entitled to a specific user. Its parameters are *-Name*, *-Version*, *-PackageID*, and *-VersionID*.
-
-For example:
-
-```PowerShell
-Get-AppvClientPackage –Name "ContosoApplication" -Version 2
-```
-
-## Add a package
-
-Use the **Add-AppvClientPackage** cmdlet to add a package to a computer.
-
-> [!IMPORTANT]
-> This example only adds a package. It does not publish the package to the user or the computer.
-
-For example:
-
-```PowerShell
-$Contoso = Add-AppvClientPackage \\\\path\\to\\appv\\package.appv
-```
-
-## Publish a package
-
-Use the **Publish-AppvClientPackage** cmdlet to publish a package that has been added to either a specific user or globally to any user on the computer.
-
-Enter the cmdlet with the application name to publish it to the user.
-
-```PowerShell
-Publish-AppvClientPackage "ContosoApplication"
-```
-
-To publish the application globally, just add the *-Global* parameter.
-
-```Powershell
-Publish-AppvClientPackage "ContosoApplication" -Global
-```
-
-## Publish a package to a specific user
-
-> [!NOTE]
-> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
-
-An administrator can publish a package to a specific user by specifying the optional *–UserSID* parameter with the **Publish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
-
-To use this parameter:
-
-- You can run this cmdlet from the user or administrator session.
-- You must be logged in with administrative credentials to use the parameter.
-- The end user must be signed in.
-- You must provide the end user’s security identifier (SID).
-
-For example:
-
-```PowerShell
-Publish-AppvClientPackage "ContosoApplication" -UserSID S-1-2-34-56789012-3456789012-345678901-2345
-```
-
-## Add and publish a package
-
-Use the **Add-AppvClientPackage** cmdlet to add a package to a computer and publish it to the user.
-
-For example:
-
-```PowerShell
-Add-AppvClientPackage | Publish-AppvClientPackage
-```
-
-## Unpublish an existing package
-
-Use the **Unpublish-AppvClientPackage** cmdlet to unpublish a package which has been entitled to a user but not remove the package from the computer.
-
-For example:
-
-```PowerShell
-Unpublish-AppvClientPackage "ContosoApplication"
-```
-
-## Unpublish a package for a specific user
-
-> [!NOTE]
-> You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
-
-An administrator can unpublish a package for a specific user by using the optional *-UserSID* parameter with the **Unpublish-AppvClientPackage** cmdlet, where *-UserSID* represents the end user’s security identifier (SID).
-
-To use this parameter:
-
-- You can run this cmdlet from the user or administrator session.
-- You must sign in with administrative credentials to use the parameter.
-- The end user must be signed in.
-- You must provide the end user’s security identifier (SID).
-
-For example:
-
-```PowerShell
-Unpublish-AppvClientPackage "ContosoApplication" -UserSID S-1-2-34-56789012-3456789012-345678901-2345
-```
-
-## Remove an existing package
-
-Use the **Remove-AppvClientPackage** cmdlet to remove a package from the computer.
-
-For example:
-
-```PowerShell
-Remove-AppvClientPackage "ContosoApplication"
-```
-
-> [!NOTE]
-> App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](/archive/blogs/appv/app-v-5-0-client-powershell-deep-dive).
-
-## Enable only administrators to publish or unpublish packages
-
-Starting in App-V 5.0 SP3, you can use the **Set-AppvClientConfiguration** cmdlet and *-RequirePublishAsAdmin* parameter to enable only administrators (not end users) to publish or unpublish packages.
-
-You can set the *-RequirePublishAsAdmin* parameter to the following values:
-
-- 0: False
-- 1: True
-
-For example:
-
-```PowerShell
-Set-AppvClientConfiguration –RequirePublishAsAdmin1
-```
-
-To use the App-V Management console to set this configuration, see [How to publish a package by using the Management Console](appv-publish-a-packages-with-the-management-console.md).
-
-## About pending packages: UserPending and GlobalPending
-
-Starting in App-V 5.0 SP2, if you run a Windows PowerShell cmdlet that affects a package currently in use, the task you're trying to perform is placed in a pending state. For example, if you try to publish a package when an application in that package is being used, and then run **Get-AppvClientPackage**, the pending status appears in the cmdlet output as follows:
-
-|Cmdlet output item|Description|
-|---|---|
-|UserPending|Indicates whether the listed package has a pending task that is being applied to the user: - True - False|
-|GlobalPending|Indicates whether the listed package has a pending task that is being applied globally to the computer: - True - False|
-
-The pending task will run later, according to the following rules:
-
-|Task type|Applicable rule|
-|---|---|
-|User-based (for example, publishing a package to a user)|The pending task will be performed after the user logs off and then logs back on.|
-|Globally based (for example, enabling a connection group globally)|The pending task will be performed when the computer is shut down and then restarted.|
-
-For more information about pending tasks, see [Upgrading an in-use App-V package](appv-application-publishing-and-client-interaction.md#upgrading-an-in-use-app-v-package).
-
-
-
-
-
-## Related topics
-
-- [Operations for App-V](appv-operations.md)
-- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/application-management/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md b/windows/application-management/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
deleted file mode 100644
index 181e13b751a..00000000000
--- a/windows/application-management/app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell (Windows 10/11)
-description: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group.
-
-A connection group XML file defines the connection group for the App-V client. For information about the connection group XML file and how to configure it, see [About the Connection Group File](appv-connection-group-file.md).
-
-This article explains the following procedures:
-
-- [To add and publish the App-V packages in the connection group](#to-add-and-publish-the-app-v-packages-in-the-connection-group)
-
-- [To add and enable the connection group on the App-V client](#to-add-and-enable-the-connection-group-on-the-app-v-client)
-
-- [To enable or disable a connection group for a specific user](#to-enable-or-disable-a-connection-group-for-a-specific-user)
-
-- [To allow only administrators to enable connection groups](#to-allow-only-administrators-to-enable-connection-groups)
-
-## To add and publish the App-V packages in the connection group
-
-1. To add and publish the App-V packages to the computer running the App-V client, type the following command:
-
- Add-AppvClientPackage –path c:\\tmpstore\\quartfin.appv | Publish-AppvClientPackage
-
-2. Repeat **step 1** of this procedure for each package in the connection group.
-
-## To add and enable the connection group on the App-V client
-
-1. Add the connection group by typing the following command:
-
- Add-AppvClientConnectionGroup –path c:\\tmpstore\\financ.xml
-
-2. Enable the connection group by typing the following command:
-
- Enable-AppvClientConnectionGroup –name "Financial Applications"
-
- When any virtual applications that are in the member packages are run on the target computer, they'll run inside the connection group’s virtual environment and will be available to all the virtual applications in the other packages in the connection group.
-
-## To enable or disable a connection group for a specific user
-
-1. Review the parameter description and requirements:
-
- - The parameter enables an administrator to enable or disable a connection group for a specific user.
-
- - You must use App-V 5.0 SP2 Hotfix Package 5 or later to use this parameter.
-
- - You can run this cmdlet from the user or administrator session.
-
- - You must be logged in with administrative credentials to use the parameter.
-
- - The end user must be logged in.
-
- - You must provide the end user’s security identifier (SID).
-
-2. Use the following cmdlets, and add the optional **–UserSID** parameter, where **-UserSID** represents the end user’s security identifier (SID):
-
- |Cmdlet|Examples|
- |--- |--- |
- |Enable-AppVClientConnectionGroup|Enable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345|
- |Disable-AppVClientConnectionGroup|Disable-AppVClientConnectionGroup "ConnectionGroupA" -UserSID S-1-2-34-56789012-3456789012-345678901-2345|
-
-## To allow only administrators to enable connection groups
-
-1. Review the description and requirement for using this cmdlet:
-
- - Use this cmdlet and parameter to configure the App-V client to allow only administrators (not end users) to enable or disable connection groups.
-
- - You must be using at least App-V 5.0 SP3 to use this cmdlet.
-
-2. Run the following cmdlet and parameter:
-
- |Cmdlet|Parameter and values|Example|
- |--- |--- |--- |
- |Set-AppvClientConfiguration|-RequirePublishAsAdmin
0 - False
1 - True|Set-AppvClientConfiguration -RequirePublishAsAdmin 1|
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-
-[Operations for App-V](appv-operations.md)
-
-[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
diff --git a/windows/application-management/app-v/appv-managing-connection-groups.md b/windows/application-management/app-v/appv-managing-connection-groups.md
deleted file mode 100644
index 7f676c5b81f..00000000000
--- a/windows/application-management/app-v/appv-managing-connection-groups.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Managing Connection Groups (Windows 10/11)
-description: Connection groups can allow administrators to manage packages independently and avoid having to add the same application multiple times to a client computer.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Managing Connection Groups
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Connection groups enable the applications within a package to interact with each other in the virtual environment, while remaining isolated from the rest of the system. By using connection groups, administrators can manage packages independently and can avoid having to add the same application multiple times to a client computer.
-
-**Note**
-In some previous versions of App-V, connection groups were referred to as Dynamic Suite Composition.
-
-**In this section:**
-
-|Links|Description|
-|--- |--- |
-|[About the Connection Group Virtual Environment](appv-connection-group-virtual-environment.md)|Describes the connection group virtual environment.|
-|[About the Connection Group File](appv-connection-group-file.md)|Describes the connection group file.|
-|[How to Create a Connection Group](appv-create-a-connection-group.md)|Explains how to create a new connection group.|
-|[How to Create a Connection Group with User-Published and Globally Published Packages](appv-create-a-connection-group-with-user-published-and-globally-published-packages.md)|Explains how to create a new connection group that contains a mix of packages that are published to the user and published globally.|
-|[How to Delete a Connection Group](appv-delete-a-connection-group.md)|Explains how to delete a connection group.|
-|[How to Publish a Connection Group](appv-publish-a-connection-group.md)|Explains how to publish a connection group.|
-|[How to Make a Connection Group Ignore the Package Version](appv-configure-connection-groups-to-ignore-the-package-version.md)|Explains how to configure a connection group to accept any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.|
-[How to Allow Only Administrators to Enable Connection Groups](appv-allow-administrators-to-enable-connection-groups.md)|Explains how to configure the App-V client so that only administrators (not end users) can enable or disable connection groups.|
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Other resources for App-V connection groups
-
-
-- [Operations for App-V](appv-operations.md)
-
-
-
-
-
-
-
-
-
diff --git a/windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version.md b/windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version.md
deleted file mode 100644
index cb9d2085c06..00000000000
--- a/windows/application-management/app-v/appv-migrating-to-appv-from-a-previous-version.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Migrating to App-V from a Previous Version (Windows 10/11)
-description: Learn how to migrate to Microsoft Application Virtualization (App-V) for Windows 10/11 from a previous version.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Migrating to App-V from previous versions
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-To migrate from App-V 4.x to App-V for Windows 10/11, you must upgrade to App-V 5.x first.
-
-## Improvements to the App-V Package Converter
-
-
-You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
-
-You can also use the `–OSDsToIncludeInPackage` parameter with the `ConvertFrom-AppvLegacyPackage` cmdlet to specify which .osd files’ information is converted and placed within the new package.
-
-|New in App-V for Windows client|Prior to App-V for Windows 10|
-|--- |--- |
-|New .xml files are created corresponding to the .osd files associated with a package; these files include the following information:
environment variables
shortcuts
file type associations
registry information
scripts
You can now choose to add information from a subset of the .osd files in the source directory to the package using the -OSDsToIncludeInPackage parameter.|Registry information and scripts included in .osd files associated with a package weren't included in package converter output.
The package converter would populate the new package with information from all of the .osd files in the source directory.|
-
-### Example conversion statement
-
-To understand the new process, review the following example `ConvertFrom-AppvLegacyPackage` package converter statement.
-
-**If the source directory (\\\\OldPkgStore\\ContosoApp) includes the following:**
-
-- ContosoApp.sft
-
-- ContosoApp.msi
-
-- ContosoApp.sprj
-
-- ContosoApp\_manifest.xml
-
-- X.osd
-
-- Y.osd
-
-- Z.osd
-
-**And you run this command:**
-
-``` syntax
-ConvertFrom-AppvLegacyPackage –SourcePath \\OldPkgStore\ContosoApp\
--DestinationPath \\NewPkgStore\ContosoApp\
--OSDsToIncludeInPackage X.osd,Y.osd
-```
-
-**The following is created in the destination directory (\\\\NewPkgStore\\ContosoApp):**
-
-- ContosoApp.appv
-
-- ContosoApp.msi
-
-- ContosoApp\_DeploymentConfig.xml
-
-- ContosoApp\_UserConfig.xml
-
-- X\_Config.xml
-
-- Y\_Config.xml
-
-- Z\_Config.xml
-
-**In the above example:**
-
-|These Source directory files…|…are converted to these Destination directory files…|…and will contain these items|Description|
-|--- |--- |--- |--- |
-|
X.osd
Y.osd
Z.osd|
X_Config.xml
Y_Config.xml
Z_Config.xml|
Environment variables:
Shortcuts
File type associations
Registry information
Scripts|Each .osd file is converted to a separate, corresponding .xml file that contains the items listed here in App-V deployment configuration format. These items can then be copied from these .xml files and placed in the deployment configuration or user configuration files as desired. In this example, there are three .xml files, corresponding with the three .osd files in the source directory. Each .xml file contains the environment variables, shortcuts, file type associations, registry information, and scripts in its corresponding .osd file.|
-|
X.osd
Y.osd|
ContosoApp.appv
ContosoApp_DeploymentConfig.xml
ContosoApp_UserConfig.xml|
Environment variables
Shortcuts
File type associations|The information from the .osd files specified in the -OSDsToIncludeInPackage parameter is converted and placed inside the package. The converter then populates the deployment configuration file and the user configuration file with the contents of the package, just as App-V Sequencer does when sequencing a new package. In this example, environment variables, shortcuts, and file type associations included in X.osd and Y.osd were converted and placed in the App-V package, and some of this information was also included in the deployment configuration and user configuration files. X.osd and Y.osd were used because they were included as arguments to the -OSDsToIncludeInPackage parameter. No information from Z.osd was included in the package, because it wasn't included as one of these arguments.|
-
-## Converting packages created using a prior version of App-V
-
-
-Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses Windows PowerShell to convert packages and can help automate the process if you have many packages that require conversion. App-V packages created with App-V 5.x don't need to be converted.
-
-
-**Important**
-After you convert an existing package you should test the package prior to deploying the package to ensure the conversion process was successful.
-
-
-
-**What to know before you convert existing packages**
-
-|Issue|Workaround|
-|--- |--- |
-|Virtual packages using DSC aren't linked after conversion.|Link the packages using connection groups. See [Managing Connection Groups](appv-managing-connection-groups.md).|
-|Environment variable conflicts are detected during conversion.|Resolve any conflicts in the associated **.osd** file.|
-|Hard-coded paths are detected during conversion.|Hard-coded paths are difficult to convert correctly. The package converter will detect and return packages with files that contain hard-coded paths. View the file with the hard-coded path, and determine whether the package requires the file. If so, it's recommended to re-sequence the package.|
-
-When converting a package check for failing files or shortcuts, locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
-
-**Note**
-It's recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
-
-If a converted package doesn't open after you convert it, it's also recommended that you resequence the application using the App-V sequencer.
-
-[How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
-
-## Migrating the App-V Server Full Infrastructure
-
-
-There's no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server.
-
-|Task|More Information|
-|--- |--- |
-|Review prerequisites.|[App-V Server prerequisite software](appv-prerequisites.md#app-v-server-prerequisite-software)|
-|Enable the App-V client.|[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)|
-|Install App-V Server.|[How to Deploy the App-V Server](appv-deploy-the-appv-server.md)|
-|Migrate existing packages.|See [Converting packages created using a prior version of App-V](#converting-packages-created-using-a-prior-version-of-app-v) earlier in this article.|
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Other resources for performing App-V migration tasks
-
-- [Operations for App-V](appv-operations.md)
-
-- [A simplified Microsoft App-V 5.1 Management Server upgrade procedure](/archive/blogs/appv/a-simplified-microsoft-app-v-5-1-management-server-upgrade-procedure)
diff --git a/windows/application-management/app-v/appv-modify-an-existing-virtual-application-package.md b/windows/application-management/app-v/appv-modify-an-existing-virtual-application-package.md
deleted file mode 100644
index d9b051f74f2..00000000000
--- a/windows/application-management/app-v/appv-modify-an-existing-virtual-application-package.md
+++ /dev/null
@@ -1,155 +0,0 @@
----
-title: How to Modify an Existing Virtual Application Package (Windows 10/11)
-description: Learn how to modify an existing virtual application package and add a new application to an existing virtual application package.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to Modify an Existing Virtual Application Package
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This article explains how to:
-
-- [Update an application in an existing virtual application package](#update-an-application-in-an-existing-virtual-application-package)
-
-- [Modify the properties associated with an existing virtual application package](#modify-the-properties-associated-with-an-existing-virtual-application-package)
-
-- [Add a new application to an existing virtual application package](#add-a-new-application-to-an-existing-virtual-application-package)
-
-**Before you update a package:**
-
-- Ensure that you’ve installed the Microsoft Application Virtualization (App-V) Sequencer, which is required for modifying a virtual application package. To install the App-V Sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
-
-- Save the .appv file in a secure location and always trust the source before trying to open the package for editing.
-
-- The Managing Authority section is erroneously removed from the deployment configuration file when you update a package. Before starting the update, copy the Managing Authority section from the existing deployment configuration file, and then paste the copied section into the new configuration file after the conversion is complete.
-
-- If you click **Modify an Existing Virtual Application Package** in the Sequencer in order to edit a package, but then make no changes and close the package, the streaming behavior of the package is changed. The primary feature block is removed from the StreamMap.xml file, and any files that were listed in the publishing feature block are removed. Users who receive the edited package experience that package as if it were stream-faulted, regardless of how the original package was configured.
-
-## Update an application in an existing virtual application package
-
-1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
-
-2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package** > **Next**.
-
-3. On the **Select Task** page, click **Update Application in Existing Package** > **Next**.
-
-4. On the **Select Package** page, click **Browse** to locate the virtual application package that contains the application to update, and then click **Next**.
-
-5. On the **Prepare Computer** page, review the issues that could cause the application update to fail or cause the updated application to contain unnecessary data. Resolve all potential issues before you continue. After making any corrections and resolving all potential issues, click **Refresh** > **Next**.
-
- **Important**
- If you're required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files are added to the package.
-
-6. On the **Select Installer** page, click **Browse** and specify the update installation file for the application. If the update doesn't have an associated installer file, and if you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
-
-7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application update so the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and then locate and run the additional installation files. When you're finished with the installation, select **I am finished installing**. Click **Next**.
-
- >**Note** The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard.
-
-8. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information. To proceed, click **Next**.
-
-9. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all of the applications to run. After all applications have run, close each of the applications, and then click **Next**.
-
- >**Note** You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop**, and then select either **Stop all applications** or **Stop this application only**.
-
-10. On the **Create Package** page, to modify the package without saving it, select the check box for **Continue to modify package without saving using the package editor**. When you select this option, the package opens in the App-V Sequencer console, where you can modify the package before it's saved. Click **Next**.
-
- To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful to identify the application version and provide other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. Click **Create**.
-
-11. On the **Completion** page, click **Close** to close the wizard. The package is now available in the sequencer.
-
-
-## Modify the properties associated with an existing virtual application package
-
-1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
-
-2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package** > **Next**.
-
-3. On the **Select Task** page, click **Edit Package** > **Next**.
-
-4. On the **Select Package** page, click **Browse** to locate the virtual application package that contains the application properties to modify, and then click **Edit**.
-
-5. In the App-V Sequencer console, perform any of the following tasks as needed:
-
- - Import and export the manifest file.
-
- - Enable or disable Browser Helper Objects.
-
- - Import or export a VFS file.
-
- - Import a directory into the virtual file system.
-
- - Import and export virtual registry keys.
-
- - View package properties.
-
- - View associated package files.
-
- - Edit registry settings.
-
- - Review the extra package settings (except operating system file properties).
-
- - Set virtualized registry key state (override or merge).
-
- - Set virtualized folder state.
-
- - Add or edit shortcuts and file type associations.
-
- >**Note** To edit shortcuts or file type associations, you must first open the package for upgrade to add a new application, and then proceed to the final editing page.
-
-6. When you finish changing the package properties, click **File** > **Save** to save the package.
-
-## Add a new application to an existing virtual application package
-
-1. On the computer that runs the sequencer, click **All Programs**, point to **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
-
-2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package** > **Next**.
-
-3. On the **Select Task** page, click **Add New Application** > **Next**.
-
-4. On the **Select Package** page, click **Browse** to locate the virtual application package to which you'll add the application, and then click **Next**.
-
-5. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or cause the revised package to contain unnecessary data. Resolve all potential issues before you continue. After making any corrections and resolving all potential issues, click **Refresh** > **Next**.
-
- >**Important** If you're required to disable virus scanning software, first scan the computer that runs the sequencer to ensure that no unwanted or malicious files can be added to the package.
-
-6. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application doesn't have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
-
-7. On the **Installation** page, when the sequencer and application installer are ready, install the application so that the sequencer can monitor the installation process. If more installation files must be run as part of the installation, click **Run**, and locate and run those installation files. When you finish the installation, select **I am finished installing** > **Next**. In the **Browse for Folder** dialog box, specify the primary directory where the application will be installed. Ensure that this directory is a new location so that you don’t overwrite the existing version of the virtual application package.
-
- >**Note** The sequencer monitors all changes and installations that occur on the computer that runs the sequencer. This includes any changes and installations that are performed outside of the sequencing wizard.
-
-8. On the **Configure Software** page, optionally run the programs contained in the package. This step completes 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 the same time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs 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**.
-
-9. On the **Installation Report** page, you can review information about the updated virtual application. In **Additional Information**, double-click the event to obtain more detailed information, and then click **Next** to open the **Customize** page.
-
-10. If you're finished installing and configuring the virtual application, select **Stop now** and skip to step 13 of this procedure. If you want to perform the following described customization, click **Customize**.
-
- If you're customizing, prepare the virtual package for streaming, and then click **Next**. Streaming improves the experience when the virtual application package is run on target computers.
-
-11. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
-
- >**Note** You can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and then select either **Stop all applications** or **Stop this application only**.
-
-12. On the **Create Package** page, to modify the package without saving it, select the **Continue to modify package without saving using the package editor** check box. Selecting this option opens the package in the App-V Sequencer console, where you can modify the package before saving it. Click **Next**.
-
- To save the package immediately, select the default **Save the package now**. Add optional **Comments** to associate with the package. Comments are useful for providing application versions and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. Click **Create**.
-
-13. On the **Completion** page, click **Close**. The package is now available in the sequencer.
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-modify-client-configuration-with-powershell.md b/windows/application-management/app-v/appv-modify-client-configuration-with-powershell.md
deleted file mode 100644
index 84f2710b451..00000000000
--- a/windows/application-management/app-v/appv-modify-client-configuration-with-powershell.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: How to Modify Client Configuration by Using Windows PowerShell (Windows 10/11)
-description: Learn how to modify the Application Virtualization (App-V) client configuration by using Windows PowerShell.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to Modify Client Configuration by Using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to configure the App-V client configuration.
-
-1. To configure the client settings using Windows PowerShell, use the **Set-AppVClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
-
-2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppVClientConfiguration** with any required parameters. For example:
-
- `$config = Get-AppVClientConfiguration`
-
- `Set-AppVClientConfiguration $config`
-
- `Set-AppVClientConfiguration –Name1 MyConfig –Name2 "xyz"`
-
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-move-the-appv-server-to-another-computer.md b/windows/application-management/app-v/appv-move-the-appv-server-to-another-computer.md
deleted file mode 100644
index 2b4ee820e3e..00000000000
--- a/windows/application-management/app-v/appv-move-the-appv-server-to-another-computer.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: How to Move the App-V Server to Another Computer (Windows 10/11)
-description: Learn how to create a new management server console in your environment and learn how to connect it to the App-V database.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to move the App-V server to another computer
-
-**Applies to**
-- Windows Server 2016
-
-Use the following information to create a new management server console in your environment.
-
-## To create a new management server console
-
-
-Follow these steps to create a new management server console:
-
-1. Install the management server on a computer in your environment. For more information about installing the management server, see [Deploying the App-V server](appv-deploying-the-appv-server.md).
-
-2. After you've completed the installation, use the following link to connect it to the App-V database - [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md).
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-operations.md b/windows/application-management/app-v/appv-operations.md
deleted file mode 100644
index 8af6d33a4dc..00000000000
--- a/windows/application-management/app-v/appv-operations.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Operations for App-V (Windows 10/11)
-description: Learn about the various types of App-V administration and operating tasks that are typically performed by an administrator.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/18/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Operations for App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This section of the Microsoft Application Virtualization (App-V) Administrator’s Guide includes information about the various types of App-V administration and operating tasks that are typically performed by an administrator. This section also includes step-by-step procedures to help you successfully perform those tasks.
-
-## Operations Information
-
-- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
-
- Describes how to create, modify, and convert virtualized packages.
-- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
-
- Describes how to use the App-V Management console to perform tasks such as sequencing an application, changing a package, using a project template, and using a package accelerator.
-- [Managing Connection Groups](appv-managing-connection-groups.md)
-
- Describes how connection groups enable virtualized applications to communicate with each other in the virtual environment; explains how to create, publish, and delete them; and describes how connection groups can help you better manage your virtualized applications.
-- [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
-
- Describes how to deploy App-V packages by using an ESD.
-- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
-
- Describes how to perform client configuration tasks using the client management console.
-- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
-
- Provides instructions for migrating to App-V from a previous version.
-- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
-
- Describes the set of Windows PowerShell cmdlets available for administrators performing various App-V server tasks.
-
-## Additional information
-
-- [Application Virtualization (App-V) overview](appv-for-windows.md)
-- [Getting Started with App-V](appv-getting-started.md)
-- [Planning for App-V](appv-planning-for-appv.md)
-- [Deploying App-V](appv-deploying-appv.md)
-- [Troubleshooting App-V](appv-troubleshooting.md)
-- [Technical Reference for App-V](appv-technical-reference.md)
-
-
-
diff --git a/windows/application-management/app-v/appv-performance-guidance.md b/windows/application-management/app-v/appv-performance-guidance.md
deleted file mode 100644
index aca51695137..00000000000
--- a/windows/application-management/app-v/appv-performance-guidance.md
+++ /dev/null
@@ -1,496 +0,0 @@
----
-title: Performance Guidance for Application Virtualization
-description: Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Performance Guidance for Application Virtualization
-
-**Applies to**:
-
-- Windows 7 SP1
-- Windows 10
-- Windows 11
-- Server 2012 R2
-- Server 2016
-
-Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
-
-Implementing multiple methods can help you improve the end-user experience. However, your environment may not support all methods.
-
-You should read and understand the following information before reading this document.
-
-- [Application Virtualization (App-V) overview](appv-for-windows.md)
-
-- [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
-
-- [App-V Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760)
-
-> [!Note]
-> Some terms used in this document may have different meanings depending on external source and context. For more information about terms used in this document followed by an asterisk `*`, review the [Application Virtualization Performance Guidance Terminology](#bkmk-terms1) section of this document.
-
-Finally, this document will provide you with the information to configure the computer running App-V client and the environment for optimal performance. Optimize your virtual application packages for performance using the sequencer, and to understand how to use User Experience Virtualization (UE-V) or other user environment management technologies to provide the optimal user experience with App-V in both Remote Desktop Services (RDS) and non-persistent virtual desktop infrastructure (VDI).
-
-To help determine what information is relevant to your environment, you should review each section's brief overview and applicability checklist.
-
-## App-V in stateful\* non-persistent deployments
-
-This section provides information about an approach that helps ensure a user will have access to all virtual applications within seconds after logging in. This access is achieved by uniquely addressing the often long-running App-V publishing refresh. As you'll discover the basis of the approach, the fastest publishing refresh, is one that doesn't have to actually do anything. Many conditions must be met and steps followed to provide the optimal user experience.
-
-Use the information in the following section for more information:
-
-[Usage Scenarios](#bkmk-us) - As you review the two scenarios, keep in mind that these scenarios are the approach extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users and/or virtual applications packages.
-
-- Optimized for Performance – To provide the optimal experience, you can expect the base image to include some of the App-V virtual application package. This and other requirements are discussed.
-
-- Optimized for Storage – If you're concerned with the storage impact, following this scenario will help address those concerns.
-
-[Preparing your Environment](#bkmk-pe)
-
-- Steps to Prepare the Base Image – Whether in a non-persistent VDI or RDSH environment, only a few steps must be completed in the base image to enable this approach.
-
-- Use UE-V as the User Profile Management (UPM) solution for the App-V approach – the cornerstone of this approach is the ability of a UEM solution to persist the contents of just a few registry and file locations. These locations constitute the user integrations\*. Be sure to review the specific requirements for the UPM solution.
-
-[User Experience Walk-through](#bkmk-uewt)
-
-- Walk-through – It's a step-by-step walk-through of the App-V and UE-V operations and the expectations users should have.
-
-- Outcome – It describes the expected results.
-
-[Impact to Package Lifecycle](#bkmk-plc)
-
-[Enhancing the VDI Experience through Performance Optimization/Tuning](#bkmk-evdi)
-
-### Applicability Checklist
-
-|Checklist|Deployment Environment|
-|--- |--- |
-||Non-Persistent VDI or RDSH.|
-||User Experience Virtualization (UE-V), other UPM solutions or User Profile Disks (UPD).|
-
-|Checklist|Expected Configuration|
-|--- |--- |
-||User Experience Virtualization (UE-V) with the App-V user state template enabled or User Profile Management (UPM) software. Non-UE-V UPM software must be capable of triggering on Login or Process/Application Start and Logoff.|
-||App-V Shared Content Store (SCS) is configured or can be configured.|
-
-
-|Checklist|IT Administration|
-|--- |--- |
-||Admin may need to update the VM base image regularly to ensure optimal performance or Admin may need to manage multiple images for different user groups.|
-
-### Usage Scenarios
-
-As you review the two scenarios, keep in mind that these scenarios represent the extremes. Based on your usage requirements, you may choose to apply these steps to a subset of users, virtual application packages, or both.
-
-- **Performance**: To provide the most optimal user experience, this approach uses the capabilities of a UPM solution and requires extra image preparation and can incur some more image management overhead.
-
- The following section describes many performance improvements in stateful non-persistent deployments. For more information, see [Sequencing Steps to Optimize Packages for Publishing Performance](#sequencing-steps-to-optimize-packages-for-publishing-performance) (in this article).
-
-- **Storage**: The general expectations of the previous scenario still apply here. However, keep in mind that VM images are typically stored in costly arrays; a slight alteration has been made to the approach. Don't pre-configure user-targeted virtual application packages in the base image.
-
- The impact of this alteration is detailed in the [User Experience Walk-through](#bkmk-uewt) (in this article).
-
-### Preparing your Environment
-
-The following information displays the required steps to prepare the base image and the UE-V or another UPM solution for the approach.
-
-#### Prepare the Base Image
-
-- **Performance**:
-
- - Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
- - Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
- - Configure for Shared Content Store (SCS) mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
- - Configure Preserve User Integrations on Login Registry DWORD.
- - Pre-configure all user and global-targeted packages, for example, **Add-AppvClientPackage**.
- - Pre-configure all user- and global-targeted connection groups, for example, **Add-AppvClientConnectionGroup**.
- - Pre-publish all global-targeted packages. Or:
- - Perform a global publishing/refresh.
- - Perform a user publishing/refresh.
- - Unpublish all user-targeted packages.
- - Delete the following user-Virtual File System (VFS) entries:
-
- - `AppData\Local\Microsoft\AppV\Client\VFS`
- - `AppData\Roaming\Microsoft\AppV\Client\VFS`
-
-- **Storage**:
-
- - Enable the App-V client as described in [Enable the App-V in-box client](appv-enable-the-app-v-desktop-client.md).
- - Enable UE-V and download the App-V Settings Template from the UE-V template Gallery, see the following steps.
- - Configure for Shared Content Store (SCS) mode. For more information, see [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
- - Configure Preserve User Integrations on Login Registry DWORD.
- - Pre-configure all global-targeted packages, for example, **Add-AppvClientPackage**.
- - Pre-configure all global-targeted connection groups, for example, **Add-AppvClientConnectionGroup**.
- - Pre-publish all global-targeted packages.
-
-#### Configurations
-
-For critical App-V Client configurations and for a little more context and how-to, review the following configuration settings:
-
-- **Shared Content Store (SCS) Mode**: When running the shared content store, only publishing data is maintained on hard disk; other virtual application assets are maintained in memory (RAM). Such a result helps to conserve local storage and minimize disk I/O per second (IOPS).
-
- This setting is recommended when low-latency connections are available between the App-V Client endpoint and the SCS content server, SAN.
-
- - Configurable in Windows PowerShell: `Set-AppvClientConfiguration -SharedContentStoreMode 1`
- - Configurable with Group Policy: See [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md).
-
-- **PreserveUserIntegrationsOnLogin**: If you have not pre-configured (**Add-AppvClientPackage**) a specific package and this setting isn't configured, the App-V Client will de-integrate* the persisted user integrations, then reintegrate*.
-
- For every package that meets the above conditions, effectively twice the work will be done during publishing/refresh.
-
- If you don't plan to pre-configure every available user package in the base image, use this setting.
-
- - Configure in the Registry under `HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Integration`.
- - Create the DWORD value **PreserveUserIntegrationsOnLogin** with a value of 1.
- - Restart the App-V client service or restart the computer running the App-V Client.
-
-- **MaxConcurrentPublishingRefresh**: This setting determines the number of users that can perform a publishing refresh/sync at the same time. The default setting is no limit.
-
- Limiting the number of concurrent publishing refreshes prevents excessive CPU usage that could impact computer performance. This limit is recommended in an RDS environment, where multiple users can log in to the same computer at the same time and perform a publishing refresh sync.
-
- If the concurrent publishing refresh threshold is reached, the time required to publish new applications and make them available to end users after they sign in could take an indeterminate amount of time.
-
- - Configure in the Registry under `HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Publishing`.
- - Create the DWORD value **MaxConcurrentPublishingrefresh** with the desired maximum number of concurrent publishing refreshes.
- - The App-V client service and computer don't need to be restarted.
-
-### Configure UE-V solution for App-V Approach
-
-We recommend using User Experience Virtualization (UE-V) to capture and centralize application settings and Windows operating system settings for a specific user. These settings are then applied to the different computers that are accessed by the user, including desktop computers, laptop computers, and virtual desktop infrastructure (VDI) sessions. UE-V is optimized for RDS and VDI scenarios.
-
-For more information, see:
-
-- [User Experience Virtualization (UE-V) for Windows client overview](/windows/configuration/ue-v/uev-for-windows)
-
-- [Get Started with UE-V](/windows/configuration/ue-v/uev-getting-started)
-
-> [!Note]
-> Without performing an additional configuration step, User Environment Virtualization (UE-V) won't be able to synchronize the Start menu shortcuts (.lnk files) on the target computer. The .lnk file type is excluded by default.
-
-UE-V will only support removing the .lnk file type from the exclusion list in the RDS and VDI scenarios, where every user's device will have the same set of applications installed to the same location and every .lnk file is valid for all the users' devices. For example, UE-V wouldn't currently support the following two scenarios, because the net result will be that the shortcut will be valid on one but not all devices.
-
-- If a user has an application installed on one device with .lnk files enabled and the same native application installed on another device to a different installation root with .lnk files enabled.
-
-- If a user has an application installed on one device but not another with .lnk files enabled.
-
-> [!Important]
-> This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
-
-Using the Microsoft Registry Editor (regedit.exe), navigate to `HKEY\_LOCAL\_MACHINE\Software\Microsoft\UEV\Agent\Configuration\ExcludedFileTypes` and remove `.lnk` from the excluded file types.
-
-## Configure other User Profile Management (UPM) solutions for App-V Approach
-
-The expectation in a stateful environment is that a UPM solution is implemented and can support persistence of user data across sessions and between logins.
-
-The requirements for the UPM solution are as follows.
-
-To enable an optimized sign-in experience, for example the App-V approach for the user, the solution must be capable of:
-
-- Persisting the below user integrations as part of the user profile/persona.
-
-- Triggering a user profile sync on sign in (or application start), which can guarantee that all user integrations are applied before publishing/refresh begin, or,
-
-- Attaching and detaching a user profile disk (UPD) or similar technology that contains the user integrations.
-
- > [!Note]
- >
- > App-V is supported when using UPD only when the entire profile is stored on the user profile disk.
- >
- > App-V packages are not supported when using UPD with selected folders stored in the user profile disk. The Copy on Write driver doesn't handle UPD selected folders.
-
-- Capturing changes to the locations, which constitute the user integrations, prior to session sign out.
-
-With App-V when you add a publishing server (**Add-AppvPublishingServer**) you can configure synchronization, for example refresh during a sign in and/or after a specified refresh interval. In both cases, a scheduled task is created.
-
-In previous versions of App-V, both scheduled tasks were configured using a VBScript that would initiate the user and global refresh. Starting with Hotfix Package 4 for Application Virtualization 5.0 SP2, the user refresh on a sign in was initiated by **SyncAppvPublishingServer.exe**. This change was introduced to provide UPM solutions a trigger process. This process delays the publish /refresh to allow the UPM solution to apply the user integrations. It will exit once the publishing/refresh is complete.
-
-### User Integrations
-
-Registry – HKEY\_CURRENT\_USER
-
-- Path - Software\\Classes
-
- Exclude: Local Settings, ActivatableClasses, AppX\*
-
-- Path - Software\\Microsoft\\AppV
-
-- Path- Software\\Microsoft\\Windows\\CurrentVersion\\App Paths
-
-### File Locations
-
-- Root – “Environment Variable” APPDATA
-
- Path – Microsoft\\AppV\\Client\\Catalog
-
-- Root – “Environment Variable” APPDATA
-
- Path – Microsoft\\AppV\\Client\\Integration
-
-- Root – “Environment Variable” APPDATA
-
- Path - Microsoft\\Windows\\Start Menu\\Programs
-
-- (To persist all desktop shortcuts, virtual and non-virtual)
-
- Root - “KnownFolder” {B4BFCC3A-DB2C-424C-B029-7FE99A87C641}FileMask - \*.lnk
-
-### User Experience Walk-through
-
-This following process is a step-by-step walk-through of the App-V and UPM operations, and the users' expectations.
-
-- **Performance**: After implementing this approach in the VDI/RDSH environment, on first login,
- - (Operation) A user-publishing/refresh is initiated.
-
- (Expectation) If it's the first time that a user has published virtual applications (for example, non-persistent), this operation will take the usual duration of a publishing/refresh.
-
-- (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
-
- (Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-out process. This result will incur the same/similar overhead as persisting the user state.
-
- **On subsequent logins**:
-
- - (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
-
- (Expectation) There will be shortcuts present on the desktop, or in the start menu, which work immediately. When the publishing/refresh completes (that is, package entitlements change), some may go away.
-
- - (Operation) Publishing/refresh will process unpublish and publish operations for changes in user package entitlements.
-
- (Expectation) If there are no entitlement changes, publishing will complete in seconds. Otherwise, the publishing/refresh will increase relative to the number and complexity of virtual applications
-
- The publishing operation (**Publish-AppVClientPackage**) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps.
-
- - (Operation) UPM solution will capture user integrations again at sign off.
-
- (Expectation) Same as previous.
-
- **Outcome**:
-
- - Because the user integrations are entirely preserved, there will be no work for example, integration for the publishing/refresh to complete. All virtual applications will be available within seconds of sign in.
- - The publishing/refresh will process changes to the users-entitled virtual applications, which impacts the experience.
-
-- **Storage**: After implementing this approach in the VDI/RDSH environment, on first login
-
- - (Operation) A user-publishing/refresh is initiated.
-
- (Expectation):
-
- - If this instance is the first time a user has published virtual applications (for example, non-persistent), this will take the usual duration of a publishing/refresh.
- - First and subsequent logins will be impacted by pre-configuring of packages (add/refresh).
-
- - (Operation) After the publishing/refresh, the UPM solution captures the user integrations.
-
- (Expectation) Depending on how the UPM solution is configured, this capture may occur as part of the sign-off process. This result will incur the same/similar overhead as persisting the user state.
-
- **On subsequent logins**:
-
- - (Operation) UPM solution applies the user integrations to the system prior to publishing/refresh.
- - (Operation) Add/refresh must pre-configure all user targeted applications.
-
- - (Expectation):
- - This may increase the time to application availability significantly (on the order of 10s of seconds).
- - This will increase the publishing refresh time relative to the number and complexity* of virtual applications.
-
- - (Operation) Publishing/refresh will process unpublish and publish operations for changes to user package entitlements.
-
- **Outcome**: Because the add/refresh must reconfigure all the virtual applications to the VM, the publishing refresh time on every login will be extended.
-
-### Impact to Package Life Cycle
-
-Upgrading a package is a crucial aspect of the package lifecycle. To help guarantee users have access to the appropriate upgraded (published) or downgraded (unpublished) virtual application packages, it's recommended you update the base image to reflect these changes. To understand why review the following section:
-
-App-V 5.0 SP2 introduced the concept of pending states. In the past,
-
-- If an administrator changed entitlements or created a new version of a package (upgraded) and during a publishing/refresh that package was in-use, the unpublish or publish operation, respectively, would fail.
-
-- Now, if a package is in use, the operation will be pended. The unpublish and publish-pend operations will be processed on service restart or if another publish or unpublish command is issued. In the latter case, if the virtual application is in-use otherwise, the virtual application will remain in a pending state. For globally published packages, a restart (or service restart) often needed.
-
-In a non-persistent environment, it's unlikely these pended operations will be processed. The pended operations, for example tasks are captured under **HKEY\_CURRENT\_USER** \\ **Software** \\ **Microsoft** \\ **AppV** \\ **Client** \\ **PendingTasks**. Although this location is persisted by the UPM solution, if it isn't applied to the environment prior to a sign in, it will not be processed.
-
-### Enhancing the VDI Experience through Performance Optimization Tuning
-
-The following section contains lists with information about Microsoft documentation and downloads that may be useful when optimizing your environment for performance.
-
-#### Windows Server
-
-Server performance tuning guidelines for [Microsoft Windows Server 2012 R2](/previous-versions/dn529133(v=vs.85))
-
-#### Server roles
-
-- [Remote Desktop Virtualization Host](/previous-versions/dn567643(v=vs.85))
-
-- [Remote Desktop Session Host](/previous-versions/dn567648(v=vs.85))
-
-- [IIS Relevance: App-V Management, Publishing, Reporting Web Services](/previous-versions/dn567678(v=vs.85))
-
-- [File Server (SMB) Relevance: If used for App-V Content Storage and Delivery in SCS Mode](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj134210(v=ws.11))
-
-#### Windows Client (guest OS) performance tuning guidance
-
-- [The Microsoft Premier Field Engineer (PFE) view on Virtual Desktop (VDI) Density](/archive/blogs/jeff_stokes/the-microsoft-premier-field-engineer-pfe-view-on-virtual-desktop-vdi-density)
-
-- [Optimization Script: (Provided by Microsoft Support)](/archive/blogs/jeff_stokes/hot-off-the-presses-get-it-now-the-windows-8-vdi-optimization-script-courtesy-of-pfe)
-
-## Sequencing Steps to Optimize Packages for Publishing Performance
-
-Several App-V features facilitate new scenarios or enable new customer deployment scenarios. These following features can impact the performance of the publishing and launch operations.
-
-|Step|Consideration|Benefits|Tradeoffs|
-|--- |--- |--- |--- |
-|No Feature Block 1 (FB1, also known as Primary FB)|No FB1 means the application will launch immediately and stream fault (application requires file, DLL and must pull down over the network) during launch. If there are network limitations, FB1 will:
Reduce the number of stream faults and network bandwidth used when you launch an application for the first time.
Delay launch until the entire FB1 has been streamed.|Stream faulting decreases the launch time.|Virtual application packages with FB1 configured will need to be resequenced.|
-
-### Removing FB1
-
-Removing FB1 doesn't require the original application installer. After completing the following steps, it's suggested that you revert the computer running the sequencer to a clean snapshot.
-
-**Sequencer UI** - Create a New Virtual Application Package.
-
-1. Complete the sequencing steps up to Customize -> Streaming.
-
-2. At the Streaming step, don't select **Optimize the package for deployment over slow or unreliable network**.
-
-3. If desired, move on to **Target OS**.
-
-**Modify an Existing Virtual Application Package**
-
-1. Complete the sequencing steps up to Streaming.
-
-2. Don't select **Optimize the package for deployment over a slow or unreliable network**.
-
-3. Move to **Create Package**.
-
-**Windows PowerShell** - Update an Existing Virtual Application Package.
-
-1. Open an elevated Windows PowerShell session.
-
-2. Import-module **appvsequencer**.
-
-3. **Update-AppvSequencerPackage** - **AppvPackageFilePath**
-
- "C:\\Packages\\MyPackage.appv" -Installer
-
- "C:\\PackageInstall\\PackageUpgrade.exe empty.exe" -OutputPath
-
- "C:\\UpgradedPackages"
-
- > [!Note]
- > This cmdlet requires an executable (.exe) or batch file (.bat). You must provide an empty (does nothing) executable or batch file.
-
-|Step|Considerations|Benefits|Tradeoffs|
-|--- |--- |--- |--- |
-|No SXS Install at Publish (Pre-Install SxS assemblies)|Virtual Application packages don't need to be resequenced. SxS Assemblies can remain in the virtual application package.|The SxS Assembly dependencies won't install at publishing time.|SxS Assembly dependencies must be pre-installed.|
-
-
-### Creating a new virtual application package on the sequencer
-
-If, during sequencer monitoring, an SxS Assembly (such as a VC++ Runtime) is installed as part of an application's installation, SxS Assembly will be automatically detected and included in the package. The administrator will be notified and will have the option to exclude the SxS Assembly.
-
-**Client Side**:
-
-When publishing a virtual application package, the App-V Client will detect if a required SxS dependency is already installed. If the dependency is unavailable on the computer and it's included in the package, a traditional Windows Installer (.**msi**) installation of the SxS assembly will be initiated. As previously documented, simply install the dependency on the computer running the client to ensure that the Windows Installer (.msi) installation won't occur.
-
-|Step|Considerations|Benefits|Tradeoffs|
-|--- |--- |--- |--- |
-|Selectively Employ Dynamic Configuration files|The App-V client must parse and process these Dynamic Configuration files.
Be conscious of size and complexity (script execution, VREG inclusions/exclusions) of the file.
Numerous virtual application packages may already have User- or computer–specific dynamic configurations files.|Publishing times will improve if these files are used selectively or not at all.|Virtual application packages would need to be reconfigured individually or via the App-V server management console to remove associated Dynamic Configuration files.|
-
-
-### Disabling a Dynamic Configuration by using Windows PowerShell
-
-- For already published packages, you can use `Set-AppVClientPackage –Name Myapp –Path c:\Packages\Apps\MyApp.appv` without
-
- **-DynamicDeploymentConfiguration** parameter
-
-- Similarly, when adding new packages using `Add-AppVClientPackage –Path c:\Packages\Apps\MyApp.appv`, don't use the
-
- **-DynamicDeploymentConfiguration** parameter.
-
-For documentation on How to Apply a Dynamic Configuration, see:
-
-- [How to Apply the User Configuration File by Using Windows PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
-
-- [How to Apply the Deployment Configuration File by Using Windows PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
-
-|Step|Considerations|Benefits|Tradeoffs|
-|--- |--- |--- |--- |
-|Account for Synchronous Script Execution during Package Lifecycle.|If script collateral is embedded in the package, Add cmdlets may be slower. Running of scripts during virtual application launch (StartVirtualEnvironment, StartProcess) and/or Add+Publish will impact the perceived performance during one or more of these lifecycle operations.|Use of Asynchronous (Non-Blocking) Scripts will ensure that the lifecycle operations complete efficiently.|This step requires working knowledge of all virtual application packages with embedded script collateral, which have associated dynamic configurations files and which reference and run scripts synchronously.|
-|Remove Extraneous Virtual Fonts from Package.|Most applications investigated by the App-V product team contained a few fonts, typically fewer than 20.|Virtual Fonts impact publishing refresh performance.|Desired fonts will need to be enabled/installed natively. For instructions, see Install or uninstall fonts.|
-
-### Determining what virtual fonts exist in the package
-
-- Make a copy of the package.
-
-- Rename Package\_copy.appv to Package\_copy.zip
-
-- Open AppxManifest.xml and locate the following syntax:
-
- ```xml
-
-
-
-
- ```
-
- > [!Note]
- > If there are fonts marked as **DelayLoad**, those won't impact first launch.
-
-### Excluding virtual fonts from the package
-
-Use the dynamic configuration file that best suits the user scope – deployment configuration for all users on computer, user configuration for specific user or users.
-
-- Disable fonts with the deployment or user configuration.
-
-Fonts
-
-```xml
--->
-
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-Help us to improve
diff --git a/windows/application-management/app-v/appv-reporting.md b/windows/application-management/app-v/appv-reporting.md
deleted file mode 100644
index 2e05013ad94..00000000000
--- a/windows/application-management/app-v/appv-reporting.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: About App-V Reporting (Windows 10/11)
-description: Learn how the App-V reporting feature collects information about computers running the App-V client and virtual application package usage.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/16/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# About App-V reporting
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Application Virtualization (App-V) includes a built-in reporting feature that collects information about computers running the App-V client and virtual application package usage. You can generate reports from a centralized database with this information.
-
-## App-V reporting overview
-
-The following list displays the end–to-end high-level workflow for reporting in App-V.
-
-1. The App-V Reporting server requires the following things:
-
- * Internet Information Service (IIS) web server role
- * Windows Authentication role (under **IIS / Security**)
- * SQL Server installed and running with SQL Server Reporting Services (SSRS)
-
- To confirm SQL Server Reporting Services is running, enter `https://localhost/Reports` in a web browser as administrator on the server that will host App-V Reporting. The SQL Server Reporting Services Home page should appear.
-2. Install the App-V reporting server and associated database. For more information about installing the reporting server, see [How to install the Reporting Server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md). Configure the time when the computer running the App-V client should send data to the reporting server.
-3. If you aren't using an electronic software distribution system such as Configuration Manager to view reports, then you can define reports in SQL Server Reporting Service.
-
- > [!NOTE]
- >If you are using the Configuration Manager integration with App-V, most reports are generated from Configuration Manager rather than from App-V.
-4. After importing the App-V Windows PowerShell module using **Import-Module AppvClient** as administrator, enable App-V client reporting. This sample Windows PowerShell command enables App-V reporting:
-
- ```PowerShell
- Set-AppvClientConfiguration -ReportingServerURL : -ReportingEnabled 1 -ReportingStartTime <0-23> -ReportingRandomDelay <#min>
- ```
-
- To immediately send App-V report data, run **Send-AppvClientReport** on the App-V client.
-
- For more information about configuring reporting on the App-V client, see [About client configuration settings](appv-client-configuration-settings.md). To administer App-V Reporting with Windows PowerShell, see [How to enable reporting on the App-V client by using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
-5. After the reporting server receives the data from the App-V client, it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server, which then notifies the App-V client.
-6. When the App-V client receives the success notification, it empties the data cache to conserve space.
-
- > [!NOTE]
- >By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
-
- If the App-V client device doesn't receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
-
-### App-V reporting server frequently asked questions
-
-The following sections provide answers to frequently asked questions about how App-V reporting works.
-
-#### How frequently is reporting information sent to the reporting database?
-
-Frequency depends on the computer running the App-V client's reporting configuration. You must configure the frequency or interval for sending the reporting data manually, as App-V reporting isn't enabled by default.
-
-#### What information is stored in the reporting server database?
-
-The following information is stored in the reporting database:
-
-* The operating system running on the computer running the App-V client: host name, version, service pack, type - client/server, processor architecture.
-* App-V client information: version.
-* Published package list: GUID, version GUID, name.
-* Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time.
-
-#### What is the average volume of information that is sent to the reporting server?
-
-It depends. Three sets of data can be sent to the reporting server:
-
-* Operating system and App-V client information, which is about 150 Bytes every time it gets sent to the server.
-* Published package lists, which are about 7 KB per 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there's no change, this information isn't sent.
-* Virtual application usage information is about 0.25 KB per event. Opening and closing count as one event if both occur before sending the information. When the information is sent through a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the Windows PowerShell cmdlet, there's an optional argument called **DeleteOnSuccess** that controls if the data needs to be resent the next time around.
-
-For example, if 20 applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15 KB + 20 × 0.25 KB, or about 5 KB/user.
-
-#### Can I schedule reporting?
-
-Yes. Besides manually sending reporting using Windows PowerShell cmdlets (**Send-AppvClientReport**), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:
-
-* Using a Windows PowerShell cmdlet: **Set-AppvClientConfiguration**. For example:
-
- ```PowerShell
- Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL http://any.com/appv-reporting
- ```
-
- For a complete list of client configuration settings, go to [About client configuration settings](appv-client-configuration-settings.md) and look for the following entries: **ReportingEnabled**, **ReportingServerURL**, **ReportingDataCacheLimit**, **ReportingDataBlockSize**, **ReportingStartTime**, **ReportingRandomDelay**, **ReportingInterval**.
-* Using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.
-
- > [!NOTE]
- >Group Policy settings override local settings configured using Windows PowerShell.
-
-## App-V Client reporting
-
-To use App-V reporting, you must enable and configure the App-V client. To configure reporting on the client, use the Windows PowerShell cmdlet **Set-AppVClientConfiguration**, or the Group Policy **ADMX Template**. For more information about the Windows PowerShell cmdlets, see [About client configuration settings](appv-client-configuration-settings.md). The following section provides examples of Windows PowerShell commands for configuring App-V client reporting.
-
-### Configuring App-V client reporting using Windows PowerShell
-
-The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
-
->[!NOTE]
->The following configuration tasks can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
-
-#### Enabling reporting and initiating data collection on the computer running the App-V client
-
-Use the following command to enable reporting and initiate date collection on the computer running the App-V client:
-
-```PowerShell
-Set-AppVClientConfiguration –ReportingEnabled 1
-```
-
-#### Configuring the client to automatically send data to a specific reporting server
-
-To configure the client to automatically send data to a specific reporting server, use a command with the following format:
-
-```PowerShell
-Set-AppVClientConfiguration -ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
-```
-
-This example command configures the client to automatically send the reporting data to the reporting server URL ```http://MyReportingServer:MyPort/```. The reporting data will be sent to the URL daily between 8:00 PM and 8:30 PM, depending on the session's generated random delay.
-
-#### Limiting the size of the client's data cache
-
-To limit the client's data cache size, use a command with the following format:
-
-```PowerShell
-Set-AppvClientConfiguration –ReportingDataCacheLimit 100
-```
-
-This example command configures the maximum size of the App-V client computer's reporting cache to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
-
-#### Configuring the data block size transmitted across the network between the client and the server
-
-To configure the data block size, use a command with the following format:
-
-```PowerShell
-Set-AppvClientConfiguration –ReportingDataBlockSize 10240
-```
-
-This example command specifies the maximum size of the data block as 10,240 MB.
-
-### Types of data collected
-
-The following table displays the types of information you can collect by using App-V reporting.
-
-|Client information|Package information|Application usage|
-|---|---|---|
-|Host name|Package name|Start and end times|
-|App-V client version|Package version|Run status|
-|Processor architecture|Package source|Shutdown state|
-|Operating system version|Percent cached|Application name|
-|Service Pack level||Application version|
-|Operating system type||Username|
-|||Connection group|
-
-The client collects and saves this data in an **.xml** format. The data cache is hidden by default and requires administrator rights to open the XML file.
-
-### Sending data to the server
-
-You can configure the computer that is running the App-V client to automatically send data to the specified reporting server. To specify the server, use the **Set-AppvClientConfiguration** cmdlet with the following settings:
-
-* ReportingEnabled
-* ReportingServerURL
-* ReportingStartTime
-* ReportingInterval
-* ReportingRandomDelay
-
-After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following Windows PowerShell cmdlet:
-
-```PowerShell
-Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess
-```
-
-If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
-
-The **-DeleteOnSuccess** parameter indicates that if the transfer is successful, then the data cache will be cleared. If the transfer-status isn't specified, then the cache won't be cleared.
-
-### Manual Data Collection
-
-You can also use the **Send-AppVClientReport** cmdlet to manually collect data. This solution is helpful with or without an existing reporting server. The following list displays information about collecting data with or without a reporting server.
-
-|With a reporting server|Without a reporting server|
-|---|---|
-|f you have an existing App-V reporting server, create a customized scheduled task or script. Specify that the client sends the data to the specified location at the desired frequency.|If you don't have an existing App-V reporting Server, use the **–URL** parameter to send the data to a specified share. For example: ```Send-AppVClientReport –URL \\Myshare\MyData\ -DeleteOnSuccess``` The previous example will send the reporting data to the ```\\MyShare\MyData\``` location indicated by the **-URL** parameter. After the data has been sent, the cache is cleared.|
-
->[!NOTE]
->If a location other than the Reporting Server is specified, the data is sent in **.xml** format with no additional processing.
-
-### Creating reports
-
-To retrieve report information and create reports using App-V, you must use one of the following methods:
-
-* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS isn't installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
-
-* Scripting—You can generate reports by scripting directly against the App-V reporting database. For example:
-
- **Stored Procedure:**
-
- **spProcessClientReport** is scheduled to run at midnight or 12:00 AM.
-
- To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. Make sure the Microsoft SQL Server Agent is set to **AutoStart**. For more information, see [Autostart SQL Server Agent (SQL Server Management Studio)](/sql/ssms/agent/autostart-sql-server-agent-sql-server-management-studio).
-
- The stored procedure is also created when you use the App-V database scripts.
-
-You should also ensure that the reporting server web service’s **Maximum Concurrent Connections** is set to a value that the server can manage without affecting availability. The recommended number of **Maximum Concurrent Connections** for the **Reporting Web Service** is **10,000**.
-
-
-
-
-
-## Related articles
-
-* [Deploying the App-V server](appv-deploying-the-appv-server.md)
-* [How to install the reporting server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md)
diff --git a/windows/application-management/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md b/windows/application-management/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md
deleted file mode 100644
index 4e4f47b94fc..00000000000
--- a/windows/application-management/app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications (Windows 10/11)
-description: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
-author: aczechowski
-ms.service: windows-client
-ms.date: 03/08/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
-
-**Applies to**
-- Windows 7 SP1
-- Windows 10
-- Windows 11
-- Windows Server 2012 R2
-- Windows Server 2016
-
-You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this task if you:
-
-- Want to install and run an application locally on client computers, but want to virtualize and run specific plug-ins that work with that local application.
-
-- Are troubleshooting an App-V client package and want to open a local application within the App-V virtual environment.
-
-Use any of the following methods to open a local application inside the App-V virtual environment:
-
-- [RunVirtual registry key](#bkmk-runvirtual-regkey)
-
-- [Get-AppvClientPackage Windows PowerShell cmdlet](#bkmk-get-appvclientpackage-posh)
-
-- [Command line switch /appvpid:<PID>](#bkmk-cl-switch-appvpid)
-
-- [Command line hook switch /appvve:<GUID>](#bkmk-cl-hook-switch-appvve)
-
-Each method accomplishes essentially the same task, but some methods may be better suited for some applications than others, depending on whether the virtualized application is already running.
-
-## RunVirtual registry key
-
-
-To add a locally installed application to a package or to a connection group’s virtual environment, you add a subkey to the `RunVirtual` registry key in the Registry Editor, as described in the following sections.
-
-There's no Group Policy setting available to manage this registry key. So, you have to use Microsoft Intune or Configuration Manager, another electronic software distribution (ESD) system, or manually edit the registry.
-
-Starting with App-V 5.0 SP3, when using RunVirtual, you can publish packages globally or to the user.
-
-
-### Steps to create the subkey
-
-1. Using the information in the following table, create a new registry key using the name of the executable file, for example, **MyApp.exe**.
-
- - **Published globally**: Create the `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual` registry key.
-
- For example, create `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe`.
-
- - **Published to the user**: Create the `HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual` registry key.
-
- For example, create `HKEY_CURRENT_USER \SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe`.
-
- - Connection group can be:
- - Packages that are published globally or just to the user
- - Packages that are published globally and to the user
-
- Use the `HKEY_LOCAL_MACHINE` or `HKEY_CURRENT_USER` key. But, all of the following conditions must be fulfilled:
-
- - If you want to include multiple packages in the virtual environment, you must include them in an enabled connection group.
- - Create only one subkey for one of the packages in the connection group. For example, you have one package that is published globally and another package that is published to the user. You create a subkey for either of these packages, but not both. Although you create a subkey for only one of the packages, all of the packages in the connection group, plus the local application, will be available in the virtual environment.
- - The key under which you create the subkey must match the publishing method you used for the package.
-
- For example, if you published the package to the user, you must create the subkey under `HKEY_CURRENT_USER\SOFTWARE\Microsoft\AppV\Client\RunVirtual`. Don't add a key for the same application under both hives.
-
-2. Set the new registry subkey’s value to the PackageId and VersionId of the package, separating the values with an underscore.
-
- **Syntax**: `_`
-
- **Example**: 4c909996-afc9-4352-b606-0b74542a09c1\_be463724-Oct1-48f1-8604-c4bd7ca92fa
-
- The application in the previous example would produce a registry export file (.reg file) like the following example:
-
- ```registry
- Windows Registry Editor Version 5.00
- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual]
- @=""
- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\RunVirtual\MyApp.exe]
- @="aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-555555555
- ```
-
-## Get-AppvClientPackage Windows PowerShell cmdlet
-
-
-You can use the **Start-AppVVirtualProcess** cmdlet to retrieve the package name and then start a process within the specified package's virtual environment. This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
-
-Use the following example syntax, and substitute the name of your package for ``:
-
-`$AppVName = Get-AppvClientPackage `
-
-`Start-AppvVirtualProcess -AppvClientObject $AppVName cmd.exe`
-
-If you don’t know the exact name of your package, you can use the command line `Get-AppvClientPackage YourExecutable`, where `YourExecutable` is the name of the application. For example, enter `Get-AppvClientPackage Word`.
-
-## Command line switch `/appvpid:`
-
-
-You can apply the `/appvpid:` switch to any command, which enables that command to run within a virtual process that you select by specifying its process ID (PID). Using this method launches the new executable in the same App-V environment as an executable that is already running.
-
-Example: `cmd.exe /appvpid:8108`
-
-To find the process ID (PID) of your App-V process, run the command **tasklist.exe** from an elevated command prompt.
-
-## Command line hook switch `/appvve:`
-
-
-This switch lets you run a local command within the virtual environment of an App-V package. Unlike the **/appvid** switch, where the virtual environment must already be running, this switch enables you to start the virtual environment.
-
-Syntax: `cmd.exe /appvve:`
-
-Example: `cmd.exe /appvve:aaaaaaaa-bbbb-cccc-dddd-eeeeeeee_11111111-2222-3333-4444-55555555`
-
-To get the package GUID and version GUID of your application, run the **Get-AppvClientPackage** cmdlet. Concatenate the **/appvve** switch with the following:
-
-- A colon
-
-- Package GUID of the desired package
-
-- An underscore
-
-- Version ID of the desired package
-
-If you don’t know the exact name of your package, use the command line `Get-AppvClientPackage YourExecutable`, where `YourExecutable` is the name of the application. For example, enter `Get-AppvClientPackage Word`.
-
-This method lets you launch any command within the context of an App-V package, regardless of whether the package is currently running.
-
-## Related articles
-
-
-[Technical Reference for App-V](appv-technical-reference.md)
diff --git a/windows/application-management/app-v/appv-security-considerations.md b/windows/application-management/app-v/appv-security-considerations.md
deleted file mode 100644
index 77bc48c66fe..00000000000
--- a/windows/application-management/app-v/appv-security-considerations.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: App-V Security Considerations (Windows 10/11)
-description: Learn about accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/16/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# App-V security considerations
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This article contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
-
->[!IMPORTANT]
->App-V isn't a security product and doesn't provide any guarantees for a secure environment.
-
-## The PackageStoreAccessControl (PSAC) feature has been deprecated
-
-Effective as of June 2014, the PackageStoreAccessControl (PSAC) feature introduced in Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2) has been deprecated in both single-user and multi-user environments.
-
-## General security considerations
-
-**Understand the security risks.** The most serious risk to App-V is from unauthorized users hijacking an App-V client's functionality, giving the hacker the ability to reconfigure key data on App-V clients. By comparison, short-term loss of App-V functionality from a denial-of-service attack wouldn't be as catastrophic.
-
-**Physically secure your computers**. A security strategy that doesn't consider physical security is incomplete. Anyone with physical access to an App-V server could potentially attack the entire client base, so potential physical attacks or thefts should be prevented at all cost. App-V servers should be stored in a physically secure server room with controlled access. Lock the computer with the operating system or a secured screen saver to keep computers secure when the administrators are away.
-
-**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/security/bb291012). (THIS LINK NEEDS TO BE UPDATED)
-
-**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](/sql/relational-databases/security/password-policy) and [Strong Passwords](/sql/relational-databases/security/strong-passwords). (THIS LINK NEEDS TO BE UPDATED)
-
-## Accounts and groups in App-V
-
-A best practice for user account management is to create domain global groups and add user accounts to them. After that, add the domain global accounts to the necessary App-V local groups on the App-V servers.
-
->[!NOTE]
->App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
-
-### App-V server security
-
-No groups are created automatically during App-V setup. You should create the following Active Directory Domain Services global groups to manage App-V server operations.
-
-|Group name|Details|Important notes|
-|---|---|---|
-|App-V Management Admin group|Used to manage the App-V management server. This group is created during the App-V Management Server installation.|The management console can't create a new group after installation is complete.|
-|Database read/write for Management Service account|Provides read/write access to the management database. This account should be created during App-V management database installation.||
-|App-V Management Service install admin account|Provides public access to schema-version table in management database. This account should be created during App-V management database installation.|This account is only required if the management database is being installed separately from the service.|
-|App-V Reporting Service install admin account|Public access to schema-version table in reporting database. This account should be created during the App-V reporting database installation.|This account is only required if reporting database is being installed separately from the service.|
-
-Consider the following additional information:
-
-* Access to the package shares: If a share exists on the same computer as the management Server, the **Network** service requires read access to the share. In addition, each App-V client computer must have read access to the package share.
- > [!NOTE]
- >In previous versions of App-V, package share was referred to as content share.
-* Registering publishing servers with Management Server: A publishing server must be registered with the Management server. For example, it must be added to the database, so that the Publishing server machine accounts are able to call into the Management service API.
-
-### App-V package security
-
-The following information will help you plan how to ensure that virtualized packages are secure.
-
-* If an application installer applies an access control list (ACL) to a file or directory, then that ACL isn't persisted in the package. If the file or directory is modified by a user when the package is deployed, the modified file or directory will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former occurs if the file or directory doesn't exist in a virtual file system location; the latter occurs if the file or directory exists in a virtual file system location, such as **%windir%**.
-
-## App-V log files
-
-During App-V setup, setup log files are created in the **%temp%** folder of the installing user.
-
-## Related articles
-
-[Preparing Your Environment for App-V](appv-preparing-your-environment.md)
diff --git a/windows/application-management/app-v/appv-sequence-a-new-application.md b/windows/application-management/app-v/appv-sequence-a-new-application.md
deleted file mode 100644
index 1af6a22f42e..00000000000
--- a/windows/application-management/app-v/appv-sequence-a-new-application.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10/11)
-description: Learn how to manually sequence a new app by using the App-V Sequencer that's included with the Windows ADK.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/16/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Starting with Windows 10 version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
-
-## Before you start sequencing
-
-1. Determine the type of virtualized application package you want to create:
-
- | Application type | Description |
- |---|---|
- | Standard | Creates a package that contains an application or a suite of applications. This is the preferred option for most application types. |
- | Add-on or plug-in | Creates a package that extends the functionality of a standard application, for example, a plug-in for Microsoft Excel. Additionally, you can use plug-ins for natively installed applications, or for another package that is linked by using connection groups. |
- | Middleware | Creates a package that is required by a standard application, for example, Java. Middleware packages are used for linking to other packages through connection groups. |
-
-2. Copy all required installation files to the computer that is running the sequencer.
-
-3. Make a backup image of your virtual environment before sequencing an application, and then revert to that image each time after you finish sequencing an application.
-
-4. Review the following items:
-
- - If an application installer changes the security access to a new or existing file or directory, those changes are not captured in the package.
- - If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume.
-
- > [!NOTE]
- > The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where *x* is any numeral. Error 0x8007139F will be generated.
-
-## Sequence a new standard application
-
-1. On the computer that runs the sequencer, select **All Programs**, and then select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
-
-2. In the sequencer, select **Create a New Virtual Application Package**. Select **Create Package (default)**, and then select **Next**.
-
-3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, select **Refresh** to display the updated information. After you have resolved all potential issues, select **Next**.
-
- >[!IMPORTANT]
- >If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
-
-4. On the **Type of Application** page, select the **Standard Application (default)** check box, and then select **Next**.
-
-5. On the **Select Installer** page, select **Browse** and specify the installation file for the application.
-
- > [!NOTE]
- > If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
-
- If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then select **Next**.
-
-6. On the **Package Name** page, specify a name for the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console. Once you're done, select **Next**.
-
-7. On the **Installation** page, when the sequencer and application installer are ready, you can install the application so that the sequencer can monitor the installation process.
-
- >[!IMPORTANT]
- >You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
-
- Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, select **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, then select **Next**.
-
-8. On the **Installation** page, wait while the sequencer configures the virtualized application package.
-
-9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then select **Run All**. To run specific programs, select the program or programs, and then select **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run.
-
- > [!NOTE]
- >To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
-
- Select **Next**.
-
-10. On the **Installation Report** page, you can review information about the virtualized application package you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, select **Next**.
-
-11. The **Customize** page is displayed. If you've finished installing and configuring the virtual application, select **Stop now** and skip to step 14 of this procedure. To perform either of the following customizations, select **Customize**.
-
- - Prepare the virtual package for streaming. Streaming improves the experience when the virtual application package is run on target computers.
- - Specify the operating systems that can run this package.
-
- Once you're ready, select **Next**.
-
-12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then select **Next**.
-
- > [!NOTE]
- > If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened. After that, depending on how the background loading is configured, it will load the rest of the application.
-
-13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. After that, select **Next**.
-
- > [!IMPORTANT]
- > Make sure that the operating systems you specify here are supported by the application you are sequencing.
-
-14. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before saving it. Select **Next**.
-
- To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments are useful for identifying the program version and other information about the package.
-
- > [!IMPORTANT]
- > The system does not support non-printable characters in **Comments** and **Descriptions**.
-
- The default **Save Location** is also displayed on this page. To change the default location, select **Browse** and specify the new location. After that, select **Create**.
-
-15. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then select **Close**. This information is also available in the **Report.xml** file located in the directory where the package was created.
-
- Your package should now be available in the sequencer.
-
- > [!IMPORTANT]
- > After you have successfully created a virtual application package, you can't run the virtual application package on the computer that is running the sequencer.
-
-## Sequence an add-on or plug-in application
-
-> [!NOTE]
-> Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer.
->
-> For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that's running the sequencer. You should also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package.
-
-1. On the computer that runs the sequencer, first, select **All Programs**, then select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
-
-2. In the sequencer, select **Create a New Virtual Application Package**, select **Create Package (default)**, and then select **Next**.
-
-3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, select **Refresh** to display the updated information. After you have resolved all potential issues, select **Next**.
-
- >[!IMPORTANT]
- >If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
-
-4. On the **Type of Application** page, select **Add-on or Plug-in**, and then select **Next**.
-
-5. On the **Select Installer** page, select **Browse** and specify the installation file for the add-on or plug-in. If the add-on or plug-in does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, then select **Next**.
-
-6. On the **Install Primary** page, ensure that the primary application is installed on the computer that runs the sequencer. Alternatively, you can expand an existing package that has been saved locally on the computer that runs the sequencer. To do this, select **Expand Package**, and then select the package. After you have expanded or installed the parent program, select **I have installed the primary parent program**.
-
-7. Select **Next**.
-
-8. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console.
-
-9. Select **Next**.
-
-10. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, select **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then select **Next**.
-
-11. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, select **Next**.
-
-12. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**.
-
- - Optimize how the package will run across a slow or unreliable network.
- - Specify the operating systems that can run this package.
-
- When you're finished, select **Next**.
-
-13. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all applications to run. After all applications have run, close each application. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Select **Next**.
-
- > [!NOTE]
- > If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, select **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
-
-14. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box, and then select the operating systems that can run this package. Select **Next**.
-
-15. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor** check box. This option opens the package in the sequencer console so that you can modify the package before it is saved. Select **Next**.
-
- To save the package immediately, select **Save the package now**. Optionally, add a **Description** for the package. Descriptions are useful for identifying the version and other important information about the package.
-
- >[!IMPORTANT]
- >The system does not support non-printable characters in Comments and Descriptions.
-
- The default **Save Location** is also displayed on this page. To change the default location, select **Browse** and specify the new location. Select **Create**.
-
-### Sequence a middleware application
-
-1. On the computer that runs the sequencer, select **All Programs**, then select **Microsoft Application Virtualization**, and then select **Microsoft Application Virtualization Sequencer**.
-
-2. In the sequencer, select **Create a New Virtual Application Package**, select **Create Package (default)**, and then select **Next**.
-
-3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, select **Refresh** to display the updated information. After you have resolved all potential issues, select **Next**.
-
- >[!IMPORTANT]
- >If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
-
-4. On the **Type of Application** page, select **Middleware**, and then select **Next**.
-
-5. On the **Select Installer** page, select **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, then select **Next**.
-
-6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
-
-7. Select **Next**.
-
-8. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, select **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then select **Next**.
-
-9. On the **Installation** page, wait while the sequencer configures the virtual application package.
-
-10. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, select **Next**.
-
-11. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Once you're done, select **Next**.
-
-12. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Select **Next**.
-
- To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package.
-
- >[!IMPORTANT]
- >The system does not support non-printable characters in comments and descriptions.
-
- The default **Save Location** is also displayed on this page. To change the default location, select **Browse** and specify the new location. Select **Create**.
-
-13. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then select **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
-
- The package is now available in the sequencer. To edit the package properties, select **Edit \[Package Name\]**.
-
- >[!IMPORTANT]
- >After you have successfully created a virtual application package, you can't run the virtual application package on the computer that is running the sequencer.
-
-
-## Related articles
-
-- [Install the App-V Sequencer](appv-install-the-sequencer.md)
-- [Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md b/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md
deleted file mode 100644
index a41e80e750f..00000000000
--- a/windows/application-management/app-v/appv-sequence-a-package-with-powershell.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: How to sequence a package by using Windows PowerShell (Windows 10/11)
-description: Learn how to sequence a new Microsoft Application Virtualization (App-V) package by using Windows PowerShell.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to Sequence a Package by using Windows PowerShell
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to create a new App-V package using Windows PowerShell.
-
-> [!NOTE]
-> Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
-
-
-**To create a new virtual application by using Windows PowerShell**
-
-1. Install the App-V sequencer. For more information about installing the sequencer, see [How to Install the Sequencer](appv-install-the-sequencer.md).
-
-2. Click **Start** and type **Windows PowerShell**. Right-click **Windows PowerShell**, and select **Run as Administrator**.
-
-3. Using the Windows PowerShell console, type the following: **import-module appvsequencer**.
-
-4. To create a package, use the **New-AppvSequencerPackage** cmdlet. The following parameters are required to create a package:
-
- - **Name** - specifies the name of the package.
-
- - **PrimaryVirtualApplicationDirectory** - specifies the path to the directory that will be used to install the application. This path must exist.
-
- - **Installer** - specifies the path to the associated application installer.
-
- - **Path** - specifies the output directory for the package.
-
- For example:
-
- ```
- New-AppvSequencerPackage –Name -PrimaryVirtualApplicationDirectory -Installer -OutputPath
- ```
-
-
-Wait for the sequencer to create the package. Creating a package by using Windows PowerShell can take time. If the package was not created successfully, an error will be returned.
-
-The following list displays additional optional parameters that can be used with **New-AppvSequencerPackage** cmdlet:
-
-- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
-
-- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
-
-- InstallMediaPath - specifies the path of the installation media
-
-- TemplateFilePath - specifies the path to a template file if you want to customize the sequencing process.
-
-- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
-
-Starting with Windows 10 version 1703, the `new-appvsequencerpackage` or the `update-appvsequencepackage` cmdlets automatically capture and store all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
-
-> [!IMPORTANT]
-> If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
-
-## Related articles
-
-- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
diff --git a/windows/application-management/app-v/appv-supported-configurations.md b/windows/application-management/app-v/appv-supported-configurations.md
deleted file mode 100644
index f96111505d6..00000000000
--- a/windows/application-management/app-v/appv-supported-configurations.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: App-V Supported Configurations (Windows 10/11)
-description: Learn the requirements to install and run App-V supported configurations in your Windows 10/11 environment.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/16/2018
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.topic: article
-ms.subservice: itpro-apps
----
-
-# App-V Supported Configurations
-
-**Applies to**:
-
-- Windows 10
-- Windows 11
-- Windows Server 2019
-- Windows Server 2016
-- Windows Server 2012 R2
-- Windows Server 2012
-- Windows Server 2008 R2 (Extended Security Update)
-
-This article specifies the requirements to install and run App-V in your Windows client environment. For information about prerequisite software such as the .NET Framework, see [App-V prerequisites](appv-prerequisites.md).
-
-## App-V Server system requirements
-
-This section lists the operating system and hardware requirements for all App-V server components.
-
-### Unsupported App-V server scenarios
-
-The App-V server does not support the following scenarios:
-
-* Deployment to a computer that runs the Server Core installation option.
-* Deployment to a computer that runs a previous version of the App-V server components. You can only install App-V side-by-side with the App-V 4.5 Lightweight Streaming Server (LWS) server. This scenario doesn't support side-by-side deployment of App-V and the Application Virtualization Management Service (HWS) 4.x.
-* Deployment to a computer running Microsoft SQL Server Express edition.
-* Deployment to a domain controller.
-* Short paths. If you plan to use a short path, you must create a new volume.
-
-### Management server operating system requirements
-
-You can install the App-V Management server on a server running Windows Server 2008 R2 with SP1 (Extended Security Update) or later.
-
->[!IMPORTANT]
->Deploying a Management server role to a computer with Remote Desktop Services enabled is not supported.
-
-### Management server hardware requirements
-
-* A 64-bit (x64) processor that runs at 1.4 GHz or faster.
-* 1-GB RAM (64-bit).
-* 200 MB of available hard disk space, not including the content directory.
-
-### Management server database requirements
-
-The following table lists the SQL Server versions that the App-V Management database installation supports.
-
-|SQL Server version|Service pack|System architecture|
-|---|---|---|
-|Microsoft SQL Server 2019|CU4|32-bit or 64-bit|
-|Microsoft SQL Server 2017||32-bit or 64-bit|
-|Microsoft SQL Server 2016|SP2|32-bit or 64-bit|
-|Microsoft SQL Server 2014||32-bit or 64-bit|
-|Microsoft SQL Server 2012|SP2|32-bit or 64-bit|
-|Microsoft SQL Server 2008 R2|SP3|32-bit or 64-bit|
-
-For more information on user configuration files with SQL server 2016 or later, see the [support article](https://support.microsoft.com/help/4548751/app-v-server-publishing-might-fail-when-you-apply-user-configuration-f).
-
-### Publishing server operating system requirements
-
-The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
-
-### Publishing server hardware requirements
-
-App-V adds require nothing beyond the requirements of Windows Server.
-
-* A 64-bit (x64) processor that runs at 1.4 GHz or faster.
-* 2-GB RAM (64-bit).
-* 200 MB of available hard disk space, not including the content directory.
-
-### Reporting server operating system requirements
-
-You can install the App-V Reporting server on a server running Windows Server 2008 R2 with SP1 or later.
-
-### Reporting server hardware requirements
-
-App-V adds no other requirements beyond those requirements of Windows Server.
-
-* A 64-bit (x64) processor that runs at 1.4 GHz or faster.
-* 2-GB RAM (64-bit).
-* 200 MB of available hard disk space, not including the content directory.
-
-### Reporting server database requirements
-
-The following table lists the SQL Server versions that are supported for the App-V Reporting database installation.
-
-|SQL Server version|Service pack|System architecture|
-|---|---|---|
-|Microsoft SQL Server 2019|CU4|32-bit or 64-bit|
-|Microsoft SQL Server 2017||32-bit or 64-bit|
-|Microsoft SQL Server 2016|SP2|32-bit or 64-bit|
-|Microsoft SQL Server 2014||32-bit or 64-bit|
-|Microsoft SQL Server 2012|SP2|32-bit or 64-bit|
-|Microsoft SQL Server 2008 R2|SP3|32-bit or 64-bit|
-
-## App-V client and Remote Desktop Services client requirements
-
-Starting with Windows 10 version 1607, the App-V client is included with Windows Enterprise and Windows Education. The App-V client is no longer part of the Microsoft Desktop Optimization Pack. Before you can use the App-V client, it must be enabled, as described in [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
-
-Similarly, the App-V Remote Desktop Services (RDS) client is included with Windows Server 2016 Standard and Windows Server 2016 Datacenter.
-
-## Sequencer system requirements
-
-Sequencer is now part of the Windows Assessment and Deployment Kit (Windows ADK). [Download the latest Windows ADK](/windows-hardware/get-started/adk-install) that is recommended for your version of the Windows OS.
-
-### Sequencer hardware requirements
-
-See the Windows or Windows Server documentation for the hardware requirements.
-
-## Supported versions of Microsoft Configuration Manager
-
-The App-V client works with Configuration Manager versions starting with Technical Preview for Configuration Manager, version 1606.
-
-## Related articles
-
-* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
-* [App-V prerequisites](appv-prerequisites.md)
diff --git a/windows/application-management/app-v/appv-technical-reference.md b/windows/application-management/app-v/appv-technical-reference.md
deleted file mode 100644
index 50ffd5963b6..00000000000
--- a/windows/application-management/app-v/appv-technical-reference.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Technical Reference for App-V (Windows 10/11)
-description: Learn strategy and context for many performance optimization practices in this technical reference for Application Virtualization (App-V).
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Technical Reference for App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This section provides reference information related to managing App-V.
-
-## In This Section
-
-
-- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
-
- Provides strategy and context for many performance optimizations. Not all practices will be applicable. However, these practices are tested and supported. Using all suggested practices that are applicable to your organization will provide the optimal end-user experience.
-
-- [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
-
-Describes how the following App-V client operations affect the local operating system:
-
-- App-V files and data storage locations
-- Package registry
-- Package store behavior
-- Roaming registry and data
-- Client application lifecycle management
-- Integration of App-V packages
-- Dynamic configuration
-- Side-by-side assemblies
-- Client logging
-
-- [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
-
- Tells how to view publishing metadata, which can help you resolve publishing-related issues.
-
-- [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
-
- Describes reasons and methods for running a locally installed application in a virtual environment, alongside applications that have been virtualized by using Application Virtualization (App-V).
-
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[How to Deploy the App-V Databases by Using SQL Scripts](appv-deploy-appv-databases-with-sql-scripts.md)
-
-[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
-
-[Windows PowerShell reference for App-V](/previous-versions/)
diff --git a/windows/application-management/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md b/windows/application-management/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
deleted file mode 100644
index d2fbaa8450f..00000000000
--- a/windows/application-management/app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console (Windows 10/11)
-description: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to transfer the access and default package configurations to another version of a package by using the management console.
-
-**To transfer access and configurations to another version of a package**
-
-1. To view the package that you want to configure, open the App-V Management Console. Select the package to which you'll transfer the new configuration, right-click the package and select **transfer default configuration from** or **transfer access and configurations from**, depending on the configuration that you want to transfer.
-
-2. To transfer the configuration, in the **Select Previous Version** dialog box, select the package that contains the settings that you want to transfer, and then click **OK**.
-
- If you select **transfer default configuration from**, then only the underlying dynamic deployment configuration will be transferred.
-
- If you select **transfer access and configurations from**, then all access permissions, and the configuration settings, will be copied.
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-troubleshooting.md b/windows/application-management/app-v/appv-troubleshooting.md
deleted file mode 100644
index 0cde4c84966..00000000000
--- a/windows/application-management/app-v/appv-troubleshooting.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Troubleshooting App-V (Windows 10/11)
-description: Learn how to find information about troubleshooting Application Virtualization (App-V) and information about other App-V articles.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Troubleshooting App-V
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-For information that can help with troubleshooting App-V for Windows client, see:
-
-- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](https://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx)
-
-- [Microsoft App-V Team Blog](/archive/blogs/appv/)
-
-- [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
-
-- [Technical Reference for App-V](appv-technical-reference.md)
-
-- [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv)
-
-
-## Other resources
-
-- [Application Virtualization (App-V) for Windows client overview](appv-for-windows.md)
-
-- [Getting Started with App-V for Windows client](appv-getting-started.md)
-
-- [Planning for App-V](appv-planning-for-appv.md)
-
-- [Deploying App-V](appv-deploying-appv.md)
-
-- [Operations for App-V](appv-operations.md)
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
diff --git a/windows/application-management/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md b/windows/application-management/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md
deleted file mode 100644
index 872fdc6b2a9..00000000000
--- a/windows/application-management/app-v/appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Upgrading to App-V for Windows 10/11 from an existing installation (Windows 10/11)
-description: Learn about upgrading to Application Virtualization (App-V) for Windows 10/11 from an existing installation.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Upgrading to App-V for Windows client from an existing installation
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-If you’re already using App-V and you’re planning to upgrade user devices to Windows 10/11, you need to make only the following few adjustments to your existing environment to start using App-V for Windows client.
-
-1. [Upgrade user devices to Windows 10/11](#upgrade-user-devices-to-windows-1011). Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings.
-
-2. [Verify that App-V applications and settings were migrated correctly](#verify-that-app-v-applications-and-settings-were-migrated-correctly).
-
-3. [Enable the in-box App-V client](#enable-the-in-box-app-v-client).
-
-4. [Configure the in-box App-V client to point to previously installed App-V server components](#configure-the-in-box-app-v-client-to-point-to-previously-installed-app-v-server-components).
-
-5. [Verify that the in-box App-V client can receive and launch .appv packages](#verify-that-the-in-box-app-v-client-can-receive-and-launch-appv-packages).
-
-These steps are explained in more detail below.
-
-## Upgrade user devices to Windows 10/11
-
-Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows document set](/windows/windows-10/) for information about upgrading user devices.
-
-## Verify that App-V applications and settings were migrated correctly
-
-After upgrading a user device, it’s important to verify that App-V applications and settings were migrated correctly during the upgrade.
-
-To verify that the user’s App-V application packages were migrated correctly, type `Get-AppvClientPackage` in Windows PowerShell.
-
-To verify that the user’s App-V settings were migrated correctly, type `Get-AppvClientConfiguration` in Windows PowerShell.
-
-## Enable the in-box App-V client
-
-With Windows 10/11, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
-
-**To enable the App-V client with Group Policy**
-
-1. Open the device’s **Group Policy Editor**.
-
-2. Navigate to **Computer Configuration > Administrative Templates > System > App-V**.
-
-3. Run **Enables App-V Client** and then select **Enabled** on the screen that appears.
-
-4. Restart the device.
-
-**To enable the App-V client with Windows PowerShell**
-
-1. Open Windows PowerShell.
-
-2. Type `Enable-Appv` and press enter.
-
-3. Restart the device.
-
-4. To verify that the App-V client is enabled on the device, enter `AppvClientEnabled` or `Get-AppvStatus` in Windows PowerShell.
-
-## Configure the in-box App-V client to point to previously installed App-V server components
-
-Once you’ve enabled the in-box App-V client, you need to configure it to point to your existing App-V server components. You can configure the App-V client with Windows PowerShell cmdlets or with the device’s local Group Policy editor.
-
-**To modify client settings to point to an existing App-V publishing server with Windows PowerShell**
-
-Type the following cmdlet in a Windows PowerShell window:
-
-`Add-AppvPublishingServer -Name AppVServer -URL https:// appvserver:2222`
-
-**To modify client settings to point to an existing App-V publishing server with Group Policy**
-
-1. Open the device’s **Local Group Policy Editor**.
-
-2. Navigate to **Computer Configuration > Administrative Templates > System > App-V > Publishing**.
-
-3. Enter your existing App-V publishing server’s details in **Options** and then click or press **Apply**.
-
-## Verify that the in-box App-V client can receive and launch .appv packages
-
-1. Add and publish a package using the following Windows PowerShell cmdlets:
-
- `Add-AppvClientPackage \\path\to\appv\package.appv | Publish-AppvClientPackage`
-
-2. Launch the published package.
-
-3. Unpublish an existing package use the following cmdlet:
-
- `Unpublish-AppvClientPackage "ContosoApplication"`
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
diff --git a/windows/application-management/app-v/appv-using-the-client-management-console.md b/windows/application-management/app-v/appv-using-the-client-management-console.md
deleted file mode 100644
index 5d99029e542..00000000000
--- a/windows/application-management/app-v/appv-using-the-client-management-console.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Using the App-V Client Management Console (Windows 10/11)
-description: Learn how to use the Application Virtualization (App-V) client management console to manage packages on the computer running the App-V client.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Using the App-V Client Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-This article provides information about using the Application Virtualization (App-V) client management console to manage packages on the computer running the App-V client.
-
-## Options for managing the App-V client
-
-The App-V client has associated settings that can be configured to determine how the client will run in your environment. You can manage these settings on the computer that runs the client, or you can use Windows PowerShell or Group Policy. For more information about configuring the client by using Windows PowerShell or Group Policy, see:
-
-- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
-
-- [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
-
-- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
-
-## The App-V client management console
-
-You can obtain information about the App-V client or perform specific tasks by using the App-V client management console. Many of the tasks that you can perform in the client management console you can also perform by using Windows PowerShell. The associated Windows PowerShell cmdlets for each action are also displayed in the following table. For more information about how to use Windows PowerShell, see [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md).
-
-The client management console contains the following described main tabs.
-
-- **Overview**: The **Overview** tab contains the following elements:
-
- - **Update**: Refreshes a virtualized application or to receive a new virtualized package.
- - **Last Refresh**: Displays the current version of the virtualized package.
- - **Download all virtual applications**: Use the Download tile to download all of the packages provisioned to the current user.
-
- Associated Windows PowerShell cmdlet: `Mount-AppvClientPackage`
-
- - **Work Offline**: Disallows all automatic and manual virtual application updates.
-
- Associated Windows PowerShell cmdlet: `-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled`
-
-- **VIRTUAL APPS**: Displays all of the packages that have been published to the user.
-
- You can also click a specific package and see all of the applications that are part of that package. This option displays information about packages that are currently in use and how much of each package has been downloaded to the computer. You can also start and stop package downloads, and repair the user state. A repair will delete all user data that is associated with a package.
-
-- **APP CONNECTION GROUPS**: Displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group.
-
- Associated Windows PowerShell cmdlets:
-
- - Download: `Mount-AppvClientConnectionGroup`
- - Repair: `AppvClientConnectionGroup`
-
-For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md b/windows/application-management/app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
deleted file mode 100644
index 97d6680ac15..00000000000
--- a/windows/application-management/app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console (Windows 10/11)
-description: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
-
-[!INCLUDE [Applies to Windows client versions](../includes/applies-to-windows-client-versions.md)]
-
-Use the following procedure to view and configure default package extensions.
-
-**To view and configure default virtual application extensions**
-
-1. To view the package that you want to configure, open the App-V Management Console. Select the package that you want to configure, right-click the package name and select **edit default configuration**.
-
-2. To view the applications contained in the specified package, in the **Default Configuration** pane, click **Applications**. To view the shortcuts for that package, click **Shortcuts**. To view the file type associations for that package, click **File Types**.
-
-3. To enable the application extensions, select **ENABLE**.
-
- To enable shortcuts, select **ENABLE SHORTCUTS**. To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane and select **Remove Shortcut**. To edit an existing shortcut, right-click the application and select **Edit Shortcut**.
-
-4. To view any other application extensions, click **Advanced** and click **Export Configuration**. Type in a filename and click **Save**. You can view all application extensions associated with the package using the configuration file.
-
-5. To edit other application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog box, click **Overwrite** to complete the process.
-
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Operations for App-V](appv-operations.md)
diff --git a/windows/application-management/app-v/appv-viewing-appv-server-publishing-metadata.md b/windows/application-management/app-v/appv-viewing-appv-server-publishing-metadata.md
deleted file mode 100644
index f652726838e..00000000000
--- a/windows/application-management/app-v/appv-viewing-appv-server-publishing-metadata.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: Viewing App-V Server Publishing Metadata (Windows 10/11)
-description: Use this procedure to view App-V Server publishing metadata, which can help you resolve publishing-related issues.
-author: aczechowski
-ms.service: windows-client
-ms.date: 04/19/2017
-ms.reviewer:
-manager: aaroncz
-ms.author: aaroncz
-ms.collection: must-keep
-ms.subservice: itpro-apps
-ms.topic: article
----
-
-# Viewing App-V Server Publishing Metadata
-
-**Applies to**
-- Windows Server 2016
-
-Use this procedure to view App-V Server publishing metadata, which can help you resolve publishing-related issues. You must be using the App-V Management server to use this procedure.
-
-This article contains the following information:
-
-- [Definition of publishing metadata](#bkmk-whatis-pub-metadata)
-
-- [Syntax to use for viewing publishing metadata](#bkmk-syntax-view-pub-meta)
-
-- [Query values for client operating system](#bkmk-values-query-pub-meta)
-
-## Definition of publishing metadata
-
-When packages are published to a computer that is running the App-V client, metadata is sent to that computer indicating which packages and connection groups are being published. The App-V Client makes two separate requests for the following:
-
-- Packages and connection groups that are entitled to the client computer.
-
-- Packages and connection groups that are entitled to the current user.
-
-The Publishing server communicates with the Management server to determine which packages and connection groups are available to the requester. The Publishing server must be registered with the Management server in order for the metadata to be generated.
-
-You can view the metadata for each request in an Internet browser by using a query that is in the context of the specific user or computer.
-
-## Query syntax for viewing publishing metadata
-
-This section provides information about queries for viewing publishing metadata for App-V 5.0 SP3 Server and App-V 5.1 server. The App-V server components have not changed since App-V 5.0 was released, so App-V 5.x Server is the version of the server used with App-V for Windows client.
-
-**Query syntax**
-
-`http://:/?ClientVersion=&ClientOS=`
-
-For information about the variables in this syntax, see the table that follows.
-
-**Query example**
-
-`http://pubsvr01:2718/?ClientVersion=10.0.14393&ClientOS=WindowsClient_10.0_x64`
-
-In this example:
-
-- A computer running Windows Server 2016 named “pubsvr01” hosts the Publishing service.
-
-- The Windows client is 64-bit.
-
-**Query parameter descriptions**
-
-The following table describes the parameters shown in the preceding **Query syntax**.
-
-| Parameter | Description |
-|------------|---------------|
-| `` | Name of the App-V Publishing server. |
-| `` | Port to the App-V Publishing server, which you defined when you configured the Publishing server. |
-| `ClientVersion=` | Windows client build number. You can obtain this number by running the following Windows PowerShell command: `(Get-CimInstance Win32_OperatingSystem).version` |
-| `ClientOS=` | Operating system of the computer that is running the App-V client. Refer to the table that follows for the correct value. You can omit this parameter, with the result that only the packages that were sequenced to support all operating systems will appear in the metadata. |
-
-To get the name of the Publishing server and the port number (`http://:`) from the App-V client, look at the URL configuration of the Get-AppvPublishingServer Windows PowerShell cmdlet.
-
-## Query values for client operating system
-
-In your publishing metadata query, enter the string values that correspond to the client operating system that you’re using.
-
-|Operating system|Architecture|String value|
-|--- |--- |--- |
-|Windows 10/11|64-bit|WindowsClient_10.0_x64|
-|Windows 10/11|32-bit|WindowsClient_10.0_x86|
-|Windows 8.1|64-bit|WindowsClient_6.2_x64|
-|Windows 8.1|32-bit|WindowsClient_6.2_x86|
-|Windows 8|64-bit|WindowsClient_6.2_x64|
-|Windows 8|32-bit|WindowsClient_6.2_x86|
-|Windows Server 2012 R2|64-bit|WindowsServer_6.2_x64|
-|Windows Server 2012 R2|32-bit|WindowsServer_6.2_x86|
-|Windows Server 2012|64-bit|WindowsServer_6.2_x64|
-|Windows Server 2012|32-bit|WindowsServer_6.2_x86|
-|Windows Server 2008 R2|64-bit|WindowsServer_6.1_x64|
-|Windows Server 2008 R2|32-bit|WindowsServer_6.1_x86|
-
-
- For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
-
-## Related articles
-
-[Technical Reference for App-V](appv-technical-reference.md)
diff --git a/windows/application-management/app-v/images/app-v-in-adk.png b/windows/application-management/app-v/images/app-v-in-adk.png
deleted file mode 100644
index a36ef9f00f8..00000000000
Binary files a/windows/application-management/app-v/images/app-v-in-adk.png and /dev/null differ
diff --git a/windows/application-management/app-v/images/checklistbox.gif b/windows/application-management/app-v/images/checklistbox.gif
deleted file mode 100644
index cbcf4a4f11e..00000000000
Binary files a/windows/application-management/app-v/images/checklistbox.gif and /dev/null differ
diff --git a/windows/application-management/app-v/images/packageaddfileandregistrydata-global.png b/windows/application-management/app-v/images/packageaddfileandregistrydata-global.png
deleted file mode 100644
index 775e290a361..00000000000
Binary files a/windows/application-management/app-v/images/packageaddfileandregistrydata-global.png and /dev/null differ
diff --git a/windows/application-management/app-v/images/packageaddfileandregistrydata-stream.png b/windows/application-management/app-v/images/packageaddfileandregistrydata-stream.png
deleted file mode 100644
index 0e1205c62b2..00000000000
Binary files a/windows/application-management/app-v/images/packageaddfileandregistrydata-stream.png and /dev/null differ
diff --git a/windows/application-management/app-v/images/packageaddfileandregistrydata.png b/windows/application-management/app-v/images/packageaddfileandregistrydata.png
deleted file mode 100644
index 603420e6278..00000000000
Binary files a/windows/application-management/app-v/images/packageaddfileandregistrydata.png and /dev/null differ
diff --git a/windows/application-management/docfx.json b/windows/application-management/docfx.json
index 7b7f7eed470..ddb34848ae9 100644
--- a/windows/application-management/docfx.json
+++ b/windows/application-management/docfx.json
@@ -39,6 +39,7 @@
"ms.collection": [
"tier2"
],
+ "zone_pivot_group_filename": "resources/zone-pivot-groups.json",
"uhfHeaderId": "MSDocsHeader-Windows",
"ms.service": "windows-client",
"ms.subservice": "itpro-apps",
@@ -50,12 +51,11 @@
"folder_relative_path_in_docset": "./"
}
},
- "titleSuffix": "Windows Application Management",
"contributors_to_exclude": [
"dstrome2",
- "rjagiewich",
+ "rjagiewich",
"American-Dipper",
- "claydetels19",
+ "claydetels19",
"jborsecnik",
"v-stchambers",
"shdyas",
@@ -68,11 +68,6 @@
"Windows 10"
]
},
- "fileMetadata": {
- "feedback_system": {
- "app-v/**/*.*": "None"
- }
- },
"template": [],
"dest": "win-app-management",
"markdownEngineName": "markdig"
diff --git a/windows/application-management/enterprise-background-activity-controls.md b/windows/application-management/enterprise-background-activity-controls.md
index 2a00963aef5..73dbb919ae3 100644
--- a/windows/application-management/enterprise-background-activity-controls.md
+++ b/windows/application-management/enterprise-background-activity-controls.md
@@ -5,7 +5,7 @@ author: aczechowski
ms.author: aaroncz
manager: aaroncz
ms.date: 10/03/2017
-ms.topic: article
+ms.topic: conceptual
ms.service: windows-client
ms.subservice: itpro-apps
ms.localizationpriority: medium
diff --git a/windows/application-management/index.yml b/windows/application-management/index.yml
index 371bc58a376..ae406114d74 100644
--- a/windows/application-management/index.yml
+++ b/windows/application-management/index.yml
@@ -9,7 +9,7 @@ metadata:
author: aczechowski
ms.author: aaroncz
manager: aaroncz
- ms.date: 08/18/2023
+ ms.date: 06/28/2024
ms.topic: landing-page
ms.service: windows-client
ms.subservice: itpro-apps
@@ -40,22 +40,3 @@ landingContent:
url: per-user-services-in-windows.md
- text: Changes to Service Host grouping in Windows 10
url: svchost-service-refactoring.md
-
- - title: Application Virtualization (App-V)
- linkLists:
- - linkListType: overview
- links:
- - text: App-V overview
- url: app-v/appv-for-windows.md
- - text: Getting started with App-V
- url: app-v/appv-getting-started.md
- - text: Planning for App-V
- url: app-v/appv-planning-for-appv.md
- - text: Deploying App-V
- url: app-v/appv-deploying-appv.md
- - text: Operations for App-V
- url: app-v/appv-operations.md
- - text: Troubleshooting App-V
- url: app-v/appv-troubleshooting.md
- - text: Technical Reference for App-V
- url: app-v/appv-technical-reference.md
diff --git a/windows/application-management/overview-windows-apps.md b/windows/application-management/overview-windows-apps.md
index ab58f88f99c..7188ebe6e00 100644
--- a/windows/application-management/overview-windows-apps.md
+++ b/windows/application-management/overview-windows-apps.md
@@ -4,7 +4,7 @@ description: Learn about the different types of apps that run on Windows. For ex
author: aczechowski
ms.author: aaroncz
manager: aaroncz
-ms.date: 08/28/2023
+ms.date: 06/28/2024
ms.topic: overview
ms.service: windows-client
ms.subservice: itpro-apps
@@ -31,7 +31,7 @@ For more information on deploying Microsoft 365 apps, see the [Deployment guide
### Power Apps
-These apps are custom, low-code apps to connect to business data, modernize processes, and solve unique challenges. Power Apps are available online and on-premises, can run in a web browser, and on mobile devices. They can be created by business analysts and professional developers.
+These apps are custom, low-code apps to connect to business data, modernize processes, and solve unique challenges. Power Apps are available online and on-premises, can run in a web browser, and on mobile devices. They can be created by business analysts and professional developers.
For more information, see [What is Power Apps?](/power-apps/powerapps-overview).
@@ -182,7 +182,7 @@ App-V allows Win32 apps to be used as virtual apps.
On an on-premises server, you install and configure the App-V server components, and then install your Win32 apps. On Windows Enterprise client devices, you use the App-V client components to run the virtualized apps. They allow users to open the virtual apps using the icons and file names they're familiar with. Users use the apps as if they're installed locally.
-The benefit is to deliver virtual apps in real time, and as-needed. For more information, see [Application Virtualization (App-V) for Windows overview](./app-v/appv-for-windows.md).
+The benefit is to deliver virtual apps in real time, and as-needed. For more information, see [Application Virtualization (App-V) for Windows overview](/microsoft-desktop-optimization-pack/app-v/appv-for-windows).
## Manage apps
diff --git a/windows/application-management/private-app-repository-mdm-company-portal-windows-11.md b/windows/application-management/private-app-repository-mdm-company-portal-windows-11.md
index 90281afcd3a..d6b6444c8db 100644
--- a/windows/application-management/private-app-repository-mdm-company-portal-windows-11.md
+++ b/windows/application-management/private-app-repository-mdm-company-portal-windows-11.md
@@ -5,7 +5,7 @@ author: aczechowski
ms.author: aaroncz
manager: aaroncz
ms.date: 04/04/2023
-ms.topic: article
+ms.topic: conceptual
ms.service: windows-client
ms.subservice: itpro-apps
ms.localizationpriority: medium
diff --git a/windows/application-management/toc.yml b/windows/application-management/toc.yml
index 63f66e42cb9..eaea302b9cc 100644
--- a/windows/application-management/toc.yml
+++ b/windows/application-management/toc.yml
@@ -1,257 +1,17 @@
items:
- name: Manage Windows applications
href: index.yml
-- name: Application management
- items:
- - name: Overview of apps in Windows
- href: overview-windows-apps.md
- - name: Add or hide Windows features
- href: add-apps-and-features.md
- - name: Sideload line of business (LOB) apps
- href: sideload-apps-in-windows.md
- - name: Private app repo on Windows 11
- href: private-app-repository-mdm-company-portal-windows-11.md
- - name: Remove background task resource restrictions
- href: enterprise-background-activity-controls.md
- - name: Service host grouping in Windows 10
- href: svchost-service-refactoring.md
- - name: Per-user services in Windows
- href: per-user-services-in-windows.md
- - name: Keep removed apps from returning during an update
- href: remove-provisioned-apps-during-update.md
-- name: Application Virtualization (App-V)
- items:
- - name: App-V for Windows overview
- href: app-v/appv-for-windows.md
- - name: Getting Started
- items:
- - name: Getting Started with App-V
- href: app-v/appv-getting-started.md
- - name: What's new
- items:
- - name: What's new in App-V for Windows 10, version 1703 and earlier
- href: app-v/appv-about-appv.md
- - name: Release Notes for App-V for Windows 10, version 1607
- href: app-v/appv-release-notes-for-appv-for-windows.md
- - name: Release Notes for App-V for Windows 10, version 1703
- href: app-v/appv-release-notes-for-appv-for-windows-1703.md
- - name: Evaluating App-V
- href: app-v/appv-evaluating-appv.md
- - name: High Level Architecture for App-V
- href: app-v/appv-high-level-architecture.md
- - name: Planning
- items:
- - name: Planning for App-V
- href: app-v/appv-planning-for-appv.md
- - name: Preparing your environment
- items:
- - name: Preparing your environment for App-V
- href: app-v/appv-preparing-your-environment.md
- - name: App-V Prerequisites
- href: app-v/appv-prerequisites.md
- - name: App-V security considerations
- href: app-v/appv-security-considerations.md
- - name: Planning to deploy
- items:
- - name: Planning to Deploy App-V
- href: app-v/appv-planning-to-deploy-appv.md
- - name: App-V Supported Configurations
- href: app-v/appv-supported-configurations.md
- - name: App-V Capacity Planning
- href: app-v/appv-capacity-planning.md
- - name: Planning for High Availability with App-V
- href: app-v/appv-planning-for-high-availability-with-appv.md
- - name: Planning to Deploy App-V with an Electronic Software Distribution System
- href: app-v/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md
- - name: Planning for the App-V Server Deployment
- href: app-v/appv-planning-for-appv-server-deployment.md
- - name: Planning for the App-V Sequencer and Client Deployment
- href: app-v/appv-planning-for-sequencer-and-client-deployment.md
- - name: Planning for Using App-V with Office
- href: app-v/appv-planning-for-using-appv-with-office.md
- - name: Planning to Use Folder Redirection with App-V
- href: app-v/appv-planning-folder-redirection-with-appv.md
- - name: App-V Planning Checklist
- href: app-v/appv-planning-checklist.md
- - name: Deploying
- items:
- - name: Deploying App-V
- href: app-v/appv-deploying-appv.md
- - name: App-V sequencer and client configuration
- items:
- - name: Deploying the App-V Sequencer and Configuring the Client
- href: app-v/appv-deploying-the-appv-sequencer-and-client.md
- - name: About Client Configuration Settings
- href: app-v/appv-client-configuration-settings.md
- - name: Enable the App-V desktop client
- href: app-v/appv-enable-the-app-v-desktop-client.md
- - name: How to Install the Sequencer
- href: app-v/appv-install-the-sequencer.md
- - name: App-V server deployment
- items:
- - name: Deploying the App-V Server
- href: app-v/appv-deploying-the-appv-server.md
- - name: How to Deploy the App-V Server
- href: app-v/appv-deploy-the-appv-server.md
- - name: How to Deploy the App-V Server Using a Script
- href: app-v/appv-deploy-the-appv-server-with-a-script.md
- - name: How to Deploy the App-V Databases by Using SQL Scripts
- href: app-v/appv-deploy-appv-databases-with-sql-scripts.md
- - name: How to Install the Publishing Server on a Remote Computer
- href: app-v/appv-install-the-publishing-server-on-a-remote-computer.md
- - name: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
- href: app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md
- - name: How to install the Management Server on a Standalone Computer and Connect it to the Database
- href: app-v/appv-install-the-management-server-on-a-standalone-computer.md
- - name: About App-V Reporting
- href: app-v/appv-reporting.md
- - name: How to install the Reporting Server on a Standalone Computer and Connect it to the Database
- href: app-v/appv-install-the-reporting-server-on-a-standalone-computer.md
- - name: App-V Deployment Checklist
- href: app-v/appv-deployment-checklist.md
- - name: Deploying Microsoft Office 2016 by Using App-V
- href: app-v/appv-deploying-microsoft-office-2016-with-appv.md
- - name: Deploying Microsoft Office 2013 by Using App-V
- href: app-v/appv-deploying-microsoft-office-2013-with-appv.md
- - name: Deploying Microsoft Office 2010 by Using App-V
- href: app-v/appv-deploying-microsoft-office-2010-wth-appv.md
- - name: Operations
- items:
- - name: Operations for App-V
- href: app-v/appv-operations.md
- - name: Creating and managing virtualized applications
- items:
- - name: Creating and Managing App-V Virtualized Applications
- href: app-v/appv-creating-and-managing-virtualized-applications.md
- - name: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
- href: app-v/appv-auto-provision-a-vm.md
- - name: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
- href: app-v/appv-auto-batch-sequencing.md
- - name: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
- href: app-v/appv-auto-batch-updating.md
- - name: Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)
- href: app-v/appv-sequence-a-new-application.md
- - name: How to Modify an Existing Virtual Application Package
- href: app-v/appv-modify-an-existing-virtual-application-package.md
- - name: How to Create and Use a Project Template
- href: app-v/appv-create-and-use-a-project-template.md
- - name: How to Create a Package Accelerator
- href: app-v/appv-create-a-package-accelerator.md
- - name: How to Create a Virtual Application Package Using an App-V Package Accelerator
- href: app-v/appv-create-a-virtual-application-package-package-accelerator.md
- - name: Administering App-V
- items:
- - name: Administering App-V Virtual Applications by Using the Management Console
- href: app-v/appv-administering-virtual-applications-with-the-management-console.md
- - name: About App-V Dynamic Configuration
- href: app-v/appv-dynamic-configuration.md
- - name: How to Connect to the Management Console
- href: app-v/appv-connect-to-the-management-console.md
- - name: How to Add or Upgrade Packages by Using the Management Console
- href: app-v/appv-add-or-upgrade-packages-with-the-management-console.md
- - name: How to Configure Access to Packages by Using the Management Console
- href: app-v/appv-configure-access-to-packages-with-the-management-console.md
- - name: How to Publish a Package by Using the Management Console
- href: app-v/appv-publish-a-packages-with-the-management-console.md
- - name: How to Delete a Package in the Management Console
- href: app-v/appv-delete-a-package-with-the-management-console.md
- - name: How to Add or Remove an Administrator by Using the Management Console
- href: app-v/appv-add-or-remove-an-administrator-with-the-management-console.md
- - name: How to Register and Unregister a Publishing Server by Using the Management Console
- href: app-v/appv-register-and-unregister-a-publishing-server-with-the-management-console.md
- - name: How to Create a Custom Configuration File by Using the App-V Management Console
- href: app-v/appv-create-a-custom-configuration-file-with-the-management-console.md
- - name: How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
- href: app-v/appv-transfer-access-and-configurations-to-another-version-of-a-package-with-the-management-console.md
- - name: How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
- href: app-v/appv-customize-virtual-application-extensions-with-the-management-console.md
- - name: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
- href: app-v/appv-view-and-configure-applications-and-default-virtual-application-extensions-with-the-management-console.md
- - name: Connection groups
- items:
- - name: Managing Connection Groups
- href: app-v/appv-managing-connection-groups.md
- - name: About the Connection Group Virtual Environment
- href: app-v/appv-connection-group-virtual-environment.md
- - name: About the Connection Group File
- href: app-v/appv-connection-group-file.md
- - name: How to Create a Connection Group
- href: app-v/appv-create-a-connection-group.md
- - name: How to Create a Connection Group with User-Published and Globally Published Packages
- href: app-v/appv-create-a-connection-group-with-user-published-and-globally-published-packages.md
- - name: How to Delete a Connection Group
- href: app-v/appv-delete-a-connection-group.md
- - name: How to Publish a Connection Group
- href: app-v/appv-publish-a-connection-group.md
- - name: How to Make a Connection Group Ignore the Package Version
- href: app-v/appv-configure-connection-groups-to-ignore-the-package-version.md
- - name: How to Allow Only Administrators to Enable Connection Groups
- href: app-v/appv-allow-administrators-to-enable-connection-groups.md
- - name: Deploying App-V packages with ESD
- items:
- - name: Deploying App-V Packages by Using Electronic Software Distribution (ESD)
- href: app-v/appv-deploying-packages-with-electronic-software-distribution-solutions.md
- - name: How to deploy App-V Packages Using Electronic Software Distribution
- href: app-v/appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md
- - name: How to Enable Only Administrators to Publish Packages by Using an ESD
- href: app-v/appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md
- - name: Using the management console
- items:
- - name: Using the App-V client management console
- href: app-v/appv-using-the-client-management-console.md
- - name: Automatically clean up unpublished packages on the App-V client
- href: app-v/appv-auto-clean-unpublished-packages.md
- - name: Migrating
- items:
- - name: Migrating to App-V from a previous version
- href: app-v/appv-migrating-to-appv-from-a-previous-version.md
- - name: How to convert a package created in a previous version of App-V
- href: app-v/appv-convert-a-package-created-in-a-previous-version-of-appv.md
- - name: Maintenance
- items:
- - name: Maintaining App-V
- href: app-v/appv-maintaining-appv.md
- - name: How to Move the App-V Server to Another Computer
- href: app-v/appv-move-the-appv-server-to-another-computer.md
- - name: Administering App-V with Windows PowerShell
- items:
- - name: Administering App-V by using Windows PowerShell
- href: app-v/appv-administering-appv-with-powershell.md
- - name: How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help
- href: app-v/appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md
- - name: How to Manage App-V Packages Running on a Stand-Alone Computer by Using Windows PowerShell
- href: app-v/appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md
- - name: How to Manage Connection Groups on a Stand-alone Computer by Using Windows PowerShell
- href: app-v/appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md
- - name: How to Modify Client Configuration by Using Windows PowerShell
- href: app-v/appv-modify-client-configuration-with-powershell.md
- - name: How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
- href: app-v/appv-configure-the-client-to-receive-updates-from-the-publishing-server.md
- - name: How to Apply the User Configuration File by Using Windows PowerShell
- href: app-v/appv-apply-the-user-configuration-file-with-powershell.md
- - name: How to Apply the Deployment Configuration File by Using Windows PowerShell
- href: app-v/appv-apply-the-deployment-configuration-file-with-powershell.md
- - name: How to Sequence a Package by Using Windows PowerShell
- href: app-v/appv-sequence-a-package-with-powershell.md
- - name: How to Create a Package Accelerator by Using Windows PowerShell
- href: app-v/appv-create-a-package-accelerator-with-powershell.md
- - name: How to Enable Reporting on the App-V Client by Using Windows PowerShell
- href: app-v/appv-enable-reporting-on-the-appv-client-with-powershell.md
- - name: How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell
- href: app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md
- - name: Troubleshooting App-V
- href: app-v/appv-troubleshooting.md
- - name: Technical Reference
- items:
- - name: Technical Reference for App-V
- href: app-v/appv-technical-reference.md
- - name: Available Mobile Device Management (MDM) settings for App-V
- href: app-v/appv-available-mdm-settings.md
- - name: Performance Guidance for Application Virtualization
- href: app-v/appv-performance-guidance.md
- - name: Application Publishing and Client Interaction
- href: app-v/appv-application-publishing-and-client-interaction.md
- - name: Viewing App-V Server Publishing Metadata
- href: app-v/appv-viewing-appv-server-publishing-metadata.md
- - name: Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
- href: app-v/appv-running-locally-installed-applications-inside-a-virtual-environment.md
+- name: Overview of apps in Windows
+ href: overview-windows-apps.md
+- name: Sideload line of business (LOB) apps
+ href: sideload-apps-in-windows.md
+- name: Private app repo on Windows 11
+ href: private-app-repository-mdm-company-portal-windows-11.md
+- name: Remove background task resource restrictions
+ href: enterprise-background-activity-controls.md
+- name: Service host grouping in Windows 10
+ href: svchost-service-refactoring.md
+- name: Per-user services in Windows
+ href: per-user-services-in-windows.md
+- name: Keep removed apps from returning during an update
+ href: remove-provisioned-apps-during-update.md
diff --git a/windows/client-management/azure-active-directory-integration-with-mdm.md b/windows/client-management/azure-active-directory-integration-with-mdm.md
index 27c5fb235c5..eefc2151aba 100644
--- a/windows/client-management/azure-active-directory-integration-with-mdm.md
+++ b/windows/client-management/azure-active-directory-integration-with-mdm.md
@@ -5,18 +5,18 @@ ms.topic: conceptual
ms.collection:
- highpri
- tier2
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Microsoft Entra integration with MDM
-Microsoft Entra ID is the world's largest enterprise cloud identity management service. It's used by organizations to access Microsoft 365 and business applications from Microsoft and third-party software as a service (SaaS) vendors. Many of the rich Windows experiences for organizational users (such as store access or OS state roaming) use Microsoft Entra ID as the underlying identity infrastructure. Windows integrates with Microsoft Entra ID, allowing devices to be registered in Microsoft Entra ID and enrolled into MDM in an integrated flow.
+Microsoft Entra ID is the world's largest enterprise cloud identity management service. It's used by organizations to access Microsoft 365 and business applications from Microsoft and third-party software as a service (SaaS) vendors. Many of the rich Windows experiences for organizational users (such as store access or OS state roaming) use Microsoft Entra ID as the underlying identity infrastructure. Windows integrates with Microsoft Entra ID, allowing devices to be registered in Microsoft Entra ID and enrolled into Mobile Device Management (MDM) in an integrated flow.
Once a device is enrolled in MDM, the MDM:
- Can enforce compliance with organization policies, add or remove apps, and more.
- Can report a device's compliance in Microsoft Entra ID.
-- Microsoft Entra ID can allow access to organization resources or applications secured by Microsoft Entra ID to devices that comply with policies.
+- Can allow access to organization resources or applications secured by Microsoft Entra ID to devices that comply with policies.
To support these rich experiences with their MDM product, MDM vendors can integrate with Microsoft Entra ID.
@@ -24,23 +24,21 @@ To support these rich experiences with their MDM product, MDM vendors can integr
There are several ways to connect your devices to Microsoft Entra ID:
-- [Join device to Microsoft Entra ID](/azure/active-directory/devices/concept-azure-ad-join)
-- [Join device to on-premises AD and Microsoft Entra ID](/azure/active-directory/devices/concept-azure-ad-join-hybrid)
-- [Add a Microsoft work account to Windows](/azure/active-directory/devices/concept-azure-ad-register)
+- [Join device to Microsoft Entra ID](/entra/identity/devices/concept-directory-join)
+- [Join device to on-premises AD and Microsoft Entra ID](/entra/identity/devices/concept-hybrid-join)
+- [Add a Microsoft work account to Windows](/entra/identity/devices/concept-device-registration)
In each scenario, Microsoft Entra authenticates the user and the device. It provides a verified unique device identifier that can be used for MDM enrollment. The enrollment flow provides an opportunity for the MDM service to render its own UI, using a web view. MDM vendors should use the UI to render the Terms of Use (TOU), which can be different for company-owned and bring-your-own-device (BYOD) devices. MDM vendors can also use the web view to render more UI elements, such as asking for a one-time PIN.
In Windows 10, the web view during the out-of-the-box scenario is displayed as full-screen by default, providing MDM vendors with the capability to create a seamless edge-to-edge user experience. However, in Windows 11 the web view is rendered within an iframe. It's important that MDM vendors who integrate with Microsoft Entra ID respect the Windows design guidelines. This step includes using a responsive web design and respecting the Windows accessibility guidelines. For example, include the forward and back buttons that are properly wired to the navigation logic. More details are provided later in this article.
-For Microsoft Entra enrollment to work for an Active Directory Federated Services (AD FS) backed Microsoft Entra account, you must enable password authentication for the intranet on the ADFS service. For more information, see [Configure Azure MFA as authentication provider with AD FS](/windows-server/identity/ad-fs/operations/configure-ad-fs-and-azure-mfa).
+For Microsoft Entra enrollment to work for an Active Directory Federated Services (AD FS) backed Microsoft Entra account, you must enable password authentication for the intranet on the ADFS service. For more information, see [Configure Microsoft Entra multifactor authentication as authentication provider with AD FS](/windows-server/identity/ad-fs/operations/configure-ad-fs-and-azure-mfa).
Once a user has a Microsoft Entra account added to Windows and enrolled in MDM, the enrollment can be managed through **Settings** > **Accounts** > **Access work or school**. Device management of either Microsoft Entra join for organization scenarios or BYOD scenarios is similar.
> [!NOTE]
> Users can't remove the device enrollment through the **Access work or school** user interface because management is tied to the Microsoft Entra ID or work account.
-
-
### MDM endpoints involved in Microsoft Entra integrated enrollment
Microsoft Entra MDM enrollment is a two-step process:
@@ -64,17 +62,15 @@ To support Microsoft Entra enrollment, MDM vendors must host and expose a **Term
The MDM is expected to use this information about the device (Device ID) when reporting device compliance back to Microsoft Entra ID using the [Microsoft Graph API](/azure/active-directory/develop/active-directory-graph-api). A sample for reporting device compliance is provided later in this article.
-
-
## Make MDM a reliable party of Microsoft Entra ID
To participate in the integrated enrollment flow outlined in the previous section, the MDM must consume access tokens issued by Microsoft Entra ID. To report compliance with Microsoft Entra ID, the MDM must authenticate itself to Microsoft Entra ID and obtain authorization in the form of an access token that allows it to invoke the [Microsoft Graph API](/azure/active-directory/develop/active-directory-graph-api).
### Cloud-based MDM
-A cloud-based MDM is a SaaS application that provides device management capabilities in the cloud. It's a multi-tenant application. This application is registered with Microsoft Entra ID in the home tenant of the MDM vendor. When an IT admin decides to use this MDM solution, an instance of this application is made visible in the tenant of the customer.
+A cloud-based MDM is a SaaS application that provides device management capabilities in the cloud. It's a multitenant application. This application is registered with Microsoft Entra ID in the home tenant of the MDM vendor. When an IT admin decides to use this MDM solution, an instance of this application is made visible in the tenant of the customer.
-The MDM vendor must first register the application in their home tenant and mark it as a multi-tenant application. For more information about how to add multi-tenant applications to Microsoft Entra ID, see the [Integrate an app that authenticates users and calls Microsoft Graph using the multi-tenant integration pattern (SaaS)](https://go.microsoft.com/fwlink/p/?LinkId=613661) code sample on GitHub.
+The MDM vendor must first register the application in their home tenant and mark it as a multitenant application. For more information about how to add multitenant applications to Microsoft Entra ID, see the [Integrate an app that authenticates users and calls Microsoft Graph using the multitenant integration pattern (SaaS)](https://go.microsoft.com/fwlink/p/?LinkId=613661) code sample on GitHub.
> [!NOTE]
> For the MDM provider, if you don't have an existing Microsoft Entra tenant with a Microsoft Entra subscription that you manage, follow these step-by-step guides:
@@ -82,7 +78,7 @@ The MDM vendor must first register the application in their home tenant and mark
> - [Quickstart: Create a new tenant in Microsoft Entra ID](/azure/active-directory/fundamentals/active-directory-access-create-new-tenant) to set up a tenant.
> - [Associate or add an Azure subscription to your Microsoft Entra tenant](/azure/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory) to add a subscription, and manage it via the Azure Portal.
-The MDM application uses keys to request access tokens from Microsoft Entra ID. These keys are managed within the tenant of the MDM provider and not visible to individual customers. The same key is used by the multi-tenant MDM application to authenticate itself with Microsoft Entra ID, in the customer tenant where the managed device belongs.
+The MDM application uses keys to request access tokens from Microsoft Entra ID. These keys are managed within the tenant of the MDM provider and not visible to individual customers. The same key is used by the multitenant MDM application to authenticate itself with Microsoft Entra ID, in the customer tenant where the managed device belongs.
> [!NOTE]
> All MDM apps must implement Microsoft Entra v2 tokens before we certify that integration works. Due to changes in the Microsoft Entra app platform, using Microsoft Entra v2 tokens is a hard requirement. For more information, see [Microsoft identity platform access tokens](/azure/active-directory/develop/access-tokens#token-formats).
@@ -107,8 +103,6 @@ For cloud-based MDM, you can roll over the application keys without requiring a
For the on-premises MDM, the Microsoft Entra authentication keys are within the customer tenant and the customer's administrator must roll over the keys. To improve security, provide guidance to customers about rolling over and protecting the keys.
-
-
## Publish your MDM app to Microsoft Entra app gallery
IT administrators use the Microsoft Entra app gallery to add an MDM for their organization to use. The app gallery is a rich store with over 2400 SaaS applications that are integrated with Microsoft Entra ID.
@@ -124,7 +118,7 @@ The following table shows the required information to create an entry in the Mic
| Item | Description |
|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **Application ID** | The client ID of your MDM app that is configured within your tenant. This ID is the unique identifier for your multi-tenant app. |
+| **Application ID** | The client ID of your MDM app that is configured within your tenant. This ID is the unique identifier for your multitenant app. |
| **Publisher** | A string that identifies the publisher of the app. |
| **Application URL** | A URL to the landing page of your app where your administrators can get more information about the MDM app and contains a link to the landing page of your app. This URL isn't used for the actual enrollment. |
| **Description** | A brief description of your MDM app, which must be under 255 characters. |
@@ -191,7 +185,7 @@ The following claims are expected in the access token passed by Windows to the T
|-----------|----------------------------------------------------------------------------------------------|
| Object ID | Identifier of the user object corresponding to the authenticated user. |
| UPN | A claim containing the user principal name (UPN) of the authenticated user. |
-| TID | A claim representing the tenant ID of the tenant. In the example above, it's Fabrikam. |
+| TID | A claim representing the tenant ID of the tenant. In the previous example, it's Fabrikam. |
| Resource | A sanitized URL representing the MDM application. Example: `https://fabrikam.contosomdm.com` |
> [!NOTE]
@@ -206,7 +200,7 @@ https://fabrikam.contosomdm.com/TermsOfUse?redirect_uri=ms-appx-web://ContosoMdm
Authorization: Bearer eyJ0eXAiOi
```
-The MDM is expected to validate the signature of the access token to ensure it is issued by Microsoft Entra ID and that the recipient is appropriate.
+The MDM is expected to validate the signature of the access token to ensure it's issued by Microsoft Entra ID and that the recipient is appropriate.
### Terms of Use content
@@ -260,8 +254,6 @@ The following table shows the error codes.
| Microsoft Entra token validation failed | 302 | unauthorized_client | unauthorized_client |
| internal service error | 302 | server_error | internal service error |
-
-
## Enrollment protocol with Microsoft Entra ID
With Azure integrated MDM enrollment, there's no discovery phase and the discovery URL is directly passed down to the system from Azure. The following table shows the comparison between the traditional and Azure enrollments.
@@ -284,8 +276,6 @@ With Azure integrated MDM enrollment, there's no discovery phase and the discove
|EnrollmentData Terms of Use binary blob as AdditionalContext for EnrollmentServiceURL|Not supported|Supported|Supported|
|CSPs accessible during enrollment|Windows 10 support: - DMClient - CertificateStore - RootCATrustedCertificates - ClientCertificateInstall - EnterpriseModernAppManagement - PassportForWork - Policy - w7 APPLICATION|||
-
-
## Management protocol with Microsoft Entra ID
There are two different MDM enrollment types that integrate with Microsoft Entra ID, and use Microsoft Entra user and device identities. Depending on the enrollment type, the MDM service may need to manage a single user or multiple users.
@@ -318,8 +308,6 @@ There are two different MDM enrollment types that integrate with Microsoft Entra
- Use the JWT Token Handler extension for WIF to validate the contents of the access token and extract claims required for use. For more information, see [JwtSecurityTokenHandler Class](/dotnet/api/system.identitymodel.tokens.jwt.jwtsecuritytokenhandler).
- Refer to the Microsoft Entra authentication code samples to get a sample for working with access tokens. For an example, see [NativeClient-DotNet](https://go.microsoft.com/fwlink/p/?LinkId=613667).
-
-
## Device Alert 1224 for Microsoft Entra user token
An alert is sent when the DM session starts and there's a Microsoft Entra user logged in. The alert is sent in OMA DM package #1. Here's an example:
@@ -372,15 +360,13 @@ Here's an example.
```
-
-
## Report device compliance to Microsoft Entra ID
Once a device is enrolled with the MDM for management, organization policies configured by the IT administrator are enforced on the device. MDM evaluates the device compliance with configured policies and then reports it to Microsoft Entra ID. This section covers the Graph API call you can use to report a device compliance status to Microsoft Entra ID.
For a sample that illustrates how an MDM can obtain an access token using OAuth 2.0 client\_credentials grant type, see [Daemon\_CertificateCredential-DotNet](https://go.microsoft.com/fwlink/p/?LinkId=613822).
-- **Cloud-based MDM** - If your product is a cloud-based multi-tenant MDM service, you have a single key configured for your service within your tenant. To obtain authorization, use this key to authenticate the MDM service with Microsoft Entra ID.
+- **Cloud-based MDM** - If your product is a cloud-based multitenant MDM service, you have a single key configured for your service within your tenant. To obtain authorization, use this key to authenticate the MDM service with Microsoft Entra ID.
- **On-premises MDM** - If your product is an on-premises MDM, customers must configure your product with the key used to authenticate with Microsoft Entra ID. This key configuration is because each on-premises instance of your MDM product has a different tenant-specific key. So, you may need to expose a configuration experience in your MDM product that enables administrators to specify the key to be used to authenticate with Microsoft Entra ID.
### Use Microsoft Graph API
@@ -415,8 +401,6 @@ Response:
- Success - HTTP 204 with No Content.
- Failure/Error - HTTP 404 Not Found. This error may be returned if the specified device or tenant can't be found.
-
-
## Data loss during unenrollment from Microsoft Entra join
When a user is enrolled into MDM through Microsoft Entra join and then disconnects the enrollment, there's no warning that the user will lose Windows Information Protection (WIP) data. The disconnection message doesn't indicate the loss of WIP data.
diff --git a/windows/client-management/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md b/windows/client-management/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md
index ab7c3e0a1c8..aca40777f6d 100644
--- a/windows/client-management/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md
+++ b/windows/client-management/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md
@@ -2,7 +2,7 @@
title: Automatic MDM enrollment in the Intune admin center
description: Automatic MDM enrollment in the Intune admin center
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Automatic MDM enrollment in the Intune admin center
diff --git a/windows/client-management/bulk-enrollment-using-windows-provisioning-tool.md b/windows/client-management/bulk-enrollment-using-windows-provisioning-tool.md
index d9938c6409f..c248120cff2 100644
--- a/windows/client-management/bulk-enrollment-using-windows-provisioning-tool.md
+++ b/windows/client-management/bulk-enrollment-using-windows-provisioning-tool.md
@@ -1,13 +1,13 @@
---
title: Bulk enrollment
-description: Bulk enrollment is an efficient way to set up a large number of devices to be managed by an MDM server without the need to reimage the devices.
+description: Bulk enrollment is an efficient way to set up an MDM server to manage a large number of devices without the need to reimage the devices.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Bulk enrollment using Windows Configuration Designer
-Bulk enrollment is an efficient way to set up a large number of devices to be managed by an MDM server without the need to reimage the devices. You can use the [Provisioning CSP](mdm/provisioning-csp.md) for bulk enrollment, except for the Microsoft Entra join enrollment scenario.
+Bulk enrollment is an efficient way to set up an MDM server to manage a large number of devices without the need to reimage the devices. You can use the [Provisioning CSP](mdm/provisioning-csp.md) for bulk enrollment, except for the Microsoft Entra join enrollment scenario.
## Typical use cases
@@ -68,7 +68,7 @@ Using the WCD, create a provisioning package using the enrollment information re
1. Configure the other settings, such as the Wi-Fi connections so that the device can join a network before joining MDM (for example, **Runtime settings** > **ConnectivityProfiles** > **WLANSetting**).
-1. When you're done adding all the settings, on the **File** menu, select **Save**.
+1. After adding all the settings, select **Save** on the **File** menu.
1. On the main menu, select **Export** > **Provisioning package**.
@@ -120,7 +120,7 @@ Using the WCD, create a provisioning package using the enrollment information re
For detailed descriptions of these settings, see [Provisioning CSP](mdm/provisioning-csp.md).
1. Configure the other settings, such as the Wi-Fi connection so that the device can join a network before joining MDM (for example, **Runtime settings** > **ConnectivityProfiles** > **WLANSetting**).
-1. When you're done adding all the settings, on the **File** menu, select **Save**.
+1. After adding all the settings, select **Save** on the **File** menu.
1. Export and build the package (steps 10-13 in previous section).
1. Apply the package to some test devices and verify that they work. For more information, see [Apply a provisioning package](#apply-a-provisioning-package).
1. Apply the package to your devices.
@@ -142,7 +142,7 @@ Using the WCD, create a provisioning package using the enrollment information re
- If the provisioning engine receives a failure from a CSP, it retries provisioning three times in a row.
- If all immediate attempts fail, a delayed task is launched to try provisioning again later. It will retry four times at a decaying rate of 15 minutes -> 1 hr -> 4 hr -> "Next System Start". These attempts are run from the SYSTEM context.
- It also retries the provisioning each time it's launched, if started from somewhere else as well.
-- In addition, provisioning will be restarted in the SYSTEM context after a sign in and the [system has been idle](/windows/win32/taskschd/task-idle-conditions).
+- In addition, provisioning will be restarted in the SYSTEM context after a sign in and the [system is idle](/windows/win32/taskschd/task-idle-conditions).
## Related articles
diff --git a/windows/client-management/certificate-authentication-device-enrollment.md b/windows/client-management/certificate-authentication-device-enrollment.md
index e53a80cc551..2cea712e444 100644
--- a/windows/client-management/certificate-authentication-device-enrollment.md
+++ b/windows/client-management/certificate-authentication-device-enrollment.md
@@ -2,7 +2,7 @@
title: Certificate authentication device enrollment
description: This section provides an example of the mobile device enrollment protocol using certificate authentication policy.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Certificate authentication device enrollment
diff --git a/windows/client-management/certificate-renewal-windows-mdm.md b/windows/client-management/certificate-renewal-windows-mdm.md
index 573cbe71b28..66d42a4d90e 100644
--- a/windows/client-management/certificate-renewal-windows-mdm.md
+++ b/windows/client-management/certificate-renewal-windows-mdm.md
@@ -2,7 +2,7 @@
title: Certificate Renewal
description: Learn how to find all the resources that you need to provide continuous access to client certificates.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Certificate Renewal
@@ -19,7 +19,7 @@ Windows supports automatic certificate renewal, also known as Renew On Behalf Of
> [!NOTE]
> Certificate renewal of the enrollment certificate through ROBO is only supported with Microsoft PKI.
-Auto certificate renewal is the only supported MDM client certificate renewal method for the device that's enrolled using WAB authentication. Meaning, the AuthPolicy is set to Federated. It also means if the server supports WAB authentication, then the MDM certificate enrollment server MUST also support client TLS to renew the MDM client certificate.
+Auto certificate renewal is the only supported MDM client certificate renewal method for a device enrolled using WAB authentication. Meaning, the AuthPolicy is set to Federated. It also means if the server supports WAB authentication, then the MDM certificate enrollment server MUST also support client TLS to renew the MDM client certificate.
For Windows devices, during the MDM client certificate enrollment phase or during MDM management section, the enrollment server or MDM server could configure the device to support automatic MDM client certificate renewal using [CertificateStore CSP's](mdm/certificatestore-csp.md) ROBOSupport node under `CertificateStore/My/WSTEP/Renew` URL.
@@ -89,7 +89,7 @@ In Windows, the renewal period can only be set during the MDM enrollment phase.
For more information about the parameters, see the [CertificateStore configuration service provider](mdm/certificatestore-csp.md).
-Unlike manual certificate renewal, the device doesn't perform an automatic MDM client certificate renewal if the certificate is already expired. To make sure the device has enough time to automatically renew, we recommend you set a renewal period a couple months (40-60 days) before the certificate expires. And, set the renewal retry interval to every few days, like every 4-5 days instead of every seven days (weekly). This change increases the chance that the device will try to connect at different days of the week.
+Unlike manual certificate renewal, the device doesn't perform an automatic MDM client certificate renewal if the certificate is already expired. To make sure the device has enough time to automatically renew, we recommend you set a renewal period a couple months (40-60 days) before the certificate expires. And, set the renewal retry interval to every few days, like every 4-5 days instead of every seven days (weekly). This change increases the chance that the device tries to connect at different days of the week.
## Certificate renewal response
@@ -99,7 +99,7 @@ When RequestType is set to Renew, the web service verifies the following (in add
- The client's certificate is in the renewal period
- The certificate is issued by the enrollment service
- The requester is the same as the requester for initial enrollment
-- For standard client's request, the client hasn't been blocked
+- For standard client's request, the client isn't blocked
After validation is completed, the web service retrieves the PKCS#10 content from the PKCS#7 BinarySecurityToken. The rest is the same as initial enrollment, except that the Provisioning XML only needs to have the new certificate issued by the CA.
diff --git a/windows/client-management/client-tools/add-remove-hide-features.md b/windows/client-management/client-tools/add-remove-hide-features.md
new file mode 100644
index 00000000000..92fa8aaf856
--- /dev/null
+++ b/windows/client-management/client-tools/add-remove-hide-features.md
@@ -0,0 +1,160 @@
+---
+title: Add, remove, or hide Windows features
+description: Learn how to add or remove Windows optional features using the Optional features page in the Settings app. Also see the group policy objects (GPO) and MDM policies that show or hide Windows Features in the Settings app. Use Windows PowerShell to show or hide specific features in Windows Features.
+ms.date: 07/01/2024
+ms.topic: how-to
+zone_pivot_groups: windows-versions-11-10
+---
+
+# Add, remove, or hide Windows features
+
+Windows has optional features that aren't included by default, but you can add later. These features are called [Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities), and can be added at any time. Some of these features are language resources like language packs or handwriting support. On organization-owned devices, you can control access to these other features. You can use group policy or mobile device management (MDM) policies to hide the UI from users, or use Windows PowerShell to enable or disable specific features.
+
+## Use the Windows Settings app to add or remove features
+
+
+
+Open the **Optional features** pane in the **Settings** app by selecting the following link:
+
+> [!div class="nextstepaction"]
+> [Optional features](ms-settings:optionalfeatures)
+
+Or
+
+1. Right-click on the **Start** menu and select **Run**.
+
+1. In the **Run** window, next to **Open:**, enter:
+
+ ```console
+ ms-settings:optionalfeatures
+ ```
+
+ and then select **OK**.
+
+Or
+
+::: zone pivot="windows-11"
+
+1. Right-click on the **Start** menu and select **Settings**.
+
+1. In the left hand pane of the Settings app, select **System**.
+
+1. In the right hand **System** pane, select **Optional features**.
+
+> [!NOTE]
+>
+> The navigation steps, UI elements, and UI text in this section are based on the latest version of Windows 11 with the latest cumulative update installed. For other versions of Windows 11 that are currently supported or don't have the latest cumulative update, some of the navigation steps, UI elements, and UI text might be different. For example, the [**Optional features**](ms-settings:optionalfeatures) pane might be located under **Settings** > **Apps**.
+
+::: zone-end
+
+::: zone pivot="windows-10"
+
+1. Right-click on the **Start** menu and select **Settings**.
+
+1. In the Settings app, select **System**.
+
+1. In the left hand pane, select **Optional features**.
+
+> [!NOTE]
+>
+> The navigation steps, UI elements, and UI text in this section are based on Windows 10 22H2 with the latest cumulative update installed. For other versions of Windows 10 that are currently supported or don't have the latest cumulative update, some of the navigation steps, UI elements, and UI text might be different. For example, the [**Optional features**](ms-settings:optionalfeatures) pane might be located under **Settings** > **Apps** > **Apps & features**.
+
+::: zone-end
+
+### Add a feature
+
+::: zone pivot="windows-11"
+
+Once the **System > Optional features** pane is open, add a feature with the following steps:
+
+1. Select the **View features** button next to **Add an optional feature**.
+
+1. In the **Add an optional feature** window that opens:
+
+ 1. Find the desired feature to add and then select the box next to the feature to add it. Multiple features can be selected.
+
+ 1. Once all of the desired features are selected, select the **Next** button.
+
+ 1. Review the selected list of features and then select the **Add** button to add the selected features.
+
+::: zone-end
+
+::: zone pivot="windows-10"
+
+Once the **Optional features** pane is open, add a feature with the following steps:
+
+1. Select the **+** button next to **Add a feature**.
+
+1. In the **Add an optional feature** window that opens:
+
+ 1. Find the desired feature to add and then select the box next to the feature to add it. Multiple features can be selected.
+
+ 1. Once all of the desired features are selected, select the **Add** button.
+
+::: zone-end
+
+> [!IMPORTANT]
+>
+> Windows Update is used to add the optional features. The device needs to be online so Windows Update can download the content that it needs to add.
+
+### Remove a feature
+
+::: zone pivot="windows-11"
+
+Once the **System > Optional features** pane is open, remove a feature with the following steps:
+
+1. Under **Installed features**, search for the feature that needs to be removed in the **Search installed features** search box, or scroll through the list of added features until the feature that needs to be removed is found.
+
+1. Once the feature that needs to be removed is found, select the feature to expand it, and then select the **Remove** button.
+
+::: zone-end
+
+::: zone pivot="windows-10"
+
+Once the **Optional features** pane is open, remove a feature with the following steps:
+
+1. Under **Installed features**, search for the feature that needs to be removed in the **Find an installed optional feature** search box, or scroll through the list of added features until the feature that needs to be removed is found.
+
+1. Once the feature that needs to be removed is found, select the feature to expand it, and then select the **Remove** button.
+
+::: zone-end
+
+## Use group policy or MDM policies to hide Windows features
+
+By default, the OS might show Windows features and allow users to add and remove these optional apps and features. To hide Windows features on your user devices, you can use group policy or an MDM provider like Microsoft Intune.
+
+### Group policy
+
+If you use group policy, use the `User Configuration\Administrative Template\Control Panel\Programs\Hide "Windows Features"` policy. By default, this policy might be set to **Not configured**, which means users can add or remove features. When this setting is **Enabled**, the settings page to add optional features is hidden on the device.
+
+You can't use group policy to disable specific Windows features. If you want to disable specific features, use [Windows PowerShell](#use-windows-powershell-to-disable-specific-features).
+
+If you want to hide the entire **Apps** feature in the Settings app, use the `User Configuration\Administrative Template\Control Panel\Programs\Hide "Programs and Features" page` policy.
+
+### MDM
+
+Using Microsoft Intune, you can use [administrative templates](/mem/intune/configuration/administrative-templates-windows) or the [settings catalog](/mem/intune/configuration/settings-catalog) to hide Windows features.
+
+If you want to hide the entire **Apps** feature in the Settings app, you can use a configuration policy on Intune enrolled devices. For more information on the settings you can configure, see [Control Panel and Settings device restrictions in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#control-panel-and-settings).
+
+## Use Windows PowerShell to disable specific features
+
+To disable specific features, use the Windows PowerShell [Disable-WindowsOptionalFeature](/powershell/module/dism/disable-windowsoptionalfeature) cmdlet.
+
+> [!NOTE]
+>
+> There isn't a group policy that disables specific Windows features.
+
+To automate disabling specific features, create a scheduled task to run a PowerShell script. For more information about Windows task scheduler, see [Task Scheduler for developers](/windows/win32/taskschd/task-scheduler-start-page).
+
+Microsoft Intune can also run PowerShell scripts. For more information, see [Use PowerShell scripts on Windows client devices in Intune](/mem/intune/apps/intune-management-extension).
+
+To enable specific features, use the [Enable-WindowsOptionalFeature](/powershell/module/dism/enable-windowsoptionalfeature) cmdlet.
+
+Another useful PowerShell cmdlet is [Get-WindowsOptionalFeature](/powershell/module/dism/get-windowsoptionalfeature). Use this cmdlet to view information about optional features in the current OS or a mounted image. This cmdlet returns the current state of features, and whether a restart might be required when the state changes.
+
+## Related content
+
+- [Features on Demand overview](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities).
+- [Available Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-non-language-fod).
+- [Language and region Features on Demand (FOD)](/windows-hardware/manufacture/desktop/features-on-demand-language-fod).
diff --git a/windows/client-management/client-tools/administrative-tools-in-windows.md b/windows/client-management/client-tools/administrative-tools-in-windows.md
index 1e319e16a49..785eb740ccf 100644
--- a/windows/client-management/client-tools/administrative-tools-in-windows.md
+++ b/windows/client-management/client-tools/administrative-tools-in-windows.md
@@ -1,18 +1,28 @@
---
-title: Windows Tools/Administrative Tools
+title: Windows Tools
description: The folders for Windows Tools and Administrative Tools are folders in the Control Panel that contain tools for system administrators and advanced users.
-ms.localizationpriority: medium
-ms.date: 08/10/2023
+ms.date: 07/01/2024
ms.topic: conceptual
+zone_pivot_groups: windows-versions-11-10
ms.collection:
-- highpri
-- tier2
- essentials-manage
---
-# Windows Tools/Administrative Tools
+# Windows Tools
-**Windows Tools** is a folder in the Windows 11 Control Panel. **Administrative Tools** is a folder in the Windows 10 Control Panel. These folders contain tools for system administrators and advanced users.
+::: zone pivot="windows-11"
+
+**Windows Tools** is a folder in the Windows 11 Control Panel. This folder contains tools for system administrators and advanced users.
+
+::: zone-end
+
+::: zone pivot="windows-10"
+
+**Administrative Tools** is a folder in the Windows 10 Control Panel. This folder contains tools for system administrators and advanced users.
+
+::: zone-end
+
+::: zone pivot="windows-11"
## Windows Tools folder
@@ -24,6 +34,10 @@ The tools in the folder might vary depending on which edition of Windows you use
:::image type="content" source="images/win11-windows-tools.png" alt-text="Screenshot of the contents of the Windows Tools folder in Windows 11." lightbox="images/win11-windows-tools.png":::
+::: zone-end
+
+::: zone pivot="windows-10"
+
## Administrative Tools folder
The following graphic shows the **Administrative Tools** folder in Windows 10:
@@ -34,34 +48,7 @@ The tools in the folder might vary depending on which edition of Windows you use
-## Tools
-
-The tools are located in the folder `C:\Windows\System32\` or its subfolders.
-
-These tools were included in previous versions of Windows. The associated documentation for each tool can help you use them. The following list provides links to documentation for each tool.
-
-- [Component Services](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731901(v=ws.11))
-- [Computer Management](https://support.microsoft.com/topic/how-to-use-computer-management-in-windows-xp-d5872f93-4498-f4dd-3a34-36d6f569924f)
-- [Defragment and Optimize Drives](https://support.microsoft.com/windows/ways-to-improve-your-computer-s-performance-c6018c78-0edd-a71a-7040-02267d68ea90)
-- [Disk Cleanup](https://support.microsoft.com/windows/disk-cleanup-in-windows-8a96ff42-5751-39ad-23d6-434b4d5b9a68)
-- [Event Viewer](/previous-versions/windows/it-pro/windows-2000-server/cc938674(v=technet.10))
-- [iSCSI Initiator](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee338476(v=ws.10))
-- [Local Security Policy](/previous-versions/tn-archive/dd277395(v=technet.10))
-- [ODBC Data Sources](/sql/odbc/admin/odbc-data-source-administrator)
-- [Performance Monitor](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc749115(v=ws.11))
-- [Print Management](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731857(v=ws.11))
-- [Recovery Drive](https://support.microsoft.com/windows/create-a-recovery-drive-abb4691b-5324-6d4a-8766-73fab304c246)
-- [Registry Editor](/windows/win32/sysinfo/registry)
-- [Resource Monitor](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd883276(v=ws.10))
-- [Services](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc772408(v=ws.11))
-- [System Configuration](/troubleshoot/windows-client/performance/system-configuration-utility-troubleshoot-configuration-errors)
-- [System Information](/previous-versions/windows/it-pro/windows-2000-server/cc957818(v=technet.10))
-- [Task Scheduler](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc766428(v=ws.11))
-- [Windows Firewall with Advanced Security](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754274(v=ws.11))
-- [Windows Memory Diagnostic](/previous-versions/technet-magazine/cc745953(v=msdn.10))
-
-> [!TIP]
-> If the linked content in this list doesn't provide the information you need to use that tool, send feedback with the **This page** link in the **Feedback** section at the bottom of this article.
+::: zone-end
## Related articles
diff --git a/windows/client-management/client-tools/change-default-removal-policy-external-storage-media.md b/windows/client-management/client-tools/change-default-removal-policy-external-storage-media.md
index 685f872e8a4..725c23927ae 100644
--- a/windows/client-management/client-tools/change-default-removal-policy-external-storage-media.md
+++ b/windows/client-management/client-tools/change-default-removal-policy-external-storage-media.md
@@ -1,12 +1,11 @@
---
title: Windows default media removal policy
-description: In Windows 10 and later, the default removal policy for external storage media changed from Better performance to Quick removal.
-ms.date: 08/10/2023
+description: Manage default media removal policy in Windows.
+ms.date: 07/01/2024
ms.topic: conceptual
-ms.localizationpriority: medium
---
-# Change in default removal policy for external storage media in Windows
+# Manage default media removal policy
Windows defines two main policies, **Quick removal** and **Better performance**, that control how the system interacts with external storage devices such as USB thumb drives or Thunderbolt-enabled external drives. Beginning in Windows 10 version 1809, the default policy is **Quick removal**. In earlier versions of Windows, the default policy was **Better performance**.
@@ -16,7 +15,7 @@ You can change the policy setting for each external device, and the policy that
You can use the storage device policy setting to change the manner in which Windows manages storage devices to better meet your needs. The policy settings have the following effects:
-- **Quick removal**: This policy manages storage operations in a manner that keeps the device ready to remove at any time. You can remove the device without using the Safely Remove Hardware process. However, to do this, Windows can't cache disk write operations. This may degrade system performance.
+- **Quick removal**: This policy manages storage operations in a manner that keeps the device ready to remove at any time. You can remove the device without using the Safely Remove Hardware process. However, to do this, Windows can't cache disk write operations. This can degrade system performance.
- **Better performance**: This policy manages storage operations in a manner that improves system performance. When this policy is in effect, Windows can cache write operations to the external device. However, you must use the Safely Remove Hardware process to remove the external drive. The Safely Remove Hardware process protects the integrity of data on the device by making sure that all cached operations finish.
> [!IMPORTANT]
diff --git a/windows/client-management/client-tools/connect-to-remote-aadj-pc.md b/windows/client-management/client-tools/connect-to-remote-aadj-pc.md
index b47fad81eec..c08492c2018 100644
--- a/windows/client-management/client-tools/connect-to-remote-aadj-pc.md
+++ b/windows/client-management/client-tools/connect-to-remote-aadj-pc.md
@@ -2,7 +2,7 @@
title: Connect to remote Microsoft Entra joined device
description: Learn how to use Remote Desktop Connection to connect to a Microsoft Entra joined device.
ms.localizationpriority: medium
-ms.date: 08/10/2023
+ms.date: 07/01/2024
ms.topic: conceptual
ms.collection:
- highpri
@@ -14,18 +14,16 @@ ms.collection:
Windows supports remote connections to devices joined to Active Directory s well as devices joined to Microsoft Entra ID using Remote Desktop Protocol (RDP).
- Starting in Windows 10, version 1809, you can [use biometrics to authenticate to a remote desktop session](/windows/whats-new/whats-new-windows-10-version-1809#remote-desktop-with-biometrics).
-- Starting in Windows 10/11, with 2022-10 update installed, you can [use Microsoft Entra authentication to connect to the remote Microsoft Entra device](#connect-with-azure-ad-authentication).
+- Starting in Windows 10/11, with 2022-10 update installed, you can [use Microsoft Entra authentication to connect to the remote Microsoft Entra device](#connect-with-microsoft-entra-authentication).
## Prerequisites
- Both devices (local and remote) must be running a supported version of Windows.
- Remote device must have the **Connect to and use this PC from another device using the Remote Desktop app** option selected under **Settings** > **System** > **Remote Desktop**.
- - It's recommended to select **Require devices to use Network Level Authentication to connect** option.
+ - Select **Require devices to use Network Level Authentication to connect** option is recommended.
- If the user who joined the device to Microsoft Entra ID is the only one who is going to connect remotely, no other configuration is needed. To allow more users or groups to connect to the device remotely, you must [add users to the Remote Desktop Users group](#add-users-to-remote-desktop-users-group) on the remote device.
- Ensure [Remote Credential Guard](/windows/access-protection/remote-credential-guard) is turned off on the device you're using to connect to the remote device.
-
-
## Connect with Microsoft Entra authentication
Microsoft Entra authentication can be used on the following operating systems for both the local and remote device:
@@ -64,8 +62,6 @@ The Windows lock screen in the remote session doesn't support Microsoft Entra au
Disconnecting the session also ensures that when the connection is relaunched after a period of inactivity, Microsoft Entra ID reevaluates the applicable conditional access policies.
-
-
## Connect without Microsoft Entra authentication
By default, RDP doesn't use Microsoft Entra authentication, even if the remote PC supports it. This method allows you to connect to the remote Microsoft Entra joined device from:
diff --git a/windows/client-management/client-tools/images/change-def-rem-policy-2.png b/windows/client-management/client-tools/images/change-def-rem-policy-2.png
index d05d5dd16fd..d99919de151 100644
Binary files a/windows/client-management/client-tools/images/change-def-rem-policy-2.png and b/windows/client-management/client-tools/images/change-def-rem-policy-2.png differ
diff --git a/windows/client-management/client-tools/images/settings-page-visibility-gp.png b/windows/client-management/client-tools/images/settings-page-visibility-gp.png
index 198fc83a7c5..eabe085176c 100644
Binary files a/windows/client-management/client-tools/images/settings-page-visibility-gp.png and b/windows/client-management/client-tools/images/settings-page-visibility-gp.png differ
diff --git a/windows/client-management/client-tools/manage-device-installation-with-group-policy.md b/windows/client-management/client-tools/manage-device-installation-with-group-policy.md
index 0aaf41776dd..052dc9e72a8 100644
--- a/windows/client-management/client-tools/manage-device-installation-with-group-policy.md
+++ b/windows/client-management/client-tools/manage-device-installation-with-group-policy.md
@@ -1,7 +1,7 @@
---
title: Manage Device Installation with Group Policy
description: Find out how to manage Device Installation Restrictions with Group Policy.
-ms.date: 08/10/2023
+ms.date: 07/01/2024
ms.topic: conceptual
---
diff --git a/windows/client-management/client-tools/manage-settings-app-with-group-policy.md b/windows/client-management/client-tools/manage-settings-app-with-group-policy.md
index bf19bb6ad7f..fb091f005b9 100644
--- a/windows/client-management/client-tools/manage-settings-app-with-group-policy.md
+++ b/windows/client-management/client-tools/manage-settings-app-with-group-policy.md
@@ -1,7 +1,7 @@
---
title: Manage the Settings app with Group Policy
description: Find out how to manage the Settings app with Group Policy so you can hide specific pages from users.
-ms.date: 08/10/2023
+ms.date: 07/01/2024
ms.topic: conceptual
---
diff --git a/windows/client-management/client-tools/mandatory-user-profile.md b/windows/client-management/client-tools/mandatory-user-profile.md
index 78e358f1fd4..5e64dd2f66c 100644
--- a/windows/client-management/client-tools/mandatory-user-profile.md
+++ b/windows/client-management/client-tools/mandatory-user-profile.md
@@ -1,16 +1,13 @@
---
title: Create mandatory user profiles
-description: A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users.
-ms.date: 08/10/2023
+description: A mandatory user profile is a special type of preconfigured roaming user profile that administrators can use to specify settings for users.
+ms.date: 07/01/2024
ms.topic: conceptual
-ms.collection:
-- highpri
-- tier2
---
# Create mandatory user profiles
-A mandatory user profile is a roaming user profile that has been pre-configured by an administrator to specify settings for users. Settings commonly defined in a mandatory profile include (but aren't limited to) icons that appear on the desktop, desktop backgrounds, user preferences in Control Panel, printer selections, and more. Configuration changes made during a user's session that are normally saved to a roaming user profile aren't saved when a mandatory user profile is assigned.
+A mandatory user profile is a roaming user profile that has been preconfigured by an administrator to specify settings for users. Settings commonly defined in a mandatory profile include (but aren't limited to) icons that appear on the desktop, desktop backgrounds, user preferences in Control Panel, printer selections, and more. Configuration changes made during a user's session that are normally saved to a roaming user profile aren't saved when a mandatory user profile is assigned.
Mandatory user profiles are useful when standardization is important, such as on a kiosk device or in educational settings. Only system administrators can make changes to mandatory user profiles.
@@ -118,12 +115,12 @@ In a domain, you modify properties for the user account to point to the mandator
### How to apply a mandatory user profile to users
1. Open **Active Directory Users and Computers** (dsa.msc).
-1. Navigate to the user account that you'll assign the mandatory profile to.
+1. Navigate to the user account that you want to assign the mandatory profile to.
1. Right-click the user name and open **Properties**.
1. On the **Profile** tab, in the **Profile path** field, enter the path to the shared folder without the extension. For example, if the folder name is `\\server\share\profile.v6`, you would enter `\\server\share\profile`.
1. Select **OK**.
-It may take some time for this change to replicate to all domain controllers.
+It can take some time for this change to replicate to all domain controllers.
## Apply policies to improve sign-in time
diff --git a/windows/client-management/client-tools/quick-assist.md b/windows/client-management/client-tools/quick-assist.md
index f902b922049..25a3039918a 100644
--- a/windows/client-management/client-tools/quick-assist.md
+++ b/windows/client-management/client-tools/quick-assist.md
@@ -1,9 +1,8 @@
---
title: Use Quick Assist to help users
description: Learn how IT Pros can use Quick Assist to help users.
-ms.date: 08/10/2023
+ms.date: 07/01/2024
ms.topic: conceptual
-ms.localizationpriority: medium
ms.collection:
- highpri
- tier1
@@ -11,11 +10,16 @@ ms.collection:
# Use Quick Assist to help users
-Quick Assist is a Microsoft Store application that enables a person to share their device with another person over a remote connection. Your support staff can use it to remotely connect to a user's device and then view its display, make annotations, or take full control. In this way, they can troubleshoot, diagnose technological issues, and provide instructions to users directly on their devices.
+Quick Assist is an application that enables a person to share their [Windows](#install-quick-assist-on-windows) or [macOS](#install-quick-assist-on-macos) device with another person over a remote connection. Your support staff can use it to remotely connect to a user's device and then view its display, make annotations, or take full control. In this way, they can troubleshoot, diagnose technological issues, and provide instructions to users directly on their devices.
+
+> [!IMPORTANT]
+> Learn how to [protect yourself from tech support scams](https://support.microsoft.com/help/4013405). Tech support scams are an industry-wide issue where scammers use scare tactics to trick you into unnecessary technical support services. Only allow a Helper to connect to your device if you initiated the interaction by contacting Microsoft Support or your IT support staff directly.
+>
+> If you or someone you know has been affected by a tech support scam, use the [technical support scam form](https://support.microsoft.com/windows/cfa4609a-92cc-4808-95e8-392b4ffd0753) to report it.
## Before you begin
-All that's required to use Quick Assist is suitable network and internet connectivity. No roles, permissions, or policies are involved. Neither party needs to be in a domain. The helper must have a Microsoft account. The sharer doesn't have to authenticate.
+All you need to use Quick Assist is suitable network and internet connectivity. No roles, permissions, or policies are involved. Neither party needs to be in a domain. The helper must have a Microsoft account. The sharer doesn't have to authenticate.
### Authentication
@@ -38,7 +42,7 @@ Quick Assist communicates over port 443 (https) and connects to the Remote Assis
| `*.trouter.skype.com` | Used for Azure Communication Service for chat and connection between parties. |
| `aadcdn.msauth.net` | Required for logging in to the application (Microsoft Entra ID). |
| `edge.skype.com` | Used for Azure Communication Service for chat and connection between parties. |
-| `login.microsoftonline.com` | Required for Microsoft login service. |
+| `login.microsoftonline.com` | Required for Microsoft sign-in service. |
| `remoteassistanceprodacs.communication.azure.com` | Used for Azure Communication Service for chat and connection between parties. |
| `turn.azure.com` | Required for Azure Communication Service. |
@@ -89,52 +93,80 @@ Microsoft logs a small amount of session data to monitor the health of the Quick
In some scenarios, the helper does require the sharer to respond to application permission prompts (User Account Control), but otherwise the helper has the same permissions as the sharer on the device.
-## Install Quick Assist
+## Install Quick Assist on Windows
### Install Quick Assist from the Microsoft Store
1. Download the new version of Quick Assist by visiting the [Microsoft Store](https://apps.microsoft.com/store/detail/quick-assist/9P7BP5VNWKX5).
-1. In the Microsoft Store, select **Get in Store app**. Then, give permission to install Quick Assist. When the installation is complete, **Get** changes to **Open**. :::image type="content" source="images/quick-assist-get.png" lightbox="images/quick-assist-get.png" alt-text="Microsoft Store window showing the Quick Assist app with a button labeled get in the bottom right corner.":::
+1. In the Microsoft Store, select **View in store**, then install Quick Assist. When the installation is complete, **Install** changes to **Open**.
For more information, visit [Install Quick Assist](https://support.microsoft.com/windows/install-quick-assist-c17479b7-a49d-4d12-938c-dbfb97c88bca).
### Install Quick Assist with Intune
-Before installing Quick Assist, you need to set up synchronization between Intune and Microsoft Store for Business. If you've already set up sync, log into [Microsoft Store for Business](https://businessstore.microsoft.com) and skip to step 5.
-
-1. In the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Tenant administration** / **Connectors and tokens** / **Microsoft Store for Business** and verify that **Microsoft Store for Business sync** is set to **Enable**.
-1. Using your Global Admin account, log into [Microsoft Store for Business](https://businessstore.microsoft.com).
-1. Select **Manage** / **Settings** and enable **Show offline apps**.
-1. Choose the **Distribute** tab and verify that **Microsoft Intune** is **Active**. You may need to use the **+Add management tool** link if it's not.
-1. Search for **Quick Assist** and select it from the Search results.
-1. Choose the **Offline** license and select **Get the app**
-1. In the Intune admin center, choose **Sync**.
-1. Navigate to **Apps** / **Windows** and you should see **Quick Assist (Offline)** in the list.
-1. Select it to view its properties.
-1. By default, the app isn't assigned to any user or device, select the **Edit** link. Assign the app to the required group of devices and choose **Review + save** to complete the application install.
-
-> [!NOTE]
-> Assigning the app to a device or group of devices instead of a user is important because it's the only way to install a store app in device context.
-
-Visit [Add Microsoft Store apps to Microsoft Intune](/mem/intune/apps/store-apps-windows) for more information.
+To deploy Quick Assist with Intune, see [Add Microsoft Store apps to Microsoft Intune](/mem/intune/apps/store-apps-microsoft).
### Install Quick Assist Offline
To install Quick Assist offline, you need to download your APPXBUNDLE and unencoded XML file from [Microsoft Store for Business](https://businessstore.microsoft.com). Visit [Download an offline-licensed app](/microsoft-store/distribute-offline-apps#download-an-offline-licensed-app) for more information.
-1. Start **Windows PowerShell** with Administrative privileges.
-1. In PowerShell, change the directory to the location you've saved the file to in step 1: `cd `
-1. Run the following command to install Quick Assist: `Add-AppxProvisionedPackage -Online -PackagePath "MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe.AppxBundle" -LicensePath "MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe_4bc27046-84c5-8679-dcc7-d44c77a47dd0.xml"`
-1. After Quick Assist has installed, run this command to confirm that Quick Assist is installed for the user: `Get-AppxPackage *QuickAssist* -AllUsers`
+1. Start **Windows PowerShell** with Administrative privileges
+1. In PowerShell, change the directory to the location where you saved the file in step 1: `cd `
+1. To install Quick Assist, run the following command: `Add-AppxProvisionedPackage -Online -PackagePath "MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe.AppxBundle" -LicensePath "MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe_4bc27046-84c5-8679-dcc7-d44c77a47dd0.xml"`
+1. After Quick Assist is installed, run this command to confirm that Quick Assist is installed for the user: `Get-AppxPackage *QuickAssist* -AllUsers`
-## Microsoft Edge WebView2
+### Microsoft Edge WebView2
-The Microsoft Edge WebView2 is a development control that uses Microsoft Edge as the rendering engine to display web content in native apps. The new Quick Assist application has been developed using this control, making it a necessary component for the app to function.
+The Microsoft Edge WebView2 is a development control that uses Microsoft Edge as the rendering engine to display web content in native apps. The new Quick Assist application is developed using this control, making it a necessary component for the app to function.
- For Windows 11 users, this runtime control is built in.
- For Windows 10 users, the Quick Assist Store app detects if WebView2 is present on launch and if necessary, installs it automatically. If an error message or prompt is shown indicating WebView2 isn't present, it needs to be installed separately.
-For more information on distributing and installing Microsoft Edge WebView2, visit [Distribute your app and the WebView2 Runtime](/microsoft-edge/webview2/concepts/distribution)
+For more information on distributing and installing Microsoft Edge WebView2, visit [Distribute your app and the WebView2 Runtime.](/microsoft-edge/webview2/concepts/distribution)
+
+## Install Quick Assist on macOS
+
+Quick Assist for macOS is available for interactions with Microsoft Support. If Microsoft products on your macOS device aren't working as expected, contact [Microsoft Support](https://support.microsoft.com/contactus) for assistance. Your Microsoft Support agent will guide you through the process of downloading and installing it on your device.
+
+> [!NOTE]
+> Quick Assist for macOS is not available outside of Microsoft Support interactions.
+
+## Disable Quick Assist within your organization
+
+If your organization utilizes another remote support tool such as [Remote Help](https://www.microsoft.com/security/business/endpoint-management/microsoft-intune-remote-help), disable or remove Quick Assist as a best practice, if it isn't used within your environment. This prevents guests from using Quick Assist to gain access to devices within your organization.
+
+### Disable Quick Assist
+
+To disable Quick Assist, block traffic to the `https://remoteassistance.support.services.microsoft.com` endpoint. This is the primary endpoint used by Quick Assist to establish a session, and once blocked, Quick Assist can't be used to get help or help someone.
+
+### Uninstall Quick Assist
+
+#### Uninstall via PowerShell
+
+Run the following PowerShell command as Administrator:
+
+`Get-AppxPackage -Name MicrosoftCorporationII.QuickAssist | Remove-AppxPackage -AllUsers`
+
+#### Uninstall via Windows Settings
+
+Navigate to **Settings** > **Apps** > **Installed apps** > Quick Assist > select the ellipsis (…), then select **Uninstall**.
+
+## Report Abuse
+
+Before joining a session, it's important for you to know who you are connecting to. Anyone that has control over your device can perform actions on your device, and potentially install malicious applications or take other actions that can damage your device.
+
+Follow these best practices for using Quick Assist or any remote desktop software:
+
+- Never allow a connection to your device by someone claiming to be "IT Support" unless you initiated the interaction with them.
+- Don't provide access to anyone claiming to have an urgent need to access your device.
+- Don't share credentials to any websites or applications.
+
+> [!NOTE]
+> Microsoft will never contact you through unsolicited emails, phone calls, or other methods to request access to your device. Microsoft will only request access to your device if you have contacted us and directly requested help with solving an issue you are experiencing. If you need customer service support from Microsoft, please visit [Microsoft Support](https://support.microsoft.com/).
+
+If you suspect that the person connecting to your device is being malicious, disconnect from the session immediately and report the concern to your local authorities and/or any relevant IT members within your organization.
+
+If you or someone you know has been affected by a tech support scam, use the [technical support scam form](https://support.microsoft.com/windows/cfa4609a-92cc-4808-95e8-392b4ffd0753) to report it.
## Next steps
diff --git a/windows/client-management/client-tools/toc.yml b/windows/client-management/client-tools/toc.yml
index 115ff9afd8a..9600b605e45 100644
--- a/windows/client-management/client-tools/toc.yml
+++ b/windows/client-management/client-tools/toc.yml
@@ -1,4 +1,6 @@
items:
+ - name: Add, remove, or hide Windows features
+ href: add-remove-hide-features.md
- name: Windows Tools/Administrative Tools
href: administrative-tools-in-windows.md
- name: Use Quick Assist to help users
@@ -13,7 +15,7 @@ items:
href: manage-settings-app-with-group-policy.md
- name: Manage default media removal policy
href: change-default-removal-policy-external-storage-media.md
- - name: What version of Windows am I running
- href: windows-version-search.md
- name: Windows libraries
href: windows-libraries.md
+ - name: What version of Windows am I running
+ href: windows-version-search.md
\ No newline at end of file
diff --git a/windows/client-management/client-tools/windows-libraries.md b/windows/client-management/client-tools/windows-libraries.md
index 3486649f207..65a263719f2 100644
--- a/windows/client-management/client-tools/windows-libraries.md
+++ b/windows/client-management/client-tools/windows-libraries.md
@@ -2,13 +2,15 @@
title: Windows Libraries
description: All about Windows Libraries, which are containers for users' content, such as Documents and Pictures.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/01/2024
---
# Windows libraries
Libraries are virtual containers for users' content. A library can contain files and folders stored on the local computer or in a remote storage location. In Windows Explorer, users interact with libraries in ways similar to how they would interact with other folders. Libraries are built upon the legacy known folders (such as My Documents, My Pictures, and My Music) that users are familiar with, and these known folders are automatically included in the default libraries and set as the default save location.
+To show libraries in File Explorer, go to **Options**, select the **View** tab, and then select **Show libraries**.
+
## Features for Users
Windows libraries provide full content search and rich metadata. Libraries offer the following advantages to users:
diff --git a/windows/client-management/client-tools/windows-version-search.md b/windows/client-management/client-tools/windows-version-search.md
index 2bb838cf729..2c342661317 100644
--- a/windows/client-management/client-tools/windows-version-search.md
+++ b/windows/client-management/client-tools/windows-version-search.md
@@ -1,7 +1,7 @@
---
title: What version of Windows am I running?
description: Discover which version of Windows you're running to determine whether or not your device is enrolled in the Long-Term Servicing Channel or General Availability Channel.
-ms.date: 08/10/2023
+ms.date: 07/01/2024
ms.topic: conceptual
---
@@ -17,8 +17,6 @@ To determine if your device is enrolled in the Long-Term Servicing Channel or th
Select **Start** > **Settings** > **System**, then select **About**. You then see **Edition**, **Version**, and **OS Build** information.
-:::image type="content" source="images/systemcollage.png" alt-text="screenshot of the system properties window for a device running Windows 10.":::
-
## Using Keyword Search
You can type the following in the search bar and press **ENTER** to see version details for your device.
diff --git a/windows/client-management/config-lock.md b/windows/client-management/config-lock.md
index 30b905a41de..f497c867125 100644
--- a/windows/client-management/config-lock.md
+++ b/windows/client-management/config-lock.md
@@ -2,7 +2,7 @@
title: Secured-core configuration lock
description: A secured-core PC (SCPC) feature that prevents configuration drift from secured-core PC features caused by unintentional misconfiguration.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
appliesto:
- ✅ Windows 11
---
@@ -63,7 +63,7 @@ The steps to turn on config lock using Microsoft Intune are as follows:
Config lock is designed to ensure that a secured-core PC isn't unintentionally misconfigured. You keep the ability to enable or disable SCPC features, for example, firmware protection. You can make these changes with group policies or MDM services like Microsoft Intune.
-:::image type="content" source="images/configlock-mem-firmwareprotect.png" alt-text="The Defender Firmware protection setting, with a description of Windows Defender System Guard protects your device from compromised firmware. The setting is set to Off.":::
+:::image type="content" source="images/configlock-mem-firmwareprotect.png" alt-text="The Defender Firmware protection setting, with a description of System Guard protects your device from compromised firmware. The setting is set to Off.":::
## FAQ
diff --git a/windows/client-management/declared-configuration-extensibility.md b/windows/client-management/declared-configuration-extensibility.md
index 3121be77f06..7b1f9991f82 100644
--- a/windows/client-management/declared-configuration-extensibility.md
+++ b/windows/client-management/declared-configuration-extensibility.md
@@ -1,13 +1,13 @@
---
title: Declared configuration extensibility
description: Learn more about declared configuration extensibility through native WMI providers.
-ms.date: 09/26/2023
+ms.date: 07/08/2024
ms.topic: how-to
---
# Declared configuration extensibility providers
-The declared configuration enrollment, which supports the declared configuration client stack, offers extensibility through native WMI providers. This feature instantiates and interfaces with a Windows Management Instrumentation (WMI) provider that has implemented a management infrastructure (MI) interface. The interface must implement GetTargetResource, TestTargetResource, and SetTargetResource methods, and may implement any number of string properties.
+The declared configuration enrollment, which supports the declared configuration client stack, offers extensibility through native WMI providers. This feature instantiates and interfaces with a Windows Management Instrumentation (WMI) provider that implements a management infrastructure (MI) interface. The interface must implement GetTargetResource, TestTargetResource, and SetTargetResource methods, and can implement any number of string properties.
> [!NOTE]
> Only string properties are currently supported by extensibility providers.
@@ -51,7 +51,7 @@ uint32 SetTargetResource(
To create a native WMI provider, follow the steps outlined in [How to implement an MI provider](/previous-versions/windows/desktop/wmi_v2/how-to-implement-an-mi-provider). These steps include how to generate the source code for an MI interface using the `Convert-MofToProvider.exe` tool to generate the DLL and prepare it for placement.
-1. Create a MOF file that defines the schema for the desired state configuration resource including parameters and methods. This file includes the required parameters for the resource.
+1. Create a Managed Object Format (MOF) file that defines the schema for the desired state configuration resource including parameters and methods. This file includes the required parameters for the resource.
2. Copy the schema MOF file along with any required files into the provider tools directory, for example: ProviderGenerationTool.
3. Edit the required files and include the correct file names and class names.
4. Invoke the provider generator tool to generate the provider's project files.
diff --git a/windows/client-management/declared-configuration.md b/windows/client-management/declared-configuration.md
index f655d1ae194..e12a89b7cae 100644
--- a/windows/client-management/declared-configuration.md
+++ b/windows/client-management/declared-configuration.md
@@ -1,7 +1,7 @@
---
title: Declared configuration protocol
description: Learn more about using declared configuration protocol for desired state management of Windows devices.
-ms.date: 09/26/2023
+ms.date: 07/08/2024
ms.topic: overview
---
diff --git a/windows/client-management/device-update-management.md b/windows/client-management/device-update-management.md
index c298893a3aa..5f61783f992 100644
--- a/windows/client-management/device-update-management.md
+++ b/windows/client-management/device-update-management.md
@@ -2,7 +2,7 @@
title: Mobile device management MDM for device updates
description: Windows provides several APIs to help mobile device management (MDM) solutions manage updates. Learn how to use these APIs to implement update management.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
ms.collection:
- highpri
- tier2
@@ -25,7 +25,7 @@ In particular, Windows provides APIs to enable MDMs to:
- Enter a per-device update approval list. The list makes sure devices only install updates that are approved and tested.
- Approve end-user license agreements (EULAs) for the end user so update deployment can be automated even for updates with EULAs.
-This article provides independent software vendors (ISV) with the information they need to implement update management in Windows. For more information, see [Policy CSP - Update](mdm/policy-csp-update.md).
+This article provides independent software publishers (ISV) with the information they need to implement update management in Windows. For more information, see [Policy CSP - Update](mdm/policy-csp-update.md).
> [!NOTE]
> The OMA DM APIs for specifying update approvals and getting compliance status refer to updates by using an Update ID. The Update ID is a GUID that identifies a particular update. The MDM will want to show IT-friendly information about the update, instead of a raw GUID, including the update's title, description, KB, update type, like a security update or service pack. For more information, see [[MS-WSUSSS]: Windows Update Services: Server-Server Protocol](/openspecs/windows_protocols/ms-wsusss/f49f0c3e-a426-4b4b-b401-9aeb2892815c).
@@ -88,7 +88,7 @@ This section describes a possible algorithm for using the server-server sync pro
First some background:
-- If you have a multi-tenant MDM, the update metadata can be kept in a shared partition, since it's common to all tenants.
+- If you have a multitenant MDM, the update metadata can be kept in a shared partition, since it's common to all tenants.
- A metadata sync service can then be implemented. The service periodically calls server-server sync to pull in metadata for the updates IT cares about.
- The MDM component that uses OMA DM to control devices (described in the next section) should send the metadata sync service the list of needed updates it gets from each client, if those updates aren't already known to the device.
@@ -130,7 +130,7 @@ The following screenshots of the administrator console show the list of update t
### SyncML example
-Set auto update to notify and defer.
+Set Microsoft AutoUpdate to notify and defer.
```xml
diff --git a/windows/client-management/disconnecting-from-mdm-unenrollment.md b/windows/client-management/disconnecting-from-mdm-unenrollment.md
index 612dd076515..cfc52d7c69e 100644
--- a/windows/client-management/disconnecting-from-mdm-unenrollment.md
+++ b/windows/client-management/disconnecting-from-mdm-unenrollment.md
@@ -2,7 +2,7 @@
title: Disconnecting from the management infrastructure (unenrollment)
description: Disconnecting is initiated either locally by the user using a phone or remotely by the IT admin using management server.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Disconnecting from the management infrastructure (unenrollment)
@@ -22,14 +22,14 @@ During disconnection, the client executes the following tasks:
In Windows, after the user confirms the account deletion command and before the account is deleted, the MDM client will notify to the MDM server that the account will be removed. This notification is a best-effort action as no retry is built in to ensure the notification is successfully sent to the device.
-This action utilizes the OMA DM generic alert 1226 function to send a user an MDM unenrollment user alert to the MDM server after the device accepts the user unenrollment request, but before it deletes any enterprise data. The server should set the expectation that unenrollment may succeed or fail, and the server can check whether the device is unenrolled by either checking whether the device calls back at scheduled time or by sending a push notification to the device to see whether it responds back. If the server plans to send a push notification, it should allow for some delay to give the device the time to complete the unenrollment work.
+This action utilizes the OMA DM generic alert 1226 function to send a user an MDM unenrollment user alert to the MDM server after the device accepts the user unenrollment request, but before it deletes any enterprise data. The server should set the expectation that unenrollment can succeed or fail, and the server can check whether the device is unenrolled by either checking whether the device calls back at scheduled time or by sending a push notification to the device to see whether it responds back. If the server plans to send a push notification, it should allow for some delay to give the device the time to complete the unenrollment work.
> [!NOTE]
> The user unenrollment is an OMA DM standard. For more information about the 1226 generic alert, see the OMA Device Management Protocol specification (OMA-TS-DM\_Protocol-V1\_2\_1-20080617-A), available from the [OMA website](https://www.openmobilealliance.org/release/DM/V1_1_2-20031209-A/).
The vendor uses the Type attribute to specify what type of generic alert it is. For device initiated MDM unenrollment, the alert type is **com.microsoft:mdm.unenrollment.userrequest**.
-After the user elects to unenroll, any active MDM OMA DM sessions are terminated. After that, the DM client starts a DM session, including a user unenroll generic alert in the first package that it sends to the server.
+After the user elects to unenroll, any active MDM OMA DM sessions are terminated. After that, the DMClient starts a DM session, including a user unenroll generic alert in the first package that it sends to the server.
The following sample shows an OMA DM first package that contains a generic alert message. For more information on WP OMA DM support, see the [OMA DM protocol support](oma-dm-protocol-support.md) article.
@@ -107,15 +107,13 @@ You can only use the Work Access page to unenroll under the following conditions
- Enrollment was done using bulk enrollment.
- Enrollment was created using the Work Access page.
-
-
## Unenrollment from Microsoft Entra join
When a user is enrolled into MDM through Microsoft Entra join and later, the enrollment disconnects, there's no warning that the user will lose Windows Information Protection (WIP) data. The disconnection message doesn't indicate the loss of WIP data.
-During the process in which a device is enrolled into MDM through Microsoft Entra join and then remotely unenrolled, the device may get into a state where it must be reimaged. When devices are remotely unenrolled from MDM, the Microsoft Entra association is also removed. This safeguard is in place to avoid leaving the corporate devices in unmanaged state.
+During the process in which a device is enrolled into MDM through Microsoft Entra join and then remotely unenrolled, the device can get into a state where it must be reimaged. When devices are remotely unenrolled from MDM, the Microsoft Entra association is also removed. This safeguard is in place to avoid leaving the corporate devices in unmanaged state.
Before remotely unenrolling corporate devices, you must ensure that there is at least one admin user on the device that isn't part of Microsoft Entra ID, otherwise the device won't have any admin user after the operation.
diff --git a/windows/client-management/docfx.json b/windows/client-management/docfx.json
index 07e6f430e86..4f0356dff41 100644
--- a/windows/client-management/docfx.json
+++ b/windows/client-management/docfx.json
@@ -56,12 +56,11 @@
"folder_relative_path_in_docset": "./"
}
},
- "titleSuffix": "Windows Client Management",
"contributors_to_exclude": [
"dstrome2",
- "rjagiewich",
+ "rjagiewich",
"American-Dipper",
- "claydetels19",
+ "claydetels19",
"jborsecnik",
"v-stchambers",
"shdyas",
diff --git a/windows/client-management/enable-admx-backed-policies-in-mdm.md b/windows/client-management/enable-admx-backed-policies-in-mdm.md
index 00618845b9a..db0f36a0855 100644
--- a/windows/client-management/enable-admx-backed-policies-in-mdm.md
+++ b/windows/client-management/enable-admx-backed-policies-in-mdm.md
@@ -3,7 +3,7 @@ title: Enable ADMX policies in MDM
description: Use this step-by-step guide to configure a selected set of Group Policy administrative templates (ADMX policies) in Mobile Device Management (MDM).
ms.topic: conceptual
ms.localizationpriority: medium
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Enable ADMX policies in MDM
diff --git a/windows/client-management/enroll-a-windows-10-device-automatically-using-group-policy.md b/windows/client-management/enroll-a-windows-10-device-automatically-using-group-policy.md
index f9ccd5cc0a7..409c2838217 100644
--- a/windows/client-management/enroll-a-windows-10-device-automatically-using-group-policy.md
+++ b/windows/client-management/enroll-a-windows-10-device-automatically-using-group-policy.md
@@ -2,7 +2,7 @@
title: Enroll a Windows device automatically using Group Policy
description: Learn how to use a Group Policy to trigger autoenrollment to MDM for Active Directory (AD) domain-joined devices.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
ms.collection:
- highpri
- tier2
@@ -12,7 +12,7 @@ ms.collection:
You can use a Group Policy to trigger autoenrollment to Mobile Device Management (MDM) for Active Directory (AD) domain-joined devices.
-The enrollment into Intune is triggered by a group policy created on your local AD and happens without any user interaction. This cause-and-effect mechanism means you can automatically mass-enroll a large number of domain-joined corporate devices into Microsoft Intune. The enrollment process starts in the background once you sign in to the device with your Microsoft Entra account.
+The group policy created on your local AD triggers enrollment into Intune without any user interaction. This cause-and-effect mechanism means you can automatically mass-enroll a large number of domain-joined corporate devices into Microsoft Intune. The enrollment process starts in the background once you sign in to the device with your Microsoft Entra account.
**Requirements**:
diff --git a/windows/client-management/enterprise-app-management.md b/windows/client-management/enterprise-app-management.md
index b6e975a1c87..323376d6736 100644
--- a/windows/client-management/enterprise-app-management.md
+++ b/windows/client-management/enterprise-app-management.md
@@ -2,7 +2,7 @@
title: Enterprise app management
description: This article covers one of the key mobile device management (MDM) features for managing the lifecycle of apps across Windows devices.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Enterprise app management
@@ -116,7 +116,7 @@ There are two basic types of apps you can deploy:
- Store apps.
- Enterprise signed apps.
-To deploy enterprise signed apps, you must enable a setting on the device to allow trusted apps. The apps can be signed by a Microsoft approved root (such as Symantec), an enterprise deployed root, or apps that are self-signed. This section covers the steps to configure the device for non-store app deployment.
+To deploy enterprise signed apps, you must enable a setting on the device to allow trusted apps. The apps can be signed by a Microsoft approved root (such as Symantec), an enterprise deployed root, or apps that are self-signed. This section covers the steps to configure the device for nonstore app deployment.
### Unlock the device for non-Store apps
@@ -154,7 +154,7 @@ Here's an example:
### Unlock the device for developer mode
-Development of apps on Windows devices no longer requires a special license. You can enable debugging and deployment of non-packaged apps using [ApplicationManagement/AllowDeveloperUnlock](mdm/policy-csp-applicationmanagement.md) policy in Policy CSP.
+Development of apps on Windows devices no longer requires a special license. You can enable debugging and deployment of nonpackaged apps using [ApplicationManagement/AllowDeveloperUnlock](mdm/policy-csp-applicationmanagement.md) policy in Policy CSP.
AllowDeveloperUnlock policy enables the development mode on the device. The AllowDeveloperUnlock isn't configured by default, which means only Microsoft Store apps can be installed. If the management server explicitly sets the value to off, the setting is disabled in the settings panel on the device.
@@ -238,8 +238,8 @@ If you purchased an app from the Store for Business, the app license must be dep
In the SyncML, you need to specify the following information in the `Exec` command:
-- License ID - This ID is specified in the LocURI. The License ID for the offline license is referred to as the "Content ID" in the license file. You can retrieve this information from the Base64 encoded license download from the Store for Business.
-- License Content - This content is specified in the data section. The License Content is the Base64 encoded blob of the license.
+- License ID - This ID is specified in the LocURI. The License ID for the offline license is referred to as the "Content ID" in the license file. You can retrieve this information from the Base 64 encoded license download from the Store for Business.
+- License Content - This content is specified in the data section. The License Content is the Base 64 encoded blob of the license.
Here's an example of an offline license installation.
@@ -469,7 +469,7 @@ When an app installation is completed, a Windows notification is sent. You can a
- NOT\_INSTALLED (0) - The node was added, but the execution wasn't completed.
- INSTALLING (1) - Execution has started, but the deployment hasn't completed. If the deployment completes regardless of success, then this value is updated.
- FAILED (2) - Installation failed. The details of the error can be found under LastError and LastErrorDescription.
- - INSTALLED (3) - Once an install is successful this node is cleaned up. If the clean up action hasn't completed, then this state may briefly appear.
+ - INSTALLED (3) - Once an install is successful this node is cleaned up. If the clean-up action hasn't completed, then this state may briefly appear.
- LastError - The last error reported by the app deployment server.
- LastErrorDescription - Describes the last error reported by the app deployment server.
- Status - An integer that indicates the progress of the app installation. In cases of an HTTPS location, this status shows the estimated download progress. Status isn't available for provisioning and only used for user-based installations. For provisioning, the value is always 0.
diff --git a/windows/client-management/esim-enterprise-management.md b/windows/client-management/esim-enterprise-management.md
index 970b5917af2..2a289815913 100644
--- a/windows/client-management/esim-enterprise-management.md
+++ b/windows/client-management/esim-enterprise-management.md
@@ -3,7 +3,7 @@ title: eSIM Enterprise Management
description: Learn how Mobile Device Management (MDM) Providers support the eSIM Profile Management Solution on Windows.
ms.localizationpriority: medium
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# How Mobile Device Management Providers support eSIM Management on Windows
@@ -28,7 +28,7 @@ If you're a Mobile Device Management (MDM) Provider and want to support eSIM Man
- Assess solution type that you would like to provide your customers
- Batch/offline solution
- IT Admin can manually import a flat file containing list of eSIM activation codes, and provision eSIM on LTE enabled devices.
-- Operator doesn't have visibility over status of the eSIM profiles and device eSIM has been downloaded and installed to
+- Operator doesn't have visibility over status of the eSIM profiles
- Real-time solution
- MDM automatically syncs with the Operator backend system for subscription pool and eSIM management, via SIM vendor solution component. IT Admin can view subscription pool and provision eSIM in real time.
- Operator is notified of the status of each eSIM profile and has visibility on which devices are being used
diff --git a/windows/client-management/federated-authentication-device-enrollment.md b/windows/client-management/federated-authentication-device-enrollment.md
index ecb42e81608..32b2fef7ef6 100644
--- a/windows/client-management/federated-authentication-device-enrollment.md
+++ b/windows/client-management/federated-authentication-device-enrollment.md
@@ -2,7 +2,7 @@
title: Federated authentication device enrollment
description: This section provides an example of the mobile device enrollment protocol using federated authentication policy.
ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 07/08/2024
---
# Federated authentication device enrollment
@@ -122,7 +122,7 @@ The discovery response is in the XML format and includes the following fields:
> [!NOTE]
> The HTTP server response must not set Transfer-Encoding to Chunked; it must be sent as one message.
-When authentication policy is set to be Federated, Web Authentication Broker (WAB) is used by the enrollment client to get a security token. The WAB start page URL is provided by the discovery service in the response message. The enrollment client calls the WAB API within the response message to start the WAB process. WAB pages are server hosted web pages. The server should build those pages to fit the device screen nicely and be as consistent as possible to other builds in the MDM enrollment UI. The opaque security token that is returned from WAB as an endpage is used by the enrollment client as the device security secret during the client certificate enrollment request call.
+When authentication policy is set to be Federated, Web Authentication Broker (WAB) is used by the enrollment client to get a security token. The WAB start page URL is provided by the discovery service in the response message. The enrollment client calls the WAB API within the response message to start the WAB process. WAB pages are server hosted web pages. The server should build those pages to fit the device screen nicely and be as consistent as possible to other builds in the MDM enrollment UI. The opaque security token that is returned from WAB as an end page is used by the enrollment client as the device security secret during the client certificate enrollment request call.
> [!NOTE]
> Instead of relying on the user agent string that is passed during authentication to get information, such as the OS version, use the following guidance:
@@ -183,7 +183,7 @@ Content-Length: 556