The SMS_StatMsgInsStrings Windows Management Instrumentation (WMI) class is an SMS Provider server class, in Configuration Manager, that represents insertion strings that are inserted into the status message.
The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties.
Class SMS_StatMsgInsStrings : SMS_BaseClass
{
UInt32 InsStrIndex;
String InsStrValue;
UInt32 RecordID;
};
|
Methods
The SMS_StatMsgInsStrings class does not define any methods.
Properties
- InsStrIndex
- Data type: UInt32Access type: Read/WriteQualifiers: [Description(""), key, ResID(302), ResDLL("SMS_RSTT.dll")]The index defining the order of the insertion strings. The index directly relates to the insertion points in the status message.
- InsStrValue
- Data type: StringAccess type: Read/WriteQualifiers: [ResID(303), ResDLL("SMS_RSTT.dll")]Text to insert into the insertion point.
- RecordID
- Data type: UInt32Access type: Read/WriteQualifiers: [key, ResID(301), ResDLL("SMS_RSTT.dll")]Record ID of the status message to which the insertion point belongs.
Remarks
Class qualifiers for this class include:
- Read (read-only)
For more information about both the class qualifiers and the property qualifiers included in the Properties section, see Configuration Manager Class and Property Qualifiers.
This class represents insertion strings for Configuration Manager component messages and user-defined messages. The status message is represented by SMS_StatusMessage Server WMI Class. Your application can use the RaiseRawStatusMsg Method in Class SMS_StatusMessage to add insertion strings. To delete insertion strings, the application deletes the associated status message.
 Note |
|---|
| Use the SMS_StatInsStr Server WMI Class for a high-performance version of this class. |
Requirements
Runtime Requirements
For more information, see Configuration Manager Server Runtime Requirements.
Development Requirements
For more information, see Configuration Manager Server Development Requirements.
See Also
Send comments about this topic to Microsoft.