7 Appendix B: Product Behavior

The information in this specification is applicable to the following product versions:

  • Windows Server® 2003 R2 operating system

  • Windows Vista® operating system with Service Pack 1 (SP1)

  • Windows Server® 2008 operating system

  • Windows® 7 operating system

  • Windows Server® 2008 R2 operating system

Exceptions, if any, are noted below. If a service pack number appears with the product version, behavior changed in that service pack. The new behavior also applies to subsequent service packs of the product unless otherwise specified.

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

<1> Section 1.3: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support retrieval and update of existing CIM Instances but do not support creation of new CIM Instances or deletion of existing CIM Instances.

<2> Section 1.3: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support the following 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.

  • Event Forwarding resource provider.

  • Text-based Command Shell resource provider.

<3> Section 1.3: Windows Server 2003 R2 with update KB936059, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support these additional features:

  • Client Certification: Allows a non-domain based authentication mechanism. In this scenario, multiple client certificates can be mapped to a single account using pattern matching rules.

  • Publisher-initiated event subscription: Allows the publisher (source) of the event to initiate the event subscription process.

  • Custom Remote Shell: Allows custom Shells to be configured, manipulated and invoked, besides Windows Command Shell.

  • Selector Filter Dialect: Allows the use of Selector Filter Dialect for enumeration of resources, as defined by [DMTF-DSP0226] Appendix C.

  • Enumeration optimization: Allows the clients to optimize the number of round trips required to enumerate the items in an enumerate request.

<4> Section 1.7: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support Identity requests, as specified in [DMTF-DSP0226] section 2.1.1.

<5> Section 2.2.1.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 return error codes that can be either (a) Win32 error codes whose values are taken from the Windows error number space defined in [MS-ERREF], or (b) application-specific error codes whose meaning must be determined from out-of-band means such as application documentation.

<6> Section 2.2.1.1: Windows Server 2003 R2 with KB936059, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 return an empty string as the value for the Machine element as part of the fault detail, except when the client and service are on the same computer.

<7> Section 2.2.1.1: Windows Server 2003 R2 with KB936059, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 do not return a providerId element as part of the fault detail.

<8> Section 2.2.2.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not support negative time stamps, which are cim:cimDateTime values that start with a dash ('-').

<9> Section 2.2.3: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not use this element.

<10> Section 2.2.3.7: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 return an ExitCode element (with the exit code of the command) when there is no error. No ExitCode element is returned when an error occurs.

<11> Section 2.2.4.1.1: Windows Server 2003 R2 Enterprise Edition, Windows Vista SP1, and Windows Server 2008 allow a minimum value of 1 for MaxProviderRequests. Windows 7 and Windows Server 2008 R2 allow a minimum value of 4294967295 (which is also used as the default value).

<12> Section 2.2.4.1.1: Windows 7 and Windows Server 2008 R2 ignore this value; if an attempt is made to modify this value on Windows 7 or Windows Server 2008 R2, a SOAP fault is returned.

<13> Section 2.2.4.2.2: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not include the "CredSSP" element in the ClientAuthType schema.

<14> Section 2.2.4.3.1: Windows Server 2003 R2 Enterprise Edition, Windows Vista SP1, and Windows Server 2008 allow a minimum value of 1 for MaxConcurrentOperations. Windows 7 and Windows Server 2008 R2 allow a minimum value of 4294967295 (which is also used as the default value).

<15> Section 2.2.4.3.1: Windows Server 2003 R2 Enterprise Edition, Windows Vista SP1, and Windows Server 2008 use this value when processing messages. Windows 7 and Windows Server 2008 R2 ignore this value; if an attempt is made to modify this value on Windows 7 or Windows Server 2008 R2, a SOAP fault is returned.

<16> Section 2.2.4.3.1: On Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008, when the value of MaxConnections is decreased, there is a chance that the server will stop responding to all incoming requests until it is restarted.

<17> Section 2.2.4.3.2: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not include the "CredSSP" element or the "CbtHardeningLevel" element in the ServiceAuthType schema.

<18> Section 2.2.4.3.5: Windows Server 2003 R2, Windows Vista SP1 and Windows Server 2008, Windows 7 and Windows Server 2008 R2 support client certificates.

<19> Section 2.2.5.1: Windows 7 and Windows Server 2008 R2 enforce a minimum value of 60000 milliseconds for IdleTimeout. If any value from 1 to 59999 is specified, the service will behave just as if 60000 had been specified

<20> Section 2.2.5.1: Windows Server 2003 R2 Enterprise Edition, Windows Vista SP1, and Windows Server 2008 allow a minimum value of 0 for MaxShellRunTime. Windows 7 and Windows Server 2008 R2 allow a minimum value of 0x7FFFFFFF (which is also used as the default value).

<21> Section 2.2.5.1: Windows Server 2003 R2 Enterprise Edition, Windows Vista SP1, and Windows Server 2008 terminate the command in progress if it takes longer than the specified amount of time. Windows 7 and Windows Server 2008 R2 ignore this value; if an attempt is made to modify this value on Windows 7 or Windows Server 2008 R2, an error is returned.

<22> Section 2.2.5.2: Windows XP SP2, Windows Server 2003 with SP1, Windows Server 2003 SP2, Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 support the use of Custom Remote Shell. Windows 7 and Windows Server 2008 R2 do not support the use of Custom Remote Shell; if an operation is issued to the resource URI http://schemas.microsoft.com/wbem/wsman/1/config/winrs/customremoteshell, an error is returned.

<23> Section 2.2.6.3: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not support the CredSSPEncryptedMessage message type.

<24> Section 2.2.8: Windows Server 2003 R2 with update KB936059 Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support publisher-initiated event subscription.

<25> Section 2.2.10: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support only the issuer role.

<26> Section 3.1.5.1.5: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 accept any MessageID format.

<27> Section 3.1.5.1.7: Windows Server 2003 R2 does not support nonzero year and nonzero month values in the OperationTimeout field unless update KB96059 is installed.

<28> Section 3.1.5.1.10: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not send the wsman:DataLocale header in either request messages or response messages.

Windows 7 and Windows Server 2008 R2 send the wsman:DataLocale header in request messages but do not send it in response messages.

<29> Section 3.1.5.1.10: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 return a fault if the wsman:DataLocale header is received in a response message.

<30> Section 3.1.5.1.11: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 return a wsman:InvalidOptions fault if the wsman:OptionSet element contains a wsman:Option element with mustComply="true" for which the option is not supported for the ResourceURI and operation, as specified in [DMTF-DSP0226].

<31> Section 3.1.5.1.12: Windows Server 2003 R2 ignores the RequestEPR header unless mustUnderstand="true", in which case they will return a s:NotUnderstood fault as specified by [SOAP1.2-1/2003]. It does not ignore this header when update KB936059 is installed.

<32> Section 3.1.5.1.13: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not send the wsman:ActivityId header.

<33> Section 3.1.5.1.13: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 return a fault if the wsman:ActivityId header is received in a response message.

<34> Section 3.1.5.2.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not include the XMLNS in results when the select statement is of the form "select a, b, c from ..."

<35> Section 3.1.5.2.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 return the selected elements in alphabetical order.

<36> Section 3.1.5.2.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not include the wsmb:Expression element in responses.

<37> Section 3.1.5.2.3: Windows Server 2003 R2 ignores the RequestTotalItemsCountEstimate header if the update KB936059 is not installed.

<38> Section 3.1.5.2.4: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support the OptimizeEnumeration element.

<39> Section 3.1.5.2.6.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support Selector Filter Dialect as specified by [DMTF-DSP0226] Appendix C.

<40> Section 3.1.5.3.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 return a was:ActionNotSupported fault or a wsman:FilteringNotSupported fault.

<41> Section 3.1.5.4.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not reject requests and reply with an error response when the number of concurrent requests exceeds the MaxConnections configuration setting. Instead, the outstanding requests are queued until the number of current requests drops below MaxConnections, at which time the outstanding requests are processed.

<42> Section 3.1.5.4.3: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 use the URI prefix http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail for fault detail.

<43> Section 3.1.5.4.4: Windows XP SP2, Windows Server 2003, Windows Server 2003 with SP1, Windows Server 2003 SP2, Windows Server 2003 R2, Windows Vista, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 use the following string for the Vendor element: Microsoft Corporation.

Windows XP SP2, Windows Server 2003, Windows Server 2003 with SP1, Windows Server 2003 SP2, Windows Server 2003 R2, Windows Vista, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 use the following format for the ProductVersion element when the Identify request is authenticated (where d is a 32-bit unsigned integer. For example: OS: 5.2.3790 SP: 1.0 Stack: 1.0):

OS: d.d.d SP: d.d Stack: d.d

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

SP: The service pack installed on the computer.

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

<44> Section 3.1.5.4.4: Windows XP SP2, Windows Server 2003, Windows Server 2003 with SP1, Windows Server 2003 SP2, Windows Server 2003 R2, Windows Vista, Windows Vista SP1, and Windows Server 2008 use the following format for the ProductVersion element when the Identify request is unauthenticated and the WSMANIDENTIFY HTTP header is present.

OS: 0.0.0000 SP: 0.0 Stack: 1.1

Windows 7 and Windows Server 2008 R2 use the following format for the ProductVersion element when the Identify request is unauthenticated and the WSMANIDENTIFY HTTP header is present.

OS: 0.0.0000 SP: 0.0 Stack: 2.0

<45> Section 3.1.5.5.3.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 only accept user names to local accounts when using Basic or Negotiate.

<46> Section 3.1.5.5.3.2: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not support Put operations on the http://schemas.microsoft.com/wbem/wsman/1/config/service/defaultports resource URI.

<47> Section 3.1.5.5.3.4: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not support the http://schemas.microsoft.com/wbem/wsman/1/config/service/security resource URI.

<48> Section 3.1.5.5.6: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 use the resource URI http://schemas.microsoft.com/wbem/wsman/1/config/winrs/customremoteshell to manipulate the Custom Remote Shell URI configuration table.Windows 7 and Windows Server 2008 R2 do not; if an operation is issued to the resource URI http://schemas.microsoft.com/wbem/wsman/1/config/winrs/customremoteshell, an error is returned.

<49> Section 3.1.6: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not support the CredSSP Encrypted Message option.

<50> Section 3.1.8: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support the subscription and delivery of events emitted by services using WS-Eventing messaging and paradigms. WS-Management places additional restrictions and constraints on the general WS-Eventing specification, as specified in [DMTF-DSP0226] section 7.

<51> Section 3.1.8.1: The following table provides the summary of the event delivery mode and subscription types supported by Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2.

Pull mode

Single push mode

Push with Ack mode

Batch push mode

Publisher initiated

No

No

Yes

Yes

Collector initiated

Yes

Yes

Yes

Yes

<52> Section 3.1.8.1.2.1: Windows Server 2003 R2 with the KB936059 update, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 support ReadExisitingEvent option only, as defined previously.

<53> Section 3.1.8.1.2.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 support ReadExisitingEvent option as well as predefined, reserved bookmark, http://schemas.dmtf.org/wbem/wsman/1/wsman/bookmark/earliest, as specified in [DMTF-DSP0226] section 7.2.6 (Bookmarks).

<54> Section 3.1.9.2.1: Windows Server 2003 R2 with the KB936059 update, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2support ReadExisitingEvent option only, as defined previously.

<55> Section 3.1.9.2.1: Windows Server 2008, Windows 7, and Windows Server 2008 R2support ReadExisitingEvent option as well as predefined, reserved bookmark, http://schemas.dmtf.org/wbem/wsman/1/wsman/bookmark/earliest, as specified in [DMTF-DSP0226] section 7.2.6 (Bookmarks).

<56> Section 3.1.9.3.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 accept WS-Policy expressions consisting of a sequence of policy assertions but do not accept nested policy assertions.

<57> Section 3.1.9.3.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 reject the request and reply with an error response when receiving WS-Policy expressions in which a single wsp:All element contains more than one wsman:Authentication assertion.

<58> Section 3.1.12: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 authorize the request by using the RootSDDL configuration setting specified in Server Configuration Data Types.

<59> Section 3.3.5.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 accept the "__cimnamespace" selector, as long as the specified namespace matches the namespace in the ResourceURI. If the namespace in the ResourceURI does not match the one specified by the "__cimnamespace" selector, the request is rejected and an error response is returned. Windows 7 and Windows Server 2008 R2 return the "__cimnamespace"” selector as a part of the EPR in the response if the ResourceURI given in the client request is a DMTF URI; that is, if the ResourceURI begins with "http://schemas.dmtf.org/".

<60> Section 3.3.5.2: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 process the request and do not reply with an error response if the "__cimnamespace" selector is specified when using a WMI ResourceURI and the namespace in the ResourceURI matches the one specified by the "__cimnamespace" selector. If the namespace in the ResourceURI does not match the one specified by the "__cimnamespace" selector, the request is rejected and an error response is returned.

<61> Section 3.3.5.4: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 use the wsman:FragmentTransfer header with WS-Transfer Get and WS-Transfer Put operations.

<62> Section 3.3.5.4: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 return a w:CannotProcessFilter fault if the xpath starts with a slash "/" character.

<63> Section 3.3.5.4: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 return a w:CannotProcessFilter fault if the xpath addresses elements or attributes that are not part of the XML representation and sub-elements of endpoint references (CIM ref properties).

<64> Section 3.3.5.4: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 return the class name (for example, CIM_Sampl) rather than the class's XSD type (for example, CIM_Sampl_Type) when the xpath identifies the type attribute of an embedded object.

<65> Section 3.3.5.5: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 process requests for CIM/WMI ResourceURIs without returning any error when the wsman:OptionSet element contains a wsman:Option element with mustComply="true" regardless of the name of the option.

<66> Section 3.4.1.1.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 use the options WINRS_NOPROFILE and WINRS_CODEPAGE when creating a remote shell.

<67> Section 3.4.1.1.3: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 return a fault if the wsman:DataLocale header is received in a response message.

<68> Section 3.4.1.1.4: Windows 7 and Windows Server 2008 R2 clients send the CompressionType SOAP header as part of the wxf:Create message with the value "xpress" to request the encoding according to the compression algorithm "COMP_ALG_W2K3", as specified in [MS-DRSR]. This SOAP header is not necessarily sent with every wxf:Create message; its inclusion is based on local configuration.

<69> Section 3.4.1.3: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 allow wxf:Delete messages to be sent to a particular Shell in order to forcibly close the Shell, asynchronously to any outstanding messages in progress to the specified Shell.

<70> Section 3.4.1.5: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 only support one outstanding command per instance of the shell processor. To achieve concurrent commands, more than one instance of the Shell must be created. An attempt to execute a new command while the data stream of a previously executed command is still active will result in a wsman:Concurrency fault.

<71> Section 3.4.1.5.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 use theoptions WINRS_CONSOLEMODE_STDIN or WINRS_SKIP_CMD_SHELL with the Command message.

<72> Section 3.4.1.10.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 use the option WSMAN_CMDSHELL_OPTION_KEEPALIVE during receive operation of the Remote Shell.

<73> Section 3.4.1.11.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 allow Receive messages to execute concurrently with Send messages.

<74> Section 3.4.1.11.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 reject processing new Command requests and reply with an error response until successfully returning a ReceiveResponse with a CommandState element, indicating that the command has terminated or succeeded.

<75> Section 3.4.1.11.1: On Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2, the streams STDOUT and STDERR always end by using the rsp:Stream/@End attribute.

<76> Section 3.4.1.11.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 do not notify that a command is blocked while waiting for input stream content by returning a rsp:CommandState element with the <Status> element set to rsp:CommandState/Pending. The <Status> element of the rsp:CommandState element is only set to rsp:CommandState/Pending when the command is pending termination; the subsequent value of the <Status> element is always rsp:CommandState/Done.

<77> Section 3.4.1.14: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7, and Windows Server 2008 R2 allow wxf:Get messages to be sent to a particular Shell, asynchronously, to any outstanding messages in progress to the specified Shell.

<78> Section 3.4.1.14: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 support wxf:Get operations on the resource URIs specified. On Windows 7 and Windows Server 2008 R2, the resource URI http://schemas.microsoft.com/wbem/wsman/1/windows/shell is used for wxf:Get operations regardless of the type of shell. If another resource URI (such as http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd) is specified, an error is returned.

<79> Section 3.4.1.15: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do not return the following elements in the wxf:GetResponse from a remote shell resource: <ResourceUri>, <Owner>, <ClientIP>, <Environment>, <WorkingDirectory>, <ShellIdleTimeout>, <ShellRunTime>, and <ShellInactivity>.Windows 7 and Windows Server 2008 R2 do return the above listed elements.

<80> Section 3.4.1.15: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 do return the <Lifetime >element in the wxf:GetResponse from a remote shell resource. Windows 7 and Windows Server 2008 R2 do not return the <Lifetime> element in the wxf:GetResponse from a remote shell resource.

<81> Section 3.4.1.16: Windows Server 2003 R2 Enterprise Edition, Windows Vista SP1, and Windows Server 2008 support wsen:Enumerate operations on the resource URIs specified.On Windows 7 and Windows Server 2008 R2, the resource URI http://schemas.microsoft.com/wbem/wsman/1/windows/shell is used for wsen:Enmerate operations regardless of the type of shell. If another resource URI (such as http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd) is specified, an error is returned.

<82> Section 3.4.1.19: Windows 7 and Windows Server 2008 R2 clients send an HTTP cookie only when it is received in a response from the server. If a Windows 7-based or Windows Server 2008 R2-based client receives an HTTP cookie as a part of a response message, it sends that HTTP cookie with any subsequent request message to that shell.

Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 clients do not send an HTTP cookie.

<83> Section 3.4.1.20.1: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 return a wsman:SchemaValidationError fault with the stated f:Message. Windows 7 and Windows Server 2008 R2 return a wsman:InvalidValue fault with the following f:Message: "The parameter is incorrect."

<84> Section 3.4.1.20.2: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 return a wsman:QuotaLimit fault when a quota limit is exceeded. Windows 7 and Windows Server 2008 R2 return a wsman:InternalError fault when a quota limit is exceeded.

<85> Section 3.4.1.20.2: Windows Server 2003 R2, Windows Vista SP1, and Windows Server 2008 return the detail f:Message as stated. Windows 7 and Windows Server 2008 R2 return the detail f:Message as follows: "The WS-Management service cannot process the request. The maximum number of concurrent shells for this user has been exceeded. Close existing shells or raise the quota for this user."

<86> Section 5.1: The default security profile used by Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 is wsman:secprofile/https/spnego-kerberos.

<87> Section 5.1: Windows Server 2003 R2, Windows Vista SP1, Windows Server 2008, Windows 7 and Windows Server 2008 R2 implement the following additional security profile: wsman:secprofile/https/mutual described in [DMTF-DSP0226] section 12.9

Page view tracker