Merge pull request #7163 from MicrosoftDocs/main

v-dihans · web-flow · commit b916b93186c3 · 2022-03-29T11:37:10.000-06:00
Publish 03/29/2022, 10:30 AM
diff --git a/memdocs/configmgr/desktop-analytics/whats-new.md b/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.
diff --git a/memdocs/configmgr/develop/core/understand/configuration-manager-objects-overview.md b/memdocs/configmgr/develop/core/understand/configuration-manager-objects-overview.md
@@ -1,6 +1,7 @@
 ---
 title: "Objects Overview"
 titleSuffix: "Configuration Manager"
+description: "The Configuration Manager objects are instances of Configuration Manager-specific WMI classes managed by the SMS Provider."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/how-to-acquire-a-lock-on-a-sedo-enabled-object.md b/memdocs/configmgr/develop/core/understand/how-to-acquire-a-lock-on-a-sedo-enabled-object.md
@@ -1,6 +1,7 @@
 ---
 title: "Acquire a Lock on a SEDO-Enabled Object"
 titleSuffix: "Configuration Manager"
+description: "Learn how to acquire a lock on a SEDO-enabled object."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/how-to-add-a-configuration-manager-context-qualifier-by-using-managed-code.md b/memdocs/configmgr/develop/core/understand/how-to-add-a-configuration-manager-context-qualifier-by-using-managed-code.md
@@ -1,6 +1,7 @@
 ---
 title: "Add a Context Qualifier by Using Managed Code"
 titleSuffix: "Configuration Manager"
+description: "To add a context qualifier by using the managed SMS Provider, use the Context property which is a Dictionary object that holds context qualifiers."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/how-to-handle-configuration-manager-asynchronous-errors-by-using-managed-code.md b/memdocs/configmgr/develop/core/understand/how-to-handle-configuration-manager-asynchronous-errors-by-using-managed-code.md
@@ -1,6 +1,7 @@
 ---
 title: "Handle Asynchronous Errors by Using Managed Code"
 titleSuffix: "Configuration Manager"
+description: "To handle a Configuration Manager error raised during an asynchronous query, test the RunWorkerCompletedEventArgs parameter Error Exception property passed to the SmsBackgroundWorker.QueryProcessorCompleted event handler."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/how-to-handle-configuration-manager-synchronous-errors-by-using-managed-code.md b/memdocs/configmgr/develop/core/understand/how-to-handle-configuration-manager-synchronous-errors-by-using-managed-code.md
@@ -1,6 +1,7 @@
 ---
 title: "Handle Synchronous Errors by Using Managed Code"
 titleSuffix: "Configuration Manager"
+description: "To handle a Configuration Manager error raised in a synchronous query, catch the SmsQueryException exception."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/special-queries.md b/memdocs/configmgr/develop/core/understand/special-queries.md
@@ -1,6 +1,7 @@
 ---
 title: "Special Queries"
 titleSuffix: "Configuration Manager"
+description: "Extended WMI Query Language (WQL) supports queries that are specific to Configuration Manager needs."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/osd/how-to-add-a-state-migration-point-folder.md b/memdocs/configmgr/develop/osd/how-to-add-a-state-migration-point-folder.md
@@ -1,6 +1,7 @@
 ---
 title: "Add a State Migration Point Folder"
 titleSuffix: "Configuration Manager"
+description: "Add an operating system deployment state migration point folder by adding the folder description to the Directories embedded property list."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/osd/how-to-add-an-operating-system-deployment-task-sequence-action.md b/memdocs/configmgr/develop/osd/how-to-add-an-operating-system-deployment-task-sequence-action.md
@@ -1,6 +1,7 @@
 ---
 title: "Add an OS Deployment Task Sequence Action"
 titleSuffix: "Configuration Manager"
+description: "Add an OS deployment task sequence action to a task sequence by creating an instance of an SMS_TaskSequence_Action derived class, and then add it to the steps of the task sequence."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/osd/how-to-add-an-operating-system-image-package-in-configuration-manager.md b/memdocs/configmgr/develop/osd/how-to-add-an-operating-system-image-package-in-configuration-manager.md
@@ -1,6 +1,7 @@
 ---
 title: "Add an OS Image Package"
 titleSuffix: "Configuration Manager"
+description: "Add an operating system image package by creating an instance of the SMS_ImagePackage class."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/apps/sms_productfileinfo-server-wmi-class.md b/memdocs/configmgr/develop/reference/apps/sms_productfileinfo-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_ProductFileInfo Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_ProductFileInfo WMI class represents a combination of file and product information for inventory and metering."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/mdm/refreshpkgsource-method-in-class-sms_devicesettingpackage.md b/memdocs/configmgr/develop/reference/mdm/refreshpkgsource-method-in-class-sms_devicesettingpackage.md
@@ -1,6 +1,7 @@
 ---
 title: RefreshPkgSource method in class SMS_DeviceSettingPackage
 titleSuffix: "Configuration Manager"
+description: "The RefreshPkgSource class method refreshes the package source at all distribution points."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_tasksequence_capturesystemimageaction-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_tasksequence_capturesystemimageaction-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_TaskSequence_CaptureSystemImageAction Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_TaskSequence_CaptureSystemImageAction class represents a task sequence action that specifies an existing network share and WIM file to use when saving the image."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_tasksequence_requeststatestoreaction-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_tasksequence_requeststatestoreaction-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_TaskSequence_RequestStateStoreAction Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_TaskSequence_RequestStateStoreAction class represents a task sequence action that requests access to a state migration point when capturing a state from a computer or restoring a state to a computer."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_tasksequencereferencesinfo-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_tasksequencereferencesinfo-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_TaskSequenceReferencesInfo Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_TaskSequenceReferencesInfo class associates a task sequence with its package."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_usersettings-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_usersettings-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_UserSettings Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_UserSettings class describes attributes that are specific to a single user that is managed by Configuration Manager."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/protect/sms_topthreatsdetected-server-wmi-class.md b/memdocs/configmgr/develop/reference/protect/sms_topthreatsdetected-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_TopThreatsDetected Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_TopThreatsDetected class summarizes the top threats found in the last 24 hours per collection."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/sum/how-to-set-software-updates-branding-information.md b/memdocs/configmgr/develop/sum/how-to-set-software-updates-branding-information.md
@@ -1,6 +1,7 @@
 ---
 title: "Set Software Updates Branding Information"
 titleSuffix: "Configuration Manager"
+description: "Set the Software Updates client branding information by modifying the necessary site control file settings."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/intune/enrollment/device-enrollment-manager-enroll.md b/memdocs/intune/enrollment/device-enrollment-manager-enroll.md
@@ -43,7 +43,7 @@ DEM user accounts and devices that are enrolled with a DEM user account have the
 - Wipe can't be done from the Company Portal. Wiping a device enrolled by a DEM user account can be done from the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
 - Only the local device appears in the Company Portal app or website.
 - DEM user accounts cannot use Apple Volume Purchase Program (VPP) apps with Apple VPP user licenses because of per-user Apple ID requirements for app management.
-- DEM accounts do not support conditional access because conditional access is intended for per-user scenarios. 
+- For all platforms, DEM accounts do not support conditional access because conditional access is intended for per-user scenarios. 
 - DEM accounts cannot be used when enrolling devices via Apple's Automated Device Enrollment (ADE).
 - Devices can install VPP apps if they have Apple VPP device licenses.
 - On Windows 10 1709 and older, conditional access isn't available for Windows devices enrolled using bulk enrollment.
diff --git a/memdocs/intune/protect/certificates-trusted-root.md b/memdocs/intune/protect/certificates-trusted-root.md
@@ -7,7 +7,7 @@ keywords:
 author: brenduns
 ms.author: brenduns
 manager: dougeby
-ms.date: 06/03/2021
+ms.date: 03/29/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: protect
@@ -41,7 +41,7 @@ You deploy the trusted certificate profile to the same devices and users that re
 
 To use PKCS,  SCEP, and PKCS imported certificates, devices must trust your root Certification Authority. To establish trust, export the Trusted Root CA certificate, and any intermediate or issuing Certification Authority certificates, as a public certificate (.cer). You can get these certificates from the issuing CA, or from any device that trusts your issuing CA.
 
-To export the certificate, refer to the documentation for your Certification Authority. You'll need to export the public certificate as a .cer file.  Don't export the private key, a .pfx file.
+To export the certificate, refer to the documentation for your Certification Authority. You'll need to export the public certificate as a DER-encoded .cer file.  Don't export the private key, a .pfx file.
 
 You'll use this .cer file when you [create trusted certificate profiles](#create-trusted-certificate-profiles) to deploy that certificate to your devices.
 
