11.01.2015 Views

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

1.2.2 Informative <strong>Reference</strong>s<br />

[<strong>MS</strong>DN-ADDP] Microsoft Corporation, "Establishing an <strong>ActiveSync</strong> Desktop-Device Partnership",<br />

August 2008, http://msdn2.microsoft.com/en-us/library/ms972959.aspx#monitor_perf_topic8<br />

[<strong>MS</strong>FT-AUTODISCOVER] Masterson, J., Turick, J., Smith IV, R., "White Paper: Exchange 2007<br />

Autodiscover Service", November 2007,<br />

http://www.microsoft.com/downloads/details.aspxFamilyID=DD422B8D-FF06-4207-B476-<br />

6B5396A18A2B<br />

[<strong>MS</strong>FT-DNS-SRV] Microsoft Corporation, "A new feature is available that enables Outlook 2007 to<br />

use DNS Service Location (SRV) records to locate the Exchange Autodiscover service", August 2007,<br />

http://support.microsoft.com/kbid=940881<br />

[<strong>MS</strong>-GLOS] Microsoft Corporation, "Windows <strong>Protocol</strong>s Master Glossary", March 2007.<br />

[<strong>MS</strong>-OXGLOS] Microsoft Corporation, "Exchange Server <strong>Protocol</strong>s Master Glossary", April 2008.<br />

[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer <strong>Protocol</strong> -- HTTP/1.1", RFC<br />

2616, June 1999, http://www.ietf.org/rfc/rfc2616.txt<br />

1.3 Overview<br />

This protocol consists of a set of XML-based commands that are used by a client device to<br />

synchronize and exchange its e-mail, files, and data with a server.<br />

The client first uses the Autodiscover command (section 2.2.2.1) to get a user's account<br />

configuration. The client can then view and modify server data related to that account, including e-<br />

mail messages and attachments, folders, contacts, and calendar requests.<br />

The client then uses the Provision command (section 2.2.2.12) to send device information to the<br />

server and to get and subsequently acknowledge security policy settings from the server. Next, the<br />

client uses the FolderSync command (section 2.2.2.4) to retrieve the folder hierarchy of the user.<br />

Next, the client typically uses the GetItemEstimate command (section 2.2.2.7) to retrieve the<br />

number of changes that need to be downloaded to the client via the first Sync command (section<br />

2.2.2.19) request. This is immediately followed by the Sync command, to get a synchronization key<br />

and then messages from the server. Optionally, the Ping command (section 2.2.2.11) or hanging<br />

Sync command can then be issued to keep the device up-to-date on any server changes.<br />

The client processes outgoing e-mail using the SendMail (section 2.2.2.15), SmartReply (section<br />

2.2.2.18), and SmartForward (section 2.2.2.17) commands. For incoming messages, the client can<br />

call the ItemOperations command (section 2.2.2.8) to fetch the message, and then use the<br />

MoveItems command (section 2.2.2.10). S/MIME messages are processed with the<br />

ResolveRecipients (section 2.2.2.13) and ValidateCert (section 2.2.2.20) commands.<br />

The client uses the FolderSync, FolderCreate (section 2.2.2.2), FolderUpdate (section 2.2.2.5),<br />

and FolderDelete (section 2.2.2.3) commands to update, create, and delete mailbox folders on<br />

the server.<br />

For meeting requests, the client uses the MeetingResponse command (section 2.2.2.9).<br />

The client can set and request server parameters by using the Settings command (section<br />

2.2.2.16).<br />

The client uses the Search command (section 2.2.2.14) to find particular items on the server.<br />

[<strong>MS</strong>-<strong>ASCMD</strong>] — v20110315<br />

<strong>ActiveSync</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Protocol</strong> <strong>Specification</strong><br />

Copyright © 2011 Microsoft Corporation.<br />

Release: Tuesday, March 15, 2011<br />

18 / 369

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!