Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into erikre-doc-13947563-ID

Author: Erikre

memdocs/configmgr/core/servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md

@@ -2,7 +2,7 @@
 title: Prepare to use an availability group
 titleSuffix: Configuration Manager
 description: Plan to use a SQL Server Always On availability group for the Configuration Manager site database.
-ms.date: 06/15/2021
+ms.date: 03/25/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -359,6 +359,8 @@ You don't need to make any changes to the configuration when adding a secondary
 
 When a site database uses an availability group, run the built-in **Backup Site server** maintenance task to back up common Configuration Manager settings and files. Don't use the MDF or LDF files created by that backup. Instead, make direct backups of these database files by using SQL Server.
 
+You can still use the SQL Server back up, however you can't restore it directly to a SQL Server Always On cluster. You need to restore it on a standalone server and move it back to SQL Server Always On.
+
 ### Transaction log
 
 Set the recovery model of the site database to **Full**. This configuration is a requirement for Configuration Manager use in an availability group. Plan to monitor and maintain the size of the site database transaction log. In the full recovery model, the transactions aren't hardened until it makes a full backup of the database or transaction log. For more information, see [Back up and restore of SQL Server databases](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases).

memdocs/configmgr/desktop-analytics/overview.md

@@ -106,10 +106,10 @@ To use Desktop Analytics, make sure your environment meets the following prerequ
   > - Use different Commercial IDs and Azure AD tenants.
   > - Configure both hierarchies to use the same Commercial ID to share the Azure AD tenant and Desktop Analytics instance. Use [different apps](connect-configmgr.md#bkmk_connect) for connecting each hierarchy. It may take up to 30 days after you disconnect a hierarchy for the portal to reflect changes.
 
-- Devices running Windows 7, Windows 8.1, or Windows 10.
+- Devices running Windows 10.
 
     > [!IMPORTANT]
-    > Starting in July 2021, Desktop Analytics supports the Windows diagnostic data processor configuration. This configuration is only for supported versions of Windows 10. Data for Windows 7, Windows 8, and earlier versions of Windows 10 will only show in Desktop Analytics until January 31, 2022. For more information, see [Support for the Windows diagnostic data processor configuration](whats-new.md#support-for-the-windows-diagnostic-data-processor-configuration).<!-- 10220671 -->
+    > Starting in July 2021, Desktop Analytics supports the Windows diagnostic data processor configuration. This configuration is only for supported versions of Windows 10. For more information, see [Support for the Windows diagnostic data processor configuration](whats-new.md#support-for-the-windows-diagnostic-data-processor-configuration).<!-- 10220671 -->
     >
     > Desktop Analytics doesn't support Windows 11.<!-- 10797955 --> For information about Windows 11 hardware readiness, Microsoft recommends that you enable tenant attach and [Endpoint analytics](../../analytics/overview.md).
 

memdocs/configmgr/desktop-analytics/whats-new.md

@@ -28,16 +28,19 @@ ms.localizationpriority: medium
 
 <!-- 10220671 -->
 
-Desktop Analytics now supports the new [Windows diagnostic data processor configuration](/windows/privacy/changes-to-windows-diagnostic-data-collection#new-windows-diagnostic-data-processor-configuration). This configuration provides you greater control of your Windows diagnostic data. Microsoft acts as a data processor, processing Windows diagnostic data for you as the controller. You'll continue to get insights to plan your deployments, and can fulfill [data subject requests](/windows/privacy/windows-10-and-privacy-compliance#3-the-process-for-exercising-data-subject-rights). These requests are typically to access or export Windows diagnostic data for a particular user.
+Desktop Analytics now supports the new [Windows diagnostic data processor configuration](/windows/privacy/changes-to-windows-diagnostic-data-collection#new-windows-diagnostic-data-processor-configuration). This configuration provides you greater control of your Windows diagnostic data. Microsoft acts as a data processor, processing Windows diagnostic data for you as the controller, as defined by the European Union General Data Protection Regulation (GDPR). You'll continue to get insights to plan your deployments, and can fulfill [data subject requests](/windows/privacy/windows-10-and-privacy-compliance#3-the-process-for-exercising-data-subject-rights). These requests are typically to access or export Windows diagnostic data for a particular user.
 
 To take advantage of this change, make sure your environment is up to date:
 
 - Use Configuration Manager version 2006 with [update rollup (4575789)](https://support.microsoft.com/topic/revised-update-rollup-for-microsoft-endpoint-configuration-manager-current-branch-version-2006-5861b9ee-9257-a15c-723e-c60110ce0c85) or a later version. Configuration Manager configures enrolled devices with policies for the Windows diagnostic data processor configuration. Update your site and clients to make sure they're using the latest configurations. Use Configuration Manager for the best experience with configuring and [enrolling devices into Desktop Analytics](enroll-devices.md#device-enrollment).
 
-- The Windows diagnostic data processor configuration is supported on the following Windows 10 versions:
-  - Pro, Education, and Enterprise editions
-  - Version 1809 or later
-  - July 2021 cumulative update or later
+- The Windows diagnostic data processor configuration is supported on devices that meet the configuration requirements:
+  - Use a supported version of Windows 10
+  - The following editions are supported:
+    - Enterprise
+    - Professional
+    - Education
+  - The device must be joined to Azure Active Directory.
 
   > [!IMPORTANT]
   > Devices with an older OS version like Windows 7 will continue to show in Desktop Analytics until January 31, 2022. Use Desktop Analytics to update those devices to a supported version of Windows 10. After that date, Desktop Analytics will only display devices with supported versions of Windows 10.

memdocs/configmgr/develop/apps/how-to-configure-automatic-software-metering-rule-generation.md

@@ -1,6 +1,7 @@
 ---
 title: "How to Configure Automatic Software Metering Rule Generation"
 titleSuffix: "Configuration Manager"
+description: "You configure Automatic Software Metering Rule Generation settings, in Configuration Manager, by modifying the site control file."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/apps/how-to-define-the-hosting-technology.md

@@ -1,6 +1,7 @@
 ---
 title: "How to Define the Hosting Technology"
 titleSuffix: "Configuration Manager"
+description: "The hosting technology is defined by implementing the `Microsoft.ConfigurationManagement.ApplicationManagement.HostingTechnology` class."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
@@ -19,7 +20,7 @@ To define a custom application management hosting technology, implement the `Mic
 
  The HostingTechnology class supports run time interaction and configuration for technologies. The class contains the hosting rules as defined in the HostingTechnology.xml file. If needed, additional methods and properties can be added to this class, though in most cases the existing base should be sufficient.  
 
- In the Remote Desktop Protocol (RDP) sample project, a new hosting technology is required to handle Remote Desktop Protocol (RDP) files. Hosting support for RDP files is not built-in to Configuration Manager, so a custom hosting technology is required.  
+ In the Remote Desktop Protocol (RDP) sample project, a new hosting technology is required to handle Remote Desktop Protocol (RDP) files. Hosting support for RDP files is not built in to Configuration Manager, so a custom hosting technology is required.  
 
 > [!IMPORTANT]
 >  The HostingTechnology class name must match the class specified in the HostingTechnology.xml file.  
@@ -33,7 +34,7 @@ To define a custom application management hosting technology, implement the `Mic
    The following example from the RDP sample project demonstrates how to define a hosting technology.  
 
 ```  
-// Defines the hosting technology for RDP files. Hosting support for RDP files is not built-in, so a custom  
+// Defines the hosting technology for RDP files. Hosting support for RDP files is not built in, so a custom  
 // hosting technology is needed on the client.   
 public class RdpHostingTechnology : HostingTechnology  
 {  

memdocs/configmgr/develop/apps/how-to-define-the-installer-technology-registration-file.md

@@ -1,4 +1,5 @@
 ---
+description: Learn how to register the custom installer technology with Configuration Manager using an XML file.
 title: "Define the Installer Technology Registration File"
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"

memdocs/configmgr/develop/apps/how-to-define-the-installer-technology.md

@@ -1,4 +1,5 @@
 ---
+description: Learn how to define the installer technology used to install a specific application to devices in Configuration Management.
 title: "How To Define the Installer Technology"
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"

memdocs/configmgr/develop/apps/how-to-enable-or-disable-a-software-metering-rule.md

@@ -1,6 +1,7 @@
 ---
 title: "Enable or Disable a Software Metering Rule"
 titleSuffix: "Configuration Manager"
+description: "Enable or disable a software metering rule, in Configuration Manager, by loading an instance of the software metering rule."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk

memdocs/configmgr/develop/apps/verifying-the-application-management-extension.md

@@ -1,6 +1,7 @@
 ---
 title: "Verifying the Application Management Extension"
 titleSuffix: "Configuration Manager"
+description: "Verifying the Application Management Extension. Verify the new Deployment Type is available in the console."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
@@ -25,7 +26,7 @@ ms.collection: openauth
 
 3.  On the **Home** tab, in the **Create** group, click **Create Application**.  
 
-4.  In the **Type** field, verify that the new deployment type is available in the pull down menu.  
+4.  In the **Type** field, verify that the new deployment type is available in the pull-down menu.  
 
      The image below shows an example from the RDP sample project.  
 
@@ -42,7 +43,7 @@ ms.collection: openauth
 
 3.  On the **Home** tab, in the **Create** group, click **Create Application**.  
 
-4.  In the **Type** field, select the new deployment type from the pull down menu.  
+4.  In the **Type** field, select the new deployment type from the pull-down menu.  
 
 5.  Continue through the wizard until successful completion.  
 
@@ -57,7 +58,7 @@ ms.collection: openauth
 
 3.  Select an application and then, on the **Home** tab, in the **Application** group, click **Create Deployment Type** to create a new deployment type for this application.  
 
-4.  In the **Type** field, select the new deployment type from the pull down menu.  
+4.  In the **Type** field, select the new deployment type from the pull-down menu.  
 
 5.  Continue through the wizard until successful completion.  
 

memdocs/configmgr/develop/compliance/about-authoring-configuration-baselines-and-configuration-items.md

@@ -11,7 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
-
+description: Learn about how to configure data through the Configuration Manager console or directly editing the DCM Digest XML file.
 
 ---