Skip to content

Commit 31efade

Browse files
author
Angela Fleischmann
authored
Merge pull request #7153 from LSchaufMS/Monday2
[bulk] Validation: add missing descriptions.
2 parents c439adf + b156e35 commit 31efade

30 files changed

Lines changed: 36 additions & 7 deletions

File tree

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/understand/about-configuration-manager-schedules.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: "Configuration Manager Schedules"
3+
description: "The SMS_ScheduleToken WMI class is an abstract parent class for the SMS_ST_ schedule token classes that handle the scheduling of events with differing frequencies."
34
ms.date: "09/20/2016"
45
ms.prod: "configuration-manager"
56
ms.technology: configmgr-sdk

memdocs/configmgr/develop/core/understand/configuration-manager-bit-field-properties.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Bit Field Properties"
33
titleSuffix: "Configuration Manager"
4+
description: "Some Configuration Manager object properties are implemented as bit fields, where individual binary bits of an integer (usually a uint32 data type) are used as Boolean flags to store information"
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk
@@ -41,7 +42,7 @@ Some Configuration Manager object properties are implemented as bit fields, wher
4142

4243
A typical value of this bit field might be 10100000111. Bit 0 is the least significant bit (on the right) and the other bits are counted right to left. Therefore, in this example, the available class permissions include READ, MODIFY, DELETE, ADMINISTER, and CREATE, corresponding to bit fields 0, 1, 2, 8, and 10, respectively.
4344

44-
The difficulty arises when the binary number 10100000111 appears as the decimal number 1287 in an Configuration Manager console display and in how you interpret the bits. The solution is to open the Windows Calculator application (Calc.exe, in the Accessories group). Use the Scientific view, set the calculator for decimal mode, and enter 1287. Use the radio buttons of the calculator to convert to a binary display. The binary bit field 10100000111 appears. You can read the selected bit flags from this display.
45+
The difficulty arises when the binary number 10100000111 appears as the decimal number 1287 in a Configuration Manager console display and in how you interpret the bits. The solution is to open the Windows Calculator application (Calc.exe, in the Accessories group). Use the Scientific view, set the calculator for decimal mode, and enter 1287. Use the radio buttons of the calculator to convert to a binary display. The binary bit field 10100000111 appears. You can read the selected bit flags from this display.
4546

4647
> [!NOTE]
4748
> In a typical bit field property, many of the bits are unused and have no defined meaning.

memdocs/configmgr/develop/core/understand/how-to-connect-to-an-sms-provider-by-using-managed-code.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Connect to an SMS Provider by Using Managed Code"
33
titleSuffix: "Configuration Manager"
4+
description: "To connect to an SMS Provider, use WqlConnectionManager.Connect."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk
@@ -15,12 +16,12 @@ ms.collection: openauth
1516

1617
---
1718
# How to Connect to an SMS Provider in Configuration Manager by Using Managed Code
18-
To connect to a SMS Provider, use **WqlConnectionManager.Connect**. After it is connected, **WqlConnectionManager.Connect** has methods to query, create, delete, and otherwise use Configuration Manager Windows Management Instrumentation (WMI) objects.
19+
To connect to an SMS Provider, use **WqlConnectionManager.Connect**. After it is connected, **WqlConnectionManager.Connect** has methods to query, create, delete, and otherwise use Configuration Manager Windows Management Instrumentation (WMI) objects.
1920

2021
> [!NOTE]
2122
> **WqlConnectionManager.Connect** is a WMI-specific derivation of [ConnectionManagerBase](/previous-versions/system-center/developer/cc147366(v=msdn.10)).
2223
23-
If you are connecting to a local SMS Provider, you do not supply user credentials. If you are connecting to a remote SMS Provider, you do not need to supply user credentials if the if the current user/computer context has permissions on the remote SMS Provider.
24+
If you are connecting to a local SMS Provider, you do not supply user credentials. If you are connecting to a remote SMS Provider, you do not need to supply user credentials if the current user/computer context has permissions on the remote SMS Provider.
2425

2526
If you do not have access privileges on the remote SMS Provider, or if you want to use a different user account, then you must supply user credentials for a user account that has access privileges.
2627

@@ -36,7 +37,7 @@ To connect to a SMS Provider, use **WqlConnectionManager.Connect**. After it is
3637
|ConnectedSiteCode|The site code for the Configuration Manager site that the connection is connected to. For example, XXX.|
3738
|ServerName|The computer name, for example, COMPUTERNAME.|
3839
|SiteName|The Configuration Manager site code. For example, Central Site.|
39-
|ConnectedServerVersion|Ther version for the connected server. For example, 4.00.5830.0000|
40+
|ConnectedServerVersion|The version for the connected server. For example, 4.00.5830.0000|
4041
|BuildNumber|The Configuration Manager installation build number. For example, 5830.|
4142

4243
> [!NOTE]

memdocs/configmgr/develop/core/understand/how-to-create-a-schedule-token.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Create a Schedule Token"
33
titleSuffix: "Configuration Manager"
4+
description: "Create a schedule token in Configuration Manager by creating and populating an instance of the appropriate SMS_ST_ schedule token class."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/osd/how-to-enable-or-disable-a-windows-driver.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Enable or Disable a Windows Driver"
33
titleSuffix: "Configuration Manager"
4+
description: "Enable or disable a Windows driver in the operating system deployment driver catalog by setting the IsEnabled property of the SMS_Driver Server WMI Class object."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk
@@ -21,7 +22,7 @@ You enable or disable a Windows driver in the operating system deployment driver
2122

2223
1. Set up a connection to the SMS Provider. For more information, see [SMS Provider fundamentals](../core/understand/sms-provider-fundamentals.md).
2324

24-
2. Get the `SMS_Driver` object for the driver you want enable or disable.
25+
2. Get the `SMS_Driver` object for the driver you want to enable or disable.
2526

2627
3. Set the `IsEnabled` property to `true` to enable the driver, or to `false` to disable the driver.
2728

memdocs/configmgr/develop/osd/how-to-import-a-new-computer-into-configuration-manager.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "Import a New Computer"
33
titleSuffix: "Configuration Manager"
4+
description: "Add a new computer directly to the Configuration Manager database by calling the ImportMachineEntry Method in Class SMS_Site."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/apps/sms_g_user_dcmdeploymentnoncompliantassetdetails-server-wmi-class.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "SMS_G_USER_DCMDeploymentNonCompliantAssetDetails Class"
33
titleSuffix: "Configuration Manager"
4+
description: "The SMS_G_USER_DCMDeploymentNonCompliantAssetDetails WMI class represents non-compliant asset details for a deployment."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

memdocs/configmgr/develop/reference/apps/sms_unmanagedapps-server-wmi-class.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: "SMS_UnManagedApps Class"
33
titleSuffix: "Configuration Manager"
4+
description: "The SMS_UnManagedApps WMI class is an SMS Provider server class that represents unmanaged apps."
45
ms.date: "09/20/2016"
56
ms.prod: "configuration-manager"
67
ms.technology: configmgr-sdk

0 commit comments

Comments
 (0)