Protocol versions: The Group Policy: Core Protocol provides a versioning capability in the gPCFunctionalityVersion attribute of the Active Directory object class for a Group Policy Object (GPO) specified in section . There is no capability negotiation that is associated with this version. The version itself is a simple integer. There is only one version currently, and if the Group Policy client receives anything other than that version for a GPO, the GPO does not participate in this protocol, as specified in section . Security and authentication methods: The Group Policy: Core Protocol supports the following authentication methods: NT LAN Manager protocol (NTLM) and Kerberos. The authentication method in use is negotiated using the mechanisms specified in . Vendor-Extensible Fields The Group Policy: Core Protocol allows vendors to define Group Policy extensions to the protocol. These Group Policy extensions enable vendors to store vendor-specific data in a GPO on the Group Policy server. For the Group Policy client to access that data, it must be able to identify a system component that can retrieve and interpret that data. To facilitate this, the GPO Active Directory object schema has two attributes, gPCMachineExtensionNames and gPCUserExtensionNames, in which a vendor can append both a CSE GUID (as specified in section 2.3.4.3) that identifies that GPO as having that vendor's particular extra Group Policy extension data stored inside it, and a tool extension GUID that allows the vendor to associate an administrative tool that can update the data. The vendor obtains the of the CSE GUID and the tool extension GUID by generating them according to the standard algorithm, as specified in . After they are generated, the vendor SHOULD include the GUID in these attributes, as specified in section . Vendors do not need to collaborate or obtain GUIDs from a central authority; the GUID generation algorithm ensures that no two vendors make use of the same GUID. Vendors MAY specify a NULL GUID for the tool extension GUID. Each CSE GUID and tool extension GUID defined by a vendor MUST be treated as a standards assignment to the gPCMachineExtensionNames and gPCUserExtensionNames attributes that MUST be declared in the Group Policy extension documentation that is associated with the CSE GUID and tool extension GUID. Standards Assignments There are no standards assignments for the Group Policy: Core Protocol.
Protocol versions: The Group Policy: Core Protocol provides a versioning capability in the gPCFunctionalityVersion attribute of the Active Directory object class for a Group Policy Object (GPO) specified in section . There is no capability negotiation that is associated with this version. The version itself is a simple integer. There is only one version currently, and if the Group Policy client receives anything other than that version for a GPO, the GPO does not participate in this protocol, as specified in section . Security and authentication methods: The Group Policy: Core Protocol supports the following authentication methods: NT LAN Manager protocol (NTLM) and Kerberos. The authentication method in use is negotiated using the mechanisms specified in . Vendor-Extensible Fields The Group Policy: Core Protocol allows vendors to define Group Policy extensions to the protocol. These Group Policy extensions enable vendors to store vendor-specific data in a GPO on the Group Policy server. For the Group Policy client to access that data, it must be able to identify a system component that can retrieve and interpret that data. To facilitate this, the GPO Active Directory object schema has two attributes, gPCMachineExtensionNames and gPCUserExtensionNames, in which a vendor can append both a CSE GUID (as specified in section 2.3.4.3) that identifies that GPO as having that vendor's particular extra Group Policy extension data stored inside it, and a tool extension GUID that allows the vendor to associate an administrative tool that can update the data. The vendor obtains the of the CSE GUID and the tool extension GUID by generating them according to the standard algorithm, as specified in . After they are generated, the vendor SHOULD include the GUID in these attributes, as specified in section . Vendors do not need to collaborate or obtain GUIDs from a central authority; the GUID generation algorithm ensures that no two vendors make use of the same GUID. Vendors MAY specify a NULL GUID for the tool extension GUID. Each CSE GUID and tool extension GUID defined by a vendor MUST be treated as a standards assignment to the gPCMachineExtensionNames and gPCUserExtensionNames attributes that MUST be declared in the Group Policy extension documentation that is associated with the CSE GUID and tool extension GUID. Standards Assignments There are no standards assignments for the Group Policy: Core Protocol.
%5BMS-GPOL%5D-150630.docx