3.2.5.1 Software Deployment Retrieval
The procedure described in this section generates the software deployment protocol sequences specified in section 2.2.2. Each of the retrieved PackageRegistration objects MUST undergo applicability filtering. If the syntax of a PackageRegistration object is not valid, the entire object MUST be ignored, and no further protocol sequences are to be generated relating to it.
Given a GPO DN, the following protocol sequences MUST be generated:
The Common LDAP Bind sequence (section 3.2.5.6) MUST be issued.
A software installation container search request message, as defined in section 2.2.2.1, MUST be generated by the client. The corresponding response for this message is as specified in section 2.2.2.2. If the ldapResult status for the response portion of the message is a success status, the sequence MUST continue with step 3. Otherwise, the sequence MUST continue with step 4.
A software installation search request message, as specified in section 2.2.2.3, MUST be generated by the client. The corresponding response for this message is specified in section 2.2.2.4.
The Common LDAP UnBind sequence (section 3.2.5.7) MUST be issued.
For each of the software packages listed in the software deployment list associated with the PolicyTarget for which the policy application is invoked, an attempt MUST be made to match this software package with one of the PackageRegistration objects returned from the previous step. A software package and PackageRegistration object match if the PackageRegistration's objectGUID attribute has the same value as the software package's PackageId state. If no such match can be made for the software package, the client MUST remove the application modeled by the software package if the ACTFLG_Orphan flag is not specified in the packageFlags attribute of the software package.