Share via

2.2.3.2.5 Package Update Message

  • Article

This message updates a PackageRegistration object in Active Directory. The LDAP portion of the message MUST be an LDAP modifyRequest message, as specified in [RFC2251].

 Parameter

 Value

object

Software package DN for the PackageRegistration object. This MUST be a DN of the form CN=<PackageId>,CN=Packages,CN=Class Store,<scoped gpo dn>, where <scoped gpo dn> is a scoped GPO DN and <PackageId> is a GUID string, as defined in [RFC4122] section 3.

modification

MUST specify the modifications to be performed as described in the following text.

The modification member is itself a sequence of operations and attribute name and value pairs.

The operation MUST be one of Add, Delete, or Replace as specified in [RFC2251] section 4.6.

The semantics of the attributes are the same as those specified for the PackageRegistration object in section 2.2.2.4.1, Software Installation Search Reply Attributes.

The following additional requirements apply to the attributes in the modification:

  1. The lastUpdateSequence attribute value MUST be present and MUST be set to the current UTC (Coordinated Universal Time) time. The current UTC is read from the clock on the computer issuing the Package Update Message. This attribute's value MUST be specified in USN format.

  2. If any package change is made, the packageFlags attribute MUST be specified as described in section 2.2.2.4.3 packageFlags Attribute Values.

  3. The msiScriptName attribute MUST also be specified for all updates according to the rules in section 2.2.3.2.3.

  4. The objectGUID attribute MUST NOT be specified in the attributes field.

  5. The msiFileList attribute MUST NOT be specified in the attributes field. This field is specified only as part of the package creation message. That is, it is an invariant of a given package.

  6. The msiScriptPath attribute MUST NOT be specified in the attributes field.

The remote file access portion of the message MUST be an application advertise script file. This part of the message is optional if the file already exists in the GPO. The file needs to be updated only in certain circumstances, as specified in section 3.1.5.2.2.