Share via

3.3.5.8.6 Sending a RopSynchronizationOpenCollector ROP Request

  • Article

A client SHOULD upload the initial ICS state, as specified in section 2.2.3.2.2, into the synchronization context returned in the RopSynchronizationOpenCollector ROP (section 2.2.3.2.4.1) response prior to using any RopSynchronizationImport* ROPs. However, the client can elect not to upload the initial ICS state. For details about how that would affect the responsibilities of the protocol roles, see section 3.3.4.3.3.

Be sure to update the stored MetaTagIdsetGiven property (section 2.2.1.1.1) value with internal identifiers of the objects that were imported into the server replica. These identifiers either are returned in the RopSynchronizationImport* ROP responses or can be extracted from GID structures ([MS-OXCDATA] section 2.2.1.3) sent as the input PidTagSourceKey property (section 2.2.1.2.5) values.

For details about the client behavior when receiving a response to this ROP, see section 3.3.5.9.