Partager via

3.1.3 Initialization

  • Article

When the Wireless/Wired \Group Policy Protocol administrative-side plug-in starts, it gets a scoped Group Policy Object (GPO) path from the Group Policy: Core Protocol, as specified in [MS-GPOL]. For each policyClass that it supports, the plug-in SHOULD<36> attempt to use LDAP (as specified in [RFC2251]) to retrieve all existing Wireless/Wired Group Policy Protocol objects by searching for the returned Active Directory objects that are an instance of the class. This Active Directory class MUST be searched under the policyContainerPath that corresponds to the policyType.

To use LDAP, the administrative-side plug-in invokes the "Initialize an ADConnection" task ([MS-ADTS] section 7.6.1.1) with the following parameters and stores the new TaskReturnADConnection returned from the task as the ADConnection Handle (section 3.1.1.1) element:

  • TaskInputTargetName: MAY be specified by the administrator, or if not specified, the joined domain name

  • TaskInputPortNumber: 389

The Wireless/Wired Group Policy Protocol administrative-side plug-in then MUST read protocol-specific policy object data with the format specified in sections 2.2.1 and 2.2.2. Any additional entries in the configuration data that do not pertain to the configuration format specified in sections 2.2.1 and 2.2.2 are not defined by this protocol and MUST NOT be processed. It is recommended that the administrative-side plug-in then display the current policy information to the administrator.

It is recommended that the administrator be informed if this step fails.