[MS-IISS]:
Internet Information Services (IIS) ServiceControl Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
§ Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies.
§ Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications.
§ No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
§ Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
§ Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
§ Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.
Revision Summary
Date / Revision History / Revision Class / Comments /07/20/2007 / 0.1 / Major / MCPP Milestone 5 Initial Availability
09/28/2007 / 0.2 / Minor / Made a change to the IDL.
10/23/2007 / 0.2.1 / Editorial / Revised and edited the technical content.
11/30/2007 / 0.2.2 / Editorial / Revised and edited the technical content.
01/25/2008 / 0.2.3 / Editorial / Revised and edited the technical content.
03/14/2008 / 0.2.4 / Editorial / Revised and edited the technical content.
05/16/2008 / 0.2.5 / Editorial / Revised and edited the technical content.
06/20/2008 / 1.0 / Major / Updated and revised the technical content.
07/25/2008 / 2.0 / Major / Updated and revised the technical content.
08/29/2008 / 2.0.1 / Editorial / Fix capitalization issues.
10/24/2008 / 2.0.2 / Editorial / Revised and edited the technical content.
12/05/2008 / 3.0 / Major / Updated and revised the technical content.
01/16/2009 / 3.0.1 / Editorial / Revised and edited the technical content.
02/27/2009 / 3.0.2 / Editorial / Revised and edited the technical content.
04/10/2009 / 3.0.3 / Editorial / Revised and edited the technical content.
05/22/2009 / 3.0.4 / Editorial / Revised and edited the technical content.
07/02/2009 / 4.0 / Major / Updated and revised the technical content.
08/14/2009 / 4.0.1 / Editorial / Revised and edited the technical content.
09/25/2009 / 4.1 / Minor / Updated the technical content.
11/06/2009 / 4.1.1 / Editorial / Revised and edited the technical content.
12/18/2009 / 4.1.2 / Editorial / Revised and edited the technical content.
01/29/2010 / 4.1.3 / Editorial / Revised and edited the technical content.
03/12/2010 / 4.1.4 / Editorial / Revised and edited the technical content.
04/23/2010 / 4.1.5 / Editorial / Revised and edited the technical content.
06/04/2010 / 4.1.6 / Editorial / Revised and edited the technical content.
07/16/2010 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
08/27/2010 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
10/08/2010 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
11/19/2010 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
01/07/2011 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
02/11/2011 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
03/25/2011 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
05/06/2011 / 4.1.6 / No change / No changes to the meaning, language, or formatting of the technical content.
06/17/2011 / 4.2 / Minor / Clarified the meaning of the technical content.
09/23/2011 / 4.2 / No change / No changes to the meaning, language, or formatting of the technical content.
12/16/2011 / 5.0 / Major / Significantly changed the technical content.
03/30/2012 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
07/12/2012 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
10/25/2012 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
01/31/2013 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
08/08/2013 / 6.0 / Major / Significantly changed the technical content.
2/2
[MS-IISS] — v20130722
Internet Information Services (IIS) ServiceControl Protocol
Copyright © 2013 Microsoft Corporation.
Release: Monday, July 22, 2013
Contents
1 Introduction 5
1.1 Glossary 5
1.2 References 5
1.2.1 Normative References 6
1.2.2 Informative References 6
1.3 Overview 6
1.4 Relationship to Other Protocols 6
1.5 Prerequisites/Preconditions 6
1.6 Applicability Statement 7
1.7 Versioning and Capability Negotiation 7
1.8 Vendor-Extensible Fields 7
1.9 Standards Assignments 7
2 Messages 8
2.1 Transport 8
2.2 Common Data Types 8
2.2.1 SERIALIZED_ENUM_SERVICE_STATUS 8
2.2.2 STATUS_BLOB 9
3 Protocol Details 11
3.1 IIS Service Control Server Details 11
3.1.1 Abstract Data Model 11
3.1.2 Timers 11
3.1.3 Initialization 11
3.1.4 Message Processing Events and Sequencing Rules 11
3.1.4.1 Stop (Opnum 7) 12
3.1.4.2 Start (Opnum 8) 13
3.1.4.3 Reboot (Opnum 9) 14
3.1.4.4 Status (Opnum 10) 15
3.1.4.5 Kill (Opnum 11) 16
3.1.5 Timer Events 17
3.1.6 Other Local Events 17
4 Protocol Examples 18
4.1 Status Method Call Example 18
5 Security 19
5.1 Security Considerations for Implementers 19
5.2 Index of Security Parameters 19
6 Appendix A: Full IDL 20
7 Appendix B: Product Behavior 21
8 Change Tracking 23
9 Index 25
2/2
[MS-IISS] — v20130722
Internet Information Services (IIS) ServiceControl Protocol
Copyright © 2013 Microsoft Corporation.
Release: Monday, July 22, 2013
1 Introduction
This specification defines the Internet Information Services (IIS) ServiceControl Protocol. This protocol is a client-to-server protocol which enables remote control of Internet services as a single unit. The interface can be used to start or stop these services. It also can be used to terminate the service processes or reboot the computer. Lastly, it provides status information about the services.
Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. Sections 1.5 and 1.9 are also normative but cannot contain those terms. All other sections and examples in this specification are informative.
1.1 Glossary
The following terms are defined in [MS-GLOS]:
Distributed Component Object Model (DCOM)
dynamic endpoint
endpoint
Interface Definition Language (IDL)
little-endian
remote procedure call (RPC)
RPC protocol sequence
RPC transport
universally unique identifier (UUID)
The following terms are specific to this document:
graceful stop: Occurs when services are notified to stop and successfully complete that operation, including finishing any outstanding work, within a specified amount of time.
Internet Information Services (IIS): The services provided on the Windows implementation that support web server functionality.
Internet services: A generic term used to refer to a server implementation of processes that support Internet functionality. In the WindowsServer implementations, this refers to a set of Windows NT services that handle protocols such as HTTP, FTP, SMTP, and others.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
References to Microsoft Open Specifications documentation do not include a publishing year because links are to the latest version of the documents, which are updated frequently. References to other documents include a publishing year when one is available.
A reference marked "(Archived)" means that the reference document was either retired and is no longer being maintained or was replaced with a new document that provides current implementation details. We archive our documents online [Windows Protocol].
1.2.1 Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information. Please check the archive site, http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624, as an additional source.
[C706] The Open Group, "DCE 1.1: Remote Procedure Call", C706, August 1997, http://www.opengroup.org/public/pubs/catalog/c706.htm
[MS-DCOM] Microsoft Corporation, "Distributed Component Object Model (DCOM) Remote Protocol".
[MS-DTYP] Microsoft Corporation, "Windows Data Types".
[MS-ERREF] Microsoft Corporation, "Windows Error Codes".
[MS-OAUT] Microsoft Corporation, "OLE Automation Protocol".
[MS-RPCE] Microsoft Corporation, "Remote Procedure Call Protocol Extensions".
[MS-SCMR] Microsoft Corporation, "Service Control Manager Remote Protocol".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc-editor.org/rfc/rfc2119.txt
1.2.2 Informative References
[MS-GLOS] Microsoft Corporation, "Windows Protocols Master Glossary".
1.3 Overview
The IIS ServiceControl Protocol provides a mechanism for remote control of Internet services as a single unit on a server. Through the IIS ServiceControl Protocol, a client can start or stop the services. The client can also terminate processes hosting the Internet services functionality or reboot the computer. Lastly, the client can also retrieve status about the services.
The IIS ServiceControl Protocol is expressed as a set of DCOM interfaces. The server end of the protocol implements support for the DCOM interface to manage the Internet services. The client end of the protocol invokes method calls on the interface to control the services on the server. The DCOM calls use standard DCOM marshaling.
1.4 Relationship to Other Protocols
This protocol depends on the Distributed Component Object Model (DCOM) Remote Protocol, as specified in [MS-DCOM].
1.5 Prerequisites/Preconditions
This protocol requires that the DCOM protocol MUST be implemented on both the client and server computers.
This protocol is implemented over DCOM and RPC and, as a result, has the prerequisites identified in [MS-DCOM] and [MS-RPCE] as being common to DCOM and RPC interfaces.
This protocol specification assumes that any security or authentication associations between the client and server are performed by the DCOM layer.
1.6 Applicability Statement
The IIS ServiceControl Protocol is applicable to remote control Internet services on a server as a single unit.
1.7 Versioning and Capability Negotiation
None.
1.8 Vendor-Extensible Fields
This protocol uses HRESULT values, as specified in [MS-ERREF]. Vendors can define their own HRESULT values, provided they set the C bit (0x20000000) for each vendor-defined value, indicating that the value is a customer code.
1.9 Standards Assignments
Parameter / Value / Reference /RPC interface UUID for IIS ServiceControl Protocol / E8FB8620-588F-11D2-9D61-00C04F79C5FE / None
COM class UUID for IIS ServiceControl Protocol / E8FB8621-588F-11D2-9D61-00C04F79C5FE / None
2 Messages
2.1 Transport
This protocol uses the DCOM protocol, as specified in [MS-DCOM], as its transport. On its behalf, the DCOM protocol uses the following RPC protocol sequence: RPC over TCP, as specified in [MS-RPCE].
This protocol uses RPC dynamic endpoints as specified in [C706] part 4.
To access an interface, the client requests a DCOM connection to its object UUID endpoint on the server, as specified in the Standards Assignments section.
The RPC version number for all interfaces is 0.0.
An implementation of the IIS ServiceControl Protocol SHOULD<1> configure its DCOM implementation or underlying RPC transport with the RPC_C_AUTHN_LEVEL_PKT_PRIVACY authentication flags to restrict client connections. See [C706] and [MS-RPCE] for more information on the meaning of this flag.
The IIS ServiceControl Protocol uses the underlying DCOM security framework (as specified in [MS-DCOM]) for access control. DCOM differentiates between launch and access. An implementation of the IIS ServiceControl Protocol MAY differentiate between launch and access permission, and impose different authorization requirements.<2>
2.2 Common Data Types
This protocol MUST indicate to the RPC runtime that it is to include support for both the NDR20 and NDR64 transfer syntaxes as well as provide the negotiation mechanism for determining which transfer syntax will be used, as specified in [MS-RPCE] section 3.
In addition to RPC base types and definitions specified in [C706] and [MS-DTYP], additional data types are defined as follows.
2.2.1 SERIALIZED_ENUM_SERVICE_STATUS
The SERIALIZED_ENUM_SERVICE_STATUS data structure provides information about the state of the Internet services on a server. It is used by the server to return data to the client in the Status method, as specified in section 3.1.4.4.