Skip to content

Commit 56a2a13

Browse files
committed
Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into erikre-doc-13947563-ID
2 parents f6acebd + c7b1495 commit 56a2a13

129 files changed

Lines changed: 142 additions & 19 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

memdocs/configmgr/develop/apps/extending-application-management-overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Extending Application Management Overview"
33
titleSuffix: "Configuration Manager"
4+
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."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk
@@ -21,7 +22,7 @@ By default, Application Management supports creating numerous deployment types s
2122

2223
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.
2324

24-
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.
25+
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.
2526

2627
In conceptualizing a custom deployment type, it might be useful to consider the in-product handling of Windows Installer files (*.msi).
2728

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
description: Learn how to create and define the custom deployment type property page XML file for use within Configuration Manager.
23
title: "Define the Deployment Type Property Sheet XML File"
34
titleSuffix: "Configuration Manager"
45
ms.date: "09/20/2016"

memdocs/configmgr/develop/core/clients/collections/how-to-create-a-static-collection.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
description: Learn how to create a static collection with defined attributes and members within Configuration Manager.
23
title: "Create a Static Collection"
34
titleSuffix: "Configuration Manager"
45
ms.date: "09/20/2016"

memdocs/configmgr/develop/core/clients/inventory/how-to-reset-the-hardware-inventory-cache.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Reset the Hardware Inventory Cache"
33
titleSuffix: "Configuration Manager"
4+
description: "In Configuration Manager, you reset the hardware inventory cache by connecting to the inventory agent namespace and deleting the inventory action status instance for hardware inventory."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/core/clients/programming/how-to-call-a-wmi-class-method-by-using-system.management.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Call a WMI Class Method by Using System.Management"
33
titleSuffix: "Configuration Manager"
4+
description: "To call a client Windows Management Instrumentation (WMI) class method, call the InvokeMethod of the WMI class's ManagementClass."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/core/reqs/server-runtime-requirements.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: Server Runtime Requirements
33
titleSuffix: Configuration Manager
4+
description: Microsoft Configuration Manager server applications that are developed by using the Configuration Manager SDK, have the following runtime requirements.
45
ms.date: 03/14/2017
56
ms.prod: configuration-manager
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/core/servers/configure/how-to-modify-advertisement-properties.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Modify Advertisement Properties"
33
titleSuffix: "Configuration Manager"
4+
description: "In Configuration Manager, the following example shows how to modify an existing advertisement by using the SMS_Advertisement class and class properties."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/core/servers/console/console-node-xml.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
description: Learn how to use the Configuration Manager Console Node XML to cause a grid view to appear in the view panel displaying the RoleName and SiteCode properties.
23
title: "Console Node XML"
34
titleSuffix: "Configuration Manager"
45
ms.date: "09/20/2016"

memdocs/configmgr/develop/core/servers/console/how-to-bind-configuration-manager-data-to-a-form.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Bind Configuration Manager Data to a Form"
33
ms.date: "09/20/2016"
4+
description: "In Configuration Manager, to bind console data to a property sheet, you use the DataBindings property of the property sheet's control class."
45
ms.prod: "configuration-manager"
56
ms.technology: configmgr-sdk
67
ms.topic: how-to

memdocs/configmgr/develop/core/servers/console/how-to-create-a-configuration-manager-property-sheet.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Create a Property Sheet"
33
titleSuffix: "Configuration Manager"
4+
description: "In Configuration Manager, to create a console property sheet, you first create a NET Framework assembly that inherits from the SMSPageControl class."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

0 commit comments

Comments
 (0)