Share via

7 Appendix B: Product Behavior

  • Article

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

  • Windows Server 2003 R2 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates 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 1.3: Windows Server 2003 R2 clients and servers implement a subset of the WS-Management Protocol as specified in [DMTF-DSP0226], WS-Management CIM Binding as specified in [DMTF-DSP0227], and WS-CIM Mapping as specified in [DMTF-DSP0230]; specifications defined not by the published specifications, but by prerelease drafts of those specifications.

<2> Section 1.3: Windows Server 2003 R2 servers support retrieval and update of existing CIM instances but do not support creation of new CIM instances or deletion of existing CIM instances.

<3> Section 1.3: Windows Server 2003 R2 servers support two resource providers:

  • The CIM resource provider, which handles CIM-related requests. The GUID of the CIM resource provider is D9A2A039-A4B3-4A70-8CB9-8D7714EAD776.

  • The Configuration resource provider, which handles configuration-related requests. The GUID of the Configuration resource provider is FCBE098D-64C7-4b07-BB5B-748DBEC256A3.

<4> Section 1.7: Windows Server 2003 R2 servers do not support Identity requests. Instead, they provide the ability to retrieve the version of the protocol using a Get request on a specific resource URI, which is described in section 3.1.4.1.22 of this specification.

<5> Section 2.2.4.4: Web Services Management Protocol Extensions for Windows Server 2003 client and server support the security profiles mentioned in section 5. When using any of these profiles, the client can preauthenticate to the Web Services Management Protocol Extensions for Windows Server 2003 server. In this case, after the connection between the client and server is established, the client sends the Authentication header to the server. If the server supports the authentication scheme, the server can respond with HTTP status code 200 (OK) to indicate success.

<6> Section 2.2.4.12: Windows Server 2003 R2 servers use the following string for the Vendor element: Microsoft Corporation.

<7> Section 2.2.4.12: Windows Server 2003 R2 servers use the following format to describe the version: OS: d.d.d SP: d.d Stack: d.d, where d is a 32-bit unsigned integer. For example, OS: 5.2.3790 SP: 1.0 Stack: 1.0.

  • OS: The major and minor version numbers of the operating system.

  • SP: The service pack installed on the machine.

  • Stack: A version number that identifies which version of the WS-Management stack implementation is running.

<8> Section 3.1.4.1.9: Windows Server 2003 R2 servers use a default value for the MaxEnvelopeSize value to the value of the MaxEnvelopeSizekb configuration setting multiplied by 1,024 if no MaxEnvelopeSize value is specified by the client or if the MaxEnvelopeSize value is more than this setting.

<9> Section 3.1.4.1.13: Windows Server 2003 R2 clients can be configured to send Enumerate requests with the wsman:Filter element. Windows Server 2003 R2 servers do not support any filtering dialects.

<10> Section 3.1.4.1.22: Windows Server 2003 R2 servers use the following string for the Vendor element: Microsoft Corporation.

<11> Section 3.1.4.1.22: Windows Server 2003 R2 servers use the following format to describe the version: OS: d.d.d SP: d.d Stack: d.d, where d is a 32-bit unsigned integer. For example, OS: 5.2.3790 SP: 1.0 Stack: 1.0.

  •  OS: The major and minor version numbers of the operating system

  • SP: The service pack installed on the machine

  • Stack: A version number that identifies which version of the WS-Management stack implementation is running.

<12> Section 3.1.4.1.29: Windows Server 2003 R2 servers only accept user names to local accounts when using Basic.

<13> Section 3.1.4.1.29: Windows Server 2003 R2 servers do not support authentication using Digest. If a client application sends a request using the Digest scheme, the request will fail with an error.

<14> Section 3.1.4.1.29: Windows Server 2003 R2 servers only accept user names to local accounts when using Basic.

<15> Section 3.1.4.1.29: Windows Server 2003 R2 servers do not support authentication using Digest. If a client application sends a request using the Digest scheme, the request fails with an error.

<16> Section 3.2.4.1.6: All Windows clients ensure that in a Pull request, the value of MaxElements lies within the specified range.

<17> Section 3.2.4.1.13: Windows Server 2003 R2 clients remove the cim:Location element when requesting a Put operation following a Get operation on an object.

<18> Section 5.1: Windows Server 2003 R2 clients remove the cim:Location element when requesting a Put operation following a Get operation on an object.