Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into 9295335-disable-udp-for-tunnel

Author: Brenduns

memdocs/autopilot/existing-devices.md

@@ -258,7 +258,7 @@ After you save the file, move it to a location for a Microsoft Endpoint Configur
     - _Limiting collection_: **All Systems**
 
       > [!NOTE]
-      > You can optionally choose to use an alternative collection for the limiting collection. The device to be upgraded must be running the Configuration Manaber client in the collection that you select.
+      > You can optionally choose to use an alternative collection for the limiting collection. The device to be upgraded must be running the Configuration Manager client in the collection that you select.
 
 1. On the **Membership Rules** page, select **Add Rule**. Specify either a direct or query-based collection rule to add the target Windows 8.1 devices to the new collection.
 

memdocs/autopilot/oem-registration.md

@@ -1,13 +1,8 @@
 ---
 title: Windows Autopilot OEM registration process
 description: How OEMs add devices to Windows Autopilot
-keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
 ms.prod: w10
-ms.mktglfcycl: deploy
 ms.localizationpriority: medium
-ms.sitesec: library
-ms.pagetype: deploy
-audience: itpro
 author: aczechowski
 ms.author: aaroncz
 ms.reviewer: jubaptis
@@ -36,6 +31,10 @@ When you purchase devices from an OEM, that OEM can automatically register the d
 
 OEMs must follow [device guidelines](autopilot-device-guidelines.md) for Windows Autopilot devices.
 
+### Service data
+
+Windows Autopilot is managed and maintained by Microsoft. This service provides the backend database that associates hardware hashes with customer tenants. When an OEM registers devices for a customer, they are writing that data to this database and not directly to the customer's tenant. No permissions to the customer's tenant are granted or required for OEMs to register devices on the customer's behalf.
+
 ### Customer consent
 
 Before an OEM can register devices for an organization, the organization must grant the OEM permission to do so. The OEM begins this process with approval granted by an Azure AD global administrator from your organization. For more information see [OEM authorization](registration-auth.md#oem-authorization).

memdocs/configmgr/core/clients/manage/cmg/plan-cloud-management-gateway.md

@@ -157,6 +157,8 @@ With a few exceptions, the configuration, operation, and functionality of the CM
 
 - A [**server authentication certificate**](server-auth-cert.md) for the CMG.
 
+- CMG names need to be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. <!--13222041-->
+
 - **Other certificates** may be required, depending upon your client OS version and authentication model. For more information, see [Configure client authentication](configure-authentication.md).
 
 - Clients must use **IPv4**.

memdocs/configmgr/core/clients/manage/cmg/supported-configurations.md

@@ -2,7 +2,7 @@
 title: Supported configurations for CMG
 titleSuffix: Configuration Manager
 description: A list of the features and configurations that the Configuration Manager cloud management gateway supports.
-ms.date: 04/08/2022
+ms.date: 07/12/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-client
 ms.topic: reference
@@ -30,6 +30,8 @@ Use this article as a reference for the features and configurations that are sup
 
 - Starting in version 2203, the option to deploy a CMG as a **cloud service (classic)** is removed.<!-- 13235079 --> All CMG deployments should use a [virtual machine scale set](plan-cloud-management-gateway.md#virtual-machine-scale-sets).<!--10966586--> For more information, see [Removed and deprecated features](../../../plan-design/changes/deprecated/removed-and-deprecated-cmfeatures.md).
 
+- CMG names need to be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and not contain consecutive hyphens. <!--13222041-->
+
 ## Support for Configuration Manager features
 
 The following table lists CMG support for Configuration Manager features:

memdocs/configmgr/core/get-started/2022/includes/2207/10928371.md

@@ -65,14 +65,14 @@ Use this cmdlet to monitor the distribution point migration status.
 Get-CMDistributionPointMigrationStatus -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point> 
 ```
 
-### Get-CMDistributionPointContentMigrationStatus 
+### Get-CMDistributionPointMigrationContentStatus 
 
 Use this cmdlet to monitor the distribution point content migration status.
 
 #### Syntax
 
 ```powershell
-Get-CMDistributionPointContentMigrationStatus -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point>
+Get-CMDistributionPointMigrationContentStatus -SourceDistributionPointName <FQDN for source distribution point> -DestinationDistributionPointName <FQDN for destination distribution point>
 ```
 
 ### Stop-CMDistributionPointMigration 

memdocs/configmgr/core/servers/manage/updates.md

@@ -59,7 +59,6 @@ The following supported versions of Configuration Manager are currently availabl
 | [**2111**](../../plan-design/changes/whats-new-in-version-2111.md)<br /> (5.00.9068) | December 1, 2021 | June 1, 2023 | No | Yes |
 | [**2107**](../../plan-design/changes/whats-new-in-version-2107.md)<br /> (5.00.9058) | August 2, 2021 | February 2, 2023 | No | Yes |
 | [**2103**](../../plan-design/changes/whats-new-in-version-2103.md)<br /> (5.00.9049) | April 5, 2021 | October 5, 2022 | Yes<sup>[Note 1](#bkmk_note1)</sup> | Yes |
-| [**2010**](../../plan-design/changes/whats-new-in-version-2010.md)<br /> (5.00.9040) | November 30, 2020 | May 30, 2022 | No | Yes |
 
 
 > [!NOTE]
@@ -84,6 +83,7 @@ The following table lists historical versions of Configuration Manager current b
 
 | Version                          | Availability date | Support end date   | Baseline | In-console update |
 |----------------------------------|-------------------|--------------------|----------|-------------------|
+| **2010** <br /> (5.00.9040)      | November 30, 2020     | May 30, 2022    | No      | Yes               |
 | **2006** <br /> (5.00.9012)      | August 11, 2020     | February 11, 2022    | No      | Yes               |
 | **2002** <br /> (5.00.8968)      | April 1, 2020     | October 1, 2021    | Yes      | Yes               |
 | **1910** <br /> (5.00.8913)      | November 29, 2019 | May 29, 2021       | No       | Yes               |

memdocs/configmgr/protect/deploy-use/defender-advanced-threat-protection.md

@@ -32,7 +32,7 @@ Microsoft Defender for Endpoint's cloud-based portal is [Microsoft Defender Secu
 You can onboard the following operating systems:
 
 - Windows 8.1
-- Windows 10, version 1607 or later
+- Windows 10, version  1709 or later
 - Windows 11
 - Windows Server 2012 R2
 - Windows Server 2016

memdocs/configmgr/sum/deploy-use/add-software-updates-to-an-update-group.md

@@ -2,7 +2,7 @@
 title: Add updates to an update group
 titleSuffix: Configuration Manager
 description: Manually or automatically add software updates to a software update group in your environment.
-ms.date: 04/08/2022
+ms.date: 07/12/2022
 ms.topic: conceptual
 ms.prod: configuration-manager
 ms.technology: configmgr-sum
@@ -19,7 +19,8 @@ ms.localizationpriority: medium
  Software update groups provide you with an effective method to organize software updates in your environment. You can manually add software updates to a software update group or automatically add software updates to a software update group by using an ADR. You can also deploy a software update group manually or deploy the group automatically by using an ADR. After you deploy a software update group, you can add new software updates to the group and Configuration Manager will automatically deploy them. Use the following procedures to add software updates to a new or existing software update group.  
 
 > [!TIP]
-> Starting in version 2203, you can organize software update groups and packages by using folders. This change allows for better categorization and management of software updates. For more information, see [Deploy software updates](deploy-software-updates.md#bkmk_folder).<!-- 3601129 -->
+> - Starting in version 2203, you can organize software update groups and packages by using folders. This change allows for better categorization and management of software updates. For more information, see [Deploy software updates](deploy-software-updates.md#bkmk_folder).<!-- 3601129 -->
+> - Devices running an unsupported operating systems will display as compliant since there aren't applicable updates to the operating system any longer. <!--13952160-->
 
 ## Add software updates to a new software update group  
 

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/sum/deploy-use/monitor-software-updates.md

@@ -5,7 +5,7 @@ description: The Configuration Manager console provides alerts and statuses to m
 author: mestew
 ms.author: mstewart
 manager: dougeby
-ms.date: 04/08/2022
+ms.date: 07/12/2022
 ms.topic: conceptual
 ms.prod: configuration-manager
 ms.technology: configmgr-sum
@@ -19,14 +19,10 @@ Configuration Manager provides many ways to help you to monitor software updates
 
 ## Software updates dashboard
 
-*(Introduced in version 1610)*
-
-Starting in Configuration Manager version 1610, you can use the Software Updates Dashboard to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk. To view the dashboard, navigate to **Monitoring** > **Overview** > **Security** > **Software Updates Dashboard**.
+You can use the Software Updates Dashboard to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk. To view the dashboard, navigate to **Monitoring** > **Overview** > **Security** > **Software Updates Dashboard**.
 
 ## Drill through required updates
 <!--4224414-->
-*(Introduced in version 1906)*
-
 You can drill through compliance statistics to see which devices require a specific Microsoft 365 Apps software update. To view the device list, you need permission to view updates and the collections the devices belong to. To drill down into the device list:
 
 1. Go to **Software Library** > **Software Updates** > **All Software Updates**.
@@ -77,6 +73,9 @@ After you configure the alert settings, if the specified conditions occur, Confi
 ##  <a name="BKMK_SUReports"></a> Software updates reports  
  The state messages for software updates provide information about the compliance of software updates and about the evaluation and enforcement state of software update deployments. You can run software update reports to display these state messages. There are more than 30 predefined software update reports available. They're organized in several categories and can be used to report on specific information about software updates and deployments. In addition to using the preconfigured reports, you can also create custom software update reports according to the needs of your enterprise. For more information, see [Operations and maintenance for reporting](../../core/servers/manage/operations-and-maintenance-for-reporting.md).  
 
+> [!NOTE]
+> Devices running an unsupported operating systems will display as compliant since there aren't applicable updates to the operating system any longer. <!--13952160-->
+
 ### Recommended software updates reports
 The following are some of the reports that are useful in identifying potential issues: