7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

  • Windows 10 operating system

  • Windows Server 2016 operating system             

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 2.1: The Windows implementation configures the underlying RPC transport with the RPC_C_AUTHN_LEVEL_PKT_PRIVACY flag.

<2> Section 2.1: In the Windows implementation, the authorization constraints do not vary by operating system (OS) release. All interfaces described in this document require a level of access (both Local Service Launch and Execute) corresponding to any of the of the following Windows security groups:


<3> Section In the Windows implementation, all services that have declared dependencies upon the IIS Admin Service (IISAdmin) will constitute the "Internet services". In Windows Server 2008 operating system, this expands to also include all services that have declared dependencies on the Windows Process Activation service (WAS).

<4> Section In the Windows implementation, the system will use the Service Control Manager (SCM) APIs to request that each service is stopped.

<5> Section In the Windows implementation, this function will start only the services that are considered "Internet services" and are configured with the Service Control Manager (SCM) to start automatically when the computer starts up. The Windows implementation will also use the SCM API to request that the services are started.

<6> Section  Only Windows XP, Windows 2000, Windows NT operating system, and Windows Server 2003 implement this function.  If the server implements this function, then the following rules apply.

The server can have all functionality through this interface disabled using actions taken locally on the server machine. In this case the function returns an error (E_ERROR_RESOURCE_DISABLED) when called and does not perform any other action.

If the interface functionality is not disabled and the function has been implemented, the server restarts.

<7> Section The Windows implementation contains a hard-coded list of processes that support the Internet services. The Windows implementation also has an extension point where the administrator can provide an extra list of processes to terminate when this method is called.