Merge pull request #7979 from MicrosoftDocs/main

Publish 07/11/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/configmgr/sum/deploy-use/monitor-orchestration-groups.md

@@ -2,7 +2,7 @@
 title: Monitor orchestration groups
 titleSuffix: Configuration Manager
 description: Monitor and reset orchestration groups.
-ms.date: 12/01/2021
+ms.date: 07/11/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-sum
 ms.topic: conceptual
@@ -37,6 +37,8 @@ From the **Assets and Compliance** workspace, select the **Orchestration Group**
 - **Orchestration Group Member Timeout (in minutes)**: Value of **Orchestration Group member timeout (in minutes)** set on the **General** page when creating the group, or the **General** tab when editing the group.
 - **Orchestration Group ID**: ID of the group, The ID is used in logs and the database.
 - **Orchestration Group Unique ID**: Unique ID of the group, The Unique ID is used in logs and the database.
+- **Last Modified Time**: The time the orchestration group was last modified (starting in version 2203). <!--12500680, 12976470-->
+- **Last Modified By**: The user that last modified the orchestration group (starting in version 2203). <!--12500680, 12976470-->
 
 ## Orchestration groups details tabs
 

memdocs/configmgr/tenant-attach/app-install-error-reference.md

@@ -2,7 +2,7 @@
 title: Application installation error codes reference
 titleSuffix: Configuration Manager
 description: Reference Application installation errors for tenant attach
-ms.date: 10/05/2021
+ms.date: 07/11/2022
 ms.topic: reference
 ms.prod: configuration-manager
 ms.technology: configmgr-core
@@ -18,7 +18,7 @@ Applications can be installed on clients by creating deployments from the Config
 
 ## <a name="bkmk_general"></a> General troubleshooting tips
 
-Generally, if an application installs successfully on a device with the given command line in the system context, it will install successfully through Configuration Manager and from the Microsoft Endpoint Manager admin center. You can simulate this by using [PSExec](/sysinternals/downloads/psexec). If you're running Configuration Manager version 2002 or version 2006 and the application is targeted to the system and configured to run in user context, a retry may not trigger a reinstall or another attempt to install.
+Generally, if an application installs successfully on a device with the given command line in the system context, it will install successfully through Configuration Manager and from the Microsoft Endpoint Manager admin center. You can simulate this by using [PSExec](/sysinternals/downloads/psexec). 
 
 1. Open an administrative command prompt.
 1. Change directory to where you saved [PSExec](/sysinternals/downloads/psexec).

memdocs/configmgr/tenant-attach/applications.md

@@ -2,7 +2,7 @@
 title: Tenant attach - Applications in the admin center
 titleSuffix: Configuration Manager
 description: Install applications for uploaded Configuration Manager devices from the admin center.
-ms.date: 01/25/2022
+ms.date: 07/11/2022
 ms.topic: conceptual
 ms.prod: configuration-manager
 ms.technology: configmgr-core
@@ -25,23 +25,12 @@ Microsoft Endpoint Manager is an integrated solution for managing all of your de
 
 ## Prerequisites
 
-For Configuration Manager versions 2103, or later:
-
 - All of the prerequisites for [Tenant attach: ConfigMgr client details](client-details.md#prerequisites).
 - An application that meets one of the following requirements: <!--8795301-->
    - Is deployed to the device
    - Is deployed to a user that's logged in to the device, primary user of the device, and applications previously installed for the user
      - When you have a large number of device available applications, using the **An administrator must approve a request for this application on the device** on application deployments is recommended. For more information, see [Display all applications for a device in the admin center](#bkmk_all).
 
-For Configuration Manager versions 2010, and earlier:
-
-- All of the prerequisites for [Tenant attach: ConfigMgr client details](client-details.md#prerequisites)
-- A minimum of [Update Rollup for Microsoft Endpoint Configuration Manager version 2002](https://support.microsoft.com/help/4560496/)
-- Enable the optional feature **Approve application requests for users per device**. For more information, see [Enable optional features from updates](../core/servers/manage/optional-features.md).
-- At least one application deployed to a device collection with the **An administrator must approve a request for this application on the device** option set on the deployment. For more information, see [Approve applications](../apps/deploy-use/app-approval.md#bkmk_opt).
-   - User targeted applications or applications without the approval option set don't appear in the application list when you're using Configuration Manager version 2002.
-- A minimum of Configuration Manager version 2006 is required for installing [user targeted applications](#bkmk_user)<!--7518897-->.
-
 ## Permissions
 
 The user account needs the following permissions:
@@ -64,8 +53,8 @@ You can filter the application list based on the status. The application status
 - **Failed**: The application installation failed.
 - **Requirements not met**: The application requirements haven't been met.
 - **Not installed**: The application isn't currently installed. Typically this status is seen if a different deployment or a user removed the application.
-- **Restart pending**: The application is installed but needs a restart to complete (starting in version 2006).
-- **Required**: Installation is required for the application (starting in version 2103)
+- **Restart pending**: The application is installed but needs a restart to complete.
+- **Required**: Installation is required for the application
 
 ## <a name="bkmk_deploy"></a> Deploy an application to a device
 
@@ -79,9 +68,8 @@ You can export all of the data currently in the view into a .csv file. At the to
 
 ## <a name="bkmk_user"></a> Deploy an application to a user
 <!--7518897-->
-*(Introduced in version 2006)*
 
-Starting in Configuration Manager version 2006, user available applications appear in the **Applications** node for a ConfigMgr device. The list of applications available for the device also includes applications deployed to the device's currently logged on user.
+User available applications appear in the **Applications** node for a ConfigMgr device. The list of applications available for the device also includes applications deployed to the device's currently logged on user.
 
 Deploying applications to a user has the following limitations:
 - Multi-user session scenarios aren't supported.
@@ -90,9 +78,9 @@ Deploying applications to a user has the following limitations:
 
 ## <a name="bkmk_repair"></a> Uninstall, repair, re-evaluate, or reinstall an application
 <!--7979972, 8227649-->
-*(Introduced in version 2010)*
 
- Starting in Configuration manager version 2010, administrators can do the following actions for applications in the Microsoft Endpoint Manager admin center:
+
+Administrators can do the following actions for applications in the Microsoft Endpoint Manager admin center:
 
 - **Uninstall** an application
 - **Repair** installation of an application
@@ -127,9 +115,8 @@ Deploying applications to a user has the following limitations:
 
 ## <a name="bkmk_all"></a> Display all applications for a device in the admin center
 <!--8795301-->
-*(Introduced in version 2103)*
 
-Starting in Configuration Manager 2103, the **Applications** view for a tenant attached device in Microsoft Endpoint Manager admin center displays more applications from Configuration Manager. This improvement allows you to review when application installations are expected to occur on a device. Displayed applications include applications that are:
+The **Applications** view for a tenant attached device in Microsoft Endpoint Manager admin center displays more applications from Configuration Manager. This improvement allows you to review when application installations are expected to occur on a device. Displayed applications include applications that are:
 - Deployed to the device
 - Deployed to a user that's logged in to the device, primary user of the device, or was previously installed.
 
@@ -150,8 +137,6 @@ The displayed application and available actions are dependent on the version of
 
 |Configuration Manager version|Applications displayed|Available actions|
 |---|---|---|
-|Configuration Manager version 2002 with devices running any client version| Device-available applications with the **An administrator must approve a request for this application on the device** option set on the deployment.| Install </br> Reinstall|
-|Configuration Manager version 2006 with devices running any client version| Device-available applications with the **An administrator must approve a request for this application on the device** option set on the deployment. </br> </br> All user-available applications| Install </br> Reinstall|
 |Configuration Manager version 2010 with devices running client versions before 2010| Device-available applications with the **An administrator must approve a request for this application on the device** option set on the deployment. </br> </br> All user-available applications| Install </br> Reinstall|
 |Configuration Manager version 2010 with devices running 2010 client versions| Device-available applications with the **An administrator must approve a request for this application on the device** option set on the deployment. </br> </br> All user-available applications|Install </br> Reinstall </br> Re-evaluate </br> Uninstall </br> Repair|
 |Configuration Manager version 2103 with devices running 2006 or earlier client versions| All applications targeted to the device </br> </br> All user targeted applications related to the device. For example, applications targeted to the logged in user, primary user, and applications previously installed for the user are displayed.| For user and device-available applications with the **An administrator must approve a request for this application on the device** option set on the deployment: </br>&nbsp;&nbsp;&nbsp;Install</br>&nbsp;&nbsp;&nbsp;Reinstall</br></br>  All other applications display status but no actions are available |

memdocs/configmgr/tenant-attach/client-details.md

@@ -2,7 +2,7 @@
 title: Tenant attach - ConfigMgr client details in the admin center
 titleSuffix: Configuration Manager
 description: View client details for Configuration Manager devices from the admin center.
-ms.date: 01/25/2022
+ms.date: 07/11/2022
 ms.topic: conceptual
 ms.prod: configuration-manager
 ms.technology: configmgr-core
@@ -29,8 +29,7 @@ Microsoft Endpoint Manager is an integrated solution for managing all of your de
    - The user account needs to be a synced user object in Azure AD (hybrid identity). This means that the user is synced to Azure Active Directory from Active Directory.
      - For Configuration Manager version 2103, and later: </br>
    Has been discovered with either [Azure Active Directory user discovery](../core/servers/deploy/configure/about-discovery-methods.md#azureaddisc) or [Active Directory user discovery](../core/servers/deploy/configure/about-discovery-methods.md#bkmk_aboutUser). <!--9089764-->
-     - For Configuration Manager version 2010, and earlier: </br>
-   Has been discovered with both [Azure Active Directory user discovery](../core/servers/deploy/configure/about-discovery-methods.md#azureaddisc) and [Active Directory user discovery](../core/servers/deploy/configure/about-discovery-methods.md#bkmk_aboutUser).
+
 ## Permissions
 
 The user account accessing tenant attach features within the Microsoft Endpoint Manager admin center needs the following permissions:
@@ -57,15 +56,15 @@ The user account accessing tenant attach features within the Microsoft Endpoint
 
 ## <a name="bkmk_list"></a> List a user’s devices based on usage in the troubleshooting portal
 <!--6974300-->
-*(Introduced in version 2010)*
 
-The troubleshooting portal in [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/) allows you to search for a user and view their associated devices. Starting in Configuration Manager version 2010, tenant attached devices that are assigned [user device affinity automatically based on usage](../apps/deploy-use/link-users-and-devices-with-user-device-affinity.md#set-up-the-site-to-automatically-create-user-device-affinities) will now be returned when searching for a user.
+The troubleshooting portal in [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/) allows you to search for a user and view their associated devices. Tenant attached devices that are assigned [user device affinity automatically based on usage](../apps/deploy-use/link-users-and-devices-with-user-device-affinity.md#set-up-the-site-to-automatically-create-user-device-affinities) will now be returned when searching for a user.
 ### Prerequisites for listing a user's device in the troubleshooting portal
 
 - An environment that's tenant attached with uploaded devices
 - Install the latest version of the Configuration Manager client
 - Target clients with **User and Device Affinity** [client settings](../core/clients/deploy/about-client-settings.md#user-and-device-affinity) to automatically create the affinities
    - For more information, see [Create user device affinity automatically based on usage](../apps/deploy-use/link-users-and-devices-with-user-device-affinity.md#set-up-the-site-to-automatically-create-user-device-affinities).
+   - 
 ### View a user's devices
 
 1. Go to the  [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).

memdocs/configmgr/tenant-attach/cmpivot-start.md

@@ -2,7 +2,7 @@
 title: Launch tenant attached CMPivot
 titleSuffix: Configuration Manager
 description: Launch CMPivot for Microsoft Endpoint Manager tenant attached devices.
-ms.date: 12/03/2020
+ms.date: 07/11/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -24,7 +24,6 @@ Bring the power of on-premises [CMPivot](../core/servers/manage/cmpivot.md) to t
 The following items are required to use CMPivot from the admin center:
 
 - All of the prerequisites for [Tenant attach: ConfigMgr client details](client-details.md)
-- A minimum of Configuration Manager version 2002 with the [Update Rollup](https://support.microsoft.com/help/4560496/) and the corresponding version of the console installed.
 - Upgrade the target devices to the latest version of the Configuration Manager client.  
 - Target clients require a minimum of PowerShell version 4.
 - To gather data for the following entities, target clients require a minimum of PowerShell version 5.0:  

memdocs/configmgr/tenant-attach/device-sync-actions.md

@@ -2,7 +2,7 @@
 title: Enable Microsoft Endpoint Manager tenant attach
 titleSuffix: Configuration Manager
 description: Upload your Configuration Manager devices to the cloud service and take actions from the admin center.
-ms.date: 07/01/2022
+ms.date: 07/11/2022
 ms.topic: conceptual
 ms.prod: configuration-manager
 ms.technology: configmgr-core
@@ -30,7 +30,7 @@ When co-management is already enabled, edit the co-management properties to enab
 1. In the ribbon, select **Properties** for your co-management production policy.
 1. In the **Configure upload** tab, select **Upload to Microsoft Endpoint Manager admin center**. Select **Apply**.
    - The default setting for device upload is **All my devices managed by Microsoft Endpoint Configuration Manager**. If needed, you can limit upload to a single device collection.
-   - Starting in Configuration Manager version 2010, when a single collection is selected, its child collections are also uploaded.
+   - When a single collection is selected, its child collections are also uploaded.
 1. Check the option to **Enable Endpoint analytics for devices uploaded to Microsoft Endpoint Manager** if you also want to get insights for optimizing the end-user experience in [Endpoint Analytics](../../analytics/overview.md).
 
 > [!Important]
@@ -62,9 +62,9 @@ When co-management isn't enabled, use the instructions below to enable device up
 
    [![Co-management Configuration Wizard](./media/3555758-comanagement-wizard.png)](./media/3555758-comanagement-wizard.png#lightbox)
 1. Choose **Next** and then **Yes** to accept the **Create AAD Application** notification. This action provisions a service principal and creates an Azure AD application registration to facilitate the sync.
-     - Optionally, you can import a previously created Azure AD application during tenant attach onboarding (starting in version 2006). For more information, see the [Import a previously created Azure AD application](#bkmk_aad_app) section.
+     - Optionally, you can import a previously created Azure AD application during tenant attach onboarding. For more information, see the [Import a previously created Azure AD application](#bkmk_aad_app) section.
 1. On the **Configure upload** page, select the recommended device upload setting for **All my devices managed by Microsoft Endpoint Configuration Manager**. If needed, you can limit upload to a single device collection.
-    - Starting in Configuration Manager version 2010, when a single collection is selected, its child collections are also uploaded. <!--8717629-->
+    - When a single collection is selected, its child collections are also uploaded. <!--8717629-->
 1. Check the option to **Enable Endpoint analytics for devices uploaded to Microsoft Endpoint Manager** if you also want to get insights to optimize the end-user experience in [Endpoint Analytics](../../analytics/overview.md).
 1. Select **Summary** to review your selection, then choose **Next**.
 1. When the wizard is complete, select **Close**.  
@@ -95,9 +95,6 @@ From the Microsoft Endpoint Manager admin center, you can review the status of y
 
 :::image type="content" source="media/7138634-connector-status.png" alt-text="Microsoft Endpoint Configuration Manager connector in the admin center" lightbox="media/7138634-connector-status.png":::
 
-> [!NOTE]
-> Some information isn't available if the hierarchy is running Configuration Manager version 2006 or earlier.
-
 ## <a name="bkmk_offboard"></a> Offboard from tenant attach
 
 While we know customers get enormous value by enabling tenant attach, there are rare cases where you might need to offboard a hierarchy. You can offboard from either the Configuration Manager console (recommend method) or from the Microsoft Endpoint Manager admin center.
@@ -119,7 +116,7 @@ If needed, you can offboard a Configuration Manager hierarchy from the Microsoft
 1. Select **Tenant administration** then **Connectors and tokens**.
 1. Select **Microsoft Endpoint Configuration Manager**.
 1. Choose the name of the site you would like to offboard, then select **Delete**.
-   - The connector may be listed as **Unknown** for version 2002 sites or if site information is lacking. <!--10569820, 10944009-->
+   - The connector may be listed as **Unknown** if the site information is lacking. <!--10569820, 10944009-->
 
 When you offboard a hierarchy from the admin center, it may take up to two hours to remove from the Microsoft Endpoint Manager admin center. If you offboard a Configuration Manager 2103 or later site that's online and healthy, the process may only take a few minutes.
 

memdocs/configmgr/tenant-attach/includes/configmgr-endpoint-security-prerequisties.md

@@ -4,7 +4,7 @@ ms.author: mstewart
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: include
-ms.date: 05/18/2021
+ms.date: 07/17/2022
 ms.localizationpriority: high
 ---
 
@@ -14,7 +14,7 @@ ms.localizationpriority: high
 
 - Access to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
 - An environment that's [tenant attached with uploaded devices](../device-sync-actions.md).
-- A minimum of Configuration Manager version 2006 and the corresponding version of the console installed.
+- A supported version of Configuration Manager and the corresponding version of the console installed.
    - Upgrade the target devices to the latest version of the Configuration Manager client.
 - At least one Configuration Manager collection that's [available for assigning Endpoint security policies](../endpoint-security-get-started.md#bkmk_collections)
 - Windows Devices that [support this profile for tenant attached devices](../endpoint-security-get-started.md#bkmk_supportedprofiles)