Common XML Attributes

Each schema defines various attributes for its outer element and inner element. Many attributes are common to all schemas and are defined here. The common attributes are included in the schema for each preference type, but they are not further defined there unless special handling is required.

 For Boolean values, specified in the schema as xs:boolean and with a possible value of 0 or 1, the default will always be 0 if unspecified.

Attribute name



Uniquely identifies each preference type. The value MUST be as documented in each protocol sample XML. The clsid is a developer generated GUID value and MUST be present in the client xml for the client to process the protocol settings. The clsid values are documented in section


(optional) Marks the entire preference type as disabled. If specified, values MUST be "1" for disabled or "0" for enabled.


Appears in the management console result view and is not used by the client-side protocol.


(optional) Appears in the management console result view and is not used by the client-side protocol.


An offset into a bitmap resource that is used to display an icon next to the item when loaded in the management console. This field is required only for the management console when the image changes and can either be set to 0 or it can be omitted to display a default folder icon.


(optional) A date that the preference was last edited. This is for display purposes. The current format MUST be "YYYY-MM-DD HH:MM:SS" in Coordinated Universal Time (UTC).


A unique GUID generated when the preferences element is created and used to uniquely identify the preference item for tracing and reporting.


(optional) A user-specified value. The value is limited by the XML standard size for attribute values. Preferences currently limit this value to 32 kilobytes in character length.


(optional) Continue processing in the event of an error. If specified, values MUST be 1 to bypass errors or 0 to stop processing this preference type.


(optional) Specifies whether processing occurs in the system context or the user context. If specified, values MUST be 1 for user context or 0 for system context. The default value changes on a per-policy basis but, in general, preferences that target users set userContext to 1, and preferences that target the computer or the Default user set userContext to 0.


(optional) Specifies whether the preferences are to be removed if the scope changes and the preference is no longer applicable. If specified, values MUST be 1 to remove the preferences or 0 to leave the preference settings.

 Attributes that are noted as not applicable for a given action will be ignored if specified.

 The <Filters> element is defined in section