Share via


SMS_StatMsgWithInsStrings Server WMI Class

 

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 R2 Configuration Manager

The SMS_StatMsgWithInsStrings Windows Management Instrumentation (WMI) class is an SMS Provider server class, in Configuration Manager, that represents an individual status message with insertion strings.

The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties.

Syntax

Class SMS_StatMsgWithInsStrings : SMS_BaseClass
{
    String Component;
    String InsString1;
    String InsString10;
    String InsString2;
    String InsString3;
    String InsString4;
    String InsString5;
    String InsString6;
    String InsString7;
    String InsString8;
    String InsString9;
    String MachineName;
    UInt32 MessageID;
    UInt32 MessageType;
    String ModuleName;
    UInt32 PerClient;
    UInt32 ProcessID;
    SInt64 RecordID;
    UInt32 ReportFunction;
    UInt32 ResourceID;
    UInt32 Severity;
    String SiteCode;
    UInt32 SuccessfulTransaction;
    UInt32 ThreadID;
    DateTime Time;
    String TopLevelSiteCode;
    UInt32 Transaction;
    UInt32 Win32Error;
};

Methods

The SMS_StatMsgWithInsStrings class does not define any methods.

Properties

  • Component
    Data type: String

    Access type: Read

    Qualifiers: None

    Name of the component that created the message. For user-defined messages, this name comes from the ApplicationName context qualifier that you must set before calling a raise status message method.

  • InsString1
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 1.

  • InsString10
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 10.

  • InsString2
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 2.

  • InsString3
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 3.

  • InsString4
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 4.

  • InsString5
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 5.

  • InsString6
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 6.

  • InsString7
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 7.

  • InsString8
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 8.

  • InsString9
    Data type: String

    Access type: Read

    Qualifiers: None

    Insertion string at position 9.

  • MachineName
    Data type: String

    Access type: Read

    Qualifiers: None

    Name of the computer that created the message. For user-defined messages, this name comes from the MachineName context qualifier that you must set before calling a raise status message method.

  • MessageID
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Unique ID of message text in a message DLL. See the MessageID property of SMS_StatusMessage Server WMI Class.

  • MessageType
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Type of message. See the MessageType property of SMS_StatusMessage Server WMI Class.

  • ModuleName
    Data type: String

    Access type: Read

    Qualifiers: None

    The DLL that is associated with the status message to raise. This is not the name of the DLL itself, but it is a display string corresponding to the ModuleName property value defined in SMS_StatusMessage Server WMI Class. You use the ModuleName value to get the DLL name.

  • PerClient
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Value indicating if the status message was generated by a client component. See the PerClient property of SMS_StatusMessage Server WMI Class.

  • ProcessID
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    ID of the process that created the message.

  • RecordID
    Data type: SInt64

    Access type: Read

    Qualifiers: [key]

    Unique ID of the status message.

  • ReportFunction
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Report function. See the ReportFunction property of SMS_StatusMessage Server WMI Class.

  • ResourceID
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Resource ID of the client, may be NULL if the message is not associated with a client.

  • Severity
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Type of status message. See the Severity property of SMS_StatusMessage Server WMI Class.

  • SiteCode
    Data type: String

    Access type: Read

    Qualifiers: None

    Site code of the site that reported the status message.

  • SuccessfulTransaction
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Value indicating transaction status. See the SuccessfulTransaction property of SMS_StatusMessage Server WMI Class.

  • ThreadID
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Identifier of the thread that created the message.

  • Time
    Data type: DateTime

    Access type: Read

    Qualifiers: None

    Date and time, in Universal Coordinated Time (UTC), when the status message was created.

  • TopLevelSiteCode
    Data type: String

    Access type: Read

    Qualifiers: None

    This property is deprecated.

  • Transaction
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Value indicating whether transactions are enabled. See the Transaction property of SMS_StatusMessage Server WMI Class.

  • Win32Error
    Data type: UInt32

    Access type: Read

    Qualifiers: None

    Win32 error code that is associated with the status message.

Remarks

Requirements

Runtime Requirements

For more information, see Configuration Manager Server Runtime Requirements.

Development Requirements

For more information, see Configuration Manager Server Development Requirements.