locked
MSDN Exchange Server Protocols Release Notes — August 2011 RRS feed

  • General discussion

  • The August 2011 release contains updates made to Microsoft Exchange Server Protocols documents since the March 2011 refresh. The August 2011 release also contains updates made to the Microsoft Exchange Server and Outlook Standards since the November 2010 refresh.

    Exchange 2010 Protocols links:

    Exchange 2010 and Outlook 2010 Standards links:

    The following new specification was added to the Exchange 2010 Protocols documents:

    • [MS-OXNSPI]: Exchange Server Name Service Provider Interface (NSPI) Protocol Specification –This document specifies the Microsoft Exchange Server implementation of the Name Service Provider Interface (NSPI) Protocol, which is used by Messaging API (MAPI) clients to access the directory service

    The following Exchange 2010 Protocols document titles were changed:

    • The title of [MS-OXBBODY] was changed from [MS-OXBBODY]: Best Body Retrieval Protocol Specification to [MS-OXBBODY]: Best Body Retrieval Algorithm.
    • The title of [MS-OXCMAIL] was changed from [MS-OXCMAIL]: RFC2822 and MIME to E-Mail Object Conversion Protocol Specification to [MS-OXCMAIL]: RFC2822 and MIME to E-Mail Object Conversion Algorithm.
    • The title of [MS-OXOSMIME] was changed from [MS-OXOSMIME]: S/MIME E-Mail Object Protocol Specification to [MS-OXOSMIME]: S/MIME E-Mail Object Algorithm.
    • The title of [MS-OXPSVAL] was changed from [MS-OXPSVAL]: E-Mail Postmark Validation Protocol Specification to [MS-OXPSVAL]: E-Mail Postmark Validation Algorithm.
    • The title of [MS-OXRTFCP] was changed from [MS-OXRTFCP]: Rich Text Format (RTF) Compression Protocol Specification to [MS-OXRTFCP]: Rich Text Format (RTF) Compression Algorithm.
    • The title of [MS-OXRTFEX] was changed from [MS-OXRTFEX]: Rich Text Format (RTF) Extensions Specification to [MS-OXRTFEX]: Rich Text Format (RTF) Extensions Algorithm.
    • The title of [MS-OXVCARD] was changed from [MS-OXVCARD]: vCard to Contact Object Conversion Protocol Specification to [MS-OXVCARD]: vCard to Contact Object Conversion Algorithm.
    • The title of [MS-OXWSXPROP] was changed from [MS-OXWSXPROP]: Extended Properties Web Service Protocol Specification to [MS-OXWSXPROP]: Extended Properties Structure.

    The following documents were removed from the documentation set and added to the Historical Document Repository:

    • None for this release cycle

    As a reminder, the following WebDav protocols were deprecated from Exchange 2010 (in November 2009):

    • [MS-XWDCAL]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Calendar Support
    • [MS-XWDCNTC]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Contacts Support
    • [MS-XWDDOC]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Documents Support
    • [MS-XWDEXT]: Web Distributed Authoring and Versioning (WebDAV) Core Extensions
    • [MS-XWDFOLD]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Folders Support
    • [MS-XWDMAIL]: Web Distributed Authoring and Versioning (WebDAV) Extensions for E-Mail Support
    • [MS-XWDNOTIF]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Notifications
    • [MS-XWDREPL]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Replication
    • [MS-XWDSEARCH]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Search
    • [MS-XWDSTRUCTDOC]: Web Distributed Authoring and Versioning (WebDAV) Extensions for Structured Documents
    • [MS-XWDVSEC]: Web Distributed Authoring and Versioning (WebDAV) Protocol Security Descriptor Extensions

    The following change was applied in the August 2011 release:

    1. Document dates have been removed from the Internal References section in [MS-OXREF].

    The following known issues exist in the August 2011 release:

    1. Underscore characters are not always visible in code in the PDF files depending on the magnification selected by the user. Those characters are present in printed versions.
    2. Information in a table row may split across two pages.
    3. Table borders are not always visible depending upon the magnification selected by the user. Borders are present in printed versions of the PDF.
    4. Cross-protocol links are only functional when the PDF files for the protocols are in the same folder.
    5. For optimal readability of the PDF documents, we recommend that they be opened and viewed by using Adobe Reader 10.0.
    6. Links in the PDFs don’t resolve in Adobe Reader 9 because Adobe has changed the default setting for view mode in Adobe Reader 9.
      To access links, perform the following procedure:
      1. In Adobe Reader 9, go to the Edit menu and click Preferences.
      2. In the Categories list, click Documents.
      3. Under PDF/A View Mode, change the selection from Only for PDF/A documents to Never, and click OK.
        Additional details on changing the setting can be located via the Adobe help site: http://help.adobe.com/en_US/Acrobat/9.0/Standard/WS3E0E8467-B787-4020-A1D3-6BC762A42DF2.w.html
    Friday, August 5, 2011 6:38 PM
    Moderator