Merge pull request #7312 from MicrosoftDocs/main

Release CM2203CB to live (ignoring preserving view warnings at the moment)

Author: mestew

memdocs/configmgr/apps/deploy-use/deploy-edge.md

@@ -100,6 +100,8 @@ Starting in Configuration Manager 2002, the Microsoft Edge Management dashboard
 
 ### Prerequisites for the dashboard
 
+For Configuration Manager version 2203 or later, the [WebView2 console extension](../../core/servers/manage/admin-console-extensions.md#bkmk_notification) must be installed. If needed, select the notification bell in the top right corner of the console to install the extension.<!--10024154-->
+
 Enable the following properties in the below [hardware inventory](../../core/clients/manage/inventory/extend-hardware-inventory.md) classes for the Microsoft Edge Management dashboard:
 
 - **Installed Software - Asset Intelligence (SMS_InstalledSoftware)**
@@ -114,6 +116,8 @@ Enable the following properties in the below [hardware inventory](../../core/cli
    - BrowserName
    - UsagePercentage
 
+
+
 ### View the dashboard
 
 From the **Software Library** workspace, click **Microsoft Edge Management** to see the dashboard. Change the collection for the graph data by clicking **Browse** and choosing another collection. By default your five largest collections are in the drop-down list. When you select a collection that isn't in the list, the newly selected collection takes the bottom spot on your drop-down list.

memdocs/configmgr/apps/deploy-use/media/7079837-deployment-status-client-notification.png

@@ -2,7 +2,7 @@
 title: Monitor applications from the console
 titleSuffix: Configuration Manager
 description: Monitor deployment applications with the Monitoring workspace in Configuration Manager.
-ms.date: 04/05/2021
+ms.date: 04/08/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-app
 ms.topic: how-to
@@ -60,27 +60,29 @@ For more information about how to configure reporting in Configuration Manager,
 
 1. In the Configuration Manager console, go to the **Monitoring** workspace, and select the **Deployments** node.
 
-    > [!TIP]
-    > If your site has a lot of deployments, filter the list to just application deployments.
-    >
-    > 1. At the top of the list next to the _Search_ field, select **Add Criteria**. Choose **Feature Type** and then select **Add**.
-    > 1. The search area adds the default criteria, **AND Feature Type Content Distribution**. Select **Content Distribution** and choose **Application** instead.
-    > 1. Select **Search** to refresh the list.
+   If your site has numerous deployments, filter the list to just application deployments.
+   1. At the top of the list next to the *Search* field, select **Add Criteria**. Choose **Feature Type** and then select **Add**.
+   1. The search area adds the default criteria, **AND Feature Type Content Distribution**. Select **Content Distribution** and choose **Application** instead.
+   1. Select **Search** to refresh the list.
 
 1. Select a deployment for the app to monitor.
 
-:::image type="content" source="media/monitor-app-deployments.png" alt-text="Screenshot of the Monitoring workspace, Deployments node, filtered to applications" lightbox="media/monitor-app-deployments.png":::
+   :::image type="content" source="media/monitor-app-deployments.png" alt-text="Screenshot of the Monitoring workspace, Deployments node, filtered to applications" lightbox="media/monitor-app-deployments.png":::
 
-- To review general status information about an application deployment, see the **Summary** tab in the details pane.
+The following two tabs in the details pane are populated for the selected deployment:
 
-- To review status for the application's deployment types, switch to the **Deployment Types** tab in the details pane.
+- **Summary**: Displays general status information about an application deployment.
+- **Deployment Types**: Displays status for the application's deployment types.
 
-- To review deployment details for each compliance state and the resources in that state, select **View status** on the **Home** tab of the ribbon. This action opens the **Deployment Status** pane. Here you can view the assets in each compliance state. To view more detailed information about the deployment status to an asset, select it in the Asset Details list. Then select **More Details** on the right side of the window.
+### Review deployment details
 
-    > [!NOTE]
-    > The maximum number of items that the **Deployment Status** pane can display is 20,000. If you need to see more items, use Configuration Manager reports to view application status data.
-    >
-    > The status of deployment types is aggregated in the **Deployment Status** pane. To view more detailed information about the deployment types, use the **Application Infrastructure Errors** report.
+From the **Deployments** node, you can review deployment details for each compliance state and the resources in that state. To review the deployment details, select **View status** on the **Home** tab of the ribbon. This action opens the **Deployment Status** pane. Here you can review the assets in each compliance state. To display Details list. Then select **More Details** on the right side of the window.
+
+- The maximum number of items that the **Deployment Status** pane can display is 20,000. If you need to see more items, use Configuration Manager reports to review application status data.
+- The status of deployment types is aggregated in the **Deployment Status** pane. To display more detailed information about the deployment types, use the **Application Infrastructure Errors** report.
+- Starting in version 2203, you can perform client notification actions, including **Run Scripts**, from the **Deployment Status** view. Use the right-click menu on either a group of clients in a **Category** or a single client in the **Asset details** pane to display the client notification actions. <!--7079837-->
+
+   :::image type="content" source="./media/7079837-deployment-status-client-notification.png" alt-text="Screenshot of the Deployment Status view showing the client notification actions. " lightbox="./media/7079837-deployment-status-client-notification.png":::
 
 ### Summarized data
 

memdocs/configmgr/apps/deploy-use/monitor-applications-from-the-console.md

@@ -2,7 +2,7 @@
 title: Packages and programs
 titleSuffix: Configuration Manager
 description: Support deployments that use legacy packages and programs with Configuration Manager.
-ms.date: 11/30/2020
+ms.date: 04/08/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-app
 ms.topic: conceptual
@@ -64,16 +64,40 @@ Packages can use some new features of Configuration Manager, including distribut
         >
         > Windows limits the source path to 256 characters or less. This limit applies to package source as well as applications. For more information, see [Naming Files, Paths, and Namespaces](/windows/win32/fileio/naming-a-file).
 
-    - Starting in version 1906, if you want to pre-cache content on a client, specify the **Architecture** and **Language** of the package. For more information, see [Configure pre-cache content](../../osd/deploy-use/configure-precache-content.md).<!--4224642-->  
+    - If you want to pre-cache content on a client, specify the **Architecture** and **Language** of the package. For more information, see [Configure pre-cache content](../../osd/deploy-use/configure-precache-content.md).<!--4224642-->  
 
-4. On the **Program Type** page of the **Create Package and Program Wizard**, select the type of program to create, and then choose **Next**. You can create a program for a [computer](#create-a-standard-program) or [device](#create-a-device-program), or you can skip this step and create a program later.  
+4. On the **Program Type** page of the **Create Package and Program Wizard**, select the **Standard** program type for computers. Or you can skip this step and create a program later.
 
-    > [!TIP]  
-    > To create a new program for an existing package, first select the package. Then, in the **Home** tab, in the **Package** group, choose **Create Program** to open the **Create Program Wizard**.  
+    > [!TIP]
+    > To create a new program for an existing package, first select the package. Then, in the **Home** tab, in the **Package** group, choose **Create Program** to open the **Create Program Wizard**.
+    >
+    > The **Program for device** type is a legacy option that only applies to mobile devices, which aren't currently managed by Configuration Manager.
 
-#### Create a standard program
+#### Custom icons for packages
 
-1. On the **Program Type** page of the **Create Package and Program Wizard**, choose **Standard Program**, and then choose **Next**.  
+<!--12486335-->
+
+Starting in version 2203, add custom icons for packages. These icons appear in Software Center when you deploy the package and program. Instead of a default icon, a custom icon can improve the user experience to better identify the software.
+
+On the **General** tab of package properties, in the section for the icon, select **Browse**. Select an icon from the default shell library, or browse to another file in a local or network path.
+
+- It supports the following file types:
+  - Programs (`.exe`)
+  - Libraries (`.dll`)
+  - Icons (`.ico`)
+  - Images (`.png`, `.jpeg`, `.jpg`)
+- The file doesn't need to be on clients that you target with the deployment. Configuration Manager includes the image with the deployment policy.
+- The maximum file size for an image is 256 KB.
+- Icons can have pixel dimensions of up to 512 x 512.
+
+When clients receive the deployment policy, they'll display the icon in Software Center.
+
+> [!NOTE]
+> To take full advantage of new Configuration Manager features, after you update the site, also update clients to the latest version. While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn't functional until the client version is also the latest.
+
+### Create a program
+
+1. On the **Program Type** page of the **Create Package and Program Wizard**, choose **Standard Program**, and then choose **Next**.
 
 2. On the **Standard Program** page, specify the following information:  
 
@@ -146,35 +170,6 @@ Packages can use some new features of Configuration Manager, including distribut
         > - You enable the option to **Run with administrative rights**
         > - You don't enable the option to **Allow users to view and interact with the program installation**  
 
-#### Create a device program  
-
-1. On the **Program Type** page of the **Create Package and Program Wizard**, select **Program for device**, and then choose **Next**.  
-
-2. On the **Program for Device** page, specify the following settings:  
-
-    - **Name**: Specify a name for the program with a maximum of 50 characters.  
-
-        > [!NOTE]  
-        > The program name must be unique within a package. After you create a program, you can't modify its name.  
-
-    - **Comment** (optional): Specify a comment for this device program with a maximum of 127 characters.  
-
-    - **Download folder**: Specify the name of the folder on the device in which it will store the package source files. The default value is `\Temp\`.  
-
-    - **Command Line**: Enter the command line to use to start this program. To browse to the file location, choose **Browse**.  
-
-    - **Run command line in download folder**: Select this option to run the program from the download folder.  
-
-    - **Run command line from this folder**: Select this option to specify a different folder from which to run the program.  
-
-3. On the **Requirements** page, specify the following settings:  
-
-    - **Estimated disk space**: Specify the amount of disk space that's required for the software. The client displays this value to mobile device users before they install the program.  
-
-    - **Download program**: Specify information about when the mobile device can download this program. You can specify **As soon as possible**, **Only over a fast network**, or **Only when the device is docked**.  
-
-    - **Additional requirements**: Specify any additional requirements for this program. Users see these requirements before they install the software. For example, you could notify users that they need to close all other applications before running the program.  
-
 ## Deploy packages and programs  
 
 1. In the Configuration Manager console, go to the **Software Library** workspace, expand **Application Management**, and select the **Packages** node.  
@@ -249,7 +244,7 @@ View the deployment in the **Deployments** node of the **Monitoring** workspace
 
 To monitor package and program deployments, use the same procedures that you use to monitor applications as detailed in [Monitor applications](monitor-applications-from-the-console.md).  
 
-Packages and programs also include a number of built-in reports, which enable you to monitor information about the deployment status of packages and programs. These reports have the report category of **Software Distribution – Packages and Programs** and **Software Distribution – Package and Program Deployment Status**.  
+Packages and programs also include a number of built-in reports, which enable you to monitor information about the deployment status of packages and programs. These reports have the report category of **Software Distribution - Packages and Programs** and **Software Distribution - Package and Program Deployment Status**.  
 
 For more information about how to configure reporting in Configuration Manager, see [Introduction to reporting](../../core/servers/manage/introduction-to-reporting.md).  
 
@@ -283,7 +278,7 @@ Opens the **Distribute Content Wizard**, to send the content for a package and p
 Opens the **Import Package Wizard**, to import a previously exported package from a .zip file.
 
 > [!TIP]
-> Starting in version 2010, when you import an object in the Configuration Manager console, it now imports to the current folder. Previously, Configuration Manager always put imported objects in the root node.<!--6601203-->
+> When you import an object in the Configuration Manager console, it imports to the current folder. In earlier versions, Configuration Manager always put imported objects in the root node.<!--6601203-->
 
 ### Update distribution points
 

memdocs/configmgr/apps/deploy-use/packages-and-programs.md

@@ -2,7 +2,7 @@
 title: Uninstall applications
 titleSuffix: Configuration Manager
 description: Uninstall an application by using Configuration Manager
-ms.date: 12/01/2021
+ms.date: 04/08/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-app
 ms.topic: how-to
@@ -85,6 +85,8 @@ Starting in version 2111, this behavior also supports [application groups](creat
 > [!NOTE]
 > In version 2111 and later, this behavior applies to deployments to device or user collections.<!--10393847--> In version 2107, this behavior only applies to deployments to device collections.
 
+Starting in version 2203, if you deploy an application or app group to a user collection that's based on a security group, and you enable implicit uninstall, changes to the security group are now honored. When the site discovers the change in group membership, Configuration Manager uninstalls the app for the user that you removed from the security group.<!--12488148-->
+
 ### Enable implicit uninstall
 
 When you [deploy the application](deploy-applications.md) to a collection, configure the following settings on the **Deployment Settings** page:
@@ -93,14 +95,14 @@ When you [deploy the application](deploy-applications.md) to a collection, confi
 
 - **Purpose**: Required
 
-- Enable the option to **Uninstall this application if the targeted object falls out of the collection**
-   - In version 2111, this option was renamed to **When a resource is no longer a member of the collection, uninstall the application**
+- Enable the following option: **When a resource is no longer a member of the collection, uninstall the application**
+
+    > [!TIP]
+    > In version 2107, this option is named: **Uninstall this application if the targeted object falls out of the collection**
 
-   
 > [!IMPORTANT]
 > Be careful with enabling this option on deployments to large query-based collections. Especially queries to external sources like Active Directory groups. An unexpected external change could automatically trigger a large number of devices to uninstall the application.
 
-
 ### Implicit uninstall process
 
 After you remove the resource from the collection, the following process happens:
@@ -115,7 +117,7 @@ Depending upon the timing of those steps, the longest time period for the client
 
 > [!NOTE]
 > - For this behavior, the site can process up to 1000 collection membership changes every 10 minutes.
-> - If the uninstall doesn't occur, it's likely that there's a conflicting install deployment of the same application, application group, or a different application group with the same apps. <!--12618105-->
+> - If the uninstall doesn't occur, it's likely that there's a conflicting install deployment of the same application, application group, or a different application group with the same apps.<!--12618105--> Configuration Manager always honors an install deployment over an uninstall deployment.
 
 ### Known issues