Merge branch 'main' into release-cm2204-tp

Author: v-alje

.openpublishing.redirection.json

@@ -1,5 +1,15 @@
 {
     "redirections": [
+        {
+            "source_path": "memdocs/intune/apps/store-apps-windows-phone-8-1.md",
+            "redirect_url": "/mem/intune/apps/apps-add",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "memdocs/intune/apps/lob-apps-windows-phone.md",
+            "redirect_url": "/mem/intune/apps/apps-add",
+            "redirect_document_id": false
+        },      
         {
             "source_path": "memdocs/intune/user-help/set-or-change-your-password-windows.md",
             "redirect_url": "https://support.microsoft.com/windows/windows-sign-in-options-and-account-protection-7b34d4cf-794f-f6bd-ddcc-e73cdf1a6fbf",

memdocs/configmgr/develop/apps/deployment-type-extension-versioning.md

@@ -1,5 +1,6 @@
 ---
 title: "Deployment Type Extension Versioning"
+description: Configuration Manager supports in-place versioning for minor upgrades and out-of-place versioning for major upgrades.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

memdocs/configmgr/develop/apps/how-to-create-the-windows-installer-file-msi.md

@@ -1,5 +1,6 @@
 ---
 title: "How to Create the Windows Installer File "
+description: After the Deployment Type Extension file (*.cmdtx) is created, you are expected to generate a Windows Installer file (\*.msi) which contains the \*.cmdtx file and the UX files.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

memdocs/configmgr/develop/apps/how-to-define-the-client-side-handler.md

@@ -1,5 +1,6 @@
 ---
 title: "How to Define the Client-side Handler"
+description: The custom client-side handler needs to implement a public COM interface and methods. The below methods will be called by the Configuration Manager client framework.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

memdocs/configmgr/develop/apps/how-to-define-the-create-deployment-type-wizard-xml-file.md

@@ -1,5 +1,6 @@
 ---
 title: "How to Define the Create Deployment Type Wizard XML File "
+description: To define the custom create deployment type wizard XML file, create an XML file based on the schema.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

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

@@ -1,5 +1,6 @@
 ---
 title: "Define the Deployment Technology Registration File "
+description: To define a deployment technology registration file, create an XML file based on the AppMgmtDigest schema.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

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

@@ -1,5 +1,6 @@
 ---
 title: "How to Define the Deployment Technology"
+description: To define a custom application management deployment technology, implement the Microsoft.ConfigurationManagement.ApplicationManagement.DeploymentTechnology class.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
@@ -19,7 +20,7 @@ To define a custom application management deployment technology, implement the `
 
  The DeploymentTechnology class is the object that is registered with the Configuration Manager Application Model SDK. The DeploymentTechnology class contains references to three different types of objects that compose the technology. When implementing a new deployment technology you must implement a class that derives from this class.  
 
- In the Remote Desktop Protocol (RDP) sample project, a new deployment technology is required for Remote Desktop Protocol (RDP) files. Deployment support for RDP files is not built-in to Configuration Manager, so a custom deployment technology is required.  
+ In the Remote Desktop Protocol (RDP) sample project, a new deployment technology is required for Remote Desktop Protocol (RDP) files. Deployment support for RDP files is not built in to Configuration Manager, so a custom deployment technology is required.  
 
 > [!IMPORTANT]
 >  The DeploymentTechnology class name must match the class specified in the DeploymentTechnology.xml file.  

memdocs/configmgr/develop/compliance/about-configuration-baselines.md

@@ -1,5 +1,6 @@
 ---
 title: "About Configuration Baselines"
+description: In Configuration Manager, baselines are used to define the configuration of a product or a system that is established at a specific point in time, capturing both structure and details.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

memdocs/configmgr/develop/compliance/how-to-enable-or-disable-the-compliance-settings--dcm--agent.md

@@ -1,5 +1,6 @@
 ---
 title: "Enable or Disable the Compliance Settings Agent"
+description: In Configuration Manager, you enable or disable the Desired Configuration Management Client Agent by modifying the site control file settings.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"

memdocs/configmgr/develop/compliance/how-to-import-configuration-baselines-and-configuration-items.md

@@ -1,5 +1,6 @@
 ---
 title: "Import Configuration Baselines and Items"
+description: In Configuration Manager, importing a configuration baseline or configuration item by using the Configuration Manager SDK requires a properly formatted XML file.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"