[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

The initial Sync request MUST include a CollectionId element (section 2.2.3.29.5), which MUST
always precede the optional Supported element. See the Collection element (section 2.2.3.28.2)
for the order of elements within the Collection node. This order is strictly enforced. A Status
element (section 2.2.3.152.16) value of 4 is returned in the Sync response if the CollectionId
element is not included in the Sync request. A Status element value of 4 is also returned if the
order of elements is incorrect within the Collection node.
0
2
The Supported element MUST be sent in a Sync command request when the SyncKey element
value (section 2.2.3.156.4) is set to 0 (zero). The server caches the list of Supported elements for
subsequent synchronizations. If the Supported element is included when the SyncKey element
value is not set to 0 (zero), no error is returned, but the server ignores the request.
All of the Contact class [MS-ASCNTC] properties can be included as child elements of the
Supported element.
To support elements of the Calendar class [MS-ASCAL], the following required elements MUST be
included as child elements of the Supported element:
•DtStamp ([MS-ASCAL] section 2.2.2.7)
•Categories ([MS-ASCAL] section 2.2.2.17)
•Sensitivity ([MS-ASCAL] section 2.2.2.11)
•BusyStatus ([MS-ASCAL] section 2.2.2.4)
•UID ([MS-ASCAL] section 2.2.2.14)
•Timezone ([MS-ASCAL] section 2.2.2.1)
•StartTime ([MS-ASCAL] section 2.2.2.13)
•Subject ([MS-ASCAL] section 2.2.2.12)
•Location ([MS-ASCAL] section 2.2.2.9)
•EndTime ([MS-ASCAL] section 2.2.2.8)
•Recurrence ([MS-ASCAL] section 2.2.2.18)
•AllDayEvent ([MS-ASCAL] section 2.2.2.2)
•Reminder ([MS-ASCAL] section 2.2.2.10)
[MS-ASCMD] — v20110315
ActiveSync Command Reference Protocol Specification
Copyright © 2011 Microsoft Corporation.
Release: Tuesday, March 15, 2011
242 / 369