Share via

SMS_G_System_Current

  • Article

The SMS_G_System_Current WMI class is an abstract class that is the parent of all hardware inventory classes representing the current state of the client, at the time of the last inventory.

The following syntax is simplified from MOF code and includes all inherited properties.

Class SMS_G_System_Current : SMS_G_System
{
  uint32 GroupID;
  uint32 ResourceID;
  uint32 RevisionID;
  datetime TimeStamp;
};

Properties

  • GroupID
    Data type: uint32
    Access type: Read-only
    Qualifiers: Key

    Distinguishes one hardware inventory instance from another within one resource (SMS client). For example, each logical disk instance for a client is assigned a unique GroupID value.

  • ResourceID
    Data type: uint32
    Access type: Read-only
    Qualifiers: Key

    SMS-supplied identifier that uniquely identifies a resource (SMS client). Inventory items with the same ResourceID values are all found on the same SMS client. A ResourceID value is not unique outside the site.

  • RevisionID
    Data type: uint32
    Access type: Read-only

    Increments if the object changed after the last time inventory was taken. The highest number is the most recent update. Objects with the same ResourceID and GroupID values are deltas. They differ from one another by RevisionID number.

  • TimeStamp
    Data type: datetime
    Access type: Read-only

    Date and time of the inventory.

Remarks

You can query classes derived from SMS_G_System_Current, such as SMS_G_System_Logical_Disk, to get the current state of individual hardware components of a client, or you can query SMS_G_System_Current to get the current state of all hardware components of a client. For example, the following query returns all hardware components for the given client:

SELECT * FROM SMS_G_System_Current
WHERE ResourceID = <resourceid>

While this is a simple solution for getting all the hardware components for a client, it is inefficient. WMI turns the query into multiple queries, one for each subclass, and spawns a thread for each query. If performance is critical, you should query each subclass yourself.

See Also

Hardware Inventory Classes, Resource Management Classes, SMS_G_System_ExtHistory, SMS_G_System_History