Merge pull request #7178 from LSchaufMS/Tuesday0329

Angela Fleischmann · web-flow · commit 2dfa46dad13e · 2022-03-30T14:29:00.000-06:00
[bulk] validation: add missing description
diff --git a/memdocs/configmgr/develop/apps/extending-application-management-overview.md b/memdocs/configmgr/develop/apps/extending-application-management-overview.md
@@ -1,6 +1,7 @@
 ---
 title: "Extending Application Management Overview"
 titleSuffix: "Configuration Manager"
+description: "Partners that must continue to use a specific deployment technology not natively supported by Configuration Manager, can extend the Application Management model to support a custom deployment type."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
@@ -21,7 +22,7 @@ By default, Application Management supports creating numerous deployment types s
 
  The deployment type object is composed of multiple objects: deployment technology, hosting technology, installer technology, content importer and the installer. The installer object is a key extension point, as it provides the properties for a technology, as well as the logic for detection, installation and uninstallation of the technology on the client system.  
 
- Extending the application model requires extending the Configuration Manager consoles and Configuration Manager clients that will leverage the custom deployment type. On the server, the extension is accomplished though creating and registering a custom deployment technology assembly and by extending Configuration Manager console (adding custom property sheets and wizards). The client extension is accomplished through extending WMI and adding a custom handler (a public COM class and methods). It should be noted that the client extension closely maps to the installer object, defined as part of the deployment type. The properties and methods defined in the installer object map directly to the property values are stored in WMI and the public COM methods defined in the custom handler.  
+ Extending the application model requires extending the Configuration Manager consoles and Configuration Manager clients that will leverage the custom deployment type. On the server, the extension is accomplished through creating and registering a custom deployment technology assembly and by extending Configuration Manager console (adding custom property sheets and wizards). The client extension is accomplished through extending WMI and adding a custom handler (a public COM class and methods). It should be noted that the client extension closely maps to the installer object, defined as part of the deployment type. The properties and methods defined in the installer object map directly to the property values are stored in WMI and the public COM methods defined in the custom handler.  
 
  In conceptualizing a custom deployment type, it might be useful to consider the in-product handling of Windows Installer files (*.msi).  
 
diff --git a/memdocs/configmgr/develop/core/understand/about-the-configuration-manager-site-control-file.md b/memdocs/configmgr/develop/core/understand/about-the-configuration-manager-site-control-file.md
@@ -1,5 +1,6 @@
 ---
 title: "Configuration Manager Site Control File"
+description: "Site control in Configuration Manager defines the settings for a specific site."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/configuration-manager-lazy-properties.md b/memdocs/configmgr/develop/core/understand/configuration-manager-lazy-properties.md
@@ -1,6 +1,7 @@
 ---
 title: Configuration Manager lazy properties
 titleSuffix: "Configuration Manager"
+description: "If lazy properties are retrieved during query operations, they have null or zero values."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/embedded-objects.md b/memdocs/configmgr/develop/core/understand/embedded-objects.md
@@ -1,6 +1,7 @@
 ---
 title: "Embedded Objects"
 titleSuffix: "Configuration Manager"
+description: "You cannot use Windows Management Instrumentation (WMI) to enumerate, query, get, or put embedded objects. You can only retrieve and store embedded objects through the parent instance."
 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-wmi.md b/memdocs/configmgr/develop/core/understand/how-to-add-a-configuration-manager-context-qualifier-by-using-wmi.md
@@ -1,6 +1,7 @@
 ---
 title: "Add a Context Qualifier by Using WMI"
 titleSuffix: "Configuration Manager"
+description: "Add context qualifiers to a connection (SWbemServices) or object (SWbemObject) by creating a SWbemNamedValueSet value set to hold the 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-create-a-configuration-manager-object-by-using-wmi.md b/memdocs/configmgr/develop/core/understand/how-to-create-a-configuration-manager-object-by-using-wmi.md
@@ -1,6 +1,7 @@
 ---
 title: "Create an Object by Using WMI"
 titleSuffix: "Configuration Manager"
+description: "Create a Configuration Manager object by calling the SWbemObject object SpawnInstance_ method."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/how-to-deploy-a-site-system-role--example---fallback-status-point-.md b/memdocs/configmgr/develop/core/understand/how-to-deploy-a-site-system-role--example---fallback-status-point-.md
@@ -1,6 +1,7 @@
 ---
 title: "Deploy a Site System Role"
 titleSuffix: "Configuration Manager"
+description: "The features and capabilities of a site are determined by the site roles applied to it. Configuring a site is performed through Windows Management Instrumentation (WMI) classes."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/core/understand/how-to-read-lazy-properties-by-using-wmi.md b/memdocs/configmgr/develop/core/understand/how-to-read-lazy-properties-by-using-wmi.md
@@ -1,6 +1,7 @@
 ---
 title: "Read Lazy Properties by Using WMI"
 titleSuffix: "Configuration Manager"
+description: "To read a lazy property from a Configuration Manager object returned in a query, you get the object instance, which in turn retrieves any lazy object properties from the SMS Provider."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/osd/how-to-clear-a-pxe-advertisement-for-a-configuration-manager-resource.md b/memdocs/configmgr/develop/osd/how-to-clear-a-pxe-advertisement-for-a-configuration-manager-resource.md
@@ -1,6 +1,7 @@
 ---
 title: "Clear a PXE Advertisement for a Resource"
 titleSuffix: "Configuration Manager"
+description: "To clear a PXE advertisement for a Configuration Manager resource, call the SMS_Collection object ClearLastNBSAdvForMachines method."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/osd/how-to-create-a-computer-variable.md b/memdocs/configmgr/develop/osd/how-to-create-a-computer-variable.md
@@ -1,6 +1,7 @@
 ---
 title: "Create a Computer Variable"
 titleSuffix: "Configuration Manager"
+description: "Create a computer variable for a computer that is running Configuration Manager by adding instances of SMS_MachineVariable to the SMS_MachineSettings class MachineVariables array property."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/osd/how-to-create-an-operating-system-deployment-task-sequence-group.md b/memdocs/configmgr/develop/osd/how-to-create-an-operating-system-deployment-task-sequence-group.md
@@ -1,6 +1,7 @@
 ---
 title: "Create an OS Deployment Task Sequence Group"
 titleSuffix: "Configuration Manager"
+description: "An operating system deployment task sequence group can be added to a task sequence by creating an instance of the SMS_TaskSequence_Group class."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/apps/sms_appdeploymentassetdetails-server-wmi-class.md b/memdocs/configmgr/develop/reference/apps/sms_appdeploymentassetdetails-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_AppDeploymentAssetDetails Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_AppDeploymentAssetDetails WMI class is an SMS Provider server class that represents asset-level details about the deployment."
 ms.date: "04/30/2020"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/compliance/sms_cicontentpackage-server-wmi-class.md b/memdocs/configmgr/develop/reference/compliance/sms_cicontentpackage-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_CIContentPackage Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_CIContentPackage WMI class represents the relationship between configuration item and associated content to SMS Package where the binary content is packaged and distributed."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/compliance/sms_configurationpolicybase-server-wmi-class.md b/memdocs/configmgr/develop/reference/compliance/sms_configurationpolicybase-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_ConfigurationPolicyBase Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_ConfigurationPolicyBase WMI class represents the base class for configuration policy."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/core/clients/sdk/applypolicyex-method-in-class-ccm_softwarecatalogutilities.md b/memdocs/configmgr/develop/reference/core/clients/sdk/applypolicyex-method-in-class-ccm_softwarecatalogutilities.md
@@ -1,6 +1,7 @@
 ---
 title: "ApplyPolicyEx Method"
 titleSuffix: "Configuration Manager"
+description: "The ApplyPolicyEx WMI class method, in Configuration Manager, applies policy."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/core/servers/configure/ccm_dts_priority-enumeration.md b/memdocs/configmgr/develop/reference/core/servers/configure/ccm_dts_priority-enumeration.md
@@ -1,6 +1,7 @@
 ---
 title: CCM_DTS_PRIORITY enumeration
 titleSuffix: Configuration Manager
+description: The CCM_DTS_PRIORITY enumeration indicates the priority of the download.
 ms.date: 09/20/2016
 ms.prod: configuration-manager
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/mdm/cancelretire-method-in-class-sms_devicemethods.md b/memdocs/configmgr/develop/reference/mdm/cancelretire-method-in-class-sms_devicemethods.md
@@ -1,6 +1,7 @@
 ---
 title: "CancelRetire Method"
 titleSuffix: "Configuration Manager"
+description: "The CancelRetire WMI class method cancels the retirement of this device from Configuration Manager."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/mdm/cancelwipe-method-in-class-sms_devicemethods.md b/memdocs/configmgr/develop/reference/mdm/cancelwipe-method-in-class-sms_devicemethods.md
@@ -1,6 +1,7 @@
 ---
 title: "CancelWipe Method"
 titleSuffix: "Configuration Manager"
+description: "The CancelWipe Windows Management Instrumentation (WMI) class method cancels a pending wipe request on mobile devices or Exchange ActiveSync devices."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/mdm/requestretire-method-in-class-sms_devicemethods.md b/memdocs/configmgr/develop/reference/mdm/requestretire-method-in-class-sms_devicemethods.md
@@ -1,6 +1,7 @@
 ---
 title: "RequestRetire Method"
 titleSuffix: "Configuration Manager"
+description: "The RequestRetire Windows Management Instrumentation (WMI) class method requests the retirement of this device from Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/addchangenotification-method-in-class-sms_operatingsysteminstallpackage.md b/memdocs/configmgr/develop/reference/osd/addchangenotification-method-in-class-sms_operatingsysteminstallpackage.md
@@ -1,6 +1,7 @@
 ---
 title: "AddChangeNotification Method in SMS_OperatingSystemInstallPackage"
 titleSuffix: "Configuration Manager"
+description: "The AddChangeNotification WMI class method adds an operating system install package change notification."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/getsequence-method-in-class-sms_tasksequencepackage.md b/memdocs/configmgr/develop/reference/osd/getsequence-method-in-class-sms_tasksequencepackage.md
@@ -1,6 +1,7 @@
 ---
 title: "GetSequence Method"
 titleSuffix: "Configuration Manager"
+description: "The GetSequence Windows Management Instrumentation (WMI) class method gets a task sequence (SMS_TaskSequence Server WMI Class) from a task sequence package (SMS_TaskSequencePackage Server WMI Class.)"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_imageservicingprogress-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_imageservicingprogress-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_ImageServicingProgress Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_ImageServicingProgress WMI class is an SMS Provider server class that represents software update installation status in offline servicing image."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_machinevariable-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_machinevariable-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_MachineVariable Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_MachineVariable WMI class defines the settings of a task sequence variable that is unique to a specific computer. "
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_tasksequence_applicationinfo-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_tasksequence_applicationinfo-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_TaskSequence_ApplicationInfo Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_TaskSequence_ApplicationInfo WMI class represents application information for the application that is installed by using a task sequence."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/osd/sms_tasksequence_joindomainworkgroupaction-server-wmi-class.md b/memdocs/configmgr/develop/reference/osd/sms_tasksequence_joindomainworkgroupaction-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_TaskSequence_JoinDomainWorkgroupAction Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_TaskSequence_JoinDomainWorkgroupAction WMI class is an SMS Provider server class that represents a task sequence action that joins a Windows domain or a Windows workgroup."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/configmgr/develop/reference/sum/sms_cm_updatepackageshistory-server-wmi-class.md b/memdocs/configmgr/develop/reference/sum/sms_cm_updatepackageshistory-server-wmi-class.md
@@ -1,6 +1,7 @@
 ---
 title: "SMS_CM_UpdatePackagesHistory Class"
 titleSuffix: "Configuration Manager"
+description: "The SMS_CM_UpdatePackagesHistory WMI class is used to get a list of all update packages."
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
 ms.technology: configmgr-sdk
diff --git a/memdocs/intune/user-help/how-do-i-find-the-serial-number-on-my-device-ios.md b/memdocs/intune/user-help/how-do-i-find-the-serial-number-on-my-device-ios.md
@@ -2,7 +2,7 @@
 # required metadata
 
 title: How do I find the serial number on my iOS device?
-description:
+description: The serial number for your device uniquely identifies it, and can help your company support with certain tasks, like replacing your device with a new one.
 keywords:
 author: lenewsad
 ms.author: lanewsad
diff --git a/memdocs/intune/user-help/how-do-i-find-the-serial-number-on-my-device-macos.md b/memdocs/intune/user-help/how-do-i-find-the-serial-number-on-my-device-macos.md
@@ -2,7 +2,7 @@
 # required metadata
 
 title: How do I find the serial number on my macOS device?
-description:
+description: To locate the serial number, go to the Apple menu > About This Mac.
 keywords:
 author: lenewsad
 
diff --git a/memdocs/intune/user-help/unable-to-get-macOS-device-managed.md b/memdocs/intune/user-help/unable-to-get-macOS-device-managed.md
@@ -2,7 +2,7 @@
 # required metadata
 
 title: Unable to get macOS device managed
-description:
+description: If you receive either of these messages while trying to get your macOS device managed, contact your company support.
 keywords:
 author: lenewsad
 
diff --git a/memdocs/intune/user-help/you-are-asked-to-identify-your-device-when-trying-to-enroll-macos.md b/memdocs/intune/user-help/you-are-asked-to-identify-your-device-when-trying-to-enroll-macos.md
@@ -2,7 +2,7 @@
 # required metadata
 
 title: You need to identify your macOS device when trying to enroll | Microsoft Docs
-description:
+description: If you are trying to enroll your macOS device in Intune, and are asked to identify your device, at least one of your devices has already been enrolled and assigned to your account using a method other than the Company Portal app.
 keywords:
 author: lenewsad
 
