3.1.5.2.5 Package Obsolescence

Administrators might want to stop a GPO from deploying an application without uninstalling the application from any client on which the GPO had already deployed the application. If specified by an administrator, package obsolescence MUST be accomplished through the following protocol sequence:

  1. The Common LDAP Bind sequence (section 3.2.5.6) MUST be issued.

  2. Mark the package as obsolete. A package update sequence (as specified in section 2.2.3.2.5) MUST be generated by the client with the following attributes:

    • packageFlags MUST have the ACTFLG_Orphan flag set.

    • msiScriptName MUST be "R".

      Information on how this causes the client to remove this application when the policy application mode sequence is invoked is specified in section 3.2.5.3.

      If the resultCode field of the modifyResponse message is non-zero, this protocol sequence MUST proceed to step 3 (LDAP UnBindRequest).

  3. The Common LDAP UnBind sequence (section 3.2.5.7) MUST be issued.