RSOP_ExtensionStatus class

Article
05/31/2018

Provides information about the overall status of a client-side extension's processing of policy.

The following syntax is simplified from MOF code.

Syntax

[AMENDMENT]
class RSOP_ExtensionStatus
{
  string   extensionGuid = "";
  string   displayName = "";
  datetime beginTime;
  datetime endTime;
  uint32   loggingStatus = 1;
  uint32   error = 0;
};

Members

The RSOP_ExtensionStatus class has these types of members:

Properties

Properties

The RSOP_ExtensionStatus class has these properties.

beginTime

Data type: datetime
Access type: Read-only
Qualifiers: DisplayName ("Begin Time")

Time at which the client-side extension was last invoked.

displayName

Data type: string
Access type: Read-only
Qualifiers: DisplayName ("Name")

Display name of the client-side extension.

endTime

Data type: datetime
Access type: Read-only
Qualifiers: DisplayName ("End Time")

Time at which the client-side extension finished its processing, after it was last invoked.

error

Data type: uint32
Access type: Read-only
Qualifiers: DisplayName ("Error Code")

Error code returned by the client-side extension after it was invoked to process policy.

extensionGuid

Data type: string
Access type: Read-only
Qualifiers: key, DisplayName ("Extension GUID")

GUID of the client-side extension.

loggingStatus

Data type: uint32
Access type: Read-only
Qualifiers: DisplayName ("Status")

The logging status of the extension.

This property can have one of the following values.

Logging - Complete (1)

The client-side extension successfully logged data.

Logging - Not Complete (2)

The client-side extension could not log data. The data might not be complete.

Logging - Not Supported (3)

The client-side extension does not support logging.

Remarks

The system typically logs an instance of RSOP_ExtensionStatus when it begins to log RSoP data. The instance marks the RSoP data as "dirty". If, for some reason, the system does not log this instance of RSOP_ExtensionStatus, policy processing ceases immediately and an error is written to the appropriate event log.

The system also logs an instance of RSOP_ExtensionStatus for each client-side extension before the system calls the extension. The instance marks the extension-specific RSoP data as "dirty". When the client-side extension completes its processing of policy, it must notify the system about the status of the RSoP data the extension logged using the ProcessGroupPolicyEx callback function. The system then marks the extension-specific data as "dirty" or "clean".

After the system logs all required data correctly, it marks the RSoP data "clean", depending on the status of the data.

Requirements


Minimum supported client	Windows Vista
Minimum supported server	Windows Server 2008
Namespace	Root\RSOP\Computer, Root\RSOP\User
MOF	Rsop.mof
DLL	GPSvc.dll

Partager via