Merge pull request #7491 from MicrosoftDocs/main

Publish 04/29/2022, 10:30 AM

Author: v-dihans

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"

memdocs/configmgr/develop/core/understand/configuration-manager-object-security.md

@@ -1,5 +1,6 @@
 ---
 title: "Object Security"
+description: The delegate verb in Configuration Manager provides administrators with a way of allowing users to assign to other users the instance permissions to an object in a very limited way.
 titleSuffix: "Configuration Manager"
 ms.date: "09/20/2016"
 ms.prod: "configuration-manager"
@@ -21,7 +22,7 @@ ms.collection: openauth
 
  To some extent, these explicitly granted rights provide the user with a certain level of ownership of the object. With the delegate right, this ownership is extended to the control of the default group of instance rights. To limit which rights a user can delegate, only rights explicitly granted to them (not a group to which they belong) can be delegated. A user can also remove other users (or groups) instance rights if the user has the delegate permission and explicit rights to an object (this is why a user is said to own an object if they have explicit instance rights). Users with administrator rights still have full control of administering permissions.  
 
- A common scenario for using the delegate verb is when a user has create and delegate rights for an object type and wants to create an object and allow members of a user group to see it. They create an instance of the object and then delegate read permissions for the instance to the user group.  
+ A common scenario for using the delegate verb is when a user has created and delegated rights for an object type and wants to create an object and allow members of a user group to see it. They create an instance of the object and then delegate read permissions for the instance to the user group.  
 
  The delegate verb is applicable to the follow Configuration Manager classes:  
 
@@ -40,7 +41,7 @@ ms.collection: openauth
 -   `SMS_MeteredProductRule`  
 
 ## System Resource (SMS_R_System) as a Secured Resource  
- Secured resources are resources (the SMS_R_* classes) that require collection read rights to be viewed. If the user has class-level collection read rights, the user can see all the instances of a secured resource. If the user only has instance-level read rights to certain collections, the user only has rights to see resources that are a members of those collections. `SMS_R_User` and `SMS_R_UserGroup` are secured resources in SMS 2.0. In SMS 2003, `SMS_R_System` (the system resource) is also a secured resource.  
+ Secured resources are resources (the SMS_R_* classes) that require collection read rights to be viewed. If the user has class-level collection read rights, the user can see all the instances of a secured resource. If the user only has instance-level read rights to certain collections, the user only has rights to see resources that are members of those collections. `SMS_R_User` and `SMS_R_UserGroup` are secured resources in SMS 2.0. In SMS 2003, `SMS_R_System` (the system resource) is also a secured resource.  
 
  Inventory instances (SMS_G_System_*) are secured similarly with the read resource verb. If a user has class-level rights, that user can see inventory data belonging to all resources. If the user does not have class-level rights, the user can see only inventory data for inventory that belongs to resources that are members of collections to which the user has instance-level read resource rights. Conversely, if a user has read resource rights to a collection, a user can see the inventory data for the members of that collection. This has not been affected by the change in security to `SMS_R_System`. Read resource rights cannot be granted to a user without granting read rights. When a user does not have the appropriate class-level collection rights, resource security is enforced through collection limiting.