[MS-WSMV]:
Web Services Management Protocol Extensions for Windows Vista
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
Fictitious Names. The example companies, organizations, products, domain names, e-mail 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 / Comments4/3/2007 / 0.1 / Version 0.1 release
6/1/2007 / 1.0 / Major / Updated and revised the technical content.
7/3/2007 / 2.0 / Major / MLonghorn+90
7/20/2007 / 2.0.1 / Editorial / Changed language and formatting in the technical content.
8/10/2007 / 3.0 / Major / Updated and revised the technical content.
9/28/2007 / 3.0.1 / Editorial / Changed language and formatting in the technical content.
10/23/2007 / 3.1 / Minor / Clarified the meaning of the technical content.
11/30/2007 / 3.1.1 / Editorial / Changed language and formatting in the technical content.
1/25/2008 / 3.1.2 / Editorial / Changed language and formatting in the technical content.
3/14/2008 / 4.0 / Major / Updated and revised the technical content.
5/16/2008 / 4.0.1 / Editorial / Changed language and formatting in the technical content.
6/20/2008 / 4.1 / Minor / Clarified the meaning of the technical content.
7/25/2008 / 5.0 / Major / Updated and revised the technical content.
8/29/2008 / 5.0.1 / Editorial / Changed language and formatting in the technical content.
10/24/2008 / 5.0.2 / Editorial / Changed language and formatting in the technical content.
12/5/2008 / 6.0 / Major / Updated and revised the technical content.
1/16/2009 / 7.0 / Major / Updated and revised the technical content.
2/27/2009 / 8.0 / Major / Updated and revised the technical content.
4/10/2009 / 9.0 / Major / Updated and revised the technical content.
5/22/2009 / 10.0 / Major / Updated and revised the technical content.
7/2/2009 / 10.1 / Minor / Clarified the meaning of the technical content.
8/14/2009 / 10.2 / Minor / Clarified the meaning of the technical content.
9/25/2009 / 10.3 / Minor / Clarified the meaning of the technical content.
11/6/2009 / 11.0 / Major / Updated and revised the technical content.
12/18/2009 / 12.0 / Major / Updated and revised the technical content.
1/29/2010 / 13.0 / Major / Updated and revised the technical content.
3/12/2010 / 14.0 / Major / Updated and revised the technical content.
4/23/2010 / 15.0 / Major / Updated and revised the technical content.
6/4/2010 / 15.1 / Minor / Clarified the meaning of the technical content.
7/16/2010 / 15.1 / None / No changes to the meaning, language, or formatting of the technical content.
8/27/2010 / 15.1 / None / No changes to the meaning, language, or formatting of the technical content.
10/8/2010 / 15.2 / Minor / Clarified the meaning of the technical content.
11/19/2010 / 16.0 / Major / Updated and revised the technical content.
1/7/2011 / 17.0 / Major / Updated and revised the technical content.
2/11/2011 / 18.0 / Major / Updated and revised the technical content.
3/25/2011 / 19.0 / Major / Updated and revised the technical content.
5/6/2011 / 19.0 / None / No changes to the meaning, language, or formatting of the technical content.
6/17/2011 / 20.0 / Major / Updated and revised the technical content.
9/23/2011 / 21.0 / Major / Updated and revised the technical content.
12/16/2011 / 22.0 / Major / Updated and revised the technical content.
3/30/2012 / 23.0 / Major / Updated and revised the technical content.
7/12/2012 / 24.0 / Major / Updated and revised the technical content.
10/25/2012 / 25.0 / Major / Updated and revised the technical content.
1/31/2013 / 25.0 / None / No changes to the meaning, language, or formatting of the technical content.
8/8/2013 / 26.0 / Major / Updated and revised the technical content.
11/14/2013 / 27.0 / Major / Updated and revised the technical content.
2/13/2014 / 27.0 / None / No changes to the meaning, language, or formatting of the technical content.
5/15/2014 / 27.0 / None / No changes to the meaning, language, or formatting of the technical content.
6/30/2015 / 28.0 / Major / Significantly changed the technical content.
10/16/2015 / 29.0 / Major / Significantly changed the technical content.
Table of Contents
1Introduction
1.1Glossary
1.2References
1.2.1Normative References
1.2.2Informative References
1.3Overview
1.3.1Typical Message Flow for CIM Operations with Streaming Output
1.3.2Typical Message Flow for CIM Operations with Prompting
1.4Relationship to Other Protocols
1.5Prerequisites/Preconditions
1.6Applicability Statement
1.7Versioning and Capability Negotiation
1.8Vendor-Extensible Fields
1.9Standards Assignments
2Messages
2.1Transport
2.2Common Message Syntax
2.2.1Namespaces
2.2.2Messages
2.2.2.1EmptyMessage
2.2.2.2AnyXmlMessage
2.2.2.3OptionalXmlMessage
2.2.2.4AcknowledgeResponseMessage
2.2.2.5InteractiveResponseMessage
2.2.3Elements
2.2.4Complex Types
2.2.4.1AuthenticationType Complex Type
2.2.4.2CapabilityType
2.2.4.3CertMappingType
2.2.4.4ClientAuthType
2.2.4.5ClientDefaultPortsType
2.2.4.6ClientType
2.2.4.7CommandLine
2.2.4.8CommandResponse
2.2.4.9CommandStateType
2.2.4.10ConfigType
2.2.4.11ConnectResponseType
2.2.4.12ConnectType
2.2.4.13CustomRemoteShell
2.2.4.14DesiredStreamType
2.2.4.15DisconnectType
2.2.4.16EnvironmentVariable
2.2.4.17EnvironmentVariableList
2.2.4.18InitializationParametersType
2.2.4.19ListenerType
2.2.4.20MachineIDType Complex Type
2.2.4.21ParamType
2.2.4.22PluginType
2.2.4.23QuotasType
2.2.4.24QueryListType
2.2.4.25QueryType
2.2.4.26Receive
2.2.4.27ReceiveResponse
2.2.4.28ResourcesContainerType
2.2.4.29ResourceType
2.2.4.30SecurityType
2.2.4.31SelectType
2.2.4.32Send
2.2.4.33SendResponse
2.2.4.34ServiceAuthType
2.2.4.35ServiceDefaultPortsType
2.2.4.36ServiceType
2.2.4.37Shell
2.2.4.38Signal
2.2.4.39SignalResponse
2.2.4.40StreamType
2.2.4.41SubscriptionType Complex Type
2.2.4.42WinrsType
2.2.4.43WSManFaultType
2.2.4.44AcknowledgeType
2.2.4.45OperationIDType Complex Type
2.2.4.46SequenceIDType Complex Type
2.2.4.47InteractiveEventType Complex Type
2.2.4.48InteractiveResponseType Complex Type
2.2.4.49InteractiveEventComplexType Complex Type
2.2.5Simple Types
2.2.5.1ArgumentType
2.2.5.2CapabilityEnumeration
2.2.5.3cim:cimDateTime
2.2.5.4CommandStateEnumeration
2.2.5.5ExitCodeType
2.2.5.6SignalCodeEnumeration
2.2.5.7StreamName
2.2.5.8StreamNameList
2.2.5.9XmlRenderingTypeEnumeration
2.2.5.10OutputBufferingModeEnumeration
2.2.5.11EventType_Type
2.2.5.12PromptType_Type
2.2.5.13ActionType_Type
2.2.5.14ResponseType
2.2.5.15StateType
2.2.5.16Type_Type
2.2.6Attributes
2.2.7Groups
2.2.8Attribute Groups
2.2.9Common Data Structures
2.2.9.1Encrypted Message Types
2.2.9.1.1NegotiateEncryptedMessage
2.2.9.1.1.1HTTP Headers
2.2.9.1.1.2Message Payload
2.2.9.1.1.2.1Metadata Fields
2.2.9.1.1.2.2Encrypted Data
2.2.9.1.2KerberosEncryptedMessage
2.2.9.1.2.1HTTP Headers
2.2.9.1.2.2Message Payload
2.2.9.1.2.2.1Metadata Fields
2.2.9.1.2.2.2Encrypted Data
2.2.9.1.3CredSSPEncryptedMessage
2.2.9.1.3.1Message Content Less Than or Equal to 16 Kilobytes
2.2.9.1.3.1.1HTTP Headers
2.2.9.1.3.1.2Message Payload
2.2.9.1.3.1.2.1Metadata Fields
2.2.9.1.3.1.2.2Encrypted Data
2.2.9.1.3.2Message Content Greater Than 16 Kilobytes
2.2.9.1.3.2.1HTTP Headers
2.2.9.1.3.2.2Message Payload
2.2.9.1.3.2.2.1Metadata Fields
2.2.9.1.3.2.2.2Encrypted Data
2.2.9.2Compressed Message Types
2.2.10Options for CIM/WMI Operations with PowerShell Semantics
3Protocol Details
3.1Server Details
3.1.1Abstract Data Model
3.1.2Timers
3.1.3Initialization
3.1.4Message Processing Events and Sequencing Rules
3.1.4.1Common Message Processing Events and Sequencing Rules
3.1.4.1.1wsman:ResourceURI
3.1.4.1.2wsman:SelectorSet
3.1.4.1.3wsa:ReplyTo
3.1.4.1.4wsa:FaultTo
3.1.4.1.5wsa:MessageID
3.1.4.1.6wsman:OperationTimeout
3.1.4.1.7wsman:MaxEnvelopeSize
3.1.4.1.8wsman:Locale
3.1.4.1.9wsmv:DataLocale
3.1.4.1.10wsman:OptionSet
3.1.4.1.10.1wsman:OptionSet/wsman:Option/@Type
3.1.4.1.11wsman:RequestEPR
3.1.4.1.12wsmv:ActivityId
3.1.4.1.13wsen:Filter
3.1.4.1.14wsen:Pull/wsen:MaxElements
3.1.4.1.15wsman:RequestTotalItemsCountEstimate
3.1.4.1.16wsman:OptimizeEnumeration
3.1.4.1.17wsman:EnumerationMode
3.1.4.1.18wsman:FragmentTransfer
3.1.4.1.19Concurrent Operations
3.1.4.1.20Inbound Message Size
3.1.4.1.21Fault Detail
3.1.4.1.22WS-Policy
3.1.4.1.23Metadata and Discovery
3.1.4.1.24Binary Attachments
3.1.4.1.25Nonprintable Characters
3.1.4.1.26Arrays
3.1.4.1.27wsmb:PolymorphismMode
3.1.4.1.28Security
3.1.4.1.29Server Configuration
3.1.4.1.29.1
3.1.4.1.29.2
3.1.4.1.29.3
3.1.4.1.29.4
3.1.4.1.29.5
3.1.4.1.30Event Subscription
3.1.4.1.30.1Subscription Options
3.1.4.1.30.2Event Delivery
3.1.4.1.30.3Event Security
3.1.4.1.30.4Event Renewal
3.1.4.1.30.5Event Filtering
3.1.4.1.30.6Heartbeat Events
3.1.4.1.31Remote Shell
3.1.4.1.31.1I/O Streams
3.1.4.1.31.2wsman:Locale/wsmv:DataLocale
3.1.4.1.31.3wsman:SchemaValidationError
3.1.4.1.31.4HTTP Cookies
3.1.4.1.31.5Shell Timeouts
3.1.4.1.31.6Remote Shell Compression
3.1.4.1.31.7Disconnecting and Reconnecting to a Shell
3.1.4.1.31.8Restrictions on the Remote Shell Protocol
3.1.4.1.32Invoking CIM Methods
3.1.4.1.33ShowExtensions Option
3.1.4.1.34Plugin Management
3.1.4.1.34.1Routing Requests to Plugins
3.1.4.1.34.2Plugin Configuration
3.1.4.1.34.3Plugins
3.1.4.1.34.3.1WMI Provider
3.1.4.1.34.3.2Event Forwarding Plugin
3.1.4.1.34.3.3SEL Plugin
3.1.4.1.34.3.4PowerShell Plugin
3.1.4.1.34.3.5PowerShell32 Plugin
3.1.4.1.34.3.6PowerShell Workflow Plugin
3.1.4.1.34.3.7PowerShell Workflow32 Plugin
3.1.4.1.34.3.8Server Manager Workflows Plugin
3.1.4.1.35Certificate Mapping
3.1.4.1.36Enumeration Garbage Collection
3.1.4.1.37wsmv:SessionId
3.1.4.1.38CIM Metadata Retrieval
3.1.4.1.39Robust Connection Support
3.1.4.2Get
3.1.4.2.1Remote Shells
3.1.4.3Put
3.1.4.4Delete
3.1.4.4.1Remote Shells
3.1.4.5Create
3.1.4.5.1Messages
3.1.4.5.2Remote Shells
3.1.4.5.2.1wsman:QuotaLimit
3.1.4.6Subscribe
3.1.4.6.1Messages
3.1.4.7Unsubscribe
3.1.4.7.1Messages
3.1.4.8Enumerate
3.1.4.8.1Messages
3.1.4.8.2Remote Shells
3.1.4.8.3Publisher-Initiated Subscriptions
3.1.4.9Pull
3.1.4.9.1Messages
3.1.4.9.2Remote Shells
3.1.4.10Release
3.1.4.10.1Messages
3.1.4.11Command
3.1.4.11.1Messages
3.1.4.12Signal
3.1.4.12.1Messages
3.1.4.13Send
3.1.4.13.1Messages
3.1.4.14Receive
3.1.4.14.1Messages
3.1.4.15Disconnect
3.1.4.15.1Messages
3.1.4.16Reconnect
3.1.4.16.1Messages
3.1.4.17Connect
3.1.4.17.1Messages
3.1.4.18Acknowledge
3.1.4.19End
3.1.4.19.1Messages
3.1.4.20Cancel
3.1.5Timer Events
3.1.5.1Enumeration Garbage Collection Timer
3.1.5.2Packet Retrieval Timer
3.1.5.3Shell Idle Timeout Timer
3.1.5.4Shell Lifetime Timer
3.1.5.5Connection KeepAlive Timer
3.1.5.6Connection AutoDisconnect Timer
3.1.6Other Local Events
3.1.6.1Create Subscription
3.1.6.2Delete Subscription
3.1.6.3Create Plugin
3.1.6.4Delete Plugin
3.1.6.5TCP Connection Terminated by Network
3.1.6.6Response Data Generated by Robust Operation
3.1.6.7Stream Output for Debug, Warning, Verbose, and Progress Messages Requested by Robust Operation
3.1.6.8Interactive Prompt Requested by Robust Operation
3.2Client Details
3.2.1Abstract Data Model
3.2.2Timers
3.2.3Initialization
3.2.4Message Processing Events and Sequencing Rules
3.2.4.1Common Message Processing Events and Sequencing Rules
3.2.4.1.1wsa:MessageID
3.2.4.1.2wsman:OperationTimeout
3.2.4.1.3wsman:MaxEnvelopeSize
3.2.4.1.4wsman:Locale
3.2.4.1.5wsmv:DataLocale
3.2.4.1.6wsman:OptionSet
3.2.4.1.7wsman:RequestEPR
3.2.4.1.8wsmv:ActivityId
3.2.4.1.9wsen:Pull/wsen:MaxElements
3.2.4.1.10wsman:RequestTotalItemsCountEstimate
3.2.4.1.11wsman:OptimizeEnumeration
3.2.4.1.12wsman:EnumerationMode
3.2.4.1.13wsman:Filter
3.2.4.1.14wsman:FragmentTransfer
3.2.4.1.15Fault Detail
3.2.4.1.16Binary Attachments
3.2.4.1.17Arrays
3.2.4.1.18wsmb:PolymorphismMode
3.2.4.1.19Remote Shell Compression
3.2.4.1.20WSMAN_CMDSHELL_OPTION_KEEPALIVE
3.2.4.1.21Refusal of Event Delivery
3.2.4.1.22Client Configuration
3.2.4.1.22.1
3.2.4.1.22.2
3.2.4.1.23wsmv:SessionId
3.2.4.2Multiple Message Operations
3.2.4.2.1Full Duplex
3.2.4.2.1.1End Message
3.2.4.2.1.2KeepAlive Message
3.2.4.2.1.3Cancel Message
3.2.4.2.2Invoking Custom Methods with a Stream Output Parameter
3.2.4.2.3Executing WMI Operations with PowerShell Semantics
3.2.5Timer Events
3.2.5.1Client Operation Timeout Timer
3.2.5.2Connection KeepAlive Timer
3.2.5.3Request Retry Timer
3.2.6Other Local Events
3.2.6.1Set Event Collector EPR
3.2.6.2Connect to a Remote Shell
3.2.6.3Disconnect from a Remote Shell
3.2.6.4Reconnect to a Remote Shell
3.2.6.5Begin an Enhanced CIM Operation
3.2.6.6End Enhanced CIM Operations
3.2.6.7Abort an Enhanced CIM Operation
3.2.7Processing Enhanced CIM Client Messages
3.2.7.1NoSemantics
3.2.7.2Debug
3.2.7.3Warning
3.2.7.4Verbose
3.2.7.5Progress
3.2.7.6Confirm
3.2.7.7ErrorAction
3.2.7.8StreamingOutput
3.2.7.9Non-InteractiveEvent Response
3.2.7.10Transport Error
4Protocol Examples
4.1CIM Examples
4.1.1Retrieving a CIM Instance
4.1.2Enumeration of Instances
4.1.2.1Enumerate Request
4.1.2.2Enumerate Response
4.1.2.3First Pull Request
4.1.2.4First Pull Response
4.1.2.5Second Pull Request
4.1.2.6Second Pull Response with EndOfSequence
4.1.3Modifying an Instance
4.1.4Invoking a Method
4.2Configuration Examples
4.2.1Retrieving Configuration
4.2.2Modifying Configuration
4.2.3Client Certificate Mapping Configuration
4.2.4Plugin Security Setting Configuration
4.3Events
4.4Event Subscription Example
4.5Encryption Example
4.6Publisher-Initiated Subscription Examples
4.6.1Enumerate Example
4.6.2Enumerate Response (Subscriptions) Example
4.6.3Event Delivery Example
4.6.4Ack Example
4.6.5End Subscription Example
4.7Remote Shell Examples
4.7.1Create Shell
4.7.2Execute Command
4.7.3Receive Output
4.7.4Send Input
4.7.5Terminate Operation
4.7.6Enumerate Remote Shells
4.7.7Retrieve Shell Instance
4.7.8Delete Shell
4.7.9Disconnect Shell
4.7.10Reconnect Shell
4.8Custom Remote Shell Examples
4.8.1Custom Remote Shell Configuration Table Setup
4.8.2Custom Shell Create
4.8.3Custom Shell Send
4.8.4Custom Shell Receive
4.8.5Custom Shell Delete
4.9Selector Filter Dialect Example
4.10Fault Detail
4.11Robust Connection/Full Duplex Examples
4.11.1A CIM Operation that Prompts Once with the Client Replying "yes"
4.11.2A CIM Operation that Returns Streaming Output
4.11.3An Operation is Reconnected After a Network Failure
5Security
5.1Security Considerations for Implementers
5.2Index of Security Parameters
6Appendix A: Full WSDL
7Appendix B: Product Behavior
8Change Tracking
9Index
1Introduction
This document describes Windows Vista operating system extensions to the WS-Management Protocol, as described in [DMTF-DSP0226], the WS-Management Common Information Model (CIM) Binding Specification, as described in [DMTF-DSP0227], and the WS-CIM Mapping Specification, as described in [DMTF-DSP0230], for accessing CIM objects as a Web service.
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 [RFC2119]. Sections 1.5 and 1.9 are also normative but do not contain those terms. All other sections and examples in this specification are informative.
1.1Glossary
The following terms are specific to this document:
action URI: A URI that identifies which operation or method needs to be applied to a resource.
CIM class: A CIM object that represents a CIM class definition as a CIM object. It is the template representing a manageable entity with a set of properties and methods.
CIM instance: An instantiation of a CIM class representing a manageable entity.
CIM method: An operation describing the behavior of a CIM class or a CIM instance. It is generally an action that can be performed against the manageable entity made up of a CIM class.
CIM namespace: A logical grouping of a set of CIM classes designed for the same purpose or sharing a common management objective within the database used to store all CIM class definitions.
CIM object: Refers to a CIM class or a CIM instance.
collector: In the context of events, the consumer of the event.
Common Information Model (CIM): The Distributed Management Task Force (DMTF) model that describes how to represent real-world computer and network objects. CIM uses an object-oriented paradigm, where managed objects are modeled using the concepts of classes and instances. See [DMTF-DSP0004].
Common Information Model (CIM) class: A collection of Common Information Model (CIM) instances that support the same type, that is, the same CIM properties and CIM methods, as specified in [DMTF-DSP0004].
Common Information Model (CIM) instance: Provides values for the CIM properties associated with the CIM instance's defining CIM class. A CIM instance does not carry values for any other CIM properties or CIM methods that are not defined in (or inherited by) its defining CIM class. For more information, see [DMTF-DSP0004].
Common Information Model (CIM) object: An object that represents a Common Information Model (CIM) object. This may be either a CIM class or a CIM instance of a CIM class.
Custom Remote Shell: Refers to any shell besides the default Text-based Command Shell configured, manipulated, and invoked by the client.
Distributed Management Task Force (DMTF): An industry organization that develops management standards and integration technology for enterprise and Internet environments.
endpoint reference (EPR): A combination of WS-Addressing ([WSAddressing]) and WS-Management–addressing elements that together describe an address for a resource in the SOAP message header.
globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).
higher layer protocol (HLP): The protocol that invoked the WSMV server.
Internet host name: The name of a host as defined in [RFC1123] section 2.1, with the extensions described in [MS-HNDS].
Managed Object Format (MOF): A textual encoding for Common Information Model (CIM) objects, this representation is not used within protocol operations defined in [MS-WMI]. MOF is defined in [DMTF-DSP0004] section 3. The MOF text encoding is only used for illustrative purposes. The binary encoding can be translated to and from the MOF format.
plugin: A software entity that implements one or more WSDL operations.
property: A name/value pair that describes a unit of data for a class. Property values must have a valid Managed Object Format (MOF) data type.
publisher: In the context of events: The source of event generation. An application or component that writes to one or more event logs. An application that publishes events.
publisher-initiated event subscription: An alternative approach to collector-initiated subscription, where the publisher initiates the subscription process instead of the collector.
qualifier: A metadata item as specified in [DMTF-DSP0004] section 4.5.4. This consists of a simple name, a type, a value, and a flavor (a propagation rule for the qualifier).
resource: Any component that a computer can access where data can be read, written, or processed. This resource could be an internal component such as a disk drive, or another computer on a network that is used to access a file.
resource URI: The Uniform Resource Identifier (URI) that is used to identify a specific type of resource, such as disks or processes, on a network ([DMTF-DSP0226] section 5.1.2.1).
selector: A name/value pair that represents a particular instance of a resource; essentially a filter or "key" that identifies the desired instance of the resource.
service: An application that provides management services to clients through the WS-Management Protocol and other web services.
SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
universally unique identifier (UUID): A 128-bit value. UUIDs can be used for multiple purposes, from tagging objects with an extremely short lifetime, to reliably identifying very persistent objects in cross-process communication such as client and server interfaces, manager entry-point vectors, and RPC objects. UUIDs are highly likely to be unique. UUIDs are also known as globally unique identifiers (GUIDs) and these terms are used interchangeably in the Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the UUID. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the UUID.
Web Services Description Language (WSDL): An XML format for describing network services as a set of endpoints that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages are described abstractly and are bound to a concrete network protocol and message format in order to define an endpoint. Related concrete endpoints are combined into abstract endpoints, which describe a network service. WSDL is extensible, which allows the description of endpoints and their messages regardless of the message formats or network protocols that are used.
Windows Management Instrumentation (WMI): The Microsoft implementation of Common Information Model (CIM), as specified in [DMTF-DSP0004]. WMI allows an administrator to manage local and remote machines and models computer and network objects using an extension of the CIM standard.
WMI provider: An add-on to (WMI) that maps topic-specific information into the CIM for uniform representation in (WMI).
Xml Schema Definition (XSD): A namespace-aware and data type–aware XML schema definition language, or an instance of an XML schema written using the language.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2References
Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
1.2.1Normative 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.
[DMTF-DSP0004] Distributed Management Task Force, "Common Information Model (CIM) Infrastructure Specification", DSP0004, version 2.3 final, October 2005,
[DMTF-DSP0217-1.0.0] DMTF, "SMASH Implementation Requirements", version 1.0.0, October 2009,