Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.01 Initial Availability 6/27/2008 1.0 Minor Revised and edited technical content 10/6/2008 1.01 Editorial Revised and edited technical content 12/12/2008 1.02 Editorial Revised and edited technical content 7/13/2009 1.03 Major Revised and edited the technical content 8/28/2009 1.04 Editorial Revised and edited the technical content 11/6/2009 1.05 Editorial Revised and edited the technical content 2/19/2010 2.0 Major Updated and revised the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Major Updated and revised the technical content 6/7/2010 2.03 Editorial Revised and edited the technical content 6/29/2010 2.04 Editorial Changed language and formatting
in the technical content. 7/23/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 8/26/2010 2.05 Minor Clarified the meaning of the technical content. 9/27/2010 2.06 Minor Clarified the meaning of the technical content. 11/15/2010 2.06 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 2.06 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 2.7 Minor Clarified the meaning of the technical content. 6/10/2011 2.7 None No changes to the meaning, language, or formatting of the technical content.
1/20/2012 2.8 Minor Clarified the meaning of the technical content. 4/11/2012 2.8 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.9 Clarified the meaning of the technical content. 10/8/2012 2.10 Clarified the meaning of the technical content. 2/11/2013 2.11 Minor Clarified the meaning of the technical content. 7/30/2013 2.11 None No changes to the meaning, language, or formatting of the technical content. 11/18/2013 2.12 Minor Clarified the meaning of the technical content. 2/10/2014 2.12 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 3.0 Major Significantly changed
the technical content. 7/31/2014 4.0 Major Significantly changed the technical content. 10/30/2014 5.0 Major Significantly changed the technical content. 9/4/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/15/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/22/2016 5.0 None No changes to the meaning, language, or formatting of the technical content.
When it receives a response to an HTTP OPTIONS request, an Office 2013, Office 2010, or the 2007 Office system protocol client checks for the presence of the DocumentManagementServer header in the response. If the header exists, the protocol client automatically enables the following features and does not assume that the protocol server supports these features: Document recovery Workflow To support workflow, the protocol server to return data by using the Workflow Web Service Protocol, as described in . An Office 2003 protocol client does not check for the DocumentManagementServer header in the response and does not enable these features. Version History By default, version history features are enabled in a protocol client only if a protocol server response contains the correct header and header In addition, version history features work correctly in a protocol client only if the protocol server supports the FrontPage Server Extensions Web Site Management Protocol, as described in . The following table describes additional conditions in which a protocol client enables version history features. Protocol client version MicrosoftSharePointTeamServices OPTIONS header DocumentManagementServer OPTIONS header Enabled Office 2003 Exists Any (exists or not) - not checked Yes The 2007 Microsoft Office system Exists and contains no value or a value that is less than "12" Any (exists or not) Yes The 2007 Office system Any (exists or not) Exists and contains the value "Version History" Yes Microsoft Office 2010 suites Exists and contains no value or a value that is less than "12" Any (exists or not) Yes Office 2010 Any (exists or not) Exists and contains the "Version History" Yes Office 2013 Exists and contains no value or a value that is less than "12" Any (exists or not) Yes Office 2013 Any (exists or not) Exists and contains the value "Version History" Yes In and Check Out
Office 2003 Does not apply Does not apply Not supported The 2007 Office system Exists and contains a value that is greater than "12" Does not Yes The 2007 Office system Does not Exists and contains the value "Properties Schema" Yes Office 2010 Exists and contains a value that is greater than "12" Does not Yes Office 2010 Does not apply Exists and contains the value "Properties Schema" Yes Office 2013 Exists and contains a value that is greater than "12" Does not Yes Office 2013 Does not apply Exists and contains the value "Properties Schema" Yes If the integrated property panel cannot be enabled because the preceding conditions cannot be met, a Web-form property panel can be used instead. The Web-form property panel is a Web that is displayed in a protocol client, typically when a document is saved to a protocol server for the first time by using a protocol client. By default, the Web-form property panel is enabled only if a protocol server response contains the correct header and header value. In addition, it works correctly only if the protocol server supports use of the FrontPage Server Extensions Web Site Management Protocol, as described in , to retrieve and set document properties. The following describes additional conditions in which a protocol client enables the Web-form property panel. Protocol client version MicrosoftOfficeWebServer OPTIONS header Integrated property panel Web-form property Office 2003 Exists and contains the value "5.0_Collab" Does not apply Yes The 2007 Office system Exists and contains the "5.0_Collab" Not enabled by the preceding conditions Yes Office 2010 Exists and contains the value "5.0_Collab" Not enabled by the preceding conditions Yes Office 2013 Exists and contains the value "5.0_Collab" Not enabled by the preceding conditions Yes
HTTP Authentication: Basic and Digest Access Authentication Defines an authentication (2) scheme that can be used to verify that both parties to a communication know a shared secret (password). If Digest Access Authentication is used, this verification can be done without sending a password as cleartext. [RFC2617] Kerberos Protocol Extensions Extends the Kerberos Network Authentication Service (V5) protocol, as described in . These extensions provide additional capabilities for authorization information, including group memberships, interactive logon information and integrity levels, and constrained delegation and encryption supported by . NT LAN Manager (NTLM) Authentication Protocol Provided by the Windows operating system, enables authentication between protocol clients and protocol servers when the Kerberos Protocol Extensions, as described in [MS-KILE], cannot be used. In Windows Server 2008 operating system with Service Pack 2 (SP2), Windows Vista, Windows Server 2003, Windows XP, and Windows 2000 Server operating system, Kerberos authentication replaces as the preferred authentication protocol. Office Forms Based Authentication Protocol Implemented by the Office system, establishes a user’s identity by using HTTP-based forms authentication when other authentication mechanisms are not available. Passport Server Side Include (SSI) Version 1.4 Protocol An protocol that enables protocol clients to authenticate to a partner server with the assistance of an authentication (2) server. Also referred to as the "Passport Tweener" protocol. Simple and Protected Negotiation Mechanism (SPNEGO) Extensions Defines a negotiation mechanism for the Generic Security Service Application Program Interface as described in . SPNEGO provides a framework for two parties that are engaged in authentication (2) to select from a set of possible authentication (2) mechanisms, in a manner that preserves the opaque nature of the security protocols to the application protocol that uses SPNEGO. SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows Provided by Windows 2000 operating system, enhances the security of Web-based transactions by using Kerberos. File Access Protocols in this table enable protocol clients in the Office system to access files in local and remote locations. Protocol name Description Short name
FrontPage Server Extensions Website Management Protocol Provides a set of methods that enables users to upload, download, lock, and move files, and to create directories and listings on a protocol server by using protocol clients. HTTP Extensions for Distributed Authoring -- WebDAV Extends the Protocol by providing a set of methods and defining headers and body formats for messages. These extensions enable users to create, query, and manage resources on a Web server by using protocol clients. Hypertext Transfer Protocol -- HTTP/1.1 An protocol for distributed, collaborative, and hypermedia information systems. It is a generic, stateless, protocol that can be used for many tasks, including file access. If other protocols are not supported, protocol clients use the HTTP GET method that is defined by this protocol to provide users with read-only access to files.
Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions Provides a set of extensions to WebDAV. extensions are implemented in all versions of Windows SharePoint Services and are therefore used during interactions between protocol clients and protocol servers that are running a version of Windows SharePoint Services. Most of the extensions are designed to enhance support for authoring and managing documents that are stored on a protocol server. For example, a protocol server can use these extensions to indicate whether it supports various capabilities for document management through other protocols based on the value of a Document Management Server header.
Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions Extends WebDAV, as described in [RFC2518], by introducing new headers that enable protocol servers to support management of additional file types and to optimize processing and related interactions with supporting protocol clients. Windows SharePoint Services Collaborative Application Protocol Enables communications between protocol clients and a to retrieve and manipulate various types of content that is stored on a protocol server. Document Management Protocols in this table enable protocol clients in the Office system to perform document management operations such as checking files in or out, and displaying and saving document properties. Protocol name Description Short name Document Workspace Web Service Protocol Defines operations for creating, editing, and deleting files, folders, and on a Document Workspace site by using the Document Management task pane in a protocol client. FrontPage Server Extensions Remote Protocol Defines operations for accessing, checking in, and checking out files that are stored on a protocol server.
Corporate Error Reporting Version 1.0 Protocol protocol used by Windows XP and Windows Server 2003 clients that allows components to send user mode and kernel mode error reports to a corporation's servers instead of to Microsoft servers. The reports are stored on a configurable shared folder location. This protocol uses SMB as a transport. All versions of the Windows operating system implement configurations, but the CER tool is required to implement the full range of server-side configuration options. The CER tool is available only under the software assurance application. side
PowerPoint Web Viewer Presentation Data Protocol This protocol enables a protocol client to send a request to retrieve presentation content from the protocol server. To facilitate this, the protocol allows the protocol client to request specific pieces of content from a presentation stored on the protocol server. In a presentation contained within a presentation, a protocol client can retrieve information describing the presentation slide contents as well as images of the presentation slide contents. The following describes the protocols used by PowerPoint 2010 and PowerPoint Online for creating and viewing a broadcast slide show. Protocol name Description Short name PowerPoint Web Broadcast Discovery Protocol This protocol enables a protocol client to send a request containing client information to the protocol server and then receive information about the endpoint (2) that is most suited for future communication with the protocol client. The protocol server uses the information provided by the protocol client such as the list of supported protocol versions to decide a suitable .
PowerPoint Web Viewer Rendered Static Content Structure A presentation consists of slides, pictures, and other content. A protocol client can use the Office Mobile PowerPoint Web Handler Protocol [MS-OMPWHP] to request specific pieces of presentation content stored on a protocol server. This structure specifies a set of data types that enable the transfer of such presentation content. It also specifies data types that encapsulate error information that enables the protocol server to signal the protocol client that it is unable to serve specific requests. Office Broadcast Presentation Service The following table describes the protocols used by the Office Broadcast Presentation Service<4>. Protocol name Description Short name Office Broadcast Presentation Service This protocol enables a protocol client to send requests to a protocol server allowing the client to begin or end a document broadcast session, and to store data about the state of a broadcast session on the protocol server. Office Broadcast Participant Service This protocol enables a protocol client to send requests to a protocol server allowing the client to join an document broadcast session, and to retrieve data about the state of a broadcast session on the protocol server. Web Application Open Platform Interface The following table describes the protocols used by the Web Application Open Platform Interface (WOPI)<5>. Protocol name Description name Web Application Open Platform Interface Protocol This protocol defines a set of operations that enables a client to access and change files stored by a protocol server, allowing the client to render files and provide file editing functionality. Apps for Office The following table describes the structure used by Office Add-ins. Protocol name Description Short name Office Web Extensibility Manifest Format This structure specifies the schema for Office Add-ins manifest files.
Index A Access 28 41 Active Directory communications 23 37 ActiveX controls 24 24 60 32 Apps for Office 45 16 47 47 47 Authenticate against a web server that is by forms authentication 48 Authentication 46 46 16 33 C 60 72 Check out and check in a document 63 Client/server protocols 47 60 45 16 Considerations 60 60 Customer Experience Improvement Program 24 38 D Data access 46 23 36 Dependencies – on other systems 46 47 Dependencies – on this system 46 46 46 46 46 46 Design intent 48 49 59 51 50 47 56 55 53 59 54 53 57 52 58 51 57 Document management 46 19 35 Download a document from a web server 49 E 45 60 Error reporting 24 37 Examples 63 61 67 65 69 66 Excel 27 39 Extensibility 71 60 F File access 46 16 33 16 16 G 7 Groove 31 H
60 I IMESync Structure 38 71 60 InfoPath 29 42 12 47 7 M 37 71 Microsoft InfoPath 29 Microsoft Office Access 28 41 Microsoft Office Excel 27 39 Microsoft Office Groove 31 Microsoft Office InfoPath 42 Microsoft Office OneNote 41 Microsoft Office Outlook 43 Microsoft Office PowerPoint 39 Microsoft Office Publisher 29 Microsoft Office Word 26 38 Microsoft OneNote 28 Microsoft Outlook 30 Microsoft PowerPoint 27 Microsoft SharePoint Workspace 31 Mobility 47 47 46 31 44 O Office broadcast presentation service 45 OneNote 28 41 Open a document by using an activex control 51 Open a historical version of a file from a web server 50 Open document from Web server gated by forms authentication 61 Outlook 30 43 Overview 23 24 16 24 23 19 16 24 29 28 27 31 29 26 28 30 27 31 31 23 32 16 P PowerPoint 27 39 47 47 47 24 Protocol discovery and feature activation – overview 19 16 32 41 37 45 33 38 36 35 39 33 38 42 37 44 45 41 43 39 36
45 38 Publish a browser-enabled form template to the server 56 Publish a non-browser-enabled form template to the server 55 Publish an access database application to a web server 53 Publish an excel workbook to a sharepoint library 59 Publish an infopath form to a server 54 Publisher 29 R Receive e-mail alerts in outlook from a sharepoint server 53 12 Requirements 60 60 16 47 Rights management 46 23 36 S 60 SharePoint Workspace 31 Start a broadcast slide show 67 57 Synchronize a sharepoint list with outlook 65 52 Synchronize ime with a remote list 69 58 16 45 60 32 16 System use cases 48 49 59 51 50 47 56 55 53 59 54 53 57 52 58 51 57 T 32 72 U 47 48 49 59 51 50 56 55 53 59 54 53 57 52 58 51 57 Use information rights management 51 V Versioning 71 60 View first slide of presentation in a Web browser 66 View the first slide of a broadcast presentation in a web browser 57 W Web application open platform interface 45 Word 26 38