Windows Management Instrumentation Interface

[MS-WMI]:
Windows Management Instrumentation Remote Protocol

Specification
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's Open Specification Promise (available here:
http://www.microsoft.com/interop/osp) or the Community Promise (available here:
http://www.microsoft.com/interop/cp/default.mspx). 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
[email protected].
 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.
 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.
1 / 168
[MS-WMI] — v20091104
Windows Management Instrumentation Remote Protocol Specification
Copyright © 2009 Microsoft Corporation.
Release: Wednesday, November 4, 2009

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 Updated the technical content.
11/30/2007 1.0 Major Updated and revised the technical content.
05/16/2008 2.0.1 Editorial Revised and edited the technical content.
2 / 168
[MS-WMI] — v20091104

Contents
1 Introduction ............................................................................................................. 7
1.1 Glossary ............................................................................................................... 7
1.2 References ............................................................................................................ 8
1.2.1 Normative References ....................................................................................... 8
1.2.2 Informative References ..................................................................................... 9
1.3 Protocol Overview (Synopsis) .................................................................................. 9
1.4 Relationship to Other Protocols .............................................................................. 12
1.5 Prerequisites/Preconditions ................................................................................... 12
1.6 Applicability Statement ......................................................................................... 13
1.7 Versioning and Capability Negotiation..................................................................... 13
1.8 Vendor-Extensible Fields ....................................................................................... 13
1.9 Standards Assignments ........................................................................................ 13
2 Messages................................................................................................................ 15
2.1 Transport............................................................................................................ 15
2.2 Common Data Types ............................................................................................ 15
2.2.1 WQL Query .................................................................................................... 15
2.2.1.1 WQL Schema and Data Query .................................................................... 15
2.2.1.2 WQL Event Query ..................................................................................... 19
2.2.2 CIM Path and Namespace ................................................................................ 21
2.2.3 Protocol Return Codes..................................................................................... 23
2.2.4 IWbemClassObject Interface ............................................................................ 23
2.2.4.1 Prototype Result Object ............................................................................. 24
2.2.4.2 Extrinsic Events ........................................................................................ 25
2.2.5 WBEM_CHANGE_FLAG_TYPE Enumeration ......................................................... 25
2.2.6 WBEM_GENERIC_FLAG_TYPE Enumeration ........................................................ 26
2.2.7 WBEM_STATUS_TYPE Enumeration................................................................... 27
2.2.8 WBEM_TIMEOUT_TYPE Enumeration ................................................................. 27
2.2.9 WBEM_QUERY_FLAG_TYPE Enumeration ........................................................... 27
2.2.10 WBEM_BACKUP_RESTORE_FLAGS Enumeration ............................................... 28
2.2.11 WBEMSTATUS Enumeration ........................................................................... 28
2.2.12 WBEM_CONNECT_OPTIONS Enumeration ........................................................ 30
2.2.13 IWbemContext ............................................................................................. 30
2.2.13.1 IWbemContextBuffer Marshaling Structure ................................................. 31
2.2.13.2 IWbemContextProperty Marshaling Structure ............................................. 32
2.2.13.3 IWbemContextString Marshaling Structure ................................................. 33
2.2.13.4 IWbemContextArray Marshaling Structure .................................................. 33
2.2.14 ObjectArray Structure ................................................................................... 34
2.2.14.1 WBEM_DATAPACKET_OBJECT Structure..................................................... 36
2.2.14.2 WBEMOBJECT_CLASS Structure ................................................................ 37
2.2.14.3 WBEMOBJECT_INSTANCE Structure .......................................................... 37
2.2.14.4 WBEMOBJECT_INSTANCE_NOCLASS Structure ........................................... 38
2.2.15 WBEM_REFRESHED_OBJECT Structure ............................................................ 39
2.2.16 WBEM_INSTANCE_BLOB Enumeration ............................................................. 40
2.2.17 WBEM_INSTANCE_BLOB_TYPE Enumeration .................................................... 40
2.2.18 RefreshedInstances ...................................................................................... 40
2.2.19 RefreshedSingleInstance ............................................................................... 41
2.2.20 _WBEM_REFRESH_INFO Structure .................................................................. 41
2.2.21 _WBEM_REFRESHER_ID Structure .................................................................. 41
2.2.22 _WBEM_RECONNECT_INFO Structure ............................................................. 42
3 / 168
[MS-WMI] — v20091104

2.2.23 _WBEM_RECONNECT_RESULTS Structure ........................................................ 42
2.2.24 _WBEM_RECONNECT_TYPE Enumeration ......................................................... 42
2.2.25 WBEM_REFRESH_TYPE Enumeration ............................................................... 43
2.2.26 _WBEM_REFRESH_INFO_NON_HIPERF Structure .............................................. 43
2.2.27 _WBEM_REFRESH_INFO_REMOTE Structure .................................................... 44
2.2.28 _WBEM_REFRESH_INFO_UNION Union............................................................ 44
2.2.29 WMI Locale Formats ..................................................................................... 44
2.2.30 __SystemSecurity class ................................................................................. 45
3 Protocol Details ...................................................................................................... 46

3.1 Server Details ..................................................................................................... 46
3.1.1 Abstract Data Model ....................................................................................... 47
3.1.1.1 Delivering Results to Client ........................................................................ 48
3.1.1.1.1 Synchronous calls ............................................................................... 48
3.1.1.1.2 Semi-Synchronous calls ....................................................................... 48
3.1.1.1.3 Asynchronous calls .............................................................................. 48
3.1.2 Timers .......................................................................................................... 49
3.1.3 Initialization .................................................................................................. 49
3.1.4 Message Processing Events and Sequencing Rules .............................................. 49
3.1.4.1 IWbemLevel1Login Interface ...................................................................... 50
3.1.4.1.1 IWbemLevel1Login::EstablishPosition (Opnum 3) .................................... 50
3.1.4.1.2 IWbemLevel1Login::RequestChallenge (Opnum 4) .................................. 51
3.1.4.1.3 IWbemLevel1Login::WBEMLogin (Opnum 5) ........................................... 52
3.1.4.1.4 IWbemLevel1Login::NTLMLogin (Opnum 6) ............................................ 52
3.1.4.2 IWbemObjectSink Interface Server Details................................................... 53
3.1.4.2.1 IWbemObjectSink::Indicate (Opnum 3) Server details ............................. 54
3.1.4.2.2 IWbemObjectSink::SetStatus (Opnum 4) Server Details .......................... 54
3.1.4.3 IWbemServices Interface ........................................................................... 55
3.1.4.3.1 IWbemServices::OpenNamespace (Opnum 3) ........................................ 58
3.1.4.3.2 IWbemServices::CancelAsyncCall (Opnum 4) ......................................... 59
3.1.4.3.3 IWbemServices::QueryObjectSink (Opnum 5) ........................................ 60
3.1.4.3.4 IWbemServices::GetObject (Opnum 6) .................................................. 61
3.1.4.3.5 IWbemServices::GetObjectAsync (Opnum 7) .......................................... 63
3.1.4.3.6 IWbemServices::PutClass (Opnum 8) .................................................... 64
3.1.4.3.7 IWbemServices::PutClassAsync (Opnum 9) ............................................ 66
3.1.4.3.8 IWbemServices::DeleteClass (Opnum 10) .............................................. 68
3.1.4.3.9 IWbemServices::DeleteClassAsync (Opnum 11) ...................................... 69
3.1.4.3.10 IWbemServices::CreateClassEnum (Opnum 12) .................................... 70
3.1.4.3.11 IWbemServices::CreateClassEnumAsync (Opnum 13) ............................ 72
3.1.4.3.12 IWbemServices::PutInstance (Opnum 14) ............................................ 73
3.1.4.3.13 IWbemServices::PutInstanceAsync (Opnum 15) .................................... 75
3.1.4.3.14 IWbemServices::DeleteInstance (Opnum 16) ....................................... 77
3.1.4.3.15 IWbemServices::DeleteInstanceAsync (Opnum 17) ............................... 79
3.1.4.3.16 IWbemServices::CreateInstanceEnum (Opnum 18) ............................... 80
3.1.4.3.17 IWbemServices::CreateInstanceEnumAsync (Opnum 19) ....................... 81
3.1.4.3.18 IWbemServices::ExecQuery (Opnum 20) ............................................. 83
3.1.4.3.19 IWbemServices::ExecQueryAsync (Opnum 21) ..................................... 84
3.1.4.3.20 IWbemServices::ExecNotificationQuery (Opnum 22) .............................. 86
3.1.4.3.21 IWbemServices::ExecNotificationQueryAsync (Opnum 23) ..................... 87
3.1.4.3.22 IWbemServices::ExecMethod (Opnum 24) ............................................ 88
3.1.4.3.23 IWbemServices::ExecMethodAsync (Opnum 25) ................................... 90
3.1.4.4 IEnumWbemClassObject Interface .............................................................. 92
3.1.4.4.1 IEnumWbemClassObject::Reset (Opnum 3) ........................................... 93
4 / 168
[MS-WMI] — v20091104

3.1.4.4.2 IEnumWbemClassObject::Next (Opnum 4) ............................................. 94
3.1.4.4.3 IEnumWbemClassObject::NextAsync (Opnum 5) ..................................... 95
3.1.4.4.4 IEnumWbemClassObject::Clone (Opnum 6) ........................................... 96
3.1.4.4.5 IEnumWbemClassObject::Skip (Opnum 7) ............................................. 96
3.1.4.5 IWbemCallResult Interface ......................................................................... 97
3.1.4.5.1 IWbemCallResult::GetResultObject (Opnum 3) ....................................... 98
3.1.4.5.2 IWbemCallResult::GetResultString (Opnum 4) ........................................ 99
3.1.4.5.3 IWbemCallResult::GetResultService (Opnum 5) .....................................100
3.1.4.5.4 IWbemCallResult::GetCallStatus (Opnum 6) ..........................................101
3.1.4.6 IWbemFetchSmartEnum Interface .............................................................101
3.1.4.6.1 IWbemFetchSmartEnum::GetSmartEnum (Opnum 3) .............................102
3.1.4.7 IWbemWCOSmartEnum Interface ..............................................................102
3.1.4.7.1 IWbemWCOSmartEnum::Next (Opnum 3) .............................................103
3.1.4.8 IWbemLoginClientID Interface ...................................................................104
3.1.4.8.1 IWbemLoginClientID::SetClientInfo (Opnum 3) ......................................104
3.1.4.9 IWbemLoginHelper Interface .....................................................................105
3.1.4.9.1 IWbemLoginHelper::SetEvent (Opnum 3) .............................................105
3.1.4.10 IWbemBackupRestore Interface ...............................................................105
3.1.4.10.1 IWbemBackupRestore::Backup (Opnum 3) ..........................................106
3.1.4.10.2 IWbemBackupRestore::Restore (Opnum 4) .........................................107
3.1.4.11 IWbemBackupRestoreEx Interface ...........................................................107
3.1.4.11.1 IWbemBackupRestoreEx::Pause (Opnum 5) ........................................108
3.1.4.11.2 IWbemBackupRestoreEx::Resume (Opnum 6) .....................................108
3.1.4.12 IWbemRefreshingServices Interface .........................................................109
3.1.4.12.1 IWbemRefreshingServices::AddObjectToRefresher (Opnum 3) ...............110
3.1.4.12.2 IWbemRefreshingServices::AddObjectToRefresherByTemplate (Opnum
4)....................................................................................................111
3.1.4.12.3 IWbemRefreshingServices::AddEnumToRefresher (Opnum 5) ................112
3.1.4.12.4 IWbemRefreshingServices::RemoveObjectFromRefresher (Opnum 6) .....113
3.1.4.12.5 IWbemRefreshingServices::GetRemoteRefresher (Opnum 7) .................114
3.1.4.12.6 IWbemRefreshingServices::ReconnectRemoteRefresher (Opnum 8) ........115
3.1.4.13 IWbemRemoteRefresher Interface ...........................................................117
3.1.4.13.1 IWbemRemoteRefresher::RemoteRefresh (Opnum 3) ...........................117
3.1.4.13.2 IWbemRemoteRefresher::StopRefreshing (Opnum 4) ...........................118
3.1.4.13.3 IWbemRemoteRefresher::Opnum5NotUsedOnWire (Opnum 5) ...............119
3.1.5 Timer Events ................................................................................................119
3.1.6 Other Local Events ........................................................................................119
3.2 Client Details......................................................................................................119
3.2.1 Abstract Data Model ......................................................................................119
3.2.2 Timers .........................................................................................................119
3.2.3 Initialization .................................................................................................120
3.2.4 Message Processing Events and Sequencing Rules .............................................120
3.2.4.1 IWbemObjectSink Interface Client Details ...................................................120
3.2.4.1.1 IWbemObjectSink::Indicate Client Details .............................................121
3.2.4.1.2 IWbemObjectSink::SetStatus Client Details ...........................................121
3.2.4.2 IWbemServices Interface Client Details ......................................................121
3.2.4.2.1 Sending Events to Server ....................................................................121
3.2.4.2.2 Calling Put Interfaces for CIM Objects with Amended Qualifiers ................122
3.2.4.2.3 Invoking Synchronous Methods Returing No Object ................................122
3.2.4.2.4 Invoking Synchronous Methods Returning Single Object .........................122
3.2.4.2.5 Invoking Semi-Synchronous Methods That Return a Single Object ............122
3.2.4.2.6 Invoking Synchronous and Semi-Synchronous Operations Returning
Multiple Objects ................................................................................123
5 / 168
[MS-WMI] — v20091104

3.2.4.2.7 Invoking Asynchronous operations .......................................................124
3.2.4.3 IWbemBackupRestore Interface Client Details .............................................125
3.2.4.4 IWbemBackupRestoreEx Interface Client Details ..........................................125
3.2.4.5 IWbemRefreshingServices Interface Client Details .......................................125
3.2.4.5.1 IWbemRefreshingServices::AddObjectToRefresher and
IWbemRefreshingServices::AddObjectToRefresherByTemplate ................125
3.2.4.5.2 IWbemRefreshingServices::AddEnumToRefresher ..................................126
3.2.4.5.3 IWbemRefreshingServices::GetRemoteRefresher ...................................126
3.2.4.5.4 IWbemRefreshingServices::ReconnectRemoteRefresher ..........................127
3.2.5 Timer Events ................................................................................................127
3.2.6 Other Local Events ........................................................................................127
4 Protocol Examples ................................................................................................ 128

4.1 Protocol Initialization ...........................................................................................128
4.2 Synchronous Operations ......................................................................................129
4.2.1 Synchronous Delivery of a Single Result ...........................................................130
4.2.2 Synchronous Delivery of Result Sets ................................................................130
4.2.2.1 Unoptimized Client and Unoptimized Server ................................................130
4.2.2.2 Unoptimized Client and Optimized Server ...................................................131
4.2.2.3 Optimized Client and Optimized Server.......................................................132
4.2.2.4 Optimized Client and Unoptimized Server ...................................................133
4.3 Semisynchronous Operations ...............................................................................134
4.3.1 Semisynchronous Delivery of a Single Result ....................................................135
4.3.2 Semisynchronous Delivery of Result Sets .........................................................135
4.4 Asynchronous Delivery of Results .........................................................................135
4.5 Optimized Asynchronous Delivery of Results ..........................................................137
4.6 Configuring Refreshing Services ...........................................................................137
4.7 Using the Refresher Interface ...............................................................................138
5 Security ................................................................................................................ 140

5.1 Security Considerations for Implementers ..............................................................140
5.2 Index of Security Parameters ...............................................................................140
6 Appendix A: Full IDL............................................................................................. 142
7 Appendix B: Product Behavior .............................................................................. 155
8 Change Tracking................................................................................................... 159
9 Index ................................................................................................................... 166
6 / 168
[MS-WMI] — v20091104

1 Introduction
Windows Management Instrumentation (WMI) is a Distributed Component Object Model
(DCOM), as specified in [MS-DCOM], a client/server–based framework that provides an open and
automated means of systems management. WMI leverages the Common Information Model
(CIM), as specified in [DMTF-DSP004], to represent various components of the operating system.
CIM is the conceptual model for storing enterprise management information. The information
available from CIM is specified by a series of classes and associations, and the elements contained
in them (methods, properties, and references). These constructs describe the data available to WMI
clients.
1.1 Glossary
The following terms are defined in [MS-GLOS]:
activation
Augmented Backus-Naur Form (ABNF)
authentication level
class identifier (CLSID)
Common Information Model (CIM)
Common Information Model (CIM) class
Common Information Model (CIM) instance
Common Information Model (CIM) method
Common Information Model (CIM) namespace
Common Information Model (CIM) object
Common Information Model (CIM) path
Common Information Model (CIM) property
Common Information Model (CIM) relative path
Distributed Component Object Model (DCOM)
extrinsic event
globally unique identifier (GUID)
Interface Definition Language (IDL)
interface pointer
intrinsic event
language code identifier (LCID)
manageable entity
Microsoft Interface Definition Language (MIDL)
opnum
release
remote procedure call (RPC)
security principal
security provider
Security Support Provider Interface (SSPI)
superclasses and subclasses
universally unique identifier (UUID)
The following terms are specific to this document:
CIM localizable information: The portion of information in a CIM class definition that could be
language-specific or country-specific.
client: In the context of this specification, "client" is used to identify the system that consumes
WMI services and initiates [MS-DCOM] calls to WMI servers.
7 / 168
[MS-WMI] — v20091104

empty CIM object: A data structure that conforms to the WMI serialization model—has no
properties, no method, and no derivation.
server: In the context of this specification, "server" is used to identify the system that
implements WMI services, provides management services, and accepts [MS-DCOM] calls from
WMI clients.
WMI asynchronous operation: An operation executed on the server side. The client continues
executing and does not check whether a response is available from the server.
WMI Query Language (WQL): A subset of the American National Standards Institute
Structured Query Language (ANSI SQL). WQL differs from standard SQL in that it retrieves
from classes rather than from tables, and returns CIM classes or instances rather than
rows. WQL is specified in section 2.2.1.
WMI semi-synchronous operation: An operation executed on the server side while the client
is regularly checking whether a response is available from the server.
WMI synchronous operation: An operation executed on the server side while the client waits
for the response message.
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
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 [email protected]. 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
[DMTF-DSP004] Distributed Management Task Force, "Common Information Model (CIM)

Infrastructure Specification", Version 2.3, October 2005,
http://www.dmtf.org/standards/published_documents/DSP0004V2.3_final.pdf
[FIPS127] Federal Information Processing Standards Publication, "Database Language SQL", FIPS
PUB 127, June 1993, http://www.itl.nist.gov/fipspubs/fip127-2.htm
[IEEE754] Institute of Electrical and Electronics Engineers, "Standard for Binary Floating-Point
Arithmetic", IEEE 754-1985, October 1985, http://ieeexplore.ieee.org/servlet/opac?punumber=2355
[MS-DCOM] Microsoft Corporation, "Distributed Component Object Model (DCOM) Remote Protocol
Specification", March 2007.
[MS-DTYP] Microsoft Corporation, "Windows Data Types", January 2007.
[MS-ERREF] Microsoft Corporation, "Windows Error Codes", January 2007.
[MS-LCID] Microsoft Corporation, "Windows Language Code Identifier (LCID) Reference", July 2007.
8 / 168
[MS-WMI] — v20091104

[MS-OAUT] Microsoft Corporation, "OLE Automation Protocol Specification", March 2007.
[MS-RPCE] Microsoft Corporation, "Remote Procedure Call Protocol Extensions", January 2007.
[MS-WMIO] Microsoft Corporation, "Windows Management Instrumentation Encoding Version 1.0

Protocol Specification", September 2007.
[RFC1001] Network Working Group, "Protocol Standard for a NetBIOS Service on a TCP/UDP
Transport: Concepts and Methods", STD 19, RFC 1001, March 1987,
http://www.ietf.org/rfc/rfc1001.txt
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC
2119, March 1997, http://www.ietf.org/rfc/rfc2119.txt
[UNICODE] The Unicode Consortium, "Unicode Home Page", 2006, http://www.unicode.org/
1.2.2 Informative References
[DFS-R WMI] Microsoft Corporation, "DFSR WMI Classes", http://msdn.microsoft.com/en-

us/library/bb540028.aspx
Note This WMI management interface is exposed as a public API in Windows Server 2003 R2,
Windows Server 2008, and Windows Server 2008 R2. A .mof file publishing the capabilities of the
WMI provider associated with DFS-R is included in the DFS-R distribution under
%%SYSTEM_ROOT%%\webm\dfsrprov.mof.
[MS-GLOS] Microsoft Corporation, "Windows Protocols Master Glossary", March 2007.
[MSDN-OpenEvent] Microsoft Corporation, "OpenEvent Function", http://msdn.microsoft.com/en-

us/library/ms684305.aspx
[MSDN-WQL] Microsoft Corporation, "Querying with WQL", http://msdn.microsoft.com/en-

us/library/aa392902.aspx
[MSDN-WMISYSCLASSES] Microsoft Corporation, "WMI System Classes",

http://msdn.microsoft.com/en-us/library/aa394583.aspx
1.3 Protocol Overview (Synopsis)
The Windows Management Instrumentation Remote Protocol is the Microsoft implementation of the
Common Information Model (CIM), as specified in [DMTF-DSP004]. The Windows Management
Instrumentation Remote Protocol uses CIM as the conceptual model for representing enterprise
management information that can be managed by an administrator.
The Windows Management Instrumentation Remote Protocol is implemented in Microsoft Windows®

in a three-tier architecture, as illustrated in the following figure.
9 / 168
[MS-WMI] — v20091104

Figure 1: Windows Management Instrumentation Remote Protocol architecture
At layer 3, the Windows Management Instrumentation Remote Protocol management data sources
are designed to interact locally with Windows manageable entities. Layer 2 supports the core of
the Windows Management Instrumentation Remote Protocol service and is called the CIM Object
Manager (CIMOM). CIMOM interacts with the Windows Management Instrumentation Remote
Protocol management data sources, the database storing and caching CIM class definitions and
CIM instances from the [DMTF-DSP004]. Layer 1 implements the Distributed Component Object
Model interfaces (as specified in [MS-DCOM]) that are used by the Windows Management
Instrumentation Remote Protocol to communicate over the network between Windows Management
Instrumentation Remote Protocol clients and servers. This layer is the only layer that communicates
over the network. Network communication is achieved by using the Distributed Component Object
Model (DCOM) Remote Protocol and a set of Windows Management Instrumentation Remote
Protocol DCOM interfaces, as specified in section 3.1.4.
10 / 168
[MS-WMI] — v20091104

Figure 2: Clients can be local or remote from the server
Windows Management Instrumentation Remote Protocol clients can be local or remote from the
server, as illustrated in the preceding figure. In either case, the same set of Windows Management
Instrumentation Remote Protocol interfaces is used. The server makes no differentiation between a
local client and a remote client. Likewise, if the client is running on the server, the client makes no
differentiation.
The communication works the same way between clients and server; all interactions between clients
and server are made through the DCOM Remote Protocol locally or remotely. Therefore, clients are
always acting in a message submission mode through the DCOM Remote Protocol to leverage the
Windows Management Instrumentation Remote Protocol interfaces that are implemented on the
server side.
11 / 168
[MS-WMI] — v20091104

The client may call the server in one of the following ways
1. Synchronous calls
2. Semi-Synchronous calls
3. Asynchronous calls
The server APIs for synchronous and semi-synchronous APIs are the same, but the call is executed
synchronously if the flags do not contain WBEM_FLAG_RETURN_IMMEDIATELY. If the flag
WBEM_FLAG_RETURN_IMMEDIATELY is specified, the call is executed semi-synchronously.
Examples for such APIs are, IWbemServices::GetObject, IWbemServices::PutClass etc.
The IWbemServices methods that end with Async are asynchronous counterparts for their
synchronous APIs. Example for async APIs are, IWbemServices::GetObjectAsync,
IWbemServices::PutClassAsync etc.
The management information that is exchanged between clients and server (and server and clients)
is transmitted over the network by the Windows Management Instrumentation Remote Protocol as a
custom-marshaled payload, as specified in [MS-DCOM].
The Windows Management Instrumentation Remote Protocol serializes the management information
that is transmitted, as specified in [MS-WMIO]. Before reading this Windows Management
Instrumentation Remote Protocol document, acquire a working knowledge of the concepts,
structures, and communication protocols as specified in [MS-DCOM], [DMTF-DSP004], and [MS-
WMIO]. Namespace security is controlled by using security descriptors, as specified in [MS-DTYP].
1.4 Relationship to Other Protocols
The Windows Management Instrumentation Remote Protocol uses the DCOM Remote Protocol to
communicate over the network and to authenticate all requests issued against the infrastructure.
The DCOM Remote Protocol is actually the foundation for the Windows Management Instrumentation
Remote Protocol and is used to accomplish the following:
Establish the protocol.
Secure the communication channel.
Authenticate clients.
Implement a reliable communication between clients and servers.
This implies that the DCOM Remote Protocol implementation provides and uses all underlying
protocols, as specified in [MS-RPCE], [MS-DCOM], and [C706].
Besides DCOM Remote Protocol support, the Windows Management Instrumentation Remote
Protocol uses a special encoding, as specified in [MS-WMIO], to transfer information as specified in
[DMTF-DSP004] over the network.
1.5 Prerequisites/Preconditions
The client that uses the protocol possesses valid credentials that are recognized by the server
accepting the client requests. The client uses security providers that recognize such credentials to
authenticate to the remote server by using the Security Support Provider Interface (SSPI),
which is supported by the Remote Procedure Call Protocol.
12 / 168
[MS-WMI] — v20091104

The server system is started with the DCOM Remote Protocol activation service fully initialized
before the activation request. The client is configured to receive activation requests from the server
if it wants to call the service asynchronously, as specified in section 4.4.
An implementation of the DCOM Remote Protocol needs to be available.
1.6 Applicability Statement
The Windows Management Instrumentation Remote Protocol implementation is designed for

managing Microsoft Windows® components that are represented by CIM classes on remote clients
and servers. This protocol is designed to act as a transport for CIM-compatible management objects
and operations on CIM objects.
1.7 Versioning and Capability Negotiation
This document covers versioning issues in the following areas. The Windows Management
Instrumentation Remote Protocol does explicit negotiation as follows:
The client of this protocol uses the mechanism, as specified in [MS-DCOM] section 1.7, to
discover which interfaces are supported by the exported object and to interpret the
E_NOINTERFACE result, as specified in [MS-DCOM] section 1.7. The client then adjusts its
behavior based on the availability of the requested interface, as specified in sections 3.2.3 and
3.2.4.2.6.
The protocol uses return codes as a capability discovery mechanism; the client interprets them as
a capability negotiation, as specified in section 3.2.4.1.1. Microsoft Windows® behavior is
documented in the respective sections.
The protocol uses return values and parameters to negotiate the locale capabilities of the server
as specified in section 3.2.3.
1.8 Vendor-Extensible Fields
In order to extend the CIM schema with Microsoft Windows® using the Windows Management
Instrumentation Remote Protocol, Vendors MUST use operations as specified in section 3.1.4.3.
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
There are no standards assignments for this protocol. This protocol uses the following class
identifiers (CLSIDs) (as specified in [MS-DCOM] section 1.9):
CLSID_WbemLevel1Login ({8BC3F05E-D86B-11D0-A075-00C04FB68820})
CLSID_WbemBackupRestore ({C49E32C6-BC8B-11D2-85D4-00105A1F8304})
The following GUIDs are used for the interfaces:
IID_IWbemLevel1Login ({F309AD18-D86A-11d0-A075-00C04FB68820})
IID_IWbemLoginClientID ({d4781cd6-e5d3-44df-ad94-930efe48a887})
IID_IWbemLoginHelper ({541679AB-2E5F-11d3-B34E-00104BCC4B4A})
13 / 168
[MS-WMI] — v20091104

IID_IWbemServices ({9556DC99-828C-11CF-A37E-00AA003240C7})
IID_IWbemBackupRestore ({C49E32C7-BC8B-11d2-85D4-00105A1F8304})
IID_IWbemBackupRestoreEx ({A359DEC5-E813-4834-8A2A-BA7F1D777D76})
IID_IWbemClassObject ({DC12A681-737F-11CF-884D-00AA004B2E24})
IID_IWbemContext ({44aca674-e8fc-11d0-a07c-00c04fb68820})
14 / 168
[MS-WMI] — v20091104

2 Messages
The following sections specify how Windows Management Instrumentation Remote Protocol
messages are transported and specify Windows Management Instrumentation Remote Protocol
message syntax.
2.1 Transport
Windows Management Instrumentation Remote Protocol messages MUST be transported via the
DCOM Remote Protocol. The Windows Management Instrumentation Remote Protocol objects that
are exported by the WMI server MUST be capable of DCOM activation, as specified in [MS-DCOM]
section 3.1.4.1.1.
The client connection MUST be secured at an authentication level that is negotiated by the DCOM
Remote Protocol infrastructure.
2.2 Common Data Types
2.2.1 WQL Query
A client has the capability to express a query against a server. This query MUST be expressed in the
WMI Query Language (WQL). WQL is a subset of the American National Standards Institute
Structured Query Language, as specified in [FIPS127] and [MSDN-WQL]. WQL differs from the
standard SQL in that WQL retrieves from classes rather than tables, and returns CIM classes or CIM
instances rather than rows. WQL supports a specific semantic designed to query against CIM classes
or CIM instances with their related characteristics. Queries MUST be of one of the following 3 forms:
Schema queries: Queries focused on CIM classes.
Data queries: Queries focused on CIM instances.
Event queries: Queries focused on events triggered by state changes of CIM classes or CIM
instances. Events triggered on CIM instances can be internal to the infrastructure (intrinsic) or
external to the infrastructure (extrinsic). Events can also be timer events.
WQL uses terminologies and concepts, as specified in [DMTF-DSP004], and requires familiarity with
the CIM model.
The next section specifies the complete syntax of WQL queries for schema, data, and event queries.
2.2.1.1 WQL Schema and Data Query
The syntax for the WQL schema and data queries is provided in Augmented Backus-Naur Form
(ABNF).
; -----------------------------------
; WQL schema and data queries
; -----------------------------------
DATA-WQL =
("SELECT" <PROPERTY-LIST> "FROM" <CLASS-NAME>
<OPTIONAL-SEL-WHERE>)/
("SELECT" ASTERISK "FROM" <CLASS-NAME> <OPTIONAL-SEL-WHERE>)/
("SELECT" ASTERISK "FROM META_CLASS" <OPTIONAL-META-WHERE>)/
15 / 168
[MS-WMI] — v20091104

("ASSOCIATORS OF {" <OBJECT-REL-PATH> "}"
<OPTIONAL-ASSOC-WHERE>)/
("REFERENCES OF {" <OBJECT-REL-PATH> "}" <OPTIONAL-REF-WHERE>)
PROPERTY-LIST = <PROPERTY-NAME> <PROPERTY-LIST2>

PROPERTY-LIST2 = [COMMA <PROPERTY-LIST>]
OPTIONAL-SEL-WHERE = ["WHERE" <EXPR>]

OPTIONAL-META-WHERE = ["WHERE __THIS ISA" <CLASS-NAME>]
OPTIONAL-ASSOC-WHERE =
["WHERE" [ "AssocClass=" <CLASS-NAME> BLANK ]
[ "RequiredAssocQualifier=" <QUALIFIER-NAME> BLANK ]
[ "RequiredQualifier=" <QUALIFIER-NAME> BLANK ]
[ "ResultClass=" <CLASS-NAME> BLANK ]
[ "ResultRole=" <PROPERTY-NAME> BLANK ]
[ "Role=" <PROPERTY-NAME> BLANK ]
[ "KeysOnly" BLANK ]
[ "ClassDefsOnly" BLANK ]
]
OPTIONAL-REF-WHERE =
["WHERE" [ "RequiredQualifier=" <QUALIFIER-NAME> BLANK ]
[ "ResultClass=" <CLASS-NAME> BLANK ]
[ "Role=" <PROPERTY-NAME> BLANK ]
[ "KeysOnly" BLANK ]
[ "ClassDefsOnly" BLANK ]
]
OBJECT-REL-PATH =
<CLASS-NAME> "=" <TYPED-CONSTANT> <OBJECT-REL-PATH2>
OBJECT-REL-PATH2 =
[COMMA <OBJECT-REL-PATH>]
; -----------------------------------
; Expression
; -----------------------------------
EXPR =
( [OPEN-PARENTHESIS] <PROPERTY-EVALUATION>
<EXPR2> [CLOSE-PARENTHESIS] ) /
( [OPEN-PARENTHESIS] "__CLASS" <EQUIVALENT-OPERATOR>
<CLASS-NAME> <EXPR2> [CLOSE-PARENTHESIS] )
EXPR2 = ( ["OR" [OPEN-PARENTHESIS] <EXPR> [CLOSE-PARENTHESIS] ])/

( ["AND" [OPEN-PARENTHESIS] <EXPR> [CLOSE-PARENTHESIS] ])
PROPERTY-EVALUATION =
( <PROPERTY-NAME> <OPERATOR> <TYPED-CONSTANT> ) /
( <PROPERTY-NAME> <IS-OPERATOR> "NULL" )
OPERATOR = <EQUIVALENT-OPERATOR> /
<COMPARE-OPERATOR>
EQUIVALENT-OPERATOR = "=" / "!="

COMPARE-OPERATOR = "<=" / ">=" / "<" / ">" / "LIKE"
IS-OPERATOR = "IS" / "IS NOT"
; -----------------------------------
; Characters
; -----------------------------------
16 / 168
[MS-WMI] — v20091104

ALPHA = %x41-5A
DIGIT = %x30-39
COMMA = ","
ASTERISK = "*"
OPEN-PARENTHESIS = "("
CLOSE-PARENTHESIS = ")"
BLANK = " " / "\x09"
STRING-IDENTIFIER = ALPHA *(ALPHA / DIGIT / (*("_") ALPHA / DIGIT))
CLASS-NAME = [__]<STRING-IDENTIFIER>
PROPERTY-NAME = [__]<STRING-IDENTIFIER>
QUALIFIER-NAME = <STRING-IDENTIFIER>
TYPED-CONSTANT = INT /
REAL /
STRING /
DATETIME /
BOOL
INT = "[-+]?\d+"
REAL = "[-+]?(\d*\.\d+)|(\d+)"
STRING = ["]([a-z][A-Z]\d)*["]
DATETIME =
"(\d\d\d\d)(0\d|1[012])(0\d|[12][0-9]|3[01])([0-1]\d|2[0-3])
([0-5]\d)([0-5]\d)[.]\d\d\d\d\d\d[+-]([0-6][02468][0]|7[0-2][0])"
BOOL = "TRUE" / "FALSE"
Schema objects and

keywords Description
CLASS-NAME Identifies the CIM class name to be queried.
PROPERTY-NAME Identifies the name of a property of the CIM class.
QUALIFIER-NAME In the context of a WQL query, QUALIFIER-NAME is an attribute of a

PROPERTY-NAME defining the nature of an association with another CIM class.
DATA-WQL A string expressing the WQL query. The WQL string uses different WQL
reserved keywords to select the type of information desired.
SELECT A keyword expressing the selection of information requested (similar to SQL

SELECT). SELECT expresses the CIM class or CIM instance to be queried. It
MUST be specified when the ASSOCIATORS OF or the REFERENCES OF
keyword is not used. It MUST NOT be used when the ASSOCIATORS OF or the
REFERENCES OF keyword is used.
PROPERTY-LIST A list of PROPERTY-NAME values. PROPERTY-NAME values in the list MUST be

separated by a comma (",").
ASTERISK Requires all properties of a CIM class or a CIM instance.
FROM A keyword that MUST be specified with the SELECT statement to express the
17 / 168
[MS-WMI] — v20091104

Schema objects and
CIM class or CIM instance the query MUST be executed against.
OPTIONAL-SEL-WHERE The WHERE statement narrows the scope of a SELECT.
OPTIONAL-META- The WHERE statement narrows the scope of a SELECT. The WHERE statement
WHERE followed by the __THIS ISA statement is narrowing the scope of the WQL query
to return CIM instances only made out of the CLASS-NAME specified.
__CLASS A keyword referring to the CIM object, indicating the class of the current CIM
object. The __CLASS keyword in a WHERE clause only selects CIM instances of
derived classes made out of the CLASS-NAME.
ASSOCIATORS OF A keyword that is a WQL statement to locate associated CIM classes or CIM
instances. It MUST NOT be used in combination with the SELECT keyword and
the REFERENCES OF keyword.
OPTIONAL-ASSOC- If the WHERE statement is specified in an ASSOCIATORS OF WQL query, it

WHERE narrows the scope to one or several characteristics of the association and
associated CIM classes. The filter expression can be made of several specific
keywords and expressions to validate these characteristics. Each expression
MUST be separated by a BLANK character, as specified in the preceding ABNF
notation. Each expression MUST NOT be used more than once in a single WQL
query. The keyword supported to narrow the scope of an ASSOCIATORS OF
query are AssocClass, RequiredAssocQualifier, RequiredQualifier, ResultClass,
ResultRole, Role, KeysOnly, and ClassDefsOnly.
REFERENCES OF A keyword that is a WQL statement to locate the CIM classes or CIM instances
associating CIM classes or CIM instances. It MUST NOT be used in combination
with the SELECT keyword and the ASSOCIATORS OF keyword.
OPTIONAL-REF-WHERE If the WHERE statement is specified in a REFERENCES OF query, it narrows the

scope to one or several characteristics of the association and associated
classes. The filter expression can be made of several specific keywords and
expressions to express these characteristics. Each expression MUST be
separated by a BLANK character. Each expression MUST NOT be used more
than once in a single WQL query. The keywords supported to narrow the scope
of a REFERENCES OF query are RequiredQualifier, ResultClass, Role, KeysOnly,
and ClassDefsOnly.
OBJECT-REL-PATH The CIM relative path of the CIM class or CIM instance to be queried. It
MUST be specified for ASSOCIATORS OF and REFERENCES OF queries.
KeysOnly If the KeysOnly keyword is being used in ASSOCIATORS OF and REFERENCES

OF queries, only the key properties of resulting CIM instances MUST be
populated.
ClassDefsOnly If the ClassDefsOnly keyword is being used in ASSOCIATORS OF and

REFERENCES OF queries only the CIM class definitions of resulting CIM
instances MUST be returned.
AssocClass If the AssocClass keyword is being used in ASSOCIATORS OF queries, the

resulting CIM instances MUST be associated with association class or CIM
instances made out of the CLASS-NAME specified.
RequiredAssocQualifier If the RequiredAssocQualifier keyword is being used in ASSOCIATORS OF

queries, the resulting CIM instances MUST have the CIM Qualifier of the given
name set in their association class or CIM instances.
18 / 168
[MS-WMI] — v20091104

Schema objects and
RequiredQualifier If the RequiredQualifier keyword is being used in ASSOCIATORS OF and

REFERENCES OF queries, the resulting CIM instances MUST have the CIM
qualifier of the given name set.
ResultClass If the ResultClass keyword is being used in ASSOCIATORS OF and

REFERENCES OF queries, the resulting CIM instances MUST be made out of the
CLASS-NAME specified.
Role If the Role keyword is being used in ASSOCIATORS OF and REFERENCES OF

queries, the result MUST only return CIM instances where the role matches the
reference CIM Property name of the association class.
ResultRole If the ResultRole keyword is being used in ASSOCIATORS OF queries, the result
MUST only return CIM instances where the role matches the reference CIM
Property name of the CIM instances.
2.2.1.2 WQL Event Query
The following example shows the syntax for WQL event queries in ABNF notation.
; -----------------------------------
; WQL event queries
; -----------------------------------
EVENT-WQL = "SELECT" <PROPERTY-LIST> "FROM" /

<EVENT-CLASS-NAME> <OPTIONAL-WITHIN> <EVENT-WHERE>
OPTIONAL-WITHIN = ["WITHIN" <INTERVAL>]

INTERVAL = 1*DIGIT
EVENT-WHERE = ["WHERE" <EVENT-EXPR>]
EVENT-EXPR = ( (<INSTANCE-STATE> "ISA" <CLASS-NAME> <EXPR2>) /

<EXPR> )
["GROUP WITHIN" <INTERVAL>
( ["BY" [<INSTANCE-STATE> DOT] <PROPERTY-NAME>]
["HAVING" <EXPR>]] )
INSTANCE-STATE = "TARGETINSTANCE" / "PREVIOUSINSTANCE"
; -----------------------------------
; Expression
; -----------------------------------
EXPR =
[OPEN-PARENTHESIS] <PROPERTY-EVALUATION> /
<EXPR2> [CLOSE-PARENTHESIS]
EXPR2 = ( ["OR" [OPEN-PARENTHESIS] <EXPR> /
[CLOSE-PARENTHESIS] ] ) /
( ["AND" [OPEN-PARENTHESIS] <EXPR> /
[CLOSE-PARENTHESIS] ] )
PROPERTY-EVALUATION =
( <PROPERTY-NAME> <OPERATOR> <TYPED-CONSTANT> ) /
( <PROPERTY-NAME> <IS-OPERATOR> "NULL" )
OPERATOR = <EQUIVALENT-OPERATOR> /
19 / 168
[MS-WMI] — v20091104

<COMPARE-OPERATOR>
EQUIVALENT-OPERATOR = "=" / "!="

COMPARE-OPERATOR = "<=" / ">=" / "<" / ">" / "LIKE"
IS-OPERATOR = "IS" / "IS NOT"
; -----------------------------------
; Characters
; -----------------------------------
ALPHA = %x41-5A
DIGIT = %x30-39
DOT = ","
COMMA = "."
ASTERISK = "*"
OPEN-PARENTHESIS = "("
CLOSE-PARENTHESIS = ")"
EVENT-CLASS-NAME = [__]<STRING-IDENTIFIER>
REAL /
STRING /
DATETIME /
BOOL
INT = "[-+]?\d*"
REAL = "[-+]?\d*(\.\d+)?"
STRING = ["]([a-z][A-Z]\d)*["]
DATETIME = "(\d\d\d\d)(0\d|1[012])(0\d|[12][0-9]|3[01])
([0-1]\d|2[0-3])([0-5]\d)([0-5]\d)[.]\d\d\d\d\d\d[+-]
([0-6][02468][0]|7[0-2][0])"
Objects and
CLASS-NAME Identifies a CIM class name to be queried for events.
PROPERTY- Identifies the name of a CIM property of a CIM class.

NAME
EVENT-WQL A string expressing the WQL event query. The WQL string uses different WQL reserved
keywords to select the type of information wanted.
SELECT A keyword expressing the selection of information requested (similar to SQL SELECT).
SELECT expresses the CIM class or CIM instance to be queried. It MUST be specified in a
WQL event query.
PROPERTY- A list of PROPERTY-NAME values. PROPERTY-NAME values in the list MUST be separated
LIST by a comma (",").
20 / 168
[MS-WMI] — v20091104

Objects and
ASTERISK Requires all properties of a CIM class or a CIM instance.
FROM A keyword that MUST be specified with the SELECT statement to express the CIM class or
CIM instance that the query MUST be run against.
EVENT- MUST be specified and MUST be an intrinsic, an extrinsic, or a timer event class. An
CLASS-NAME intrinsic event class is a class derived from __InstanceOperationEvent,
__ClassOperationEvent, or __NamespaceOperationEvent, representing possible intrinsic
events. An extrinsic event class is a class derived from __ExtrinsicEvent, representing
possible extrinsic events. A timer event class is a class derived from __TimerEvent event
class, representing possible timer events.
WITHIN A keyword indicating the server to poll the system for an event. In case of an intrinsic
EVENT-CLASS-NAME, the WITHIN keyword MUST be specified. The WITHIN keyword is
optional for extrinsic EVENT-CLASS-NAME. If the WITHIN keyword is specified, the
INTERVAL MUST be specified.
INTERVAL INTERVAL specifies the polling interval. It MUST be expressed in seconds. If "WITHIN" is
specified, the INTERVAL MUST be specified.
EVENT- The WHERE statement narrows the scope of a SELECT event query if the EVENT-CLASS-
WHERE NAME is an extrinsic or timer event CIM class. The WHERE statement MUST be specified to
narrow the scope of a SELECT event query if the EVENT-CLASS-NAME is an intrinsic CIM
class.
INSTANCE- Indicates the type of instance to be evaluated. INSTANCE-STATE MUST be specified if

STATE CLASS-NAME is an intrinsic CIM class. INSTANCE-STATE is optional if CLASS-NAME is an
extrinsic CIM class. If specified, INSTANCE-STATE MUST be PREVIOUSINSTANCE (to
indicate that the state of the CIM class or CIM instance before the event MUST be
evaluated) or TARGETINSTANCE (to indicate that the state of the CIM class or CIM
instance after the event MUST be evaluated).
ISA A keyword that MUST be used in combination with the INSTANCE-STATE keyword. It is
used as a comparative operator between the INSTANCE-STATE and a CLASS-NAME to
reduce the scope of events returned to the CIM instances made out of the CLASS-NAME.
GROUP If the GROUP WITHIN keyword is used, the INTERVAL MUST be specified. This keyword
WITHIN indicates that all events occurring during the WITHIN INTERVAL period MUST be grouped
as one event.
HAVING If the HAVING keyword is specified, it MUST be followed by EXPR to filter the selection of
events. This keyword indicates that all events grouped during the GROUP WITHIN period
MUST meet the expression specified in EXPR before being returned as one event.
BY A keyword that groups event instances sharing a same value on a specified PROPERTY-
NAME. In such a case, events are returned that represent a group of events sharing the
same PROPERTY-NAME value. The system MUST return as many events representing a
group of events as there are PROPERTY-NAME values.
EVENT-EXPR An expression for filtering WMI events.
2.2.2 CIM Path and Namespace
The syntax for CIM path and namespace is provided in ABNF notation.
; -----------------------------------
21 / 168
[MS-WMI] — v20091104

; CIM PATH
; -----------------------------------
CIMPATH = ( <NAMESPACE-PATH> COLON <OBJECT-PATH> ) /

<OBJECT-PATH>
NAMESPACE-PATH = [<MACHINE-PATH>] NAMESPACE
MACHINE-PATH = BACKSLASH BACKSLASH <MACHINENAME> BACKSLASH
OBJECT-PATH = <CLASS-NAME> [<INSTANCE-KEY>]
INSTANCE-KEY = (EQUAL "@") / DOT <KEY-VALUE-LIST>
KEY-VALUE-LIST = <PROPERTY-NAME> EQUAL
<TYPED-CONSTANT> <KEY-VALUE-LIST2>
KEY-VALUE-LIST2 = [ COMMA KEY-VALUE-LIST ]
; -----------------------------------
; NAMESPACE
; -----------------------------------
NAMESPACE = <STRING-IDENTIFIER> <SUB-NAMESPACE>

<SUB-NAMESPACE> = [ BACKSLASH <NAMESPACE> ]
REAL /
STRING /
DATETIME /
BOOL
INT = "[-+]?\d*"
REAL = "[-+]?\d*(\.\d+)?"
STRING = ["]([a-z][A-Z]\d)*["]
DATETIME =
"(\d\d\d\d)(0\d|1[012])(0\d|[12][0-9]|3[01])
([0-1]\d|2[0-3])([0-5]\d)([0-5]\d)[.]\d\d\d\d\d\d[+-]
([0-6][02468][0]|7[0-2][0])"
; -----------------------------------
; Characters
; -----------------------------------
ALPHA = %x41-5A
DIGIT = %x30-39
BACKSLASH = "\"
DOT = "."
COLON=":"
MACHINENAME = <STRING-IDENTIFIER> / DOT
Objects and
OBJECT-PATH The path of the CIM class or CIM instance to be referenced.
22 / 168
[MS-WMI] — v20091104

Objects and
MACHINENAME The network-identifiable name of the machine where the referenced WMI class,
instance, or namespace resides.
CLASS-NAME Identifies a CIM class name.
INSTANCE-KEY Uniquely identifies the instance of a given CIM class.
KEY-VALUE-LIST List of PROPERTY-NAME and their values, separated by a ",". Each property value
pair is represented as propertyName=value format.
PROPERTY-NAME Identifies the name of a property of the CIM class.
2.2.3 Protocol Return Codes
Codes that are returned by the protocol are represented as an HRESULT, as specified in [MS-ERREF]
section 2.1.
The HRESULT values that are documented in the following table are interpreted by the protocol
through a specific set of interface methods, as specified in sections 3.1.4.3, 3.1.4.4.2, and
3.2.4.1.1.
The severity bit of HRESULT MUST be interpreted as specified in [MS-ERREF] section 2.1. HRESULT
errors are not recoverable by the protocol. HRESULT successes, other than the ones specified in the
following table, MUST be considered as equal to WBEM_S_NO_ERROR.
Constant/value Description
WBEM_S_NO_ERROR The operation was successful.

0x00000000
WBEM_S_FALSE Either no more CIM objects are available, the number of returned CIM objects is
0x00000001 less than the number requested, or this is the end of an enumeration.
WBEM_S_TIMEDOUT A call timed out. This is not an error condition.

0x00040004
WBEM_S_NEW_STYLE The operation was successful and indicates that the receiver of the call is able to
0x000400FF receive optimized IWbemObjectSink::Indicate calls.
2.2.4 IWbemClassObject Interface
The signatures of many methods that are related to the Windows Management Instrumentation
Remote Protocol include a parameter to specify an IWbemClassObject interface pointer. This
parameter MUST be custom marshaled by the DCOM Remote Protocol, as specified in the following
table. The IWbemClassObject interface represents a WMI object, such as a WMI class or an object
instance. All CIM objects (CIM classes and CIM instances) that are passed during WMI calls between
the client and server are objects of this interface.
Parameter/source Value/description
Interface UUID {DC12A681-737F-11CF-884D-00AA004B2E24}
23 / 168
[MS-WMI] — v20091104

Marshaling buffer The buffer representing a CIM object MUST be encoded using the EncodingUnit
layout object block, as specified in [MS-WMIO] section 2.2.1.
Unmarshaler CLSID {4590F812-1D3A-11D0-891F-00AA004B2E24}

This CLSID MUST represent the unmarshaler CLSID that is supplied by WMI to
DCOM and MUST be sent over the network by DCOM when custom marshaling is
implemented. For more information (OBJREF_CUSTOM), see the DCOM Remote
Protocol.
2.2.4.1 Prototype Result Object
The prototype result object is an IWbemClassObject that is returned when the lFlags parameter of
the IWbemServices::ExecQuery or IWbemServices::ExecQueryAsync method includes the
WBEM_FLAG_PROTOTYPE flag.
The query returns the CIM class object that is specified in the CLASS-NAME of the query that is
modified to match the query.
If the query specifies PROPERTY-LIST, as specified in section 2.2.1.1, the class object is modified
to represent the results of the query by removing all the properties that are not specified in the
PROPERTY-LIST of the query and by adding selected properties with the Order qualifier (see the
2nd paragraph following concerning the Order qualifier). In this case, the CIM class is encoded as an
IWbemClassObject object, as specified in section 2.2.4, with an ObjectFlags block that contains a
0x10 value that is set as specified in [MS-WMIO] section 2.2.6. If any key property is removed
because it is not specified in PROPERTY-LIST, the 0x40 flag is set on ObjectFlags.
If the query specifies ASTERISK, as specified in section 2.2.1.1, the class object is returned with all
the properties added to the Order qualifier. In this case, the CIM class is encoded as an
IWbemClassObject object and the 0x10 flag is not set in ObjectFlags.
The Order qualifier (QUALIFIER-NAME attribute set to Order, see 2.2.1.1) is an array of 32-bit
signed integers. Each value in the array represents the position of the property in PROPERTY-LIST
(if PROPERTY-LIST is specified) or represents the order in which the property appears in the class
(if the query specifies ASTERISK). The position is encoded starting from 0.
For example,
select prop1,prop2,prop1 from class1
results in class1 containing only two properties, prop1 and prop2. The prop1 property is added to
an Order qualifier that has a value of {0,2}, and the prop2 property is added to an Order qualifier
that has a value of {1}.
Note The prop1 property occurs twice in the PROPERTY-LIST, at positions 1 and 3, and
therefore, has two values {0,2}.
If the query specifies a PROPERTY-LIST that does not contain at least one of the following
properties, the DerivationList in ClassPart of the CurrentClass, as specified in [MS-WMIO] section
2.2.17, is encoded as empty:
__DERIVATION
__SUPERCLASS
24 / 168
[MS-WMI] — v20091104

__DYNASTY
Otherwise, the DerivationList in ClassPart of the CurrentClass is encoded in the same way as the
actual CIM class that represents the CLASS-NAME of the query.
The PropertyLookupTable, NdTable, ValueTable, and ClassHeap in ClassPart of the CurrentClass (as
specified in [MS-WMIO] section 2.2.15) are encoded to contain only the selected properties in the
query.
Remaining items are encoded in the same way as the CIM class that represents the CLASS-NAME
that is specified in the query.
2.2.4.2 Extrinsic Events
Extrinsic events are events generated by a component outside the implementation. In WMI,
extrinsic events are represented as instances of a class that is derived from the __ExtrinsicEvent
class. If any component wants to generate an event, the component defines a class that is derived
from the __ExtrinsicEvent class. Instances of the derived class defined by the component,
represented by using IWbemClassObject, are used to send events.
__ExtrinsicEvent class is defined by WMI as shown in the following MOF text.
[abstract]
class __SystemClass
{
};
[abstract]
class __IndicationRelated : __SystemClass
{
};
[abstract: DisableOverride ToInstance ToSubClass]

class __Event : __IndicationRelated
{
uint64 TIME_CREATED;
uint8 SECURITY_DESCRIPTOR[];
};
class __ExtrinsicEvent : __Event

{
};
Where TIME_CREATED is the time at which the event is generated, represented as a 64-bit value
that represents the number of 100-nanosecond intervals since January 1, 1601 (UTC), and
SECURITY_DESCRIPTOR is a standard Windows security descriptor, as defined in [MS-DTYP],
represented as an array of bytes. The security descriptor MUST specify security for events as
specified in section 5.2.
2.2.5 WBEM_CHANGE_FLAG_TYPE Enumeration
The WBEM_CHANGE_FLAG_TYPE enumeration is used to indicate and update the type of the flag.
25 / 168
[MS-WMI] — v20091104

typedef [v1_enum] enum tag_WBEM_CHANGE_FLAG_TYPE
{
WBEM_FLAG_UPDATE_ONLY = 0x01,
WBEM_FLAG_CREATE_ONLY = 0x02,
WBEM_FLAG_UPDATE_SAFE_MODE = 0x20,
WBEM_FLAG_UPDATE_FORCE_MODE = 0x40
} WBEM_CHANGE_FLAG_TYPE;
WBEM_FLAG_UPDATE_ONLY: This flag causes the put operation to update the class or
instance. The class or instance MUST exist for the call to be successful.
WBEM_FLAG_CREATE_ONLY: This flag causes the put operation to create the class or
instance. For the call to be successful, the class or instance MUST NOT exist.
WBEM_FLAG_UPDATE_SAFE_MODE: This flag allows updates of classes even if there are

child classes, as long as the change does not cause any conflicts with child classes. An
example of an update that this flag allows is the adding of a new property to the base class
that was not previously mentioned in any of the child classes. If the class has instances, the
update fails.
WBEM_FLAG_UPDATE_FORCE_MODE: This flag forces updates of classes when conflicting

child classes exist. An example of an update that this flag forces is when a class qualifier is
defined in a child class and the base class tries to add the same qualifier that conflicted with
the existing one. In force mode, this conflict is resolved by deleting the conflicting qualifier in
the child class.
2.2.6 WBEM_GENERIC_FLAG_TYPE Enumeration
The WBEM_GENERIC_FLAG_TYPE enumeration is used to indicate and update the type of the
flag.
typedef [v1_enum] enum tag_WBEM_GENERIC_FLAG_TYPE

{
WBEM_FLAG_RETURN_IMMEDIATELY = 0x10,
WBEM_FLAG_FORWARD_ONLY = 0x20,
WBEM_FLAG_SEND_STATUS = 0x80,
WBEM_FLAG_ENSURE_LOCATABLE = 0x100,
WBEM_FLAG_DIRECT_READ = 0x200,
WBEM_FLAG_USE_AMENDED_QUALIFIERS = 0x20000
} WBEM_GENERIC_FLAG_TYPE;
WBEM_FLAG_RETURN_IMMEDIATELY: This flag causes the call to return without waiting for
the operation to complete. The call result parameter contains the IWbemCallResult object by
using the status of the operation that can be retrieved.
WBEM_FLAG_FORWARD_ONLY: This flag causes a forward-only enumerator

(IEnumWbemClassObject, (section 3.1.4.4)) to be returned. Forward-only enumerators
are typically much faster and use less memory than conventional enumerators; however, they
do not allow calls to IEnumWbemClassObject::Clone or
IEnumWbemClassObject::Reset.
WBEM_FLAG_SEND_STATUS: This flag registers a request with WMI to receive intermediate

status reports through the client implementation of IWbemObjectSink::SetStatus, if
supported by the provider.
26 / 168
[MS-WMI] — v20091104

WBEM_FLAG_ENSURE_LOCATABLE: This flag ensures that any returned objects have enough
information in them so that system properties, such as __PATH, __RELPATH, and
__SERVER,<1> are non-NULL.
WBEM_FLAG_DIRECT_READ: This flag causes direct access to the provider for the specified
class without regard to its parent class or subclasses.
WBEM_FLAG_USE_AMENDED_QUALIFIERS: If this flag is set, the server retrieves any

qualifiers in the CIM object that can be localized in the current connection's locale. The set of
localized qualifiers and the list of locales for which the qualifier is localized are implementation
dependent. When the localized information is available, the server retrieves the localized
values using the client-preferred locale. If the localized values are not available, the server
returns values using the default locale.
If this flag is not set, the server does not retrieve any localized qualifiers for the CIM object.
2.2.7 WBEM_STATUS_TYPE Enumeration
The WBEM_STATUS_TYPE enumeration gives information about the status of the operation.
typedef enum tag_WBEM_STATUS_TYPE

{
WBEM_STATUS_COMPLETE = 0,
WBEM_STATUS_PROGRESS = 0x02
} WBEM_STATUS_TYPE;
WBEM_STATUS_COMPLETE: When the WMI operation is completed, WMI calls

IWbemObjectSink::SetStatus with WBEM_STATUS_COMPLETE.
WBEM_STATUS_PROGRESS: WMI reports the progress of the operation to

IWbemObjectSink::SetStatus with flag WBEM_STATUS_PROGRESS.
2.2.8 WBEM_TIMEOUT_TYPE Enumeration
The WBEM_TIMEOUT_TYPE enumeration gives information about the type of time-out for the
process.
typedef [v1_enum] enum tag_WBEM_TIMEOUT_TYPE

{
WBEM_NO_WAIT = 0,
WBEM_INFINITE = 0xFFFFFFFF
} WBEM_TIMEOUT_TYPE;
WBEM_NO_WAIT: If passed as a time-out parameter to the IEnumWbemClassObject::Next

method, the call returns the available objects, if any, at the time of the call; it does not wait
for any more objects.
WBEM_INFINITE: If passed as a time-out parameter to IEnumWbemClassObject::Next, the

call blocks until objects are available.
2.2.9 WBEM_QUERY_FLAG_TYPE Enumeration
The WBEM_QUERY_FLAG_TYPE enumeration gives information about the type of the flag.
27 / 168
[MS-WMI] — v20091104

typedef [v1_enum] enum tag_WBEM_QUERY_FLAG_TYPE
{
WBEM_FLAG_DEEP = 0,
WBEM_FLAG_SHALLOW = 1,
WBEM_FLAG_PROTOTYPE = 2
} WBEM_QUERY_FLAG_TYPE;
WBEM_FLAG_DEEP: If used in IWbemServices::CreateClassEnum or

IWbemServices::CreateClassEnumAsync, the WBEM_FLAG_DEEP constant causes the
enumeration to return all the subclasses in the hierarchy of a specified class but to not return
the class itself.
If used in IWbemServices::CreateInstanceEnum or
IWbemServices::CreateInstanceEnumAsync, this constant causes the enumeration to
return the instances of this class and also the instances of subclasses in the hierarchy of the
class.
WBEM_FLAG_SHALLOW: If used in IWbemServices::CreateClassEnum or

IWbemServices::CreateClassEnumAsync, the WBEM_FLAG_SHALLOW constant causes the
enumeration to return the immediate subclasses of a specified class.
If used in IWbemServices::CreateInstanceEnum or
IWbemServices::CreateInstanceEnumAsync, this constant causes the enumeration to
return only the instances of this class and excludes all instances of subclasses.
WBEM_FLAG_PROTOTYPE: This flag is used for prototyping. It does not run the query;
instead, it returns the Prototype Result Object as specified in section 2.2.4.1.
2.2.10 WBEM_BACKUP_RESTORE_FLAGS Enumeration
The WBEM_BACKUP_RESTORE_FLAGS enumeration gives information about the backup and

restore state of the process.
typedef [v1_enum] enum tag_WBEM_BACKUP_RESTORE_FLAGS

{
WBEM_FLAG_BACKUP_RESTORE_FORCE_SHUTDOWN = 1
} WBEM_BACKUP_RESTORE_FLAGS;
WBEM_FLAG_BACKUP_RESTORE_FORCE_SHUTDOWN: While the WMI repository is being

restored, any clients connected to WMI are forcibly disconnected.
2.2.11 WBEMSTATUS Enumeration
The WBEMSTATUS enumeration gives information about the status of an operation. If the server
encounters an error condition for which this protocol does not explicitly state an error value, the
server can return any HRESULT to indicate failure by setting the Severity (S bit) of the HRESULT, as
defined in [MS-ERREF] section 2.1.
typedef [v1_enum] enum tag_WBEMSTATUS

{
WBEM_S_NO_ERROR = 0x00,
WBEM_S_FALSE = 0x01,
WBEM_S_TIMEDOUT = 0x40004,
WBEM_E_FAILED = 0x80041001,
28 / 168
[MS-WMI] — v20091104

WBEM_E_NOT_FOUND = 0x80041002,
WBEM_E_ACCESS_DENIED = 0x80041003,
WBEM_E_INVALID_PARAMETER = 0x80041008,
WBEM_E_NOT_AVAILABLE = 0x80041009,
WBEM_E_NOT_SUPPORTED = 0x8004100c,
WBEM_E_INVALID_OPERATION = 0x80041016,
WBEM_E_ALREADY_EXISTS = 0x80041019,
E_NOTIMPL = 0x80004001,
WBEM_E_INVALID_SUPERCLASS = 0x8004100D,
WBEM_E_INVALID_NAMESPACE = 0x8004100E,
WBEM_E_INVALID_CLASS = 0x80041010,
WBEM_E_INVALID_QUERY = 0x80041017,
WBEM_E_INVALID_QUERY_TYPE = 0x80041018,
WBEM_E_CLASS_HAS_CHILDREN = 0x80041025,
WBEM_E_CLASS_HAS_INSTANCES = 0x80041026,
WBEM_E_INVALID_CIM_TYPE = 0x8004102D,
WBEM_E_INVALID_METHOD = 0x8004102E,
WBEM_E_INVALID_METHOD_PARAMETERS = 0x8004102F,
WBEM_E_CALL_CANCELLED = 0x80041032,
WBEM_E_INVALID_OBJECT_PATH = 0x8004103A
} WBEMSTATUS;
WBEM_S_NO_ERROR: The connection was established and no error occurred.
WBEM_S_FALSE: Return a value of false regardless of status.
WBEM_S_TIMEDOUT: The attempt to establish the connection has expired.
WBEM_E_FAILED: The attempt to establish the connection failed.
WBEM_E_NOT_FOUND: The object is not found.
WBEM_E_ACCESS_DENIED: Access is denied.
WBEM_E_INVALID_PARAMETER: The parameter is incorrect.
WBEM_E_NOT_AVAILABLE: The resource is unavailable.
WBEM_E_NOT_SUPPORTED: The attempted operation is not supported.
WBEM_E_INVALID_OPERATION: The attempted operation is not valid for this scenario.
WBEM_E_ALREADY_EXISTS: The object already exists.
E_NOTIMPL: The attempted operation is not implemented. The value of this element is as
specified in [MS-ERREF] section 2.1.
WBEM_E_INVALID_SUPERCLASS: The parent class is invalid.
WBEM_E_INVALID_NAMESPACE: The namespace is invalid.
WBEM_E_INVALID_CLASS: The class is invalid.
WBEM_E_INVALID_QUERY: The query is invalid.
WBEM_E_INVALID_QUERY_TYPE: The query language specified is invalid.
29 / 168
[MS-WMI] — v20091104

WBEM_E_CLASS_HAS_CHILDREN: The class cannot be updated because it has derived
classes.
WBEM_E_CLASS_HAS_INSTANCES: The class cannot be updated because it has instances.
WBEM_E_INVALID_CIM_TYPE: The CIM Type specified is not valid.
WBEM_E_INVALID_METHOD: The method is invalid.
WBEM_E_INVALID_METHOD_PARAMETERS: The parameter to method is not valid.
WBEM_E_CALL_CANCELLED: The server canceled execution of the request.
WBEM_E_INVALID_OBJECT_PATH: The object path is invalid.
2.2.12 WBEM_CONNECT_OPTIONS Enumeration
The WBEM_CONNECT_OPTIONS enumeration gives information about the type of options of the
connection.
typedef [v1_enum] enum tag_WBEM_CONNECT_OPTIONS

{
WBEM_FLAG_CONNECT_REPOSITORY_ONLY = 0x40,
WBEM_FLAG_CONNECT_PROVIDERS = 0x100
} WBEM_CONNECT_OPTIONS;
WBEM_FLAG_CONNECT_REPOSITORY_ONLY: The connection is established to operate only

on the static data (classes and instances) stored in the database. Operations requiring a
provider will not be supported on this connection.
WBEM_FLAG_CONNECT_PROVIDERS: The connection is established to operate only on the

provider.
2.2.13 IWbemContext
The signatures of many methods that are related to the Windows Management Instrumentation
Remote Protocol include a parameter to specify an IWbemContext interface pointer. The
IWbemContext interface represents an IWbemContext object,<2> which acts as a property bag
(a specialized container for properties that store variants) that a client MAY use to store additional
information to be used by the server. This information MUST be composed of a property list, the
property types, and the assigned property values.
When used through Windows Management Instrumentation Remote Protocol methods, the
IWbemContext parameter MUST be custom marshaled by the DCOM Remote Protocol, as specified
in the following list.
Interface UUID {44ACA674-E8FC-11D0-A07C-00C04FB68820}
Marshaling buffer The marshaling buffer has the format of the IWbemContextBuffer structure, as
layout specified in section 2.2.13.1.
Unmarshaler CLSID {674B6698-EE92-11D0-AD71-00C04FD8FDFF}

This CLSID represents the unmarshaler CLSID that is supplied by the Windows
Management Instrumentation Remote Protocol to the DCOM Remote Protocol and
30 / 168
[MS-WMI] — v20091104

MUST be sent over the network by the DCOM Remote Protocol when custom
marshaling is implemented. For more information, refer to [MS-DCOM] section
2.2.1.18.6.
For the IDL of these two IWbemContext interfaces, see Appendix A, which contains the full IDL of
the Windows Management Instrumentation Remote Protocol.
All scalar types that are encountered in the following structures MUST be stored in little-endian
format.
The IWbemContext interface is marshaled or unmarshaled by using the following data structures.
Structure Description
IWbemContextBuffer Marshaling Structure requirements for marshaling a buffer.
IWbemContextProperty Marshaling Structure requirements for marshaling a property.
IWbemContextString Marshaling Structure requirements for marshaling a string.
IWbemContextArray Marshaling Structure requirements for marshaling an array.
The IWbemContext interface pointer is specified as a parameter for many remote methods in WMI.
The data structures that are listed here define the wire formats for the data that is used by this
protocol.
2.2.13.1 IWbemContextBuffer Marshaling Structure
The IWbemContextBuffer data structure defines the wire format for buffer data that is used by this
protocol. It's structure has the following encoding format (defined in ABNF notation as specified in
[RFC4234]).
IWbemContextBuffer = NumGuids *GUID NumProps *IWbemContextProperty
The stream MUST start with a 32-bit integer (numGUIDs, in the following list) that MUST be set
to 1. The following ABNF represents the number of GUIDs that are present in the next
GuidArray.
 NumGuids = UINT32
NumGuids MUST be followed by an array of standard GUIDs and MUST contain NumGuids
elements.
The stream MUST contain a 32-bit integer that represents the property count.
 NumProps = UINT32
The property list MUST immediately follow the property count and MUST be marshaled as a
continuous list without padding between properties, as specified in IWbemContextProperty
(section 2.2.13.2). The number of IWbemContextProperty properties MUST be equal to
NumProps.
31 / 168
[MS-WMI] — v20091104

2.2.13.2 IWbemContextProperty Marshaling Structure
The IWbemContextProperty data structure defines the wire format for property data that is used by
this protocol. The property is a variable-length structure and has the following structure:
IWbemContextProperty = PropertyName PropertyFlags PropertyType PropertyValue
PropertyName MUST be the name of the property, marshaled as a string in the

IWbemContextString format specified in 2.2.13.3.
PropertyName = IWbemContextString
PropertyFlags is a 32-bit integer. It MUST be set to 0 and ignored.
PropertyFlags = UINT32
PropertyType is a 16-bit unsigned integer that represents the type of the property.
PropertyType = UINT16
MUST have one of the following values as specified in [MS-OAUT] section 2.2.7:
VT_NULL
VT_I2
VT_I4
VT_R4
VT_R8
VT_BSTR
VT_BOOL
VT_UI1
VT_UI2
VT_UI4
VT_UNKNOWN
VT_I1
If the value is an array, the listed property types MUST be combined by using the bitwise OR
operation with VT_ARRAY (also specified in [MS-OAUT] section 2.2.7).
PropertyValue is marshaled as shown in the following table.
32 / 168
[MS-WMI] — v20091104

Property types Marshaling
VT_BSTR MUST be marshaled as an IWbemContextString.
VT_IUNKNOWN MUST be marshaled as a buffer for the IWbemClassObject interface.
VT_NULL MUST be marshaled as an array of size 0.
VT_UI1, VT_I1 MUST be marshaled as an array of 8 bytes with the first byte containing the value
of the property.
VT_I2, VT_UI2, MUST be marshaled as an array of 8 bytes with the first 2 bytes containing the
VT_BOOL value of the property.
VT_I4, VT_UI4 MUST be marshaled as an array of 8 bytes with the first 4 bytes containing the
value of the property.
VT_R4 MUST be marshaled as an array of 8 bytes with the first 4 bytes containing the
value of the property, as specified in [IEEE754], a 4-byte floating-point format.
VT_R8 MUST be marshaled in an 8-byte floating-point format as specified in [IEEE754].
VT_ARRAY | VT_* MUST be marshaled as an IWbemContextArray structure, as specified in 2.2.13.4.
2.2.13.3 IWbemContextString Marshaling Structure
The IWbemContextString data structure defines the wire format for the string data that is used by
this protocol. Strings (property names and VT_BSTR properties values) MUST be represented as a
32-bit character count and followed by a sequence of characters that are encoded in UTF-16, as
specified in [UNICODE].
IWbemContextString has the following structure.
IWbemContextString = StringLength *UnicodeCharacter
StringLength MUST represent the length of the string as a character count.
StringLength = UINT32
UnicodeCharacter = 2OCTET
StringLength MUST be followed by a sequence of characters encoded with UTF-16, as specified in

[UNICODE]. The length of the sequence MUST be equal to StringLength. The string MUST NOT
have a terminating NIL (0x0000) character.
2.2.13.4 IWbemContextArray Marshaling Structure
The IWbemContextArray data structure defines the wire format for array data that is used by this
protocol. IWbemContextArray has the following structure:
IWbemContextArray = ElementCount ElementSize *Elements
ElementCount MUST be an integer that represents the number of elements in the array.
33 / 168
[MS-WMI] — v20091104

ElementCount = UINT32
ElementSize MUST represent the size of a single element in the array. The size MUST match the
size of the elements.
ElementSize = UINT32
Elements is a variable stream of bytes that represent all element values in the array. (Array
elements are marshaled in a different representation from nonarray elements.)
Each element MUST be marshaled as an array of bytes that use the following representation.
Type Marshaling
VT_BSTR MUST be marshaled as an IWbemContextString. In this case, ElementSize

SHOULD be set to 4 or 8.<3>
VT_IUNKNOWN MUST be marshaled as an array of bytes that represent a marshaling buffer for the
IWbemClassObject interface. In this case, ElementSize SHOULD be set to 4 or 8.
<4>
VT_NULL MUST be marshaled as 0 bytes.
VT_I1, VT_UI1 MUST be marshaled as 1 byte.
VT_I4, VT_UI4 MUST be marshaled in 4-byte little-endian format.
VT_R4 MUST be marshaled as an array of 8 bytes with the first 4 bytes containing the
value of the property, as specified in [IEEE754], in a 4-byte floating-point format.
VT_R8 MUST be marshaled as an 8-byte floating-point format, as specified in [IEEE754].
VT_I2, VT_BOOL, MUST be marshaled as a 2-byte little-endian format.

VT_UI2
2.2.14 ObjectArray Structure
The ObjectArray structure MUST be used to encode multiple CIM objects that are returned in
response to the IWbemWCOSmartEnum::Next (section 3.1.4.7.1) method. This structure is
also used to encode parameters of the optimized IWbemObjectSink::Indicate (section
3.1.4.2.1) method.<5> To minimize network bandwidth, a server SHOULD support the ObjectArray
structure when an array of CIM objects is sent.
The optimization MUST be achieved by sending the CIM class information just once at the beginning
of the communication. This CIM class MUST be identified by a randomly generated GUID that is
maintained by both the server and the client. The remaining CIM instances MUST be sent without
the CIM class information. The CIM class definition that is identified by the GUID is used to
reconstruct the full CIM instances on the client side.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
dwByteOrdering
34 / 168
[MS-WMI] — v20091104

abSignature
...
dwSizeOfHeader1
dwDataSize1
dwFlags
bVersion bPacketType dwSizeOfHeader2
... dwDataSize2
... dwSizeOfHeader3
... dwDataSize3
... dwNumObjects
... wbemObjects (variable)
...
dwByteOrdering (4 bytes): The byte ordering. It MUST be one of the following values.<6>
Value Meaning
0x00000000 The value when byte ordering is little-endian.
0xFFFFFFFF The value when byte ordering is big-endian.
abSignature (8 bytes): MUST be set to {0x57, 0x42, 0x45, 0x4D, 0x44, 0x41, 0x54, 0x41} (a
byte array containing the unquoted, unterminated ASCII string "WBEMDATA").
dwSizeOfHeader1 (4 bytes): This stores the total size of these fields: dwByteOrdering,
abSignature, dwSizeofHeader1, dwDataSize1, dwFlags, bVersion, and bPacketType.
The size of the header MUST be 0x0000001A. Data immediately follows the header.
dwDataSize1 (4 bytes): MUST indicate the length, in bytes, of the data that follows this
header, starting at the dwSizeOfHeader2 field.
dwFlags (4 bytes): The flag value MUST be 0x00000000.
bVersion (1 byte): The version number of the header. The version MUST be 1.
35 / 168
[MS-WMI] — v20091104

bPacketType (1 byte): The value of this field is dependent on the call context.
Value Meaning
0x00000000 The value in the context of an optimized IWbemObjectSink::Indicate call.
0x00000001 The value in the context of an optimized IWbemWCOSmartEnum::Next call.
dwSizeOfHeader2 (4 bytes): This stores the size of these fields: dwSizeofHeader2 and
dwDataSize2.
This size MUST be 8. Data immediately follows after the field dwDataSize2.
dwDataSize2 (4 bytes): MUST be the size, in bytes, of the data that follows this field.
dwSizeOfHeader3 (4 bytes): This stores the size of these fields: dwSizeofHeader3,

dwDataSize3, and dwNumObjects. This size MUST be 12. Data immediately follows after
the field dwNumObjects.
dwDataSize3 (4 bytes): MUST indicate the length of the remaining data, starting at the
wbemObjects field.
dwNumObjects (4 bytes): MUST be the number of CIM objects in the ObjectArray.
wbemObjects (variable): The objects array that contains the CIM class definition and CIM
instances. These CIM objects MUST be encoded in the WBEM_DATAPACKET_OBJECT structure.
2.2.14.1 WBEM_DATAPACKET_OBJECT Structure
The WBEM_DATAPACKET_OBJECT MUST contain the CIM class definition and CIM instances.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
dwSizeOfHeader
dwSizeOfData
bObjectType Object (variable)
...
dwSizeOfHeader (4 bytes): The size, in bytes, of the WBEM_DATAPACKET_OBJECT header,

which MUST be 0x00000009.
dwSizeOfData (4 bytes): The size, in bytes, of the data following the

WBEM_DATAPACKET_OBJECT header.
bObjectType (1 byte): The type of data in the data packet. The type MUST take one of the
following specified values.
36 / 168
[MS-WMI] — v20091104

Value Meaning
1 Object is type WBEMOBJECT_CLASS.

Structure contains the complete CIM Class definition.
2 Object is type WBEMOBJECT_INSTANCE.

Structure contains the complete CIM Instance definition.
3 Object is type WBEMOBJECT_INSTANCE_NOCLASS.

Structure contains CIM Instance without the CIM Class definition.
Object (variable): The CIM object carried into the WBEM_DATAPACKET_OBJECT, having
dwSizeOfData bytes. The embedded CIM object MUST match the selector field bObjectType.
2.2.14.2 WBEMOBJECT_CLASS Structure
The WBEMOBJECT_CLASS structure MUST contain a complete CIM class definition.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
dwSizeOfHeader
dwSizeOfData
ObjectData (variable)
...
dwSizeOfHeader (4 bytes): The size, in bytes, of the header, which MUST be 0x00000008.
dwSizeOfData (4 bytes): The size, in bytes, of the data that follows the header.
ObjectData (variable): Contains the string of bytes that represent the CIM class, encoded as
EncodingUnitObjectBlock, as specified in [MS-WMIO] section 2.2.2.
2.2.14.3 WBEMOBJECT_INSTANCE Structure
The WBEMOBJECT_INSTANCE structure MUST contain a complete CIM instance.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
dwSizeOfHeader
dwSizeOfData
37 / 168
[MS-WMI] — v20091104

classID
...
...
...
...
classID (16 bytes): The unique identifier of the CIM class type.
ObjectData (variable): Contains the string of bytes that represent the CIM instance, encoded
as EncodingUnitObjectBlock, as specified in [MS-WMIO] section 2.2.2.
2.2.14.4 WBEMOBJECT_INSTANCE_NOCLASS Structure
The WBEMOBJECT_INSTANCE_NOCLASS structure MUST contain a CIM instance without the CIM
class definition.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
dwSizeOfHeader
dwSizeOfData
classID
...
...
...
...
38 / 168
[MS-WMI] — v20091104

classID (16 bytes): The unique identifier of the CIM class type.
ObjectData (variable): Contains the string of bytes that represent the CIM instance, encoded
as the EncodingUnitInstanceNoClass object block, as specified in [MS-WMIO] section 2.2.3.
The CIM instance transmitted using EncodingUnitInstanceNoClass does not have a
CurrentClass block (as specified in [MS-WMIO] section 2.2.13) to minimize the data
transmitted because CurrentClass contains the same data for all the CIM instances.
The CurrentClass for another instance of the same CIM class is previously sent using the
WBEMOBJECT_INSTANCE structure. To match the WBEMOBJECT_INSTANCE structure that has the
CurrentClass block, the classID specified in WBEMOBJECT_INSTANCE_NOCLASS MUST be matched
with the classID of WBEMOBJECT_INSTANCE. If a matching WBEMOBJECT_INSTANCE is found, the
CurrentClass block in the WBEMOBJECT_INSTANCE MUST be used to encode or decode
EncodingUnitInstanceNoClass. If no matching WBEMOBJECT_INSTANCE is found during decoding, it
MUST be treated as an error. If no matching WBEMOBJECT_INSTANCE is found during encoding, the
CIM instance MUST be encoded as a WBEMOBJECT_INSTANCE structure.
2.2.15 WBEM_REFRESHED_OBJECT Structure
The WBEM_REFRESHED_OBJECT structure MUST be used to encode the results of the remote
refreshing service that is returned by the IWbemRemoteRefresher::RemoteRefresh (section
3.1.4.13.1) interface method.
typedef struct _WBEM_REFRESHED_OBJECT {

long m_lRequestId;
long m_lBlobType;
long m_lBlobLength;
[size_is(m_lBlobLength)] byte* m_pBlob;
} WBEM_REFRESHED_OBJECT;
m_lRequestId: MUST contain the request ID.
m_lBlobType: MUST represent the type of the CIM object that is encoded in m_pbBlob as
specified in 2.2.17.
m_lBlobLength: MUST represent the length of the m_pbBlob array.
m_pBlob: When the m_lBlobType parameter is set to WBEM_BLOB_TYPE_ALL, it MUST contain

the instance information that is represented in the RefreshedSingleInstance format for a single
IWbemClassObject interface pointer being part of the refreshing result.
When m_lBlobType is set to WBEM_BLOB_TYPE_ERROR, the m_lBlobLength parameter MUST

be set to NULL.
When m_lBlobType is set to WBEM_BLOB_TYPE_ENUM, it MUST contain the instance

information that is represented in the WBEM_INSTANCE_BLOB format for several
IWbemClassObject interface pointers being part of the refreshing result.
39 / 168
[MS-WMI] — v20091104

2.2.16 WBEM_INSTANCE_BLOB Enumeration
The WBEM_INSTANCE_BLOB is used to represent the refreshed object or enumeration in the

m_pBlob attribute of the WBEM_REFRESHED_OBJECT structure.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Version
numObjects
Objects (variable)
...
Version (4 bytes): MUST represent the encoding version. Version MUST be set to 0x00000001.
numObjects (4 bytes): MUST represent the number of CIM objects encoded that are contained
in the package.
Objects (variable): MUST contain a sequence of IWbemClassObjects of count numObjects,

with each IWbemClassObject encoded in RefreshedInstances format.
2.2.17 WBEM_INSTANCE_BLOB_TYPE Enumeration
The WBEM_INSTANCE_BLOB_TYPE enumeration is used to indicate the type of a CIM object.
typedef [v1_enum] enum _WBEM_INSTANCE_BLOB_TYPE

{
WBEM_BLOB_TYPE_ALL = 2,
WBEM_BLOB_TYPE_ERROR = 3,
WBEM_BLOB_TYPE_ENUM = 4
} WBEM_INSTANCE_BLOB_TYPE;
WBEM_BLOB_TYPE_ALL: The object is a single CIM object.
WBEM_BLOB_TYPE_ERROR: Represents an error condition. In this case the object is NULL.
WBEM_BLOB_TYPE_ENUM: The object is an enumeration of objects of a specific CIM type.
2.2.18 RefreshedInstances
The RefreshedInstances packet is contained within the WBEM_INSTANCE_BLOB.
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
blobSize
40 / 168
[MS-WMI] — v20091104

Blob (variable)
...
blobSize (4 bytes): MUST represent the length of the blob array.
Blob (variable): MUST be a byte stream representing an IWbemClassObject encoded as a

RefreshedSingleInstance.
2.2.19 RefreshedSingleInstance
The RefreshedSingeInstance MUST be encoded as a sequence of bytes representing the following

elements of the original IWbemClassObject, without any padding:
1. InstanceHeap size, encoded as 4 bytes.
2. InstanceData
3. InstanceQualifierSet
4. InstanceHeap
The elements of IWbemClassObject are defined in [MS-WMIO].
2.2.20 _WBEM_REFRESH_INFO Structure
The _WBEM_REFRESH_INFO structure MUST be populated by the Windows Management

Instrumentation Remote Protocol service that provides the refresher information. The structure
MUST be used to return to information from IWbemRefreshingServices (section 3.1.4.12)
interface methods.
typedef struct {
long m_lType;
[switch_is(m_lType)] WBEM_REFRESH_INFO_UNION m_Info;
long m_lCancelId;
} _WBEM_REFRESH_INFO;
m_lType: MUST be one of the constants specified in WBEM_REFRESH_TYPE.
m_Info: MUST be one of the WBEM_REFRESH_INFO_UNION types.
m_lCancelId: MUST be a unique identifier for the refresher object that is being used to cancel
the refreshing object when the refresher object is using
IWbemRemoteRefresher::StopRefreshing (section 3.1.4.13.2).
2.2.21 _WBEM_REFRESHER_ID Structure
The _WBEM_REFRESHER_ID structure identifies the client that is requesting refreshing services.
The structure MUST be used to return information from IWbemRefreshingServices (section
3.1.4.12) interface methods.
typedef struct {
41 / 168
[MS-WMI] — v20091104

[string] PSTR m_szMachineName;
DWORD m_dwProcessId;
GUID m_guidRefresherId;
} _WBEM_REFRESHER_ID;
m_szMachineName: MUST be the NetBIOS name of the client machine.
m_dwProcessId : It MUST be an identifier created by the client and it MUST be unique within
the context of the client.<7>
m_guidRefresherId: MUST be a client-generated GUID.
2.2.22 _WBEM_RECONNECT_INFO Structure
The _WBEM_RECONNECT_INFO structure MUST contain the type for the information about the
target CIM instance.
typedef struct {
long m_lType;
[string] LPCWSTR m_pwcsPath;
} _WBEM_RECONNECT_INFO;
m_lType: MUST be one of the WBEM_RECONNECT_TYPE enumeration values.
m_pwcsPath : MUST be a CIM path to the remote CIM instance to be added to the refresher.
2.2.23 _WBEM_RECONNECT_RESULTS Structure
The _WBEM_RECONNECT_RESULTS structure defines the status of a reconnect operation. The

structure MUST be used to return information from IWbemRefreshingServices (section
typedef struct {
long m_lId;
HRESULT m_hr;
} _WBEM_RECONNECT_RESULTS;
m_lId: MUST be a unique identifier for the refresher object used to cancel the refreshing object
by using the IWbemRemoteRefresher::StopRefreshing (section 3.1.4.13.2) interface
method.
m_hr: MUST be the HRESULT of the reconnect operation.
2.2.24 _WBEM_RECONNECT_TYPE Enumeration
The _WBEM_RECONNECT_TYPE enumeration defines possible types of remote CIM instances. The
structure MUST be used to return to information from IWbemRefreshingServices (section
typedef enum
42 / 168
[MS-WMI] — v20091104

{
WBEM_RECONNECT_TYPE_OBJECT = 0,
WBEM_RECONNECT_TYPE_ENUM = 1,
WBEM_RECONNECT_TYPE_LAST = 2
} WBEM_RECONNECT_TYPE;
WBEM_RECONNECT_TYPE_OBJECT: The refresher MUST connect to refresh an object.
WBEM_RECONNECT_TYPE_ENUM: The refresher MUST connect to refresh an enumeration.
WBEM_RECONNECT_TYPE_LAST: This member is used only by the server to track the range
of values for this enumeration. It MUST NOT be used by the client.
2.2.25 WBEM_REFRESH_TYPE Enumeration
The WBEM_REFRESH_TYPE enumeration defines refresh types for the _WBEM_REFRESH_INFO

structure.
typedef enum
{
WBEM_REFRESH_TYPE_INVALID = 0,
WBEM_REFRESH_TYPE_REMOTE = 3,
WBEM_REFRESH_TYPE_NON_HIPERF = 6
} WBEM_REFRESH_TYPE;
WBEM_REFRESH_TYPE_INVALID: The server uses this value internally. The server MUST
NOT return this value.
WBEM_REFRESH_TYPE_REMOTE: The m_Info member of the _WBEM_REFRESH_INFO

structure contains the _WBEM_REFRESH_INFO_REMOTE structure.
WBEM_REFRESH_TYPE_NON_HIPERF: The m_Info member of the

_WBEM_REFRESH_INFO structure contains the _WBEM_REFRESH_INFO_NON_HIPERF
structure.
2.2.26 _WBEM_REFRESH_INFO_NON_HIPERF Structure
The _WBEM_REFRESH_INFO_NON_HIPERF structure MUST be returned by the server when the

requested CIM instance cannot be part of the refreshing results.
typedef struct {
[string] WCHAR* m_wszNamespace;
IWbemClassObject* m_pTemplate;
} _WBEM_REFRESH_INFO_NON_HIPERF;
m_wszNamespace: MUST be a CIM namespace where enumeration of a given class exists.
m_pTemplate: MUST be a pointer to an IWbemClassObject interface, which MUST represent a

CIM instance with all properties set to the default values. Default property values are as
specified in [MS-WMIO] section 2.2.26.
43 / 168
[MS-WMI] — v20091104

2.2.27 _WBEM_REFRESH_INFO_REMOTE Structure
The _WBEM_REFRESH_INFO_REMOTE structure MUST be used when the client is on a different

computer than the computer on which the WMI service providing the refreshed information resides.
typedef struct {
IWbemRemoteRefresher* m_pRefresher;
GUID m_Guid;
} _WBEM_REFRESH_INFO_REMOTE;
m_pRefresher: MUST be a pointer to the IWbemRemoteRefresher interface that the client used
to retrieve the refreshed information.
m_pTemplate: MUST be a pointer to an IWbemClassObject interface that MUST represent a

CIM instance with all properties set to the default values as specified in [MS-WMIO] section
2.2.26.
m_Guid: MUST be a globally unique identifier (GUID) created to identify this

_WBEM_REFRESH_INFO object.
2.2.28 _WBEM_REFRESH_INFO_UNION Union
The _WBEM_REFRESH_INFO_UNION union defines a union of one of the following types:

m_Remote, m_NonHiPerf, or m_hres.
typedef
[switch_type(long)]
union _WBEM_REFRESH_INFO_UNION {
[case(WBEM_REFRESH_TYPE_REMOTE)]
_WBEM_REFRESH_INFO_REMOTE m_Remote;
[case(WBEM_REFRESH_TYPE_NON_HIPERF)]
_WBEM_REFRESH_INFO_NON_HIPERF m_NonHiPerf;
[case(WBEM_REFRESH_TYPE_INVALID)]
HRESULT m_hres;
} WBEM_REFRESH_INFO_UNION;
m_Remote: An m_Remote _WBEM_REFRESH_INFO_REMOTE type.
m_NonHiPerf: An m_NonHiPerf _WBEM_REFRESH_INFO_NON_HIPERF type.
m_hres: An m_hres HRESULT type.
2.2.29 WMI Locale Formats
The client can request data from the WMI server in a client-preferred locale. The format of each
locale MUST conform to one of the following:
"MS_xxx" format, where "xxx" is a string representation of LCID in BASE16, which MUST identify
the locale as specified in [MS-LCID]. For example, to send LCID 1033 (0x409), the string MUST
be "MS_409".
Locale name format as specified in [MS-LCID]. For example, LCID 1033 (0x409) maps to en-US
and MUST be passed as "en-US" in this representation.
44 / 168
[MS-WMI] — v20091104

2.2.30 __SystemSecurity class
The __SystemSecurity class is used to read or modify the security descriptor for a CIM namespace.
The class is defined by WMI as shown in the following MOF text.
singleton: DisableOverride ToInstance ToSubClass]

class __SystemSecurity
{
[Static] uint32 GetSD([out] uint8 sd[]);
[Static] uint32 SetSD([in] uint8 sd[]);
};
The GetSD and SetSD methods exchange a byte array containing a self-relative
SECURITY_DESCRIPTOR structure, as defined in [MS-DTYP] section 2.4.6.
45 / 168
[MS-WMI] — v20091104

3 Protocol Details
The following sections specify details of the Windows Management Instrumentation Remote Protocol,
including abstract data models, interface method syntax, and message processing rules. A client in
the context of this specification is a machine that issues a Windows Management Instrumentation
Remote Protocol request. The request is issued against a Windows Management Instrumentation
Remote Protocol server. In this context, a server is a machine that handles the request issued by
the client. Detailed sequence diagrams are as specified in section 4.
3.1 Server Details
A client in the context of this specification is a machine that issues a Windows Management
Instrumentation Remote Protocol request. The request is issued against a Windows Management
Instrumentation Remote Protocol server. In this context, a server is a machine that handles the
request issued by the client. Detailed sequence diagrams are as specified in section 4. However, an
overview of a typical protocol sequence is illustrated as follows.
46 / 168
[MS-WMI] — v20091104

Figure 3: Typical protocol sequence
3.1.1 Abstract Data Model
The namespace implemented by a server is backed up by a CIM database.
47 / 168
[MS-WMI] — v20091104

3.1.1.1 Delivering Results to Client
3.1.1.1.1 Synchronous calls
The server MUST complete the requested operation before returning from the synchronous method
call. The status of the operation is returned as return value of the method. On successful execution
of the synchronous methods, the server MUST return result object or objects in the out parameter of
the method.
3.1.1.1.2 Semi-Synchronous calls
The server MUST start the requested operation and MUST return the appropriate response without
waiting for the operation to complete. If the requested operation fails to start, the server MUST
return an error as a return value of the method and MUST NOT return IEnumWbemClassObject or
IWbemCallResult as an out parameter.
For the requested operation to begin successfully, the server MUST return an object of type
IEnumWbemClassObject for the following methods, and the return value MUST be
WBEM_S_NO_ERROR. When the client calls the methods of IEnumWbemClassObject, the
IEnumWbemClassObject method MUST deliver the results of the requested operation. The
enumeration of IEnumWbemClassObject MUST return the same result set as the corresponding
synchronous operation.
IWbemServices::ExecQuery
IWbemServices::CreateInstanceEnum
IWbemServices::CreateClassEnum
IWbemServices::ExecNotificationQuery
If the requested operation begins successfully, the server MUST return an object of type
IWbemCallResult for the following methods, and the return value MUST be WBEM_S_NO_ERROR.
When the client calls the methods of IWbemCallResult, IWbemCallResult MUST deliver the
result of the requested operation.
IWbemServices::OpenNamespace
IWbemServices::PutInstance
IWbemServices::GetObject
IWbemServices::PutClass
IWbemServices::DeleteClass
IWbemServices::DeleteInstance
IWbemServices::ExecMethod
3.1.1.1.3 Asynchronous calls
The server MUST start the requested operation and MUST return the appropriate response without
waiting for the completion of the operation. If starting the requested operation fails, the server
MUST return the error as a return value of the method; MUST NOT keep a reference to
IWbemObjectSink (passed as a response handler); and MUST NOT call
IWbemObjectSink::Indicate or IWbemObjectSink::SetStatus.
48 / 168
[MS-WMI] — v20091104

For the requested operation to begin successfully, the server MUST return WBEM_S_NO_ERROR and
MUST keep a reference to IWbemObjectSink passed as a response handler.
The server MUST invoke the IWbemObjectSink::Indicate and IWbemObjectSink::SetStatus

methods, as specified in sections 3.2.4.1.1 and 3.2.4.1.2. If the call to
IWbemObjectSink::Indicate or IWbemObjectSink::SetStatus fails, the server MUST cancel the
asynchronous operation.
The server MAY call IWbemObjectSink::SetStatus multiple times when it executes the
asynchronous operation in order to report the operation progress,<8> as explicitly requested by a
client using a WBEM_SEND_STATUS flag. In this situation, the HRESULT parameter contains the
progress information.
Calls made by the server into the client-provided IWbemObjectSink interface SHOULD use an
authentication level that is greater than NONE. If that fails, the server SHOULD retry with an
authentication level of NONE.<9> The server MUST try to make the calls by using the machine
principal name.
3.1.2 Timers
The server MUST use timers to ensure that the conversation between itself and its clients remains
active. The Windows Management Instrumentation Remote Protocol uses two timers:
Sink timer: Each asynchronous operation has a corresponding timer, which MUST be initialized to
30 seconds when the server calls the client back using IWbemObjectSink. The timer MUST be
reset when the call completes.
Backup timer: Each IWbemBackupRestoreEx has a corresponding timer, which MUST be

initialized to 15 minutes when the server receives an IWbemBackupRestoreEx::Pause. The
timer MUST be reset when the server receives an IWbemBackupRestoreEx::Resume.
3.1.3 Initialization
The protocol MUST be initialized after successful activation of one of the two interfaces that are
registered with the DCOM Remote Protocol infrastructure, as specified in [MS-DCOM] section 1.9.
3.1.4 Message Processing Events and Sequencing Rules
The server MUST accept multiple parallel invocations from different clients running under different
security principals. On each interface, the server MUST support multiple outstanding calls.
The errors returned by the server are not actionable unless explicitly specified in this section. The
server MUST perform an access check against all operations and ensure secure access to the results.
The methods MUST be secured by using access rights as specified in section 5.2.
If the server detects that the IWbemClassObject that is sent by the client does not conform to [MS-
WMIO] encoding, as specified in section 2.2.4, the server MUST return an HRESULT that has the S
(severity) bit set as specified in [MS-ERREF]. The exact code is implementation-dependent.
If the server is expected to set the value of the output parameter, but the output parameter is set to
NULL upon input, the server SHOULD return an error to indicate failure. In this case, the server
cannot modify the output parameter.
49 / 168
[MS-WMI] — v20091104

3.1.4.1 IWbemLevel1Login Interface
The IWbemLevel1Login interface allows a user to connect to the management services interface
in a particular namespace. The interface MUST be uniquely identified by the UUID {F309AD18-
D86A-11d0-A075-00C04FB68820}.
Methods in RPC Opnum Order
Method Description
EstablishPosition Opnum: 3
RequestChallenge Opnum: 4
WBEMLogin Opnum: 5
NTLMLogin Opnum: 6
The object that exports this interface also implements the IWbemLoginClientID and
IWbemLoginHelper interfaces. The IRemUnknown and IRemUnknown2 interfaces, as specified
in [MS-DCOM], MUST be used to manage the interfaces exposed by the object. The object MUST be
uniquely identified with the CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}.
Figure 4: The IWbemLevel1Login interface
3.1.4.1.1 IWbemLevel1Login::EstablishPosition (Opnum 3)
The IWbemLevel1Login::EstablishPosition method does not perform any action.
HRESULT EstablishPosition(
[in, unique, string] wchar_t* reserved1,
[in] DWORD reserved2,
[out] DWORD* LocaleVersion
50 / 168
[MS-WMI] — v20091104

);
reserved1: MUST be set to NULL when sent and MUST be ignored on receipt.
reserved2: MUST be set to 0 when sent and MUST be ignored on receipt.
LocaleVersion: The server MUST set the value of LocaleVersion based on the server behavior
when IWbemLevel1Login::NTLMLogin is passed an unrecognized locale name in the
wszPreferredLocale parameter:<10>
The return value and LocaleVersion are used for Locale capability negotiation before calling
IWbemLevel1Login::NTLMLogin, as described in section 3.2.3.
If the server ignores an unrecognized locale name passed to

IWbemLevel1Login::NTLMLogin, and completes the execution of the
IWbemLevel1Login::NTLMLogin method, the server MUST set the LocaleVersion
parameter to 1.
If the server returns an error for an unrecognized locale name passed to
IWbemLevel1Login::NTLMLogin, the server MUST set the LocaleVersion parameter to 0.
Return Values: The server MUST return one of the following values, based on server behavior
for the wszPreferredLocale parameter in IWbemLevel1Login::NTLMLogin.
Return value/code Description
0x00 If the server accepts as a locale parameter for the

WBEM_S_NO_ERROR IWbemLevel1Login::NTLMLogin method all locales valid for
Windows Vista as defined in Appendix A of MS-LCID, the server MUST
return WBEM_S_NO_ERROR for IWbemLevel1Login::EstablishPosition.
0x80004001 If the server returns WBEM_E_INVALID_PARAMETER for any valid

E_NOTIMPL Windows Vista locales as specified in Appendix A of [MS-LCID] that has
been passed as a locale parameter to the
IWbemLevel1Login::NTLMLogin method, the server MUST return
E_NOTIMPL for IWbemLevel1Login::EstablishPosition.
3.1.4.1.2 IWbemLevel1Login::RequestChallenge (Opnum 4)
This method does not perform any action.
HRESULT RequestChallenge(
[out, size_is(16), length_is(16)]
unsigned char* reserved3
);
51 / 168
[MS-WMI] — v20091104

0x8004100c The server MAY return this value.<11>

WBEM_E_NOT_SUPPORTED
3.1.4.1.3 IWbemLevel1Login::WBEMLogin (Opnum 5)
This method does not perform any action.
HRESULT WBEMLogin(
[in, size_is(16), length_is(16), unique]
unsigned char* reserved2,
[in] long reserved3,
[in] IWbemContext* reserved4,
[out] IWbemServices** reserved5
);
reserved3: MUST be set to 0 when sent and MUST be ignored on receipt.
0x80004001 The server MAY return this value.<12>

E_NOTIMPL
3.1.4.1.4 IWbemLevel1Login::NTLMLogin (Opnum 6)
The IWbemLevel1Login::NTLMLogin method MUST connect a user to the management services

interface in a specified namespace.
HRESULT NTLMLogin(
[in, unique, string] LPWSTR wszNetworkResource,
[in, unique, string] LPWSTR wszPreferredLocale,
[in] long lFlags,
[in] IWbemContext* pCtx,
[out] IWbemServices** ppNamespace
);
wszNetworkResource: The string MUST represent the namespace on the server to which the
returned IWbemServices object is associated. This parameter MUST NOT be NULL and MUST
match the namespace syntax as specified in section 2.2.2.
wszPreferredLocale: MUST be a pointer to a string that MUST specify the locale values in the
preferred order, separated by a comma. Each locale format SHOULD conform to the WMI
locale format, as specified in WMI Locale Formats section 2.2.29. Any subsequent calls that
request CIM localizable information (WBEM_FLAG_USE_AMENDED_QUALIFIERS)
52 / 168
[MS-WMI] — v20091104

SHOULD return the localized information in the order of preference if the information is
available in the LCID.<13>
lFlags: MUST be zero. The server SHOULD consider any other value as not valid and return
WBEM_E_INVALID_PARAMETER; otherwise, the server behavior is implementation-
specific.<14>
pCtx: MUST be a pointer to an IWbemContext interface, which MUST contain additional

information sent by the client. If pCtx is NULL, the parameter MUST be ignored.
ppNamespace: If the call succeeds, ppNamespace MUST return a pointer to an

IWbemServices interface pointer. This parameter MUST be set to NULL when an error
occurs.
Return Values: This method MUST return an HRESULT value that MUST indicate the status of
the method call. The server MUST return WBEM_S_NO_ERROR, as specified in section 2.2.11,
to indicate the successful completion of the method.
WBEM_S_NO_ERROR (0x00)
The security principal that makes the call MUST have WBEM_REMOTE_ENABLE and WBEM_ENABLE
access to the namespace; otherwise, WBEM_ACCESS_DENIED MUST be returned.
In response to the IWbemLevel1Login::NTLMLogin method, the server MUST return an

IWbemServices interface that corresponds to the wszNetworkResource parameter.
All subsequent IWbemServices method invocations that request localized information MUST return
the information in the language that is specified in wszPreferredLocale. When the preferred locale is
NULL, the server SHOULD<15> use implementation-specific logic to decide the locale.
The successful method execution MUST fill the ppNamespace parameter with an IWbemServices
interface pointer and MUST return WBEM_S_NO_ERROR.
The failed method execution MUST set the output parameter to NULL and MUST return an error in
the format specified in section 2.2.3.
3.1.4.2 IWbemObjectSink Interface Server Details
The IWbemObjectSink interface MUST be implemented by the WMI client if the WMI client uses
asynchronous method calls as specified in section 3.2.4.2.7. In this case, the WMI client acts as an
IWbemObjectSink server. The WMI server acts as an IWbemObjectSink client and invokes the
IWbemObjectSink methods to deliver the results (IWbemClassObjects, if any, and the status code)
of the IWbemServices method for which this IWbemObjectSink is passed as a response handler.
If the WMI client calls the IWbemServices::QueryObjectSink method, the IWbemObjectSink

interface MUST be implemented by the WMI server and MUST be returned to the client in the
ppResponseHandler parameter, as specified in section 3.1.4.3.3. In this case, the WMI server acts
as an IWbemObjectSink server. The WMI client acts as an IWbemObjectSink client and invokes the
IWbemObjectSink methods to deliver the results, that is, IWbemClassObjects that represent the
extrinsic events the client wants to deliver to the server.
Because this interface is implemented by the WMI client and the WMI server and called by both, the
server in this section refers to the implementer of this interface and the client refers to the caller in
a specific scenario.
53 / 168
[MS-WMI] — v20091104

The IWbemObjectSink interface is a DCOM Remote Protocol (as specified in [MS-DCOM])
interface. The interface MUST be uniquely identified by UUID {7c857801-7381-11cf-884d-
00aa004b2e24}.
Method Description
Indicate The server receives the IWbemClassObject interfaces, which are sent in an ObjectArray
structure. These objects are the result of an IWbemServices asynchronous method call
that was started with this sink as the response handler.
Opnum: 3
SetStatus The server receives either a completion status code or information about the progress of the
operation that was started with this sink as the response handler.
Opnum: 4
3.1.4.2.1 IWbemObjectSink::Indicate (Opnum 3) Server details
When the IWbemObjectSink::Indicate method is called, the apObjArray parameter MUST contain
additional result objects as an array of an IWbemClassObject, sent by the client to the server. The
IWbemObjectSink::Indicate method has the following syntax, expressed in Microsoft Interface
Definition Language (MIDL).
HRESULT Indicate(
[in] long lObjectCount,
[in, size_is(lObjectCount)] IWbemClassObject** apObjArray
);
lObjectCount: MUST be the number of CIM objects in the array of pointers in the ppObjArray
parameter.
apObjArray: MUST contain an array of result objects sent by the caller.
the method call.
When the IWbemObjectSink::Indicate method is called for the first time, the server that
implements the ObjectArray structure MUST return WBEM_S_NEW_STYLE if the execution of the
method succeeds.<16> If a server does not implement the ObjectArray structure, it MUST return
WBEM_S_NO_ERROR for successful execution of the method.
If the server implements the ObjectArray structure and WBEM_S_NEW_STYLE is returned during the
first call to the IWbemObjectSink::Indicate method, the server MUST support subsequent calls to
the IWbemObjectSink::Indicate method by using both the DCOM Remote Protocol marshaling
and the ObjectArray structure as specified in section 2.2.14.
3.1.4.2.2 IWbemObjectSink::SetStatus (Opnum 4) Server Details
When the IWbemObjectSink::SetStatus method is called, the parameter MUST contain the result
of the operation or the progress status information.
54 / 168
[MS-WMI] — v20091104

HRESULT SetStatus(
[in] long lFlags,
[in] HRESULT hResult,
[in] BSTR strParam,
[in] IWbemClassObject* pObjParam
);
lFlags: Flags that give information about the operation status. The flags MUST be interpreted as
specified in the following table.
Note The flags are not bit flags and cannot be combined.
Value Meaning
WBEM_STATUS_COMPLETE Indicates the end of the asynchronous operation.

0x00000000
WBEM_STATUS_PROGRESS Indicates the progress state of the asynchronous operation.

0x00000002
Any other DWORD value that does not match the condition shown MUST be treated as not
valid and an error MUST be returned.
hResult: The hResult value of the asynchronous operation or notification. This hResult MUST be
the same HRESULT that the WMI client gets from the matching synchronous operation when
the WMI client makes an asynchronous request to the WMI server.
strParam: If the parameter is NULL, the server MUST ignore the parameter. If the parameter is
not NULL, it MUST represent the operational result of the asynchronous operation. The string
MUST be the same as the string that is returned from the IWbemCallResult::GetResultString
(Opnum 4) method when the operation is executed synchronously.
pObjParam: If the parameter is NULL, the server MUST ignore the parameter. If the parameter
is not NULL, the object MUST contain additional error information for the asynchronous
operation failure.
the method call. The server MUST return WBEM_S_NO_ERROR (specified in section 2.2.11)
3.1.4.3 IWbemServices Interface
The IWbemServices interface exposes methods that MUST provide management services to client
processes. The implementation MUST implement all methods and return errors if the semantics of
the operation cannot be completed. IWbemServices defines the execution scope for all methods
implemented on the interface. The initial scope MUST be established by the
IWbemLevel1Login::NTLMLogin call, which returns the interface pointer.
55 / 168
[MS-WMI] — v20091104

Method Description
OpenNamespace Provides the client with an IWbemServices interface pointer that is

scoped to the requested namespace.
Opnum: 3
CancelAsyncCall Cancels a currently pending asynchronous method call identified by the

IWbemObjectSink pointer passed to the initial asynchronous method.
Opnum: 4
QueryObjectSink Obtains a notification handler that allows the client to send events
directly to the server.
Opnum: 5
GetObject Retrieves a CIM class or a CIM instance.

Opnum: 6
GetObjectAsync Asynchronous version of the IWbemServices::GetObject method.

Opnum: 7
PutClass Creates a new class or updates an existing class in the namespace

associated with the current IWbemServices interface.
Opnum: 8
PutClassAsync Asynchronous version of the IWbemServices::PutClass method.

Opnum: 9
DeleteClass Deletes a specified class from the namespace associated with the
current IWbemServices interface.
Opnum: 10
DeleteClassAsync Asynchronous version of the IWbemServices::DeleteClass method.

Opnum: 11
CreateClassEnum Creates a class enumeration.

Opnum: 12
CreateClassEnumAsync Asynchronous version of the IWbemServices::CreateClassEnum method.

Opnum: 13
PutInstance Creates or updates an instance of an existing class.

Opnum: 14
PutInstanceAsync Asynchronous version of the PutInstance method.

Opnum: 15
DeleteInstance Deletes an instance of an existing class from the namespace that is

pointed to by the IWbemServices interface object that is used to call
the method.
Opnum: 16
DeleteInstanceAsync Asynchronous version of the IWbemServices::DeleteInstance

method.
Opnum: 17
56 / 168
[MS-WMI] — v20091104

Method Description
CreateInstanceEnum Creates an instance enumeration of all class instances that satisfy the
selection criteria.
Opnum: 18
CreateInstanceEnumAsync Asynchronous version of the IWbemServices::CreateInstanceEnum

method.
Opnum: 19
ExecQuery Returns an enumerable collection of IWbemClassObject interface

objects based on a query.
Opnum: 20
ExecQueryAsync Asynchronous version of the IWbemServices::ExecQuery method.

Opnum: 21
ExecNotificationQuery Server runs a query to receive events when called by a client to request
subscription to the events.
Opnum: 22
ExecNotificationQueryAsync Asynchronous version of the IWbemServices::ExecNotificationQuery

method.
Opnum: 23
ExecMethod Executes a CIM method implemented by a CIM class or a CIM instance

retrieved from the IWbemServices interface.
Opnum: 24
ExecMethodAsync Asynchronous version of the IWbemServices::ExecMethod method.

Opnum: 25
IWbemServices MUST be a DCOM Remote Protocol interface. The interface MUST be uniquely
identified by UUID {9556dc99-828c-11cf-a37e-00aa003240c7}. The object exporting this interface
also implements the IWbemRefreshingServices interface, as shown in the following diagram.
Figure 5: The IWbemServices interface
57 / 168
[MS-WMI] — v20091104

3.1.4.3.1 IWbemServices::OpenNamespace (Opnum 3)
The IWbemServices::OpenNamespace method provides the client with an IWbemServices

interface pointer that is scoped to the requested namespace. The specified namespace MUST be a
child namespace of the current namespace through which this method is called.
HRESULT OpenNamespace(
[in] const BSTR strNamespace,
[in] long lFlags,
[in, out, unique] IWbemServices** ppWorkingNamespace,
[in, out, unique] IWbemCallResult** ppResult
);
strNamespace: MUST be the CIM path to the target namespace. This namespace MUST be
relative to the current namespace that is associated with the IWbemServices interface
pointer that is used to make the OpenNamespace method call. This parameter MUST NOT be
NULL.
lFlags: Flags that affect the behavior of the OpenNamespace method. The behavior of each
flag MUST be interpreted as follows:
If this bit is not set, the server MUST make the method call synchronous.
If this bit is set, the server MUST make the method call semisynchronously.
Name Value
WBEM_FLAG_RETURN_IMMEDIATELY 0x00000010
Any other DWORD value that does not match the preceding condition MUST be treated as
invalid.
pCtx: This parameter MUST be NULL.
ppWorkingNamespace: This parameter MUST NOT be NULL on input when

WBEM_FLAG_RETURN_IMMEDIATELY is not set. In such a case, it MUST receive a pointer to
an IWbemServices interface pointer to the requested namespace.
The output parameter MUST be based on the state of the lFlags parameter (whether
WBEM_FLAG_RETURN_IMMEDIATELY is set) as listed in the following table.
Flag state Success operation Failure operation
WBEM_FLAG_RETURN_IMMEDIATELY MUST be set to the MUST be set to

is not set. requested IWbemCallResult if the
IWbemServices input parameter is not-NULL.
interface.
WBEM_FLAG_RETURN_IMMEDIATELY MUST be set to NULL if MUST be set to NULL if the

is set. the input parameter is input parameter is not-NULL.
not-NULL.
ppResult: The output parameter MUST be filled according to the state of the lFlags parameter
(whether WBEM_FLAG_RETURN_IMMEDIATELY is set) as listed in the following table.
58 / 168
[MS-WMI] — v20091104

WBEM_FLAG_RETURN_IMMEDIATELY is MUST be set to NULL if the MUST be set to NULL if

not set. input parameter is not- the input parameter is
NULL. not-NULL.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST be set to the MUST be set to NULL if

set. requested IWbemCallResult the input parameter is
interface. not-NULL.
This parameter MUST NOT be NULL on input when WBEM_FLAG_RETURN_IMMEDIATELY

equals 1. In such a case, it receives a pointer to an IWbemCallResult interface pointer.
In response to the IWbemServices::OpenNamespace method, the server MUST evaluate whether

the strNamespace parameter, which is specified in the preceding list, is a child of the namespace
that is associated with the current interface pointer, and on success, MUST create another
IWbemServices interface pointer associated with this namespace.
If the method returns a success code, the method MUST fill one of the two output parameters, as
indicated by the use of the lFlags parameter, which is previously specified.
The successful synchronous method execution MUST fill the ppWorkingNamespace parameter with
an IWbemServices interface pointer and MUST return WBEM_S_NO_ERROR.
The semisynchronous method execution MUST follow the rules that are specified in section
3.1.1.1.2.
The failed method execution MUST set the output parameters to NULL and MUST return an error in
the format that is specified in section 2.2.11.
3.1.4.3.2 IWbemServices::CancelAsyncCall (Opnum 4)
The IWbemServices::CancelAsyncCall method cancels a currently pending asynchronous method

call identified by the IWbemObjectSink pointer passed to the initial asynchronous method.
HRESULT CancelAsyncCall(
[in] IWbemObjectSink* pSink
);
pSink: MUST be a pointer to the IWbemObjectSink interface object that was passed to the
asynchronous method that the client wants to cancel. This parameter MUST NOT be NULL.
the method call. The server MUST return WBEM_S_NO_ERROR (as specified in section 2.2.11)
59 / 168
[MS-WMI] — v20091104

0x00 Indicates a successful completion to the method call.

WBEM_S_NO_ERROR
The server MUST validate that the security principal making the
IWbemServices::CancelAsyncCall is the same principal that has made the call to be cancelled.
Otherwise, the server MUST return a WBEM_E_ACCESS_DENIED error.
In response to the IWbemServices::CancelAsyncCall method, the server MUST identify and

cancel all pending asynchronous operations initiated by an asynchronous method execution, such as
IWbemServices::GetObjectAsync, which used the pSink interface pointer parameter as their
response handler. The server MUST return an error if the interface pointer is NULL, and it MUST
return an error if the pSink parameter is not associated with any pending operation.
The server MUST NOT wait for any response from the client to complete the cancellation to prevent
protocol performance degradation.
The successful method execution MUST return WBEM_S_NO_ERROR.
The failed method execution MUST return an error in the format specified in section 2.2.11.
3.1.4.3.3 IWbemServices::QueryObjectSink (Opnum 5)
The QueryObjectSink method obtains a notification handler that allows the client to send events
directly to the server.
HRESULT QueryObjectSink(
[in] long lFlags,
[out] IWbemObjectSink** ppResponseHandler
);
lFlags: This parameter is not used and its value MUST be 0x0.
ppResponseHandler: MUST be a pointer to a QueryObjectSink interface pointer to the

notification handler that allows the client to send events directly to the server. This parameter
MUST be set to NULL on error.
the method call. The server MUST return WBEM_S_NO_ERROR (specified in section 2.2.11) to
indicate the successful completion of the method.
The security principal that makes the call MUST have WBEM_REMOTE_ENABLE and
WBEM_FULL_WRITE accesses to the namespace; otherwise, WBEM_E_ACCESS_DENIED MUST be
returned.
In response to the IWbemServices::QueryObjectSink method, the server MUST return an

IWbemObjectSink interface pointer in ppResponseHandler. The server MUST return an error if the
ppResponseHandler is NULL or if it is unable to create the requested interface pointer.
The successful method execution MUST fill the ppResponseHandler parameter and MUST return
WBEM_S_NO_ERROR.
60 / 168
[MS-WMI] — v20091104

the format as specified in section 2.2.11.
When extrinsic events are delivered to the server by using IWbemObjectSink::Indicate as

specified in section 3.1.4.2.1, the server MUST send the event objects to all WMI clients whose
notification query satisfies the event objects that are delivered through
IWbemObjectSink::Indicate and whose security permissions match the security descriptor as
specified in section 5.2. The notification query is made by the client to the server by calling
IWbemServices::ExecNotificationQuery or IWbemServices::ExecNotificationQueryAsync.
Refer to sections 3.1.4.3.20 and 3.1.4.3.21 for information about how result objects are delivered to
the client.
3.1.4.3.4 IWbemServices::GetObject (Opnum 6)
The IWbemServices::GetObject method retrieves a CIM class or a CIM instance. This method
MUST retrieve CIM objects from the namespace that is associated with the current IWbemServices
interface.
HRESULT GetObject(
[in] const BSTR strObjectPath,
[in] long lFlags,
[out, in, unique] IWbemClassObject** ppObject,
[out, in, unique] IWbemCallResult** ppCallResult
);
strObjectPath: MUST be the CIM path of the CIM object to be retrieved. If the parameter is
NULL, the server MUST return an empty CIM Object.
lFlags: Specifies the behavior of the IWbemServices::GetObject method. Flag behavior MUST
be interpreted as specified in the following table.
The server MUST allow any combination of zero or more flags from the following table and
MUST comply with all the restrictions in a flag description. Any other DWORD value that does
not match a flag condition MUST be treated as not valid.
Value Meaning
WBEM_FLAG_USE_AMENDED_QUALIFIERS If this bit is not set, the server SHOULD return no CIM
0x00020000 localizable information.
If this bit is set, the server SHOULD return CIM
localizable information for the CIM object, as specified
in section 2.2.6.
WBEM_FLAG_RETURN_IMMEDIATELY If this bit is not set, the server MUST make the
0x00000010 method call synchronously.
If this bit is set, the server MUST make the method
call semisynchronously.
WBEM_FLAG_DIRECT_READ If this bit is set, the server MUST disregard any

0x00000200 derived class when it searches the result.
If this bit is not set, the server MUST consider the
entire class hierarchy when it returns the result.
61 / 168
[MS-WMI] — v20091104

information that the client wants to pass for processing to the implementer of the CIM object
that is referred to by strObjectPath. If the parameter is set to NULL, the server MUST ignore
it.
ppObject: If the parameter is set to NULL, the server MUST ignore it. If the parameter is not
NULL, the server MUST return an IWbemClassObject interface pointer that contains the
requested CIM object. In this case, the output parameter MUST be filled according to the state
of the lFlags parameter (whether WBEM_FLAG_RETURN_IMMEDIATELY is set) as listed in the
following table.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST contain an MUST be set to NULL if

not set. IWbemClassObject interface the input parameter is
pointer. non-NULL.

set. input parameter is non-NULL. the input parameter is
non-NULL.
ppCallResult: This parameter is optional. If the parameter is set to NULL, the server MUST
ignore it. If the parameter is non-NULL, the server MUST return an IWbemCallResult
interface pointer that contains the operation call result. In this case, the output parameter
MUST be filled according to the state of the lFlags parameter (whether

not set. input parameter is non-NULL. the input parameter is
non-NULL.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST contain the MUST be set to NULL if

set. IWbemCallResult interface the input parameter is
pointer. non-NULL.
Return Values: This method MUST return an HRESULT that MUST indicate the status of the
method call. The HRESULT MUST have the type and values as specified in section 2.2.11. The
server MUST return WBEM_S_NO_ERROR (as specified in section 2.2.11) to indicate the
successful completion of the method.
accesses to the namespace; otherwise, WBEM_E_ACCESS_DENIED MUST be returned.
In response to the IWbemServices::GetObject method, the server MUST evaluate the

strObjectPath parameter and MUST return the requested CIM object. The method MUST fail if the
CIM object that is referred to by strObjectPath does not exist, if the method parameters are not
valid as specified in the preceding list, or if the server is unable to execute the method.
The successful synchronous method execution MUST provide the retrieved IWbemClassObject
interface pointer in the ppObject parameter and MUST return WBEM_S_NO_ERROR.
62 / 168
[MS-WMI] — v20091104

3.1.1.1.2.
3.1.4.3.5 IWbemServices::GetObjectAsync (Opnum 7)
The IWbemServices::GetObjectAsync method is the asynchronous version of the

IWbemServices::GetObject method.
HRESULT GetObjectAsync(
[in] long lFlags,
[in] IWbemObjectSink* pResponseHandler
);
strObjectPath: MUST be the CIM path of the CIM object to be retrieved. If this parameter is set
to NULL, the server MUST return an empty CIM object.
lFlags: Specifies the behavior of the GetObjectAsync method. Flag behavior MUST be
interpreted as specified in the following table.
The server MUST accept a combination of zero or more flags from the following table and
Value Meaning
in section 2.2.6.
WBEM_FLAG_SEND_STATUS If this bit is not set, the server MUST make one final
0x00000080 IWbemObjectSink::SetStatus call on the interface
pointer that is provided in the pResponseHandler
parameter.
If this bit is set, the server MAY make intermediate
IWbemObjectSink::SetStatus calls on the interface
pointer prior to call completion.
WBEM_FLAG_DIRECT_READ If this bit is not set, the implementer MUST consider

0x00000200 the entire class hierarchy when it returns the result.
If this bit is set, the server MUST disregard any
derived class when it searches the result.

information that the client wants to provide to the server about the CIM object referred to by
strObjectPath. If pCtx is NULL, the parameter MUST be ignored.
pResponseHandler: MUST be a pointer to the IWbemObjectSink interface that is

implemented by the caller, where enumeration results must be delivered. The parameter
63 / 168
[MS-WMI] — v20091104

MUST NOT be NULL. If the parameter is NULL, the server MUST return
WBEM_E_INVALID_PARAMETER.
In response to the GetObjectAsync method, the server MUST evaluate the strObjectPath
parameter and MUST return the requested CIM object. The method MUST fail if the CIM object
referred to by strObjectPath does not exist, if the method parameters are not valid as specified in
this section, or if the server is unable to execute the method.
The asynchronous method execution MUST follow the rules that are specified in section 3.1.1.1.3.
3.1.4.3.6 IWbemServices::PutClass (Opnum 8)
The IWbemServices::PutClass method creates a new class or updates an existing class in the
namespace that is associated with the current IWbemServices interface. The server MUST NOT
allow the creation of classes that have names that begin or end with an underscore because those
names are reserved for system classes.
HRESULT PutClass(
[in] IWbemClassObject* pObject,
[in] long lFlags,
);
pObject: MUST be a pointer to an IWbemClassObject interface pointer that MUST contain the
class information to create a new class or update an existing class. This parameter MUST NOT
be NULL.
lFlags: Specifies the behavior of the PutClass method. Flag behavior MUST be interpreted as
Value Meaning
WBEM_FLAG_USE_AMENDED_QUALIFIERS If this bit is set, the server SHOULD ignore all the
0x00020000 amended qualifiers while it creates or updates the
CIM class.<17>
If this bit is not set, the server SHOULD include all the
qualifiers, including amended qualifiers, while it
updates or creates the CIM class.
64 / 168
[MS-WMI] — v20091104

Value Meaning

WBEM_FLAG_UPDATE_ONLY The server MUST update a CIM class pObject if the

0x00000001 CIM class is present.
This flag is mutually exclusive with
WBEM_FLAG_CREATE_ONLY. If none of these flags
are set, the server MUST create or update a CIM class
pObject.
WBEM_FLAG_CREATE_ONLY The server MUST create a CIM class pObject if the

0x00000002 CIM class is not already present.
WBEM_FLAG_UPDATE_FORCE_MODE The server MUST update the class even if conflicting

0x00000040 child classes exist.
WBEM_FLAG_UPDATE_SAFE_MODE The server MUST update the class as long as the

0x00000020 change does not cause any conflicts with existing
child classes or instances.
WBEM_FLAG_UPDATE_FORCE_MODE. If none of these
flags are set, the server MUST update the class if
there is no derived class, if there is no instance for
that class, or if the class is unchanged.

information that the client wants to provide to the server about the CIM class that is referred
to by pObject. If the pCtx parameter is NULL, it MUST be ignored.
ppCallResult: The output parameter MUST be filled according to the state of the lFlags
parameter (whether WBEM_FLAG_RETURN_IMMEDIATELY is set) as listed in the following
table.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST be set to MUST be set to NULL

not set IWbemCallResult if the input if the input
parameter is non-NULL. parameter is non-
NULL.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST contain the MUST be set to NULL

set. IWbemCallResult interface if the input
pointer. parameter is non-
NULL.
This parameter is optional. If the parameter is set to NULL, the server MUST ignore it. If the
parameter is non-NULL, the server MUST return an IWbemCallResult interface pointer that
contains the operation call result.
65 / 168
[MS-WMI] — v20091104

returned.
In response to the IWbemServices::PutClass method, the server MUST evaluate the pObject
parameter and MUST add or update this class into the current namespace. The method MUST fail if
pObject represents a read-only class, if the method parameters or their combinations are not valid
as specified in this section, or if the server is unable to execute the method.
The successful synchronous method execution MUST return WBEM_S_NO_ERROR.
3.1.1.1.2.
The failed method execution MUST set output parameters to NULL and MUST return an error in the
format specified in section 2.2.11.
3.1.4.3.7 IWbemServices::PutClassAsync (Opnum 9)
The IWbemServices::PutClassAsync method is the asynchronous version of the

IWbemServices::PutClass method. The PutClassAsync method creates a new class or updates
an existing class. The server MUST NOT allow the creation of classes that have names that begin or
end with an underscore because those names are reserved for system classes.
HRESULT PutClassAsync(
[in] long lFlags,
);
pObject: MUST be a pointer to an IWbemClassObject interface pointer that MUST contain the
class information to create a new class or update an existing class. The class that is specified
by the parameter MUST have been correctly initialized with all the required property values.
This parameter MUST NOT be NULL.
lFlags: Specifies the behavior of the PutClassAsync method. Flag behavior MUST be interpreted
as specified in the following table.
Value Meaning
0x00020000 amended qualifiers while it creates or updates a CIM
class.<18>
qualifiers, including amended qualifiers, while it
updates or creates a CIM class.
66 / 168
[MS-WMI] — v20091104

Value Meaning
WBEM_FLAG_UPDATE_ONLY The server MUST update a CIM class pObject if the

0x00000001 CIM class is present.
are set, the server MUST create or update a CIM class
pObject.
WBEM_FLAG_CREATE_ONLY The server MUST create a CIM class pObject if the

0x00000002 CIM class is not already present.
WBEM_FLAG_UPDATE_FORCE_MODE The server MUST forcefully update the class even

0x00000040 when conflicting child classes exist.
WBEM_FLAG_UPDATE_SAFE_MODE The server MUST update the class as long as the

0x00000020 change does not cause any conflicts with existing
child classes or instances.
WBEM_FLAG_UPDATE_FORCE_MODE.
If none of these flags are set, the server MUST update
the class if there is no derived class, if there is no
instance for that class, or if the class is unchanged.
0x00000080 IWbemObjectSink::SetStatus method call on the
interface pointer that is provided in the
pResponseHandler parameter.

information that the client wants to pass to the server. If the pCtx parameter is NULL, the
parameter MUST be ignored.
pResponseHandler: MUST be a pointer to an IWbemObjectSink interface object that is

implemented by the client of this method. The parameter MUST NOT be NULL.
returned.
In response to the IWbemServices::PutClassAsync method, the server MUST evaluate the

pObject parameter (previously specified) and it MUST add or update this class into the current
namespace. The method MUST fail if pObject represents a read-only class, if the method parameters
or their combinations are not valid (as previously specified), or if the server is unable to execute the
method.
67 / 168
[MS-WMI] — v20091104

The asynchronous method execution MUST follow the rules specified in section 3.1.1.1.3.
3.1.4.3.8 IWbemServices::DeleteClass (Opnum 10)
The IWbemServices::DeleteClass method MUST delete a specified class from the namespace that
is associated with the current IWbemServices interface.
HRESULT DeleteClass(
[in] const BSTR strClass,
[in] long lFlags,
[in, out, unique] IWbemCallResult** ppCallResult
);
strClass: MUST be the name of the class to delete. This parameter MUST NOT be NULL.
lFlags: Specifies the behavior of the DeleteClass method. Flag behavior MUST be interpreted as
Value Meaning
WBEM_FLAG_RETURN_IMMEDIATELY If this bit is set, the server MUST make the method call
0x00000010 semisynchronously.
If this bit is not set, the server MUST make the method call
synchronously.
invalid.

information that the client wants to pass to the server. If pCtx is NULL, the parameter MUST
be ignored.
ignore it. If the parameter is not NULL, the server MUST return an IWbemCallResult
interface pointer that contains the operation call result. The output parameter MUST be filled
according to the state of the lFlags parameter (whether WBEM_FLAG_RETURN_IMMEDIATELY
is set) as listed in the following table.

not set. IWbemCallResult if the input if the input
NULL.

NULL.
68 / 168
[MS-WMI] — v20091104

returned.
In response to the IWbemServices::DeleteClass method, the server MUST evaluate the strClass
parameter (specified in this section) and MUST delete the strClass parameter from the current
namespace. The server MUST delete all the instances of the class and recursively delete all the
derived classes. The method MUST fail if the following applies: if strClass does not exist; if the
method parameters or their combinations are not valid as specified in this section; or if the server is
unable to execute the method.
3.1.1.1.2.
3.1.4.3.9 IWbemServices::DeleteClassAsync (Opnum 11)
The IWbemServices::DeleteClassAsync method is the asynchronous version of the

IWbemServices::DeleteClass method. The DeleteClassAsync method MUST delete a specified
class from the namespace.
HRESULT DeleteClassAsync(
[in] long lFlags,
);
strClass: MUST be the name of the class to delete. This parameter MUST NOT be NULL.
lFlags: Specifies the behavior of the DeleteClassAsync method. Flag behavior MUST be
Value Meaning
0x00000080 IWbemObjectSink::SetStatus call on the interface pointer that is
provided in the pResponseHandler parameter.
IWbemObjectSink::SetStatus calls on the interface pointer prior
to call completion.
Any other DWORD value that does not match the preceding condition MUST be treated as not
valid.

be ignored.
69 / 168
[MS-WMI] — v20091104

implemented by the client of this method. This parameter MUST NOT be NULL.
returned.
In response to the IWbemServices::DeleteClassAsync method, the server MUST evaluate the

strClass parameter (specified in this section) and MUST delete strClass from the current namespace.
The server MUST delete all the instances of the class and recursively delete all the derived classes.
The method MUST fail if the following applies: if strClass does not exist; if the method parameters or
their combinations are not valid as previously specified; or if the server is unable to execute the
method.
3.1.4.3.10 IWbemServices::CreateClassEnum (Opnum 12)
The IWbemServices::CreateClassEnum method provides a class enumeration. When this method

is invoked, the server MUST return all classes that satisfy the selection criteria from the namespace
that is associated with the current IWbemServices interface.
HRESULT CreateClassEnum(
[in] const BSTR strSuperClass,
[in] long lFlags,
[out] IEnumWbemClassObject** ppEnum
);
strSuperClass: MUST specify a superclass name. Only classes that are subclasses of this class
MUST be returned. If strSuperClass is NULL or a zero-length string, all classes in the
namespace MUST be included in the result set. The results MUST be filtered by using the
lFlags parameter. Classes without a base class MUST be considered to be derived from the
NULL superclass.
lFlags: Flags affect the behavior of the CreateClassEnum method. Flag behavior MUST be
Value Meaning
70 / 168
[MS-WMI] — v20091104

Value Meaning
in section 2.2.6.
WBEM_FLAG_SHALLOW When this bit is not set, the server MUST return all
0x00000001 classes that are derived from the requested class and
all its subclasses.
When this bit is set, the server MUST return only the
classes that are directly derived from the requested
class.
WBEM_FLAG_FORWARD_ONLY When this bit is not set, the server MUST return an
0x00000020 enumerator that has reset capability.
When this bit is set, the server MUST return an
enumerator that does not have reset capability, as
specified in section 3.1.4.4.
pCtx: MUST be a pointer to an IWbemContext interface that MUST contain additional

information that the client wants to pass to the server. If the pCtx parameter is NULL, it MUST
be ignored.
ppEnum: MUST receive the pointer to the enumerator that implements the
IEnumWbemClassObject interface. This parameter MUST NOT be NULL.
In response to the IWbemServices::CreateClassEnum method, the server MUST evaluate the

strSuperClass parameter (specified in the preceding list) and MUST return all classes that match the
input parameters from the current namespace. The method MUST fail if strSuperClass does not
exist; if the method parameters or their combinations are not valid as previously specified; or if the
server is unable to execute the method.
The successful synchronous method execution MUST fill the ppEnum parameter with an
IEnumWbemClassObject interface pointer after all classes are collected and MUST return
WBEM_S_NO_ERROR.
3.1.1.1.2.
The failed method execution MUST set the value that is referenced by the output parameters to
NULL and MUST return an error in the format that is specified in section 2.2.11.
71 / 168
[MS-WMI] — v20091104

3.1.4.3.11 IWbemServices::CreateClassEnumAsync (Opnum 13)
The IWbemServices::CreateClassEnumAsync method provides an asynchronous class

enumeration. When this method is invoked, the server MUST return all classes that satisfy the
selection criteria.
HRESULT CreateClassEnumAsync(
[in] long lFlags,
);
strSuperClass: Specifies a superclass name. Only classes that are subclasses of this class MUST
be returned. If strSuperClass is NULL or a zero-length string, all classes in the namespace
MUST be considered in the result set. The results MUST be filtered by using the lFlags
parameter. Classes without a base class are considered to be derived from the NULL
superclass.
lFlags: Flags that affect the behavior of the CreateClassEnum method. Flag behavior MUST be
Value Meaning
localizable information for the CIM object as specified
in section 2.2.6.
parameter.
WBEM_FLAG_SHALLOW When this bit is not set, the server MUST return all
0x00000001 classes that are derived from the requested class and
all its subclasses.
When this bit is set, the server MUST only return the
classes that are directly derived from the requested
class.

be ignored.
pResponseHandler: MUST be a pointer to the IWbemObjectSink that is implemented by the

caller, where enumeration results must be delivered. The parameter MUST NOT be NULL. In
72 / 168
[MS-WMI] — v20091104

error cases, indicated by the return value, the supplied IWbemObjectSink interface pointer
MUST NOT be used. If WBEM_S_NO_ERROR is returned, the user IWbemObjectSink
interface pointer MUST be called to indicate the results of the CreateClassEnumAsync
operation, as specified later in this section.
Return Values: This method MUST return an HRESULT, which MUST indicate the status of the
method call. The HRESULT MUST have the type and values as specified in section 2.2.11. The
server MUST return WBEM_S_NO_ERROR (specified in section 2.2.11) to indicate the
In response to the IWbemServices::CreateClassEnumAsync method, the server MUST evaluate

the strSuperClass parameter (specified in this section) and MUST return all classes that match the
input parameters from the current namespace. The method MUST fail if strSuperClass does not
exist, if the method parameters or their combinations are not valid as specified earlier in this
section, or if the server is unable to execute the method.
3.1.4.3.12 IWbemServices::PutInstance (Opnum 14)
The IWbemServices::PutInstance method creates or updates an instance of an existing class.
The PutInstance method opnum equals 14.
HRESULT PutInstance(
[in] IWbemClassObject* pInst,
[in] long lFlags,
);
pInst: MUST be a pointer to an IWbemClassObject interface object that MUST contain the class
instance that the client wants to create or update. This parameter MUST NOT be NULL.
lFlags: Flags that affect the behavior of the PutInstance method. Flag behavior MUST be
Value Meaning
0x00020000 amended qualifiers while this method creates or
updates a CIM instance.
qualifiers, including amended qualifiers, while this
method creates or updates a CIM instance.
73 / 168
[MS-WMI] — v20091104

Value Meaning
WBEM_FLAG_UPDATE_ONLY The server MUST update a CIM instance pObject if the

0x00000001 CIM instance is present.
are set, the server MUST create or update a CIM
instance pObject.
WBEM_FLAG_CREATE_ONLY The server MUST create a CIM instance pObject if the

0x00000002 CIM instance is not already present.
pCtx: This parameter is optional. The pCtx parameter MUST be a pointer to an IWbemContext
interface object. The pCtx parameter indicates whether the client is requesting a partial-
instance update or a full-instance update. A partial-instance update modifies a subset of the
CIM instance properties. In contrast, a full-instance update modifies all the properties. If
NULL, this parameter indicates that the client application is requesting a full-instance update.
When pCtx is used to perform a partial-instance update, the IWbemContext interface object
MUST be filled in with the properties that are specified in the following table.
Property name Type Description
__PUT_EXTENSIONS VT_BOOL If this property is set to TRUE, one or more of the

other IWbemContext values have been specified.
To perform a partial instance update, this property
MUST be set to TRUE and the properties that follow
MUST be set as specified in their respective
descriptions.
__PUT_EXT_STRICT_NULLS VT_BOOL If this property is set to TRUE, the server MUST force
the setting of properties to NULL. This parameter is
optional.
__PUT_EXT_PROPERTIES VT_ARRAY | Contains a CIM property list to update. The server

VT_BSTR MUST ignore the properties that are not listed. To
perform a partial instance update, the list of
properties MUST be specified.
__PUT_EXT_ATOMIC VT_BOOL If the return code indicates success, all CIM property
updates MUST have been successful.
On failure, the server MUST revert any changes to
the original state for all CIM property that was
updated. On failure, not a single change MUST
remain. The operation is successful when all
properties are updated.
interface pointer that contains the result of the operation call. The output parameter MUST be
filled according to the state of the lFlags parameter (whether
WBEM_FLAG_RETURN_IMMEDIATELY is set), as listed in the following table.
74 / 168
[MS-WMI] — v20091104


parameter is not-NULL. parameter is not-
NULL.

pointer. parameter is not-
NULL.
returned.
In response to the IWbemServices::PutInstance method, the server MUST evaluate the pInst
parameter as specified in this section. It MUST add or update this instance into the current
namespace. The method MUST fail if the following applies: if the server does not allow creation of
new instances for the pInst class or does not allow modification of the instance that is represented
by pInst; if the method parameters or their combinations are not valid as specified in this section;
or if the server is unable to execute the method.
The semisynchronous method execution MUST follow the rules as specified in section 3.1.1.1.2.
format that is specified in section 2.2.11.
3.1.4.3.13 IWbemServices::PutInstanceAsync (Opnum 15)
The IWbemServices::PutInstanceAsync method is the asynchronous version of the

PutInstance method. The PutInstanceAsync method creates or updates an instance of an
existing class.
HRESULT PutInstanceAsync(
[in] long lFlags,
);
pInst: MUST be a pointer to an IWbemClassObject interface object that MUST contain the class
instance that the client wants to create or update. This parameter MUST NOT be NULL.
lFlags: Flags that affect the behavior of the PutInstanceAsync method. Flag behavior MUST be
75 / 168
[MS-WMI] — v20091104

not comply with this condition MUST be treated as not valid.
Value Meaning
0x00020000 amended qualifiers while this method creates or
updates a CIM instance.
qualifiers, including amended qualifiers, while this
method creates or updates a CIM instance.
WBEM_FLAG_UPDATE_ONLY The server MUST update a CIM instance pObject if the

0x00000001 CIM instance is present.
are set, the server MUST create or update a CIM
instance pObject.
WBEM_FLAG_CREATE_ONLY The server MUST create a CIM instance pObject if the

0x00000002 CIM instance is not already present.
parameter.
pCtx: This parameter is optional. The pCtx parameter MUST be a pointer to an IWbemContext
interface object that is specified in section 2.2.13. The pCtx parameter indicates whether the
client is requesting a partial-instance update or full-instance update. A partial-instance update
modifies a subset of CIM instance properties; a full-instance update modifies all the
properties. If NULL, this parameter indicates that the client application is requesting a full-
instance update. When pCtx is used to perform a partial-instance update, the IWbemContext
interface MUST be completed with the properties that are specified in the following table.
__PUT_EXTENSIONS VT_BOOL If this property is set to TRUE, one or more of the

other IWbemContext values have been specified. To
perform a partial-instance update, this property
MUST be set to TRUE.
__PUT_EXT_STRICT_NULLS VT_BOOL If this property is set to TRUE, the server MUST

force the setting of properties to NULL. This
parameter is optional.
__PUT_EXT_PROPERTIES VT_ARRAY | Contains a CIM property list to update. The server

VT_BSTR MUST ignore properties that are not listed. To
perform a partial-instance update, the list of
properties MUST be specified.
__PUT_EXT_ATOMIC VT_BOOL If the return code indicates success, all CIM property
76 / 168
[MS-WMI] — v20091104

updates MUST have been successful.

On failure, the server MUST revert any changes to
the original state for all CIM property that is
updated. On failure, not a single change MUST
remain. The operation is successful when all
properties are updated.

returned.
In response to an IWbemServices::PutInstanceAsync method, the server MUST evaluate the

pInst parameter as specified in this section. It MUST add or update this instance into the current
namespace. The method MUST fail if one of the following is true: the server does not allow the
creation of new instances for the class of pInst or does not allow modification of the instance that is
represented by pInst; the method parameters or their combinations are not valid, as specified
earlier in this section; or the server is unable to execute the method.
The asynchronous method execution MUST follow the rules as specified in 3.1.1.1.3.
The failed method execution MUST return an error in the format that is specified in section 2.2.11.
3.1.4.3.14 IWbemServices::DeleteInstance (Opnum 16)
The IWbemServices::DeleteInstance method deletes an instance of an existing class from the

namespace that is pointed to by the IWbemServices interface object that is used to call the
method.
HRESULT DeleteInstance(
[in] long lFlags,
);
strObjectPath: MUST be the CIM path to the class instance that the client wants to delete. This
parameter MUST NOT be NULL. The CIM path MUST contain the class name and the value of
the key properties.
lFlags: Flags that affect the behavior of the IWbemServices::DeleteInstance method. Flag
behavior MUST be interpreted as specified in the following table.
77 / 168
[MS-WMI] — v20091104

Value Meaning
WBEM_FLAG_RETURN_IMMEDIATELY If this bit is not set, the server MUST make the method call
0x00000010 synchronously.
If this bit is set, the server MUST make the method call
semisynchronously.
invalid.

be ignored.
interface pointer that contains the result of the operation call. The output parameter MUST be
filled according to the state of the lFlags parameter (whether
WBEM_FLAG_RETURN_IMMEDIATELY is set), as listed in the following table.

NULL.

NULL.
returned.
In response to the IWbemServices::DeleteInstance method, the server MUST evaluate the

strObjectPath parameter (as specified in this section) and MUST delete the instance that is identified
by strObjectPath from the current namespace. The method MUST fail if the following applies: if
strObjectPath does not exist; if the method parameters or their combinations are not valid as
specified in the preceding list; or if the server is unable to execute the method.
78 / 168
[MS-WMI] — v20091104

3.1.4.3.15 IWbemServices::DeleteInstanceAsync (Opnum 17)
The IWbemServices::DeleteInstanceAsync method is the asynchronous version of the

IWbemServices::DeleteInstance method. The IWbemServices::DeleteInstanceAsync method
deletes an instance of an existing class from the namespace that is pointed to by the
IWbemServices interface that is used to call the method.
HRESULT DeleteInstanceAsync(
[in] long lFlags,
);
strObjectPath: MUST be the CIM path to the class instance that the client wants to delete. This
the key properties.
lFlags: Flags that affect the behavior of the IWbemServices::DeleteInstanceAsync method.

Flag behavior MUST be interpreted as specified in the following table.
Value Meaning
to call completion.
invalid.
pCtx: MUST be a pointer to an IWbemContext interface, which contains additional information

that the client wants to pass to the server. If pCtx is NULL, the parameter MUST be ignored.

returned.
In response to an IWbemServices::DeleteInstanceAsync method, the server MUST evaluate the

strObjectPath parameter (as specified in this section) and MUST delete the instance that is identified
by strObjectPath from the current namespace. The method MUST fail if the following applies: if
strObjectPath does not exist; if the method parameters or their combinations are not valid as
specified in this section; or if the server is unable to execute the method.
79 / 168
[MS-WMI] — v20091104

The asynchronous method execution MUST follow the rules as specified in 3.1.1.1.3.
3.1.4.3.16 IWbemServices::CreateInstanceEnum (Opnum 18)
The IWbemServices::CreateInstanceEnum method provides an instance enumeration. When this

method is invoked, the server MUST return all class instances that satisfy the selection criteria.
HRESULT CreateInstanceEnum(
[in] long lFlags,
);
strSuperClass: MUST contain the name of the CIM class for which the client wants instances.
lFlags: Flags that affect the behavior of the CreateInstanceEnum method. Flag behavior MUST
Value Meaning
in section 2.2.6.
WBEM_FLAG_DIRECT_READ If this bit is not set, the server MUST consider the
0x00000200 entire class hierarchy when it returns the result.
WBEM_FLAG_SHALLOW If this bit is set, the server MUST return instances of

0x00000001 the requested class only and MUST exclude instances
of classes that are derived from the requested class.
If this bit is not set, the server MUST return all
instances of the requested class as well as instances
WBEM_FLAG_FORWARD_ONLY If this bit is not set, the server MUST return an

If this bit is set, the server MUST return an
enumerator that does not have reset capability, as
80 / 168
[MS-WMI] — v20091104

Value Meaning
pCtx: MUST be a pointer to an IWbemContext interface, which contains additional information

that the client wants to pass to the server. If pCtx is NULL, the parameter MUST be ignored.
ppEnum: MUST receive the pointer to the enumerator that is used to enumerate through the
returned class instances, which implements the IEnumWbemClassObject interface. This
parameter MUST NOT be NULL.
the method call. The server MUST return the following value (specified in section 2.2.11) to
The security principal that makes the call MUST have WBEM_ENABLE and WBEM_REMOTE_ENABLE
In response to the IWbemServices::CreateInstanceEnum method, the server MUST evaluate the

strSuperClass parameter (as specified in this section) and MUST return all instances for the specific
class in the current namespace. The method MUST fail if the following applies: if strSuperClass does
not exist; if the method parameters or their combinations are not valid, as specified in this section;
or if the server is unable to execute the method.
The successful synchronous method execution MUST fill the ppEnum parameter with an
IEnumWbemClassObject interface pointer after all instances are collected and MUST return
WBEM_S_NO_ERROR.
3.1.4.3.17 IWbemServices::CreateInstanceEnumAsync (Opnum 19)
The IWbemServices::CreateInstanceEnumAsync method provides an asynchronous instance

enumeration. When this method is invoked, the server MUST return instances of all classes that
satisfy the selection criteria.
HRESULT CreateInstanceEnumAsync(
[in] long lFlags,
);
strSuperClass: MUST contain the name of the CIM class for which the client wants instances.
lFlags: Flags that affect the behavior of the IWbemServices::CreateInstanceEnumAsync

method. Flag behavior MUST be interpreted as specified in the following table.
81 / 168
[MS-WMI] — v20091104

Value Meaning
in section 2.2.6.
WBEM_FLAG_SEND_STATUS If this bit is not set the server MUST make one final
parameter.
WBEM_FLAG_SHALLOW If this bit is set, the server MUST return instances of

0x00000001 the requested class only and MUST exclude instances
If this bit is not set, the server MUST return all
instances of the requested class as well as instances

be ignored.

implemented by the caller and where enumeration results must be delivered. The parameter
MUST NOT be NULL.
In response to IWbemServices::CreateInstanceEnumAsync, the server MUST evaluate the

strSuperClass parameter (as specified in this section) and MUST return all instances for the specified
class in the current namespace. The method MUST fail if the following applies: if strSuperClass does
not exist; if the method parameters or their combinations are not valid as specified earlier in this
section; or if the server is unable to execute the method.
82 / 168
[MS-WMI] — v20091104

The asynchronous method execution MUST follow the rules specified in 3.1.1.1.3.
3.1.4.3.18 IWbemServices::ExecQuery (Opnum 20)
The IWbemServices::ExecQuery method returns an enumerable collection of IWbemClassObject

interface objects based on a query.
HRESULT ExecQuery(
[in] const BSTR strQueryLanguage,
[in] const BSTR strQuery,
[in] long lFlags,
);
strQueryLanguage: MUST be set to "WQL".
strQuery: MUST contain the "WQL" query text as specified in [UNICODE] (UTF-16) and in
section 2.2.1. This parameter MUST NOT be NULL.
lFlags: Specifies the behavior of the IWbemServices::ExecQuery method. Flag behavior MUST
Value Meaning
WBEM_FLAG_USE_AMENDED_QUALIFIERS If this bit is not set, the server SHOULD not return
0x00020000 CIM localizable information.
in section 2.2.6.
WBEM_FLAG_PROTOTYPE If this bit is not set, the server MUST run the query.
0x00000002 If this bit is set, the server MUST only return the class
schema of the resulting objects.
WBEM_FLAG_FORWARD_ONLY If this bit is not set, the server MUST return an

If this bit is set, the server MUST return an
enumerator without reset capability, as specified in
83 / 168
[MS-WMI] — v20091104

Value Meaning
section 3.1.4.4.

be ignored.
ppEnum: MUST receive the pointer to the IEnumWbemClassObject that is used to enumerate
through the CIM objects that are returned for the query result set. This parameter MUST NOT
be NULL.
In response to IWbemServices::ExecQuery, the server MUST evaluate the strQuery and

strQueryLanguage parameters (as specified in this section) and MUST return all instances that
match the provided query. The method MUST fail if the method parameters or their combinations
are not valid, as specified earlier in this section, or if the server is unable to execute the method.
The successful synchronous method execution MUST fill the ppEnum parameter with a
IEnumWbemClassObject interface pointer after all instances are collected and MUST return
WBEM_S_NO_ERROR.
3.1.1.1.2.
NULL and MUST return an error in the format specified in section 2.2.11.
3.1.4.3.19 IWbemServices::ExecQueryAsync (Opnum 21)
The IWbemServices::ExecQueryAsync method is the asynchronous version of the

IWbemServices::ExecQuery method. The IWbemServices::ExecQueryAsync method returns
an enumerable collection of IWbemClassObject interface objects based on a query.
HRESULT ExecQueryAsync(
[in] long lFlags,
);
strQuery: MUST contain the WQL query text as specified in section 2.2.1. This parameter MUST
NOT be NULL.
84 / 168
[MS-WMI] — v20091104

lFlags: Specifies the behavior of the IWbemServices::ExecQueryAsync method. Flag behavior
MUST be interpreted as specified in the following table.
Value Meaning
WBEM_FLAG_USE_AMENDED_QUALIFIERS If this bit is not set, the server SHOULD not return
0x00020000 CIM localizable information.
in section 2.2.6.
WBEM_FLAG_SEND_STATUS If this bit is not set the server MUST make one final
parameter.
WBEM_FLAG_PROTOTYPE If this bit is not set, the server MUST run the query.
0x00000002 If this bit is set, the server MUST only return the class
schema of the resulting objects.

be ignored.

implemented by the caller, where enumeration results must be delivered. The parameter
MUST NOT be NULL.
In response to an IWbemServices::ExecQueryAsync method call, the server MUST evaluate the

strQueryLanguage and strQuery parameters (as specified in this section) and return all instances
that match the requested query. The method MUST fail if the method parameters or their
combinations are not valid as specified earlier in this section, or if the server is unable to execute
the method.
85 / 168
[MS-WMI] — v20091104

3.1.4.3.20 IWbemServices::ExecNotificationQuery (Opnum 22)
The IWbemServices::ExecNotificationQuery method provides a subscription for event

notifications. When this method is invoked, the server runs a query to deliver events matching the
query. The call is executed semisynchronously and MUST follow the rules that are specified in
section 3.1.1.1.2. The WMI client can poll the returned enumerator for events as they arrive.
Releasing the returned enumerator cancels the query.
HRESULT ExecNotificationQuery(
[in] long lFlags,
);
strQuery: MUST contain the WQL event-related query text as specified in section 2.2.1. This
lFlags: Specifies the behavior of the IWbemServices::ExecNotificationQuery method. Flag

behavior MUST be interpreted as specified in the following table.
Value Meaning
in section 2.2.6.
WBEM_FLAG_RETURN_IMMEDIATELY If this bit is set, the server MUST make the method
0x00000010 call semisynchronously.
This flag MUST always be set.
WBEM_FLAG_FORWARD_ONLY If this bit is set, the server MUST return an

0x00000020 enumerator that does not have reset capability, as
This flag MUST always be set.

be ignored.
86 / 168
[MS-WMI] — v20091104

ppEnum: MUST receive the pointer to the IEnumWbemClassObject that is used to enumerate
through the CIM objects that are returned for the query result set. This parameter MUST NOT
be NULL.
In response to IWbemServices::ExecNotificationQuery, the server MUST evaluate the strQuery

and strQueryLanguage parameters (as specified in this section) and MUST return all events that
match the query. The method MUST fail if the method parameters or their combinations are not
valid as specified earlier in this section, or if the server is unable to execute the method. Because
the stream of events that are returned by the server is not finite, the method
IWbemServices::ExecNotificationQuery MUST NOT be executed synchronously. As previously
specified, this request MUST fail because the method parameters are not valid.
NULL and MUST return an error in the format specified in section 2.2.11.
3.1.4.3.21 IWbemServices::ExecNotificationQueryAsync (Opnum 23)
The IWbemServices::ExecNotificationQueryAsync method is the asynchronous version of the

IWbemServices::ExecNotificationQuery method. The
IWbemServices::ExecNotificationQueryAsync method provides subscription for asynchronous
event notifications. When this method is invoked, the server performs the same task as the
IWbemServices::ExecNotificationQuery method, except that events are supplied to the specified
response handler (pResponseHandler) until the IWbemServices::CancelAsyncCall method is
called.
HRESULT ExecNotificationQueryAsync(
[in] long lFlags,
);
strQuery: MUST contain the WQL event-related query text as specified in section 2.2.1. This
lFlags: Specifies the behavior of the IWbemServices::ExecNotificationQueryAsync method.

Flag behavior MUST be interpreted as specified in the following table.
87 / 168
[MS-WMI] — v20091104

Value Meaning
localizable information.
WBEM_FLAG_SEND_STATUS This flag is ignored.

0x00000080

information that the client wants to pass to the server. If pCtx is NULL, this parameter MUST
be ignored.

implemented by the caller, where enumeration results must be delivered. This parameter
MUST NOT be NULL.
In response to IWbemServices::ExecNotificationQueryAsync, the server MUST evaluate the

strQueryLanguage and strQuery parameters (as specified earlier in this section) and MUST start to
provide events that match the requested query. The method MUST fail if the method parameters or
their combinations are not valid, as specified earlier in this section, or if the server is unable to
execute the method.
If method execution succeeds, the server MUST run the notification query until the query is canceled
or execution fails. The server MUST NOT call IWbemObjectSink::SetStatus to send success or
operation progress information. When query execution fails, the server MUST call
IWbemObjectSink::SetStatus to send the error to the client, and the server MUST release
IWbemObjectSink.
3.1.4.3.22 IWbemServices::ExecMethod (Opnum 24)
The IWbemServices::ExecMethod method executes a CIM method that is implemented by a CIM

class or a CIM instance that is retrieved from the IWbemServices interface.
HRESULT ExecMethod(
[in] const BSTR strMethodName,
[in] long lFlags,
[in] IWbemClassObject* pInParams,
[out, in, unique] IWbemClassObject** ppOutParams,
88 / 168
[MS-WMI] — v20091104

);
strObjectPath: MUST be the CIM path to the class or instance that implements the method. This
the key properties.
strMethodName: MUST be the name of the method to be executed. This parameter MUST NOT
be NULL.
lFlags: Specifies the behavior of the IWbemServices::ExecMethod method. Flag behavior

MUST be interpreted as specified in the following table.
Value Meaning
WBEM_FLAG_RETURN_IMMEDIATELY If this bit is not set, the server MUST make the method call
0x00000010 synchronously.
If this bit is set, the server MUST make the method call
semisynchronously.
invalid.

be ignored.
pInParams: MUST be a pointer to an IWbemClassObject interface pointer, which MUST

contain the values that correspond to all input parameters that are accepted by the method.
This parameter MUST be NULL when the method has no input parameters.
ppOutParams: If ppOutParams is NULL, the parameter MUST be ignored. When the parameter
is not NULL, it MUST return an IWbemClassObject interface pointer that contains output
parameters. The output parameter MUST be filled according to the state of the lFlags
parameter (whether WBEM_FLAG_RETURN_IMMEDIATELY is set) as listed in the following
table.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST contain an MUST be set to NULL

not set. IWbemClassObject interface if the input parameter
pointer. is non-NULL.
WBEM_FLAG_RETURN_IMMEDIATELY is MUST return NULL. MUST be set to NULL

set. if the input parameter
is non-NULL.
ignore it. However, if the parameter is not NULL, the server MUST return an
IWbemCallResult interface pointer that contains the operation call result. In this situation,
the output parameter MUST be filled according to the state of the lFlags parameter (whether
89 / 168
[MS-WMI] — v20091104

Condition Success operation Failure operation

NULL.

NULL.
Return Values: This method MUST return an HRESULT, which MUST indicate the status of the
method call. HRESULT MUST have the type and values as specified in section 2.2.11. The
server MUST return WBEM_S_NO_ERROR (specified in section 2.2.11) to indicate the
The security principal that makes the call MUST have WBEM_METHOD_EXECUTE and
WBEM_REMOTE_ENABLE accesses to the namespace; otherwise, WBEM_E_ACCESS_DENIED MUST
be returned.
In response to IWbemServices::ExecMethod, the server MUST evaluate the strObjectPath and

strMethodName parameters (as specified in this section) and MUST execute the method that is
identified by strMethodName and implemented by the CIM object that is referred to by
strObjectPath. The method MUST use the parameters that are provided by pInParams. The method
MUST fail if the CIM object that is referred to by strObjectPath does not exist, if the method
parameters are not valid, as specified earlier in this section, or if the server is unable to execute the
method.
The successful synchronous method execution MUST return the output parameters that are
encapsulated in an IWbemClassObject interface pointer in the ppObject parameter and MUST return
WBEM_S_NO_ERROR.
3.1.1.1.2.
3.1.4.3.23 IWbemServices::ExecMethodAsync (Opnum 25)
The IWbemServices::ExecMethodAsync method asynchronously executes a CIM method that is

implemented by a CIM class or a CIM instance that is retrieved from the IWbemServices interface.
HRESULT ExecMethodAsync(
[in] long lFlags,
);
90 / 168
[MS-WMI] — v20091104

strObjectPath: MUST be the CIM path to the class or instance that implements the method. This
the key properties.
strMethodName: MUST be the name of the method to be executed. This parameter MUST NOT
be NULL.
lFlags: Specifies the behavior of the ExecMethodAsync method. Flag behavior MUST be
Value Meaning
WBEM_FLAG_SEND_STATUS If this bit is not set, the server MUST make just one final
to call completion.
invalid.

be ignored.
pInParams: MUST be a pointer to an IWbemClassObject interface pointer, which MUST

contain the values of all input parameters that are accepted by the method. This parameter
MUST be NULL when the method has no input parameters.

The security principal that makes the call MUST have WBEM_METHOD_EXECUTE and
WBEM_REMOTE_ENABLE accesses to the namespace; otherwise, WBEM_E_ACCESS_DENIED MUST
be returned.
In response to IWbemServices::ExecMethodAsync, the server MUST evaluate strObjectPath and

strMethodName (as specified in this section) and MUST execute the method that is identified by
strMethodName, implemented by the strObjectPath CIM object using the provided pInParams
parameter. The method MUST fail if the method parameters or their combinations are not valid, as
specified earlier in this section, or if the server is unable to execute the method.
91 / 168
[MS-WMI] — v20091104

3.1.4.4 IEnumWbemClassObject Interface
The IEnumWbemClassObject interface MUST be used to return results from synchronous and
semisynchronous method calls, which can return multiple CIM objects as result. The interface MUST
be implemented by the server. The interface MUST be uniquely identified by UUID {027947e1-d731-
11ce-a357-000000000001}.
Method Description
Reset Causes the server to reset the enumeration sequence to the beginning of the collection of
CIM objects.
Opnum: 3
Next Causes the server to get one or more CIM objects starting at the current position in an
enumeration, and to move the current position by the number of CIM objects in the uCount
parameter.
Opnum: 4
NextAsync Asynchronous version of the IEnumWbemClassObject::Next method.

Opnum: 5
Clone Causes the server to make a logical copy of the entire enumerator.
Opnum: 6
Skip Causes the server to move the current position in an enumeration ahead by a specified
number of CIM objects.
Opnum: 7
An IEnumWbemClassObject interface object MUST be returned by

IWbemServices::CreateClassEnum, IWbemServices::CreateInstanceEnum, or
IWbemServices::ExecQuery, IWbemServices::ExecNotificationQuery, as specified in
IWbemServices section 3.1.4.3.
The object that exports this interface MUST implement the IWbemFetchSmartEnum interface. The
IRemUnknown and IRemUnknown2 interfaces, as specified in [MS-DCOM], MUST be used to
manage the interfaces exposed by the object.
92 / 168
[MS-WMI] — v20091104

Figure 6: IEnumWbemClassObject interface
3.1.4.4.1 IEnumWbemClassObject::Reset (Opnum 3)
When the IEnumWbemClassObject::Reset method is invoked, the server MUST reset the
enumeration sequence to the beginning of the collection of CIM objects.
HRESULT Reset();
This method has no parameters.
indicate the successful completion of the method. If the IEnumWbemClassObject::Reset
method is invoked on an enumerator that does not support reset capability, the server MUST
return WBEM_E_INVALID_OPERATION.
The server MUST validate that the security principal that makes the call is the same as the security
principal that obtained the IEnumWbemClassObject interface pointer; otherwise,
WBEM_E_ACCESS_DENIED MUST be returned.
In response to the IEnumWbemClassObject::Reset method, the server MUST reset the status of
the enumeration (as specified in this section) if the enumerator is not created by using
WBEM_FLAG_FORWARD_ONLY.
If the enumerator is created by using WBEM_FLAG_FORWARD_ONLY, the server MUST return

WBEM_E_INVALID_OPERATION.
A successful method execution MUST return WBEM_S_NO_ERROR.
A failed method execution MUST set the current index position to 0x0 and return an error in the
format that is specified in section 2.2.11.
93 / 168
[MS-WMI] — v20091104

3.1.4.4.2 IEnumWbemClassObject::Next (Opnum 4)
When the IEnumWbemClassObject::Next method is invoked, the server MUST either return
WBEM_S_TIMEDOUT with 0 CIM objects, or MUST get one or more CIM objects starting at the
current position in an enumeration. The server MUST also move the current position by the number
of CIM objects in the uCount parameter. When IEnumWbemClassObject is created, the current
position MUST be set on the first CIM object of the collection. The order of the CIM objects that are
stored in the enumerator is arbitrary.
HRESULT Next(
[in] long lTimeout,
[in] ULONG uCount,
[out, size_is(uCount), length_is(*puReturned)]
IWbemClassObject** apObjects,
[out] ULONG* puReturned
);
lTimeout: MUST be the maximum amount of time, in milliseconds, that the

IEnumWbemClassObject::Next method call allows to pass before it times out. If the
constant WBEM_INFINITE (0xFFFFFFFF) is specified, the call MUST wait until one or more CIM
objects are available. If the value 0x0 (WBEM_NO_WAIT) is specified, the call MUST return the
available CIM objects, if any, at the time the call is made, and MUST NOT wait for any more
objects.
uCount: MUST be the number of requested CIM objects to return.
apObjects: MUST be a pointer to an array of IWbemClassObject interface pointers. At entry,

this parameter MUST NOT be NULL. Upon return by the server, this parameter can be NULL if
a failure occurs or if there are no results.
puReturned: MUST be a pointer to a ULONG type that receives the number of CIM objects that
are returned. When sent by the client, this parameter MUST NOT be NULL. Upon return by the
server, this parameter can be NULL if a failure occurs or if there are no results.
In response to the IEnumWbemClassObject::Next method call, the server MUST evaluate the
uCount and lTimeout parameters (as specified in this section) and MUST return the requested
number of CIM objects, if any are available. The server MUST perform the operation within the time
allowed by lTimeout.
If the server is unable to return all the requested CIM objects in the requested amount of time, it
MUST return WBEM_S_TIMEDOUT. The requested number of CIM objects MUST start from the
current index position. The current index position in the enumeration MUST be incremented with the
number of CIM objects returned.
94 / 168
[MS-WMI] — v20091104

The successful method execution MUST return WBEM_S_NO_ERROR. If the number of the remaining
CIM objects to be retrieved is less than the number of requested CIM objects, the server MUST
return WBEM_S_FALSE. Regardless, the server MUST fill the output parameters of the method as
specified previously in this section.
If the original semisynchronous operation fails, the server MUST return the error code that the
original method would have returned in its synchronous version.
3.1.4.4.3 IEnumWbemClassObject::NextAsync (Opnum 5)
The IEnumWbemClassObject::NextAsync method is the asynchronous version of the

IEnumWbemClassObject::Next method. It provides controlled asynchronous retrieval of CIM
objects to a sink. The server MUST asynchronously get one or more CIM objects, starting at the
current position in an enumeration, and MUST move the current position by the number of CIM
objects in the uCount parameter. When IEnumWbemClassObject is created, the current position
MUST be set on the first CIM object of the collection. The order of the CIM objects that are stored in
the enumerator is arbitrary.
HRESULT NextAsync(
[in] ULONG uCount,
);
uCount: MUST be the number of CIM objects being requested. This parameter MUST NOT be
NULL.
pSink: MUST be a pointer to the IWbemObjectSink interface, which MUST represent the sink
to receive the CIM object. As each batch of CIM objects is requested, they MUST be delivered
to the IWbemObjectSink::Indicate method to which pSink points (as specified in section
3.1.4.2.1) and MUST be followed by a final call to the IWbemObjectSink::SetStatus method
to which pSink points, as specified in section 3.1.4.2.2. This parameter MUST NOT be NULL. In
error cases, indicated by the HRESULT return value, the supplied IWbemObjectSink
interface pointer MUST NOT be used by the server.
The server MUST validate that the security principal that makes the call is the same as the one that
obtained the IEnumWbemClassObject interface pointer; otherwise, WBEM_E_ACCESS_DENIED
MUST be returned.
In response to IEnumWbemClassObject::NextAsync, the server MUST evaluate the uCount

parameter as specified in this section. The lesser of either the requested number or the number of
CIM objects MUST start from the current index position. If the number of remaining CIM objects to
retrieve is less than the number of requested CIM objects, the lesser number of CIM objects MUST
be returned. The current index position in the enumeration MUST be incremented by the number of
returned CIM objects.
95 / 168
[MS-WMI] — v20091104

The method execution MUST NOT wait for delivery of the CIM objects through pSink. The server
MUST use the provided pSink to report data and status by using the IWbemObjectSink::Indicate
method that is specified in IWbemObjectSink::SetStatus and sections 3.1.4.2.1 and 3.1.4.2.2.
3.1.4.4.4 IEnumWbemClassObject::Clone (Opnum 6)
The IEnumWbemClassObject::Clone method makes a logical copy of the entire enumerator. The
cloned enumerator MUST have the same current position as the source enumerator.
HRESULT Clone(
);
ppEnum: Upon return, MUST contain a pointer to an IEnumWbemClassObject interface CIM

object that is a logical copy of the entire enumerator that made the Clone method call,
retaining the current position in an enumeration. This parameter MUST NOT be NULL. When
returned by the server, this parameter can be NULL if a failure occurred or if there are no
results.
The server MUST validate that the security principal that makes the call is the same security
The successful method execution MUST fill the ppEnum parameter with an
IEnumWbemClassObject interface pointer, as specified in section 3.1.4.4, which MUST be a copy
of the source enumerator that retains the current position in an enumeration. The method MUST
return WBEM_S_NO_ERROR.
3.1.4.4.5 IEnumWbemClassObject::Skip (Opnum 7)
When the IEnumWbemClassObject::Skip method is invoked, the server MUST move the current
position in an enumeration ahead by a specified number of CIM objects.
The IEnumWbemClassObject::Skip method opnum equals 7.
HRESULT Skip(
[in] long lTimeout,
[in] ULONG nCount
);
96 / 168
[MS-WMI] — v20091104

lTimeout: MUST be the maximum amount of time, in milliseconds, that the call to Skip allows to
pass before it times out. If the constant WBEM_INFINITE (0xFFFFFFFF) is used, the Skip
method call waits until the operation succeeds.
nCount: MUST be the number of CIM objects to skip in the enumeration. If this parameter is
greater than the number of CIM objects that remain to enumerate, the call MUST skip to the
end of the enumeration, and WBEM_S_FALSE MUST be the returned value for the method.
In response to the IEnumWbemClassObject::Skip method, the server MUST evaluate the uCount
and lTimeout parameters as specified in this section. The server MUST skip the requested number of
CIM objects from the result set. The server MUST complete the operation within the time allowed by
lTimeout. The requested number of CIM objects MUST start from the current index position. The
current index position in the enumeration MUST be incremented by the number of CIM objects
skipped.
If the call succeeds, it MUST return WBEM_S_NO_ERROR. If the call gets to the end of the
enumeration and the number of remaining CIM objects is less than the number of requested CIM
objects, the server MUST return WBEM_S_FALSE. If the server is not able to skip the requested
number of CIM objects in the requested amount of time, it MUST return WBEM_S_TIMEDOUT.
3.1.4.5 IWbemCallResult Interface
The IWbemCallResult interface MUST be used to return call results from semisynchronous calls
that return a single CIM object. The interface MUST be implemented by the server. The interface
MUST be uniquely identified by UUID {44aca675-e8fc-11d0-a07c-00c04fb68820}.
Method Description
GetResultObject Causes the server to attempt to retrieve a CIM object from a previous
semisynchronous call to the IWbemServices::GetObject method or
IWbemServices::ExecMethod method.
Opnum: 3
GetResultString Causes the server to return the assigned CIM path of a CIM instance that was created
by the IWbemServices::PutInstance method.
Opnum: 4
GetResultService Causes the server to retrieve a pointer to the IWbemServices interface that results
97 / 168
[MS-WMI] — v20091104

Method Description
from a semisynchronous call to the IWbemServices::OpenNamespace method.

Opnum: 5
GetCallStatus Causes the server to return the status of the current outstanding semisynchronous
call.
Opnum: 6
3.1.4.5.1 IWbemCallResult::GetResultObject (Opnum 3)
When the IWbemCallResult::GetResultObject method is called, the server MUST attempt to

retrieve a CIM object from a previous semisynchronous call to the IWbemServices::GetObject
method or the IWbemServices::ExecMethod method.
HRESULT GetResultObject(
[in] long lTimeout,
[out] IWbemClassObject** ppResultObject
);
lTimeout: MUST be the maximum amount of time, in milliseconds, that the call to the
IWbemCallResult::GetResultObject method allows to pass before it times out. If the
constant WBEM_INFINITE (0xFFFFFFFF) is used, the GetResultObject method call MUST wait
until the operation succeeds. If this parameter is set to 0 and the result object is available at
the time of the method call, the object MUST be returned in ppResultObject and
WBEM_S_NO_ERROR MUST also be returned. If this parameter is set to 0 but the result object
is not available at the time of the method call, WBEM_S_TIMEDOUT MUST be returned.
ppResultObject: MUST be a copy of the CIM object when the semisynchronous operation is
complete. A new CIM object MUST NOT be returned on error. When sent by the client, this
parameter MUST NOT be NULL. Upon return by the server, this parameter can be NULL if
there is a failure or if there are no results.
The IWbemCallResult::GetResultObject method MUST be called on the interface obtained in

responses to a previous call to a semisynchronous operation returning an IWbemCallResult
interface.
In response to the IWbemCallResult::GetResultObject method, the server MUST return the CIM
object in the ppResultObject parameter in the time allowed by the lTimeout parameter. The method
MUST fail if the method parameters are not valid, as specified earlier in this section, or if the server
is unable to execute the method.
The successful method execution MUST fill ppResultObject with an IWbemClassObject interface
pointer and MUST return WBEM_S_NO_ERROR.
The failed method execution sets the value referenced by the output parameters to NULL and MUST
return an error in the format specified in section 2.2.11. In case the operation is not completed after
98 / 168
[MS-WMI] — v20091104

lTimeout milliseconds, the server MUST return WBEM_S_TIMEDOUT and the client MUST retry the
operation.
If the original semisynchronous operation fails, the IWbemCallResult::GetResultObject method

MUST return the error code that the original method would have returned in its synchronous
version.
3.1.4.5.2 IWbemCallResult::GetResultString (Opnum 4)
When the IWbemCallResult::GetResultString method is called, the server MUST return the
assigned CIM path of a CIM instance that was created by the IWbemServices::PutInstance
method that returned IWbemCallResult in the ppCallResult parameter.
HRESULT GetResultString(
[in] long lTimeout,
[out] BSTR* pstrResultString
);
lTimeout: MUST be a maximum amount of time, in milliseconds, that the call to

GetResultString allows to pass before timing out. If the constant WBEM_INFINITE
(0xFFFFFFFF) is used, the GetResultString method call MUST wait until the operation
succeeds. This parameter MUST NOT be NULL.
pstrResultString: MUST be a pointer to a BSTR value, which MUST contain the CIM path of the
CIM object instance, which MUST lead to the CIM instance that was created using
IWbemServices::PutInstance. In case of failure of the semisynchronous operation, the
returned string MUST be NULL. When sent by the client, this pointer parameter MUST NOT be
NULL. If the original operation does not return a string, the returned string MUST be NULL.
The IWbemCallResult::GetResultString method MUST be called on the interface obtained in

responses to a previous call to a semisynchronous operation returning an IWbemCallResult
interface.
IWbemCallResult::GetResultString MUST be called to obtain the CIM path created after the
IWbemServices::PutInstance execution. In response to the
IWbemCallResult::GetResultString method, the server MUST return the string result of the
operation in the pstrResultString parameter. The method MUST fail if the method parameters are
not valid, as specified earlier in this section, or if the server is unable to execute the method.
The successful method execution MUST fill pstrResultString with a string value of type BSTR and
MUST return WBEM_S_NO_ERROR.
The failed method execution sets the value referenced by the output parameters to NULL and MUST
return an error in the format specified in section 2.2.11. In case the operation is not completed after
lTimeout milliseconds, the server MUST return WBEM_S_TIMEDOUT and MUST allow for further
retries to be made.
99 / 168
[MS-WMI] — v20091104

If the original semisynchronous operation fails, the IWbemCallResult::GetResultString method
version.
3.1.4.5.3 IWbemCallResult::GetResultService (Opnum 5)
When the IWbemCallResult::GetResultService method is called, the server MUST retrieve a

pointer to the IWbemServices interface that results from a semisynchronous call to the
IWbemServices::OpenNamespace method.
HRESULT GetResultService(
[in] long lTimeout,
[out] IWbemServices** ppServices
);
lTimeout: MUST be the time, in milliseconds, that the call to GetResultService allows to pass
before timing out. If the constant WBEM_INFINITE (0xFFFFFFFF) is used, the Skip method call
MUST wait until the operation succeeds.
ppServices: MUST be a pointer to the IWbemServices interface that is requested by the

original call to IWbemServices::OpenNamespace when that interface becomes available. If
the semisynchronous operation fails, the returned parameter MUST be NULL. When sent by
the client, this pointer parameter MUST NOT be NULL. If the original operation does not return
an interface pointer, the returned parameter MUST be NULL.
The IWbemCallResult::GetResultService method MUST be called on the interface that is

obtained in response to a previous call to a semisynchronous operation that returns an
IWbemCallResult interface.
IWbemCallResult::GetResultService MUST be called to obtain the IWbemServices interface

pointer that is returned by the IWbemServices::OpenNamespace execution. In response to the
IWbemCallResult::GetResultService method, the server MUST return the IWbemServices
interface pointer result of the operation in the ppServices parameter. The method MUST fail if the
method parameters are not valid, as specified earlier in this section, or if the server is unable to
execute the method.
The successful method execution MUST fill the ppServices parameter with an IWbemServices
interface pointer and MUST return WBEM_S_NO_ERROR.
The failed method execution sets the value that is referenced by the output parameters to NULL and
MUST return an error in the format that is specified in section 2.2.11. If the operation does not
complete within lTimeout milliseconds, the server MUST return WBEM_S_TIMEDOUT and MUST allow
for further retries to be made.
If the original semisynchronous operation fails, the IWbemCallResult::GetResultService method

version.
100 / 168
[MS-WMI] — v20091104

3.1.4.5.4 IWbemCallResult::GetCallStatus (Opnum 6)
When the IWbemCallResult::GetCallStatus method is invoked, the server MUST return the status
of the current outstanding semisynchronous call.
HRESULT GetCallStatus(
[in] long lTimeout,
[out] long* plStatus
);
lTimeout: MUST be the maximum amount of time, in milliseconds, that the call to
GetCallStatus allows to pass before timing out. If the constant WBEM_INFINITE
(0xFFFFFFFF) is used, the Skip method call waits until the operation succeeds.
plStatus: MUST be the status of a call to an IWbemServices method if the

WBEM_S_NO_ERROR code is returned for this method. When sent by the client, this
parameter MUST NOT be NULL. Upon return by the server, this parameter can be NULL if
The IWbemCallResult::GetCallStatus method MUST be called on the interface that is obtained in

response to a previous call to a semisynchronous operation that returns an IWbemCallResult
interface.
In response to an IWbemCallResult::GetCallStatus method, the server MUST return operation

status in the plStatus parameter in the time allowed by the lTimeout parameter. The method MUST
fail if the method parameters are not valid, as specified earlier in this section, or if the server is
unable to execute the method.
The successful method execution MUST fill plStatus with the operation status code of the
IWbemServices method operation and MUST return WBEM_S_NO_ERROR.
The failed method execution sets the value that is referenced by the output parameters to NULL and
MUST return an error in the format that is specified in section 2.2.11.
3.1.4.6 IWbemFetchSmartEnum Interface
The IWbemFetchSmartEnum interface (an [MS-DCOM] interface) is a helper interface used to

retrieve a network-optimized enumerator interface. The server MUST fail the
IRemUnknown::QueryInterface operation if the interface is not implemented by the server.
The IWbemFetchSmartEnum is a DCOM Remote Protocol interface. The interface MUST be

uniquely identified by the UUID {1C1C45EE-4395-11d2-B60B-00104B703EFD}.
Method Description
GetSmartEnum Retrieves an IWbemWCOSmartEnum interface, which is a network-optimized
101 / 168
[MS-WMI] — v20091104

Method Description
enumerator interface.
Opnum: 3
3.1.4.6.1 IWbemFetchSmartEnum::GetSmartEnum (Opnum 3)
The IWbemFetchSmartEnum::GetSmartEnum method retrieves an IWbemWCOSmartEnum

interface, which is a network-optimized enumerator interface.
HRESULT GetSmartEnum(
[out] IWbemWCOSmartEnum** ppSmartEnum
);
ppSmartEnum: MUST be a pointer to a pointer to a network-optimized enumerator interface.

This parameter MUST NOT be NULL. Upon return by the server, this parameter can be NULL if
In response to the IWbemFetchSmartEnum::GetSmartEnum method, the server MUST return an

IWbemWCOSmartEnum (section 3.1.4.7) interface in the ppSmartEnum output parameter.
A successful execution MUST return the IWbemWCOSmartEnum interface in the output parameter
and MUST return WBEM_S_NO_ERROR.
3.1.4.7 IWbemWCOSmartEnum Interface
The server MUST implement the IWbemWCOSmartEnum interface if it implements

IWbemFetchSmartEnum::GetSmartEnum. The IWbemWCOSmartEnum interface is intended
to provide an alternate synchronous enumeration of CIM objects for IEnumWbemClassObject.
The interface MUST be uniquely identified by UUID {423EC01E-2E35-11d2-B604-00104B703EFD}.
Method Description
Next Returns an array of IWbemClassObject interface pointers that are encoded by using the
ObjectArray structure for optimization purposes.
Opnum: 3
102 / 168
[MS-WMI] — v20091104

3.1.4.7.1 IWbemWCOSmartEnum::Next (Opnum 3)
The IWbemWCOSmartEnum::Next method MUST return an array of IWbemClassObject interface

pointers that are encoded by using the ObjectArray structure for optimization purposes. The array of
objects that are returned in the ObjectArray structure MUST be identical to the array of CIM objects
that are returned by IEnumWbemClassObject::Next.
HRESULT Next(
[in] REFGUID proxyGUID,
[in] long lTimeout,
[in] ULONG uCount,
[out] ULONG* puReturned,
[out] ULONG* pdwBuffSize,
[out, size_is(,*pdwBuffSize)] byte** pBuffer
);
proxyGUID: MUST be a client-generated GUID that MUST identify the client. This parameter
MUST NOT be NULL.
lTimeout: MUST be the maximum amount of time, in milliseconds, that the Next method call
allows to pass before it times out. If the constant WBEM_INFINITE (0xFFFFFFFF) is used, the
Skip method call waits until the operation succeeds. This parameter MUST NOT be NULL.
uCount: MUST be the number of requested CIM objects. This parameter MUST NOT be NULL.
puReturned: MUST be a pointer to a ULONG value that MUST contain the number of CIM objects
that are returned by the Next method. This parameter MUST NOT be NULL.
pdwBuffSize: MUST be a pointer to a ULONG value that MUST contain the buffer size, in bytes.
pBuffer: MUST be a pointer to the byte array that MUST represent the packet. This parameter
MUST NOT be NULL. The byte array represents an array of CIM objects that are encoded by
using the ObjectArray format as specified in section 2.2.14. When returned by the server, this
parameter can be NULL if a failure occurs or if there are no results to return.
If a failure occurs, the server MUST return an HRESULT whose S (severity) bit is set as
specified in [MS-ERREF] section 2.1. The actual HRESULT value is implementation dependent.
The IWbemWCOSmartEnum::Next method MUST be called on an IWbemWCOSmartEnum

interface that is returned by a previous call to IWbemFetchSmartEnum::GetSmartEnum.
In response to IWbemWCOSmartEnum::Next, the server MUST evaluate the lTimeout parameter

(as specified in this section) and MUST evaluate the GUID in order to identify the client. The server
MUST return the maximum number of CIM objects that are requested by uCount.
103 / 168
[MS-WMI] — v20091104

If the server is unable to return all the requested CIM objects in the requested amount of time, it
MUST return WBEM_S_TIMEDOUT. The requested number of CIM objects MUST start from the
current index position. The current index position in the enumeration MUST be incremented by the
number of returned CIM objects.
On success, the server MUST return data in the pBuffer by using an ObjectArray structure as
specified in section 2.2.14.
The successful method execution MUST return WBEM_S_NO_ERROR. If the number of remaining
CIM objects to be retrieved is less than the number of requested CIM objects, the server MUST
return WBEM_S_FALSE. Regardless, the server MUST fill the output parameters of the method as
3.1.4.8 IWbemLoginClientID Interface
This interface is not required for the protocol to work.
The interface MUST be uniquely identified by UUID {d4781cd6-e5d3-44df-ad94-930efe48a887}.
Method Description
SetClientInfo Passes the client NETBIOS name and a unique client generated number to the server.
Opnum: 3
3.1.4.8.1 IWbemLoginClientID::SetClientInfo (Opnum 3)
The IWbemLoginClientID::SetClientInfo method MUST pass the client NETBIOS name and a
unique client-generated number to the server.
HRESULT SetClientInfo(
[in, unique, string] LPWSTR wszClientMachine,
[in] long lClientProcId,
[in] long lReserved
);
wszClientMachine: MUST specify the client NETBIOS name. This parameter MUST NOT be
NULL.
lClientProcId: MUST specify a unique client-generated number.
lReserved: This parameter is not used, and its value MUST be NULL.
In case of failure, the server MUST return an HRESULT whose S (severity) bit is set as
104 / 168
[MS-WMI] — v20091104

3.1.4.9 IWbemLoginHelper Interface
The server MUST fail the IRemUnknown::QueryInterface operation if the interface is not
implemented by the server. This interface is not required for the protocol to work.
The interface MUST be uniquely identified by UUID {541679AB-2E5F-11d3-B34E-00104BCC4B4A}.
Method Description
SetEvent Signals an event on the server with name that MUST be specified as a parameter of the
method.
Opnum: 3
3.1.4.9.1 IWbemLoginHelper::SetEvent (Opnum 3)
The IWbemLoginHelper::SetEvent MUST return WBEM_S_NO_ERROR. The SetEvent method

SHOULD NOT perform any action.<19>
The opnum of the SetEvent method equals 3.
HRESULT SetEvent(
[in] LPCSTR sEventToSet
);
sEventToSet: MUST contain the name of the event to be signaled. This parameter MUST NOT be
NULL.
If the method fails, the server MUST return an HRESULT whose S (severity) bit is set as
3.1.4.10 IWbemBackupRestore Interface
The IWbemBackupRestore interface exposes methods that back up and restore the contents of
the CIM database. The interface MUST be implemented by the server to support backup/restore
scenarios. The interface MUST be uniquely identified by UUID {C49E32C7-BC8B-11d2-85D4-
00105A1F8304}.
Method Description
Backup Causes the server to back up the contents of the CIM database.
Opnum: 3
Restore Causes the server to restore the contents of the CIM database.
105 / 168
[MS-WMI] — v20091104

Method Description
Opnum: 4
The object exporting this interface MUST also implement the IWbemBackupRestoreEx interface.
The IRemUnknown and IRemUnknown2 interfaces, as specified in [MS-DCOM], MUST be used to
manage the interfaces exposed by the object. The object MUST be uniquely identified with CLSID
{C49E32C6-BC8B-11D2-85D4-00105A1F8304}.
Figure 7: The IWbemBackupRestore interface
3.1.4.10.1 IWbemBackupRestore::Backup (Opnum 3)
On the IWbemBackupRestore::Backup method invocation, the server MUST back up the contents
of the CIM database.
HRESULT Backup(
[in, string] LPCWSTR strBackupToFile,
[in] long lFlags
);
strBackupToFile: MUST be a UTF-16 string, which MUST contain the name of the file to which
the CIM database is backed up. This parameter MUST NOT<20> be NULL.
lFlags: This parameter is not used, and its value MUST be 0x0.
106 / 168
[MS-WMI] — v20091104

The IWbemBackupRestore::Backup method MUST be called on the interface that is obtained
from the DCOM Remote Protocol activation of a CLSID_WbemBackupRestore interface, as specified
in this section.
In response to the IWbemBackupRestore::Backup method, the server MUST back up the CIM
database in a file that is specified in the strBackupToFile parameter. The server SHOULD<21> verify
that the security principal making the call is allowed to back up the CIM database using
implementation-specific authorization policy. If the security principal is not authorized, the server
MUST return WBEM_E_ACCESS_DENIED.
3.1.4.10.2 IWbemBackupRestore::Restore (Opnum 4)
On the IWbemBackupRestore::Restore method invocation, the server MUST restore the contents
of the CIM database.
HRESULT Restore(
[in, string] LPCWSTR strRestoreFromFile,
[in] long lFlags
);
strRestoreFromFile: MUST be a UTF-16 string that MUST contain the name of the file from
which to restore the CIM database. This parameter MUST NOT<22> be NULL.
lFlags: Flags that affect the behavior of the Restore method. The flags' behavior MUST be
Value Meaning
WBEM_FLAG_BACKUP_RESTORE_FORCE_SHUTDOWN If the bit is not set and if there are any

0x00000001 active clients, the server MUST NOT
perform the restore.
If the bit is set, the server MUST shut
down any active clients before performing
the restore operation.
In response to the IWbemBackupRestore::Restore method, the server MUST restore the CIM
database from the file that is specified in the strRestoreFromFile parameter. The server
SHOULD<23> verify that the security principal making the call is allowed to restore the CIM
database using implementation-specific authorization policy. If the security principal is not
authorized, the server MUST return WBEM_E_ACCESS_DENIED.
3.1.4.11 IWbemBackupRestoreEx Interface
The IWbemBackupRestoreEx interface extends the IWbemBackupRestore interface and <24>

exposes methods that pause and resume the activity in the Windows Management Instrumentation
107 / 168
[MS-WMI] — v20091104

Remote Protocol. These methods are used to provide an alternative solution for backing up the
contents of the CIM database. The interface MUST be implemented in order to support
backup/restore scenarios without stopping the server.
The IWbemBackupRestoreEx interface is a DCOM Remote Protocol interface (as specified in [MS-
DCOM]). The interface MUST be uniquely identified by UUID {A359DEC5-E813-4834-8A2A-
BA7F1D777D76}.
Method Description
Pause Causes the server to lock the CIM database in a consistent state while it is copied.
Opnum: 5
Resume Causes the server to unlock the CIM database and resume operations.
Opnum: 6
3.1.4.11.1 IWbemBackupRestoreEx::Pause (Opnum 5)
On the IWbemBackupRestoreEx::Pause method invocation, the server MUST flush the CIM
database in a consistent state and MUST block all the write operations to the CIM database until
IWbemBackupRestoreEx::Resume is called.
HRESULT Pause();
The IWbemBackupRestoreEx::Pause method MUST be called on the interface that is obtained

from the DCOM Remote Protocol activation of the CLSID_WbemBackupRestore interface, as
specified in this section.
In response to the IWbemBackupRestoreEx::Pause method, the server MUST lock the CIM
database until the IWbemBackupRestoreEx::Resume MUST be called or the backup timer (see
section 3.1.5) expires.
3.1.4.11.2 IWbemBackupRestoreEx::Resume (Opnum 6)
On the IWbemBackupRestoreEx::Resume method invocation, the server MUST unlock the CIM
database and resume operations.
HRESULT Resume();
108 / 168
[MS-WMI] — v20091104

the method call. The server MUST return a WBEM_S_NO_ERROR (specified in section 2.2.11)
3.1.4.12 IWbemRefreshingServices Interface
The IWbemRefreshingServices interface MUST be implemented by the server. This interface (an
[MS-DCOM] interface)<25> provides methods that allow clients to get updates of numerous objects
in a single DCOM Remote Protocol method invocation; whereas the IWbemServices interface
provides methods that allow clients to get updates on a class or an instance.
The IWbemRefreshingServices interface requires multiple calls to set up the remote refresher;
however, after the remote refresher is set up, obtaining updates requires only a single call. The
IWbemRefreshingServices interface provides a faster CIM instance refreshing service when
updated data on CIM instances have to be retrieved multiple times.
This interface MUST be uniquely identified by UUID {2C9273E0-1DC3-11d3-B364-00105A1F8177}.
Method Description
AddObjectToRefresher Adds a CIM instance to the list of CIM objects to be refreshed.

Opnum: 3
AddObjectToRefresherByTemplate Adds a CIM instance that is identified by its CIM object instance, to
the list of CIM objects to be refreshed.
Opnum: 4
AddEnumToRefresher Adds all CIM instances of the CIM class name to the list of CIM
objects to be refreshed.
Opnum: 5
RemoveObjectFromRefresher Removes a CIM instance from the list of CIM instances to be

refreshed.
Opnum: 6
GetRemoteRefresher Retrieves an IWbemRemoteRefresherinterface pointer.

Opnum: 7
ReconnectRemoteRefresher Restores a set of CIM instances and enumerations to a server

refresher.
Opnum: 8
109 / 168
[MS-WMI] — v20091104

3.1.4.12.1 IWbemRefreshingServices::AddObjectToRefresher (Opnum 3)
The IWbemRefreshingServices::AddObjectToRefresher method MUST add a CIM instance,

which is identified by its CIM path, to the list of CIM instances that can be refreshed.
HRESULT AddObjectToRefresher(
[in] _WBEM_REFRESHER_ID* pRefresherId,
[in, string] LPCWSTR wszPath,
[in] long lFlags,
[in] IWbemContext* pContext,
[in] DWORD dwClientRefrVersion,
[out] _WBEM_REFRESH_INFO* pInfo,
[out] DWORD* pdwSvrRefrVersion
);
pRefresherId: MUST be a pointer to the _WBEM_REFRESHER_ID structure, as specified in

section 2.2.21, which identifies the client that is requesting refreshing services. This
wszPath: MUST be a string that MUST contain the CIM path of the CIM instance. This parameter
MUST NOT be NULL.
lFlags: This parameter is not used, and its value SHOULD be 0x0.
pContext: MUST be a pointer to an IWbemContext interface object, which MUST contain

additional information for the server refresher. If pContext is NULL, the parameter MUST be
ignored.
dwClientRefrVersion: MUST be the version of the client refresher. This value SHOULD be
0x2.<26> The server MUST allow all client versions.
pInfo: MUST be an output parameter that MUST return a _WBEM_REFRESH_INFO structure, as

specified in section 2.2.20, which MUST contain refresher information about the CIM instance
in wszPath. It MUST NOT be NULL.
pdwSvrRefrVersion: MUST be an output parameter that MUST be the version of the server
refresher. The value of this parameter SHOULD be 0x1.
In response to IWbemRefreshingServices::AddObjectToRefresher, the server MUST evaluate

the CIM path to the CIM instance and MUST return information to the client to handle the specific
CIM instance as specified in this section.
A successful call to IWbemRefreshingServices::AddObjectToRefresher MUST return

WBEM_S_NO_ERROR and MUST fill the output _WBEM_REFRESH_INFO structure as specified in
section 2.2.20.
110 / 168
[MS-WMI] — v20091104

The server MUST return the _WBEM_REFRESH_INFO structure that has an m_lType that is set to
either _WBEM_REFRESH_INFO_REMOTE or _WBEM_REFRESH_TYPE_NON_HIPERF,
depending on implementation-specific criteria.
If the server sets m_lType to _WBEM_REFRESH_INFO_REMOTE, the server MUST return an

IWbemRemoteRefresher interface pointer in _WBEM_REFRESH_INFO_REMOTE that is part of
_WBEM_REFRESH_INFO.
If the server sets m_lType to _WBEM_REFRESH_TYPE_NON_HIPERF, the server MUST return a

_WBEM_REFRESH_TYPE_NON_HIPERF structure as part of _WBEM_REFRESH_INFO.
In case of failure, the server MUST fill in the _WBEM_REFRESH_INFO structure with 0x0, set its
m_lType member to WBEM_REFRESH_TYPE_INVALID, and return an HRESULT error in the format
that is specified in section 2.2.11.
3.1.4.12.2 IWbemRefreshingServices::AddObjectToRefresherByTemplate (Opnum

4)
The IWbemRefreshingServices::AddObjectToRefresherByTemplate method MUST add a CIM

instance, which is identified by its CIM object instance, to the list of CIM instances to be refreshed.
The AddObjectToRefresherByTemplate method opnum equals 4.
HRESULT AddObjectToRefresherByTemplate(
[in] IWbemClassObject* pTemplate,
[in] long lFlags,
);

pTemplate: MUST be a pointer to an IWbemClassObject interface CIM instance that MUST be

a template for the CIM instances to be refreshed by the refresher. This parameter MUST NOT
be NULL.

additional information for the server refresher. If pContext is NULL, the parameter MUST be
ignored.
pInfo: MUST be an output parameter that returns a _WBEM_REFRESH_INFO structure, as

in wszPath. This parameter MUST NOT be NULL.
111 / 168
[MS-WMI] — v20091104

In response to IWbemRefreshingServices::AddObjectToRefresherByTemplate, the server

MUST evaluate the pTemplate parameter that defines the CIM instance, and it MUST return
information to the client to handle the specific CIM instance as specified in this section.
A successful call to IWbemRefreshingServices::AddObjectToRefresherByTemplate MUST

return WBEM_S_NO_ERROR and MUST fill the output _WBEM_REFRESH_INFO structure, as specified
in this section.

_WBEM_REFRESH_INFO.
If the server sets m_lType to _WBEM_REFRESH_TYPE_NON_HIPERF, the server MUST return

the _WBEM_REFRESH_TYPE_NON_HIPERF structure as part of _WBEM_REFRESH_INFO.
In case of failure, the server MUST fill in the _WBEM_REFRESH_INFO parameter with 0x0, set its
m_lType member to WBEM_REFRESH_TYPE_INVALID, and return an error in the format that is
3.1.4.12.3 IWbemRefreshingServices::AddEnumToRefresher (Opnum 5)
The IWbemRefreshingServices::AddEnumToRefresher method MUST add all CIM instances that

are identified by the CIM class name to the list of CIM instances to be refreshed.
HRESULT AddEnumToRefresher(
[in, string] LPCWSTR wszClass,
[in] long lFlags,
);

wszClass: MUST be a string that MUST contain the enumeration CIM class name. This parameter
MUST NOT be NULL.
112 / 168
[MS-WMI] — v20091104

additional information for the server refresher. If pContext is NULL, the parameter is ignored.
pInfo: MUST be an output parameter that returns a _WBEM_REFRESH_INFO structure, as

in wszPath. This parameter MUST NOT be NULL.
pdwSvrRefrVersion: MUST be an output parameter, which MUST be the version of the server
In response to IWbemRefreshingServices::AddEnumToRefresher, the server MUST evaluate

the wszClass parameter, and it MUST return information to the client so that the server knows how
to handle the specific class as specified in this section.
This method MUST add all instances of a class, instead of a single instance of a class, as is the case
for the IWbemRefreshingServices::AddObjectToRefresher and
IWbemRefreshingServices::AddObjectToRefresherByTemplate methods.
A successful call to IWbemRefreshingServices::AddEnumToRefresher MUST return

WBEM_S_NO_ERROR and MUST fill the output _WBEM_REFRESH_INFO structure as specified in
section 2.2.20.

_WBEM_REFRESH_INFO.
If the server sets m_lType to _WBEM_REFRESH_TYPE_NON_HIPERF, the server MUST return

the _WBEM_REFRESH_TYPE_NON_HIPERF structure as part of _WBEM_REFRESH_INFO.
In case of failure, the server MUST fill in the _WBEM_REFRESH_INFO structure with 0x0, set
m_lType to WBEM_REFRESH_TYPE_INVALID, and return an error in the format that is specified in
section 2.2.11.
3.1.4.12.4 IWbemRefreshingServices::RemoveObjectFromRefresher (Opnum 6)
The IWbemRefreshingServices::RemoveObjectFromRefresher method MUST remove a CIM

instance, which is identified by its CIM path, from the list of CIM instances that can be refreshed.
HRESULT RemoveObjectFromRefresher(
113 / 168
[MS-WMI] — v20091104

[in] long lId,
[in] long lFlags,
);

section 2.2.21, that identifies the client that is requesting refreshing services. This parameter
MUST NOT be NULL.
lId: This parameter MUST be an identifier to the object that is being removed. This parameter
MUST NOT be NULL.
pdwSvrRefrVersion: MUST be an output parameter, which MUST be the version of the server
refresher. This value SHOULD be 0x1.
the method call. If there are no failures, the server MUST always return
WBEM_E_NOT_AVAILABLE.<30>
WBEM_E_NOT_AVAILABLE (0x80041009)
In response to IWbemRefreshingServices::RemoveObjectFromRefresher, the server MUST set

pdwSvrRefrVersion to 0x1 and return WBEM_E_NOT_AVAILABLE.
In case of failure, the server MUST set pdwSvrRefrVersion to 1 and MUST return an error in the
3.1.4.12.5 IWbemRefreshingServices::GetRemoteRefresher (Opnum 7)
The IWbemRefreshingServices::GetRemoteRefresher method MUST return an

IWbemRemoteRefresher interface pointer. This pointer is needed by the client to refresh objects
and enumerations.
HRESULT GetRemoteRefresher(
[in] long lFlags,
[out] IWbemRemoteRefresher** ppRemRefresher,
[out] GUID* pGuid,
);

section 2.2.21, that identifies the client that is requesting refreshing services. This parameter
MUST NOT be NULL.
114 / 168
[MS-WMI] — v20091104

ppRemRefresher: MUST be a pointer to an IWbemRemoteRefresher interface pointer that

the client can use to call the IWbemRemoteRefresher::RemoteRefresh method to refresh
CIM instances and enumerations. This parameter MUST NOT be NULL.
pGuid: MUST be an output parameter that MUST be a pointer to a GUID value that MUST identify
the returned refresher object. This parameter MUST NOT be NULL.
The IWbemRefreshingServices::GetRemoteRefresher method evaluates the pRefresherID

parameter and MUST return an IWbemRemoteRefresher interface pointer and a GUID that is
randomly generated by the server in order to identify this interface pointer. The
IWbemRefreshingServices interface pointer MUST have the same value as the one initially
returned by the IWbemRefreshingServices::AddObjectToRefresher,
IWbemRefreshingServices::AddObjectToRefresherByTemplate, or
IWbemRefreshingServices::AddEnumToRefresher method.
A successful call to IWbemRefreshingServices::GetRemoteRefresher MUST return

WBEM_S_NO_ERROR and fill the ppRemRefresher and pGuid fields. The pdwSvrRefrVersion field is
reserved for future use and MUST be set to 0x1.
The returned IWbemRemoteRefresher interface MUST be used in calls to the

IWbemRemoteRefresher::RemoteRefresh and IWbemRemoteRefresher::StopRefreshing
methods.
3.1.4.12.6 IWbemRefreshingServices::ReconnectRemoteRefresher (Opnum 8)
The IWbemRefreshingServices::ReconnectRemoteRefresher method MUST restore a set of

CIM instances and enumerations that are passed in apReconnectInfo to a refresher.
HRESULT ReconnectRemoteRefresher(
[in] long lFlags,
[in] long lNumObjects,
[in, size_is(lNumObjects)] _WBEM_RECONNECT_INFO* apReconnectInfo,
[in, out, size_is(lNumObjects)]
_WBEM_RECONNECT_RESULTS* apReconnectResults,
115 / 168
[MS-WMI] — v20091104

);

section 2.2.21, which identifies the client that is requesting refresh services. This parameter
MUST NOT be NULL.
lNumObjects: MUST be the number of CIM instances that are contained in the apReconnectInfo
array.
apReconnectInfo: MUST be a pointer to the _WBEM_RECONNECT_INFO structure array

(specified in section 2.2.22) that contains a type and a CIM path to the refresher objects. This
apReconnectResults: MUST be a pointer to the _WBEM_RECONNECT_RESULTS structure array,

which MUST contain the identifier for each CIM instance and enumeration, and the success or
failure status of the reconnection. This parameter MUST NOT be NULL.
pdwSvrRefrVersion: MUST be an output parameter that is the version of the server refresher.
This value SHOULD be 0x1.
the method call. The server MUST return WBEM_S_NO_ERROR, which is specified in section
2.2.11, to indicate the successful completion of the method.
The description of IWbemRefreshingServices is specified in IWbemRefreshingServices

Interface.
In response to IWbemRefreshingServices::ReconnectRemoteRefresher, the server MUST

evaluate the pRefresherId and apReconnectInfo arrays; and MUST reconnect to the refresher the
requested CIM objects and enumerators that are listed in apReconnectInfo, as specified in this
section.
If one of the CIM objects cannot be reconnected, the apReconnectResults element that corresponds
to apReconnectInfo MUST be set with an HRESULT return code.
A successful call to IWbemRefreshingServices::ReconnectRemoteRefresher MUST return

WBEM_S_NO_ERROR and MUST fill the reconnection status in the apReconnectResults array.
In case of failure, the server MUST return an HRESULT value that indicates the status of the method
call.
Each array element MUST contain a refresher CIM object identifier (the m_lId member of
_WBEM_RECONNECT_RESULTS) that can be used to cancel the object. The m_lId member MUST be
116 / 168
[MS-WMI] — v20091104

a unique identifier for the refresher object that is used to cancel the refreshing object when the
refresher object is using IWbemRemoteRefresher::StopRefresher.
3.1.4.13 IWbemRemoteRefresher Interface
The IWbemRemoteRefresher interface (an [MS-DCOM] interface) MUST be implemented by the

server. The interface MUST be uniquely identified by UUID {F1E9C5B2-F59B-11d2-B362-
00105A1F8177}.<33>
Method Description
RemoteRefresh Retrieves the updated set of CIM instances and enumerations configured by
an IWbemRefreshingServices interface pointer.
Opnum: 3
StopRefreshing Removes a set of CIM instance and enumerations configured by

IWbemRefreshingServices interface pointer.
Opnum: 4
Opnum5NotUsedOnWire This method is reserved for local use and is not used remotely.
Opnum: 5
3.1.4.13.1 IWbemRemoteRefresher::RemoteRefresh (Opnum 3)
The IWbemRemoteRefresher::RemoteRefresh method MUST return the updated collection of

CIM instances and enumerations previously configured by the IWbemRefreshingServices
interface pointer.
HRESULT RemoteRefresh(
[in] long lFlags,
[out] long* plNumObjects,
[out, size_is(,*plNumObjects)]
WBEM_REFRESHED_OBJECT** paObjects
);
plNumObjects: If successful, plNumObjects MUST be a pointer to the number of CIM instances

and enumerations that the method returns. It MUST NOT be NULL.
If the method fails, the server MUST set plNumObjects to NULL.
paObjects: If successful, paObjects MUST be a pointer to an array of

WBEM_REFRESHED_OBJECT objects specified in section 2.2.15. The array MUST contain CIM
instances and enumerations. It MUST NOT be NULL.
If the method fails, the server MUST set paObjects to NULL.
the method call.
The server MUST return WBEM_S_NO_ERROR (specified in section 2.2.11) to indicate the
117 / 168
[MS-WMI] — v20091104

The IWbemRemoteRefresher::RemoteRefresh method MUST be called on the

IWbemRemoteRefresher interface pointer returned as a member of the _WBEM_REFRESH_INFO
structure from IWbemRefreshingServices methods or on the interface returned by
IWbemRefreshingServices::GetRemoteRefresher method invocation.
In response to IWbemRemoteRefresher::RemoteRefresh method, the server MUST read the

current values of all the CIM objects previously added to the set of refreshing objects using
IWbemRefreshingServices methods. The updated values for all CIM objects MUST be encoded
into the output parameter using the format specified in this section.
3.1.4.13.2 IWbemRemoteRefresher::StopRefreshing (Opnum 4)
The IWbemRemoteRefresher::StopRefreshing method MUST remove a set of CIM instances or

enumerations from the collection previously configured by the IWbemRefreshingServices
interface pointer.
HRESULT StopRefreshing(
[in] long lNumIds,
[in, size_is(lNumIds)] long* aplIds,
[in] long lFlags
);
lNumIds: MUST be the number of identifiers in the array of object identifiers in the aplIds
parameter.
aplIds: MUST be an array of object identifiers that MUST identify the CIM instances and
enumerations to stop refreshing. The object identifier is the m_lCancelId member from the
_WBEM_REFRESH_INFO structure that is specified in section 2.2.20 and MUST be obtained
from a previous call to the IWbemRefreshingServices::AddObjectToRefresher,
IWbemRefreshingServices::AddEnumToRefresher method specified in section 3.1.4.12.
the method call. In case of success, the server MUST return WBEM_S_NO_ERROR (as
specified in section 2.2.11) to indicate the successful completion of the method.
The IWbemRemoteRefresher::StopRefreshing method MUST be called on the

IWbemRemoteRefresher interface pointer that is returned as a member of the
_WBEM_REFRESH_INFO structure from the methods of the IWbemRefreshingServices interface
or on the interface that is returned by the IWbemRefreshingServices::GetRemoteRefresher
method invocation.
In response to the IWbemRemoteRefresher::StopRefreshing method, the server MUST remove

a list of CIM objects that were previously added to the set of refreshing objects using the
IWbemRefreshingServices methods. The CIM objects MUST be identified by their identifier, the
m_lCancelId member of the _WBEM_REFRESH_INFO structure that is returned by a previous
IWbemRefreshingServices::AddObjectToRefresher,
118 / 168
[MS-WMI] — v20091104

IWbemRefreshingServices::AddEnumToRefresher call.
In case of failure the server MUST return an error in the format specified in section 2.2.11.
3.1.4.13.3 IWbemRemoteRefresher::Opnum5NotUsedOnWire (Opnum 5)
The IWbemRemoteRefresher::Opnum5NotUsedOnWire method MUST return a random GUID

that identifies the server object that receives the call.
HRESULT Opnum5NotUsedOnWire(
[in] long lFlags,
[out] GUID* pGuid
);
pGuid: MUST be an output parameter, which MUST be a pointer to a GUID value that MUST
identify the server object. This parameter MUST NOT be NULL.<34>
3.1.5 Timer Events
The Windows Management Instrumentation Remote Protocol uses two timers:
Sink timer: If the timer expires and the call is not completed, the server MUST cancel the
asynchronous operation for which the timer expired.
Backup Timer: If the timer expires, the server MUST resume operations by simulating
IWbemBackupRestoreEx::Resume and MUST reset the timer to 0.
3.1.6 Other Local Events
None.
3.2 Client Details
3.2.1 Abstract Data Model
The client MUST maintain association between _WBEM_REFRESHER_ID and the objects refreshed in
respective ID by the server. This information MUST be passed to the server when reconnecting the
refresher.
3.2.2 Timers
None
119 / 168
[MS-WMI] — v20091104

3.2.3 Initialization
The client MUST activate the IWbemLevel1Login interface on the machine that is running the
target WMI server by using the CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}, as specified
in the DCOM Remote Protocol. The client SHOULD obtain the IWbemLoginClientID interface by
using the IRemUnknown and IRemUnknown2 interfaces, MS-DCOM, on the
IWbemLevel1Login interface. If the server returns an error for the IWbemLoginClientID
interface, the client MUST ignore the error. If the server returns the IWbemLoginClientID
interface, the client SHOULD call the IWbemLoginClientID::SetClientInfo method to set the
client information on the server.
The client SHOULD NOT obtain the IWbemLoginHelper interface from IWbemLevel1Login by
calling the IRemUnknown and IRemUnknown2 interfaces.<35>
The client MUST call the IWbemLevel1Login::NTLMLogin method. If the

IWbemLevel1Login::NTLMLogin method completes successfully, the ppNamespace parameter
has an IWbemServices interface pointer that can be used by the client to call the
IWbemServices methods.
If the client has multiple preferred locales or any locale string that does not match the "MS_xxx"
format as the pszPreferredLocale parameter to IWbemLevel1Login::NTLMLogin, the client MUST
determine whether the server supports the locale and filter out unsupported locales before calling
IWbemLevel1Login::NTLMLogin. To determine supported locales, the client MUST call
IWbemLevel1Login::EstablishPosition. If the return value is E_NOTIMPL, the client MUST
choose the first locale that matches the "MS_xxx" format and MUST remove other locales from the
string.
If the return value from IWbemLevel1Login::EstablishPosition is WBEM_S_NO_ERROR and

LocaleVersion is set to 0, the client MUST filter out locale lists that are not supported in the
Windows Vista® operating system, as specified in [MS-LCID]. If the locale list is empty after
unsupported locales are filtered out, the client MUST pass NULL for pszPreferredLocale.
3.2.4 Message Processing Events and Sequencing Rules
If the client detects that the IWbemClassObject that is returned by the WMI server does not
conform to [MS-WMIO] encoding, as specified in section 2.2.4, the results MUST be ignored and the
requested operation MUST be considered as failed.
3.2.4.1 IWbemObjectSink Interface Client Details
The IWbemObjectSink interface is implemented by the WMI client if the WMI client uses
asynchronous method calls as specified in section 3.2.4.2.7. In this case, the WMI client acts as an
IWbemObjectSink server. The WMI server acts as an IWbemObjectSink client. The WMI server
MUST invoke the IWbemObjectSink methods to deliver the results (IWbemClassObjects, if any, and
the status code) of the IWbemServices method for which this IWbemObjectSink is passed as a
response handler, as specified in section 3.1.1.1.3.
Because this interface is implemented by the WMI client and the WMI server and invoked by both,
the server in this section refers to the implementer of this interface, and client refers to the invoker
in a specific scenario.
The IWbemObjectSink interface is implemented by the WMI server and returned to the WMI client in
a ppResponseHandler parameter, if the WMI client calls the IWbemServices::QueryObjectSink
method. In this case, the WMI server acts as an IWbemObjectSink server. The WMI client acts as an
IWbemObjectSink client. The WMI client MUST invoke IWbemObjectSink methods to deliver the
120 / 168
[MS-WMI] — v20091104

results, that is, IWbemClassObjects that represent the extrinsic event the client wants to deliver to
the server.
Method Description
Indicate Called by the client to return additional results.

Opnum: 3
SetStatus Called by the client either to indicate the end of an operation or to send status information to
the server.
Opnum: 4
3.2.4.1.1 IWbemObjectSink::Indicate Client Details
If there are no IWbemClassObject results to be reported, the client MUST NOT call the
IWbemObjectSink::Indicate method.
Otherwise, the client MUST call the IWbemObjectSink::Indicate method one or more times until
the entire IWbemClassObject results are delivered to the server. Each time the
IWbemObjectSink::Indicate method is called, a subset of the result is delivered to the server. For
a specific set of result objects, the client uses implementation-specific criteria to choose the number
and timing of the IWbemObjectSink::Indicate method calls that are used to deliver the result
objects.<36>
Clients that implement the ObjectArray structure MUST call IWbemObjectSink::Indicate by using
DCOM Remote Protocol marshaling for the first time. If a server returns WBEM_S_NEW_STYLE, the
client SHOULD send the remainder of the results by using the ObjectArray structure as specified in
section 2.2.14. If the server does not return WBEM_S_NEW_STYLE, the client MUST send the
remainder of the results in the IWbemObjectSink::Indicate call by using DCOM Remote Protocol
marshaling and MUST NOT use the ObjectArray structure.
3.2.4.1.2 IWbemObjectSink::SetStatus Client Details
The client MUST call the IWbemObjectSink::SetStatus method operation to send the final status
of the IWbemServices method operation by passing WBEM_STATUS_COMPLETE as an lFlags
parameter and the operation return code as an HRESULT parameter. After calling
IWbemObjectSink::SetStatus with final status information, the client MUST release the
IWbemObjectSink interface and MUST NOT call any other methods of IWbemObjectSink.
When the reported operation status is success, the client MUST set the pObjParam parameter to
NULL.
The client MAY call IWbemObjectSink::SetStatus multiple times during the operation execution to
report the operation progress.<37> In this case, lFlags MUST be set to WBEM_STATUS_PROGRESS
and the hResult parameter MUST contain the progress information.
When sending operation progress information, the client MAY call IWbemObjectSink::SetStatus
any time before final status is sent.
3.2.4.2 IWbemServices Interface Client Details
3.2.4.2.1 Sending Events to Server
If the client wants to send the events to the WMI server, the client MUST call the
IWbemServices::QueryObjectSink method on the IWbemObjectSink interface that is obtained
121 / 168
[MS-WMI] — v20091104

as specified in section 3.2.3. When the method execution succeeds, the client gets the
IWbemObjectSink interface. The extrinsic events, represented as IWbemClassObject Prototype
Result Object, as specified in 2.2.4.1, MUST be delivered to the server by calling
IWbemObjectSink::Indicate.When the client completes delivering the extrinsic events, the client
MUST release the IWbemObjectSink.
3.2.4.2.2 Calling Put Interfaces for CIM Objects with Amended Qualifiers
If the client calls the PutClass, PutClassAsync, PutInstance, or PutInstanceAsync method to

update or create a CIM Object that contains amended qualifiers, the client SHOULD set the
WBEM_FLAG_USE_AMENDED_QUALIFIERS flag.
3.2.4.2.3 Invoking Synchronous Methods Returing No Object
If the client wants to invoke following WMI methods synchronously, the client MUST NOT set
WBEM_FLAG_RETURN_IMMEDIATELY when making method calls. When the method completes, the
result of the operation is returned as return value. List of methods returning no objects in
synchronous mode are
IWbemServices::PutInstance
IWbemServices::PutClass
IWbemServices::DeleteClass
IWbemServices::DeleteInstance
3.2.4.2.4 Invoking Synchronous Methods Returning Single Object
If the client wants to invoke any of the following WMI methods synchronously, the client MUST NOT
set WBEM_FLAG_RETURN_IMMEDIATELY when making method calls. When the method completes
successfully, the output parameter contains the result object of the operation. The following table
lists the methods and output parameter containing the result object of the operation.
S.No Methode name Output Parameter contatining result object
1 IWbemServices::OpenNamespace ppWorkingNamespace
2 IWbemServices::GetObject ppObject
3 IWbemServices::ExecMethod ppOutParams
When the call to the method fails, the output parameter will be NULL.
3.2.4.2.5 Invoking Semi-Synchronous Methods That Return a Single Object
If the client wants to invoke any of the following WMI methods semi-synchronously, the client MUST
set WBEM_FLAG_RETURN_IMMEDIATELY when it makes the method calls.
When the method returns success, the IWbemCallResult parameter MUST be used to get the
result of the actual semi-synchronous operation. The client MUST call the methods of
IWbemCallResult, as specified in the following table, to obtain the results of the semi-synchronous
operation that is initiated by the client. The client MUST NOT call other methods of
IWbemCallResult except as specified in the following table.
122 / 168
[MS-WMI] — v20091104

Method Rule
IWbemServices::OpenNamespace The IWbemCallResult::GetResultService method MUST be

called to retrieve the IWbemServices pointer.
IWbemServices::PutInstance The IWbemCallResult::GetResultString method MUST be

called to obtain the CIM path that was assigned to the CIM
instance.
IWbemServices::GetObject The IWbemCallResult::GetResultObject method MUST be

called to retrieve the CIM object.
IWbemServices::PutClass The IWbemCallResult::GetCallStatus method MUST be called

IWbemServices::DeleteClass to return the call status.
IWbemServices::DeleteInstance
IWbemServices::ExecMethod The IWbemCallResult::GetResultObject method MUST be

called to retrieve the output parameters.
When the semisynchronous IWbemServices method fails, the output parameter does not have the
IWbemCallResult interface.
3.2.4.2.6 Invoking Synchronous and Semi-Synchronous Operations Returning

Multiple Objects
If the client wants to invoke any of the following WMI methods semi-synchronously, the client MUST
set WBEM_FLAG_RETURN_IMMEDIATELY when making method. If the client wants to invoke any of
the following methods synchronously, the client MUST NOT set WBEM_FLAG_RETURN_IMMEDIATELY
when making IWbemServices method calls.
List of methods returning multiple objects are:
IWbemServices::ExecQuery
IWbemServices::CreateInstanceEnum
IWbemServices::CreateClassEnum
IWbemServices::ExecNotificationQuery
When the method execution failed as indicated by return value, the output parameter will not have
IEnumWbemClassObject.
When IWbemServices method execution succeeds, an object of type IEnumWbemClassObject is

returned to the client.
The client SHOULD obtain IWbemFetchSmartEnum interface using IRemUnknown and

IRemUnknown2 interfaces as specified in [MS-DCOM], on this IEnumWbemClassObject interface.
If client obtains IWbemFetchSmartEnum, the client MUST call
IWbemFetchSmartEnum::GetSmartEnum to obtain IWbemWCOSmartEnum. The client SHOULD call
IWbemWCOSmartEnum::Next method repeatedly to retrieve the objects. When
IWbemWCOSmartEnum::Next returns WBEM_S_NO_ERROR or WBEM_S_TIMEDOUT, the client
SHOULD call IEnumWbemClassObject::Next again. If IWbemWCOSmartEnum::Next returns
an error as specified in 2.2.11 or returns WBEM_S_FALSE, the client MUST NOT call
IWbemWCOSmartEnum::Next again.
123 / 168
[MS-WMI] — v20091104

If the server returns error while obtaining IWbemFetchSmartEnum, the client MUST ignore the error
and SHOULD call IEnumWbemClassObject::Next method repeatedly to retrieve the objects.
When IEnumWbemClassObject::Next returns WBEM_S_NO_ERROR or WBEM_S_TIMEDOUT, the
client SHOULD call IEnumWbemClassObject::Next again. If IEnumWbemClassObject::Next
returns an error as specified in 2.2.11 or returns WBEM_S_FALSE, the client MUST NOT call
IEnumWbemClassObject::Next again.
When the client made a semi-synchronous call and subsequent IEnumWbemClassObject::Next or

IWbemWCOSmartEnum::Next call returns an error, the client MUST interpret the error as the
error of actual semi-synchronous operation as though the operation is executed synchronously.
The client MUST NOT call IEnumWbemClassObject::Reset or IEnumWbemClassObject::Clone,

if the IWbemServices method that created the IEnumWbemClassObject is passed
WBEM_FLAG_FORWARD_ONLY flag.
If the client wants to start the enumerator from the first object, the client MUST call
IEnumWbemClassObject::Reset, if the IWbemServices method that created the
IEnumWbemClassObject is not passed WBEM_FLAG_FORWARD_ONLY flag.
If the client wants to create a new enumerator containing the same result set, the client MUST call
IEnumWbemClassObject::Clone, if the IWbemServices method that created the
IEnumWbemClassObject is not passed WBEM_FLAG_FORWARD_ONLY flag. The client SHOULD
use IEnumWbemClassObject created using IEnumWbemClassObject::Clone as another result
object by calling IEnumWbemClassObject::Next.
If the client wants to get some results of the operation asynchronously, the client MUST call
IEnumWbemClassObject::NextAsync with the uCount, in this case next uCount result objects
are returned in IWbemObjectSink passed as a parameter to
IEnumWbemClassObject::NextAsync.
3.2.4.2.7 Invoking Asynchronous operations
List of methods providing asynchronous behaviors are:
IWbemServices::GetObjectAsync (section 3.1.4.3.5)
IWbemServices::PutClassAsync (section 3.1.4.3.7)
IWbemServices::DeleteClassAsync (section 3.1.4.3.9)
IWbemServices::CreateClassEnumAsync (section 3.1.4.3.11)
IWbemServices::PutInstanceAsync (section 3.1.4.3.13)
IWbemServices::DeleteInstanceAsync (section 3.1.4.3.15)
IWbemServices::CreateInstanceEnumAsync (section 3.1.4.3.17)
IWbemServices::ExecQueryAsync (section 3.1.4.3.19)
IWbemServices::ExecNotificationQueryAsync (section 3.1.4.3.21)
IWbemServices::ExecMethodAsync (section 3.1.4.3.23)
If the client wants to invoke any of the above asynchronous methods, the client MUST pass an
object implementing IWbemObjectSink interface to the above method calls as a response handler.
124 / 168
[MS-WMI] — v20091104

When the method invocation succeeds, the client SHOULD wait for the result of the operation to be
returned to the client using IWbemObjectSink::Indicate and IWbemObjectSink::SetStatus on
the IWbemObjectSink passed to the asynchronous method.
When the IWbemServices method invocation fails, the result of the operation is returned as a
return value of the method.
After the IWbemServices asynchronous method invocation succeeds, if the client wants to cancel
the pending asynchronous operation the client MUST call IWbemServices::CancelAsyncCall
method. If the client calls IWbemServices::CancelAsyncCall, the client MUST pass the
IWbemObjectSink passed to the asynchronous IWbemServices method that is still pending.
3.2.4.3 IWbemBackupRestore Interface Client Details
If client wants to invoke methods of IWbemBackupRestore interface, the client MUST activate
IWbemBackupRestore interface on the target WMI server machine using CLSID {C49E32C6-
BC8B-11D2-85D4-00105A1F8304} as specified in DCOM remote protocol.
3.2.4.4 IWbemBackupRestoreEx Interface Client Details
If client wants to invoke methods of IWbemBackupRestoreEx interface, the client MUST activate
IWbemBackupRestoreEx interface on the target WMI server machine using CLSID {C49E32C6-
BC8B-11D2-85D4-00105A1F8304} as specified in DCOM remote protocol. The client may obtain
IWbemBackupRestoreEx by calling IRemUnknown and IRemUnknown2 interfaces, as specified in
[MS-DCOM], on IWbemBackupRestore interface obtained as specified in section 3.1.4.10
3.2.4.5 IWbemRefreshingServices Interface Client Details
The client MUST obtain IWbemRefreshingServices interface, if the client wants to get updates to
the objects in an efficient manner. The client MUST obtain IWbemRefreshingServices interface by
calling IRemUnknown and IRemUnknown2 on IWbemServices interface obtained as specified in
section 3.2.3.
The client MUST generate _WBEM_REFRESHER_ID as specified in section 2.2.21. The client may call
IWbemRefreshingServices::AddObjectToRefresher,
IWbemRefreshingServices::AddObjectToRefresherByTemplate or
IWbemRefreshingServices::AddEnumToRefresher to add multiple objects and enums to the
refresher.
3.2.4.5.1 IWbemRefreshingServices::AddObjectToRefresher and

IWbemRefreshingServices::AddObjectToRefresherByTemplate
The client MUST pass the _WBEM_REFRESHER_ID that is generated as specified in section 2.2.21 to
the IWbemRefreshingServices::AddObjectToRefresher and
IWbemRefreshingServices::AddObjectToRefresherByTemplate methods.
When the client calls the IWbemRefreshingServices::AddObjectToRefresher or

IWbemRefreshingServices::AddObjectToRefresherByTemplate method with pRefresherId
generated by the client, the server returns the refresher information in the _WBEM_REFRESH_INFO
structure if the method succeeds.
The client MUST allow all the version numbers that are returned by the server in pdwSvrRefrVersion.
If the returned _WBEM_REFRESH_INFO structure contains m_lType as

WBEM_REFRESH_TYPE_REMOTE, the m_Info structure contains the
125 / 168
[MS-WMI] — v20091104

_WBEM_REFRESH_INFO_REMOTE structure. The client MUST obtain the IWbemRemoteRefresher
from the m_pRefresher in _WBEM_REFRESH_INFO_REMOTE. The client MUST use the
IWbemRemoteRefresher::RemoteRefresh method to get the updated object. If the client wants
to remove the particular object from the remote refresher, the client MUST use m_lCancelId, which
is returned in _WBEM_REFRESH_INFO, to invoke the IWbemRemoteRefresher::StopRefreshing
method.

WBEM_REFRESH_TYPE_NON_HIPERF, the client MUST retrieve the CIM instance using
IWbemServices::GetObject or IWbemServices::GetObjectAsync on the initial
IWbemServices interface.
When the IWbemRefreshingServices::AddObjectToRefresher or

IWbemRefreshingServices::AddObjectToRefresherByTemplate method fails, the server does
not return the _WBEM_REFRESH_INFO structure.
3.2.4.5.2 IWbemRefreshingServices::AddEnumToRefresher
The client MUST pass the _WBEM_REFRESHER_ID that is generated as specified in section 2.2.21 to
the IWbemRefreshingServices::AddEnumToRefresher method.
When the client calls the IWbemRefreshingServices::AddEnumToRefresher method with

pRefresherId generated by the client, the server returns the refresher information in the
_WBEM_REFRESH_INFO structure if the method succeeds.

WBEM_REFRESH_TYPE_REMOTE, the m_Info structure contains the
_WBEM_REFRESH_INFO_REMOTE structure. The client MUST obtain the IWbemRemoteRefresher
from the m_pRefresher in _WBEM_REFRESH_INFO_REMOTE. The client MUST use the
IWbemRemoteRefresher::RemoteRefresh method to get the updated enumeration. The client
MUST use m_lCancelId, which is returned in _WBEM_REFRESH_INFO, to invoke the
IWbemRemoteRefresher::StopRefreshing method if the client wants to remove the particular
enumeration from the remote refresher.

WBEM_REFRESH_TYPE_NON_HIPERF, the client MUST retrieve the CIM instances using
IWbemServices::CreateInstanceEnum or IWbemServices::CreateInstanceEnumAsync on
the initial IWbemServices interface.
When the IWbemRefreshingServices::AddEnumToRefresher method fails, the client MUST NOT

use the _WBEM_REFRESH_INFO structure.
3.2.4.5.3 IWbemRefreshingServices::GetRemoteRefresher
When invoking the methods of the IWbemRemoteRefresher interface, if the connection is lost
and reported to the client as an RPC disconnect error (see [MS-ERREF]), the client SHOULD try to
reconnect to WMI by obtaining IWbemServices as specified in section 3.2.3 and to obtain the
IWbemRemoteRefresher interface using the IWbemServices interface as specified in section
3.2.4.5, and SHOULD call the IWbemRefreshingServices::GetRemoteRefresher method on this
interface.
If the IWbemRefreshingServices::GetRemoteRefresher method call succeeds, the client gets a

GUID of the remote refresher in the pGuid parameter.
126 / 168
[MS-WMI] — v20091104

The client MUST allow all the version numbers that are returned by the server in the
pdwSvrRefrVersion parameter.
If the GUID is equal to the GUID that is returned in WBEM_REFRESH_INFO_REMOTE when the
remote refresher is first received by calling either
IWbemRefreshingServices::AddEnumToRefresher,
IWbemRefreshingServices::AddObjectToRefresher, or
IWbemRefreshingServices::AddObjectToRefresherByTemplate, the client MUST NOT call
IWbemRefreshingServices::ReconnectRemoteRefresher. The client SHOULD call
IWbemRemoteRefresher::RemoteRefresh on the IWbemRemoteRefresher interface, which is
obtained by using IWbemRefreshingServices::GetRemoteRefresher to refresh the object. The
client MUST NOT call the methods on the IWbemRemoteRefresher interface whose connection is
initially lost.
If the GUID is not equal to the GUID that is returned in WBEM_REFRESH_INFO_REMOTE when the
remote refresher is first received by calling either
IWbemRefreshingServices::AddEnumToRefresher,
IWbemRefreshingServices::AddObjectToRefresher or
IWbemRefreshingServices::AddObjectToRefresherByTemplate, the client MUST call
IWbemRefreshingServices::ReconnectRemoteRefresher to reconnect all the objects to the
refresher. The client MUST NOT call methods on the new remote refresher until
IWbemRefreshingServices::ReconnectRemoteRefresher is executed successfully. The client
MUST NOT call methods on the IWbemRemoteRefresher interface whose connection is lost
initially.
If the IWbemRefreshingServices::GetRemoteRefresher method call fails, the client SHOULD

retry after allowing a time-out.
3.2.4.5.4 IWbemRefreshingServices::ReconnectRemoteRefresher
The client SHOULD call IWbemRefreshingServices::ReconnectRemoteRefresher if the

IWbemRemoteRefresher method call failed and the client is attempting to reconnect the remote
refresher as specified in section 3.2.4.5.3.
When the method executes successfully, the client MUST validate all _WBEM_RECONNECT_RESULTS
to see if any object or enumerator has failed to be added to the refresher.
3.2.5 Timer Events
None.
3.2.6 Other Local Events
None.
127 / 168
[MS-WMI] — v20091104

4 Protocol Examples
The following sections describe several operations as used in common scenarios to illustrate the
function of the Windows Management Instrumentation Remote Protocol.
4.1 Protocol Initialization
The protocol is initiated by the DCOM Remote Protocol activation of the CLSID _IWbemLevel1Login.
For a client application to connect to the WMI service on a remote server, the client application first
obtains an IWbemLevel1Login interface pointer to the server on the remote computer by using
the COM activation. The client then uses the DCOM Remote Protocol to obtain an
IWbemLevel1Login interface pointer.
The client calls the IWbemLevel1Login::NTLMLogin method to obtain an IWbemServices

interface pointer. The IWbemServices interface pointer is the starting point for all other activities.
128 / 168
[MS-WMI] — v20091104

Figure 8: Protocol initialization example
4.2 Synchronous Operations
A synchronous operation completes when the entire result set is ready on the server. The following
sections describe the different scenarios where synchronous operations are applicable.
129 / 168
[MS-WMI] — v20091104

4.2.1 Synchronous Delivery of a Single Result
The IWbemServices::GetObject and IWbemServices::ExecMethod methods support

synchronous calls returning a single marshaled IWbemClassObject interface pointer.
Figure 9: Synchronous delivery of a single result
4.2.2 Synchronous Delivery of Result Sets
In this context of operation, there are two kinds of client behavior and two kinds of server behavior,
depending in the product version, resulting in four cases of client-server interaction.
The client behaviors are as follows:
Unoptimized Client behavior<38>
Optimized Client behavior<39>
The server behaviors are as follows:
Unoptimized Server behavior<40>
Optimized Server behavior<41>
The resulting client-server interactions are defined in the following sections:
Unoptimized Client and Unoptimized Server (section 4.2.2.1)
Unoptimized Client and Optimized Server (section 4.2.2.2)
Optimized Client and Optimized Server (section 4.2.2.3)
Optimized Client and Unoptimized Server (section 4.2.2.4)
4.2.2.1 Unoptimized Client and Unoptimized Server
The product versions that exhibit unoptimized client behavior and unoptimized server behavior are
listed in section 4.2.2.
To make a synchronous operation from a client to a server, the client uses the IWbemServices
interface pointer. The client calls the IWbemServices synchronous methods
130 / 168
[MS-WMI] — v20091104

IWbemServices::CreateInstanceEnum, IWbemServices::CreateClassEnum, and
IWbemServices::ExecQuery. In response to the method executed, the server returns an
IEnumWbemClassObject interface pointer. The client then uses the
IEnumWbemClassObject::Next method to repeatedly retrieve the IWbemClassObject objects
from the query result set.
Figure 10: Unoptimized Client and Unoptimized Server
4.2.2.2 Unoptimized Client and Optimized Server
The product versions that exhibit unoptimized client behavior and optimized server behavior are
IEnumWbemClassObject interface pointer. The client then uses the
IEnumWbemClassObject::Next method to repeatedly retrieve the IWbemClassObject objects
from the query result set.
The call sequence here is the same as that in 4.2.2.1 because in both cases, the client is
unoptimized, and therefore still uses the old mechanism for communication. Sections 4.2.2.3 and
4.2.2.4 explain the call sequences between the newer versions of client and server behavior.
131 / 168
[MS-WMI] — v20091104

Figure 11: Unoptimized Client and Optimized Server
4.2.2.3 Optimized Client and Optimized Server
The product versions that exhibit optimized client behavior and optimized server behavior are listed
in section 4.2.2.
IEnumWbemClassObject interface pointer. The client uses IRemUnknown and
IRemUnknown2, as specified in [MS-DCOM], to obtain an IWbemFetchSmartEnum interface
pointer from the IEnumWbemClassObject interface pointer. The client then calls the
IWbemFetchSmartEnum::GetSmartEnum method to obtain the IWbemWCOSmartEnum
interface pointer. The client uses the IWbemWCOSmartEnum::Next method repeatedly to
retrieve the IWbemClassObject interface pointers that contains the result set. The results are
encoded as an ObjectArray as specified in section 2.2.14.
132 / 168
[MS-WMI] — v20091104

Figure 12: Optimized Client and Optimized Server
4.2.2.4 Optimized Client and Unoptimized Server
The product versions that exhibit optimized client behavior and unoptimized server behavior are
IEnumWbemClassObject interface pointer. The client uses IRemUnknown and
133 / 168
[MS-WMI] — v20091104

IRemUnknown2, as specified in [MS-DCOM], to obtain an IWbemFetchSmartEnum interface
pointer from IEnumWbemClassObject interface pointer. The operation fails because the server is
not implementing the IWbemFetchSmartEnum interface. The client falls back to unoptimized
client behavior.
Figure 13: Optimized Client and Unoptimized Server
4.3 Semisynchronous Operations
In semisynchronous cases, the call returns before the requested operation completes, and another
interface is used to retrieve the operation results. The returned interface depends on the
IWbemServices methods that are invoked by the client. The following sections describe the two
different behaviors.
134 / 168
[MS-WMI] — v20091104

4.3.1 Semisynchronous Delivery of a Single Result
The methods returning a single element such as IWbemServices::OpenNamespace,

IWbemServices::GetObject, IWbemServices::PutClass, IWbemServices::DeleteClass,
IWbemServices::PutInstance, IWbemServices::DeleteInstance, or
IWbemServices::ExecMethod return an IWbemCallResult interface pointer. To obtain the
operation results, the client uses the IWbemCallResult methods.
Figure 14: Semisynchronous delivery of a single result
4.3.2 Semisynchronous Delivery of Result Sets
The semisynchronous operation uses the same sequence as the synchronous calls, as specified in
section 4.2.2, to request a result set. However, in semisynchronous cases, the
IEnumWbemClassObject interface pointer is returned before the result set is available on the
server. This is different from the synchronous case, in which the interface pointer is returned only
after the result set is available on the server. The IEnumWbemClassObject interface pointer is
returned before the result set is available on the server. When the client calls the
IEnumWbemClassObject::Next method, it specifies a time-out within which the server returns
the requested results. When one of the previous conditions is satisfied, the call completes.
4.4 Asynchronous Delivery of Results
An asynchronous method returns before the requested operation completes. The server continues to
execute the request and delivers the results to the client by using a response handler when the
results are available. A response handler is used to receive the results as they become available.
135 / 168
[MS-WMI] — v20091104

The IWbemObjectSink::Indicate method is called by the server when a result is found during the
operation.
To make an asynchronous query, the client uses the IWbemServices interface pointer and it
passes the IWbemObjectSink interface when calling an asynchronous method of the
IWbemServices interface.
If the asynchronous call returns SUCCESS, the server keeps a reference to the IWbemObjectSink
interface pointer. If the server is required to return WMI objects to the client, the server delivers the
results through the IWbemObjectSink::Indicate method.
After the delivery of all objects, the server makes a single call to IWbemObjectSink::SetStatus to
indicate that the operation finished, specifying the final status of the operation. After that, the
server releases the IWbemObjectSink pointer.
136 / 168
[MS-WMI] — v20091104

Figure 15: Asynchronous delivery of results
4.5 Optimized Asynchronous Delivery of Results
The asynchronous communication is optimized to reduce the network usage by making use of the
ObjectArray structure as specified in section 2.2.14.
A client supporting that capability notifies the server by returning 0x400FF (WBEM_S_NEW_STYLE)
in the first Indicate operation. A server that does not support the ObjectArray structure interprets
this as a success return code, while a server supporting the ObjectArray structure notices the code
and sends the rest of the results by using the ObjectArray structure, as specified in section 2.2.14.
Figure 16: Optimized asynchronous delivery of results
4.6 Configuring Refreshing Services
When using the refresher mechanism, a client application that is connected to a remote computer
through an IWbemServices pointer uses the IRemUnknown and IRemUnknown2 interfaces, as
specified in [MS-DCOM], to obtain an IWbemRefreshingServices interface, and it adds CIM
objects or enumerators as needed. The following diagram illustrates this behavior.
137 / 168
[MS-WMI] — v20091104

Figure 17: Configuring refreshing services
4.7 Using the Refresher Interface
The IWbemRemoteRefresher interface pointer that is returned from IWbemRefreshingServices

is used to obtain an updated result set. For the usage of the remote refresher, the client calls the
IWbemRemoteRefresher::RemoteRefresh method when the client needs to get an updated set
of data.
138 / 168
[MS-WMI] — v20091104

Figure 18: Using the refresher interface
139 / 168
[MS-WMI] — v20091104

5 Security
The following sections specify security considerations for implementers of the Windows Management
Instrumentation Remote Protocol.
5.1 Security Considerations for Implementers
For all methods, the server MUST evaluate the authentication level and the security principal rights
to open a CIM namespace, and the server MUST fail the operation if the security requirements are
not met.<42>
5.2 Index of Security Parameters
The server MUST secure access to each CIM namespace by using standard Microsoft Windows®
security descriptors,<43> as specified in [MS-DTYP]. The access mask that controls the security
principal rights contains the following specific rights, which are interpreted as specified in the table.
Constants Value Meaning
WBEM_ENABLE 0x1 Grants the security principal read permissions.
WBEM_FULL_WRITE 0x4 Grants the security principal to write to classes and instances.
WBEM_METHOD_EXECUTE 0x2 Grants the security principal to execute methods.
WBEM_PARTIAL_WRITE_REP 0x8 Grants the security principal to update information in the cache
only.
WBEM_REMOTE_ENABLE 0x20 Grants the security principal to remotely access the server.
WBEM_WRITE_PROVIDER 0x10 Grants the security principal to update real-time information

only.
In order to change the namespace security descriptor, a client MUST use the Windows Management
Instrumentation Remote Protocol and the required CIM object encoding, as specified in [MS-WMIO].
To query or change the security descriptor, the __SystemSecurity class methods GetSD and SetSD
defined in section 2.2.30 MUST be used. To manage the namespace security, the __SystemSecurity
class MUST be implemented at the top level of every namespace. The GetSD and SetSD methods
are invoked as specified in sections 3.1.4.3.22 and 3.1.4.3.23.
If the event object that is delivered to the WMI server (as specified in 3.2.4.2.1), contains a
SECURITY_DESCRIPTOR as specified in 2.2.4.2, the server MUST secure access to the event object
by using standard Windows security descriptors. The access mask that controls the security principal
rights has the following specific rights, which are interpreted as specified in the following table.
WBEM_RIGHTS_PUBLISH 0x80 Grants the security principal permission to send events to the WMI
server as specified in 3.2.4.2.1.
WBEM_RIGHT_SUBSCRIBE 0x40 Grants the security principal permission to receive the event object
using the IWbemServices::ExecNotificationQuery or
IWbemServices::ExecNotificationQueryAsync method call. If
this permission is not granted, the client can make
IWbemServices::ExecNotificationQuery or
IWbemServices::ExecNotificationQueryAsync calls, but the
140 / 168
[MS-WMI] — v20091104

event is not delivered.
141 / 168
[MS-WMI] — v20091104

6 Appendix A: Full IDL
For ease of implementation, the full IDL is provided, where "ms-oaut.idl" is the IDL found in [MS-
OAUT] appendix A.
import "ms-dtyp.idl";
import "ms-oaut.idl";
typedef GUID *REFGUID;
interface IWbemClassObject;
interface IWbemServices;
interface IWbemObjectSink;
interface IEnumWbemClassObject;
interface IWbemCallResult;
interface IWbemContext;
interface IWbemBackupRestore;
interface IWbemBackupRestoreEx;
interface IWbemLoginClientID;
interface IWbemLevel1Login;
interface IWbemLoginHelper;
[
restricted,
uuid(8BC3F05E-D86B-11d0-A075-00C04FB68820)
]
coclass WbemLevel1Login {
interface IWbemLevel1Login;
};
typedef long HRESULT;
typedef [v1_enum] enum tag_WBEM_QUERY_FLAG_TYPE {

WBEM_FLAG_DEEP = 0,
WBEM_FLAG_SHALLOW = 1,
WBEM_FLAG_PROTOTYPE = 2
} WBEM_QUERY_FLAG_TYPE;
typedef [v1_enum] enum tag_WBEM_CHANGE_FLAG_TYPE {

WBEM_FLAG_UPDATE_ONLY = 0x01,
WBEM_FLAG_CREATE_ONLY = 0x02,
WBEM_FLAG_UPDATE_SAFE_MODE = 0x20,
WBEM_FLAG_UPDATE_FORCE_MODE = 0x40
} WBEM_CHANGE_FLAG_TYPE;
typedef [v1_enum] enum tag_WBEM_CONNECT_OPTIONS {

WBEM_FLAG_CONNECT_REPOSITORY_ONLY = 0X40,
WBEM_FLAG_CONNECT_PROVIDERS = 0X100
} WBEM_CONNECT_OPTIONS;
typedef [v1_enum] enum tag_WBEM_GENERIC_FLAG_TYPE {

WBEM_FLAG_RETURN_IMMEDIATELY = 0x10,
WBEM_FLAG_FORWARD_ONLY = 0x20,
WBEM_FLAG_SEND_STATUS = 0x80,
WBEM_FLAG_ENSURE_LOCATABLE = 0x100,
WBEM_FLAG_DIRECT_READ = 0x200,
WBEM_FLAG_USE_AMENDED_QUALIFIERS = 0x20000
142 / 168
[MS-WMI] — v20091104

} WBEM_GENERIC_FLAG_TYPE;
typedef enum tag_WBEM_STATUS_TYPE {

WBEM_STATUS_COMPLETE = 0,
WBEM_STATUS_PROGRESS = 2
} WBEM_STATUS_TYPE;
typedef [v1_enum] enum tag_WBEM_TIMEOUT_TYPE {

WBEM_NO_WAIT = 0,
WBEM_INFINITE = 0xFFFFFFFF
} WBEM_TIMEOUT_TYPE;
typedef [v1_enum] enum tag_WBEM_BACKUP_RESTORE_FLAGS {

WBEM_FLAG_BACKUP_RESTORE_FORCE_SHUTDOWN = 1
} WBEM_BACKUP_RESTORE_FLAGS;
typedef [v1_enum] enum tag_WBEMSTATUS {

WBEM_S_NO_ERROR = 0x00,
WBEM_S_FALSE = 0x01,
WBEM_S_TIMEDOUT = 0x40004,
WBEM_E_FAILED = 0x80041001,
WBEM_E_NOT_FOUND = 0x80041002,
WBEM_E_ACCESS_DENIED = 0x80041003,
WBEM_E_INVALID_PARAMETER = 0x80041008,
WBEM_E_NOT_AVAILABLE = 0x80041009,
WBEM_E_NOT_SUPPORTED = 0x8004100C,
WBEM_E_INVALID_OPERATION = 0x80041016,
WBEM_E_ALREADY_EXISTS = 0x80041019,
E_NOTIMPL = 0x80004001,
WBEM_E_INVALID_SUPERCLASS = 0x8004100D,
WBEM_E_INVALID_NAMESPACE = 0x8004100E,
WBEM_E_INVALID_CLASS = 0x80041010,
WBEM_E_INVALID_QUERY = 0x80041017,
WBEM_E_INVALID_QUERY_TYPE = 0x80041018,
WBEM_E_CLASS_HAS_CHILDREN = 0x80041025,
WBEM_E_CLASS_HAS_INSTANCES = 0x80041026,
WBEM_E_INVALID_CIM_TYPE = 0x8004102D,
WBEM_E_INVALID_METHOD = 0x8004102E,
WBEM_E_INVALID_METHOD_PARAMETERS = 0x8004102F,
WBEM_E_CALL_CANCELLED = 0x80041032,
WBEM_E_INVALID_OBJECT_PATH = 0x8004103A
} WBEMSTATUS;
[
restricted,
uuid(674B6698-EE92-11d0-AD71-00C04FD8FDFF)
]
coclass WbemContext
{
interface IWbemContext;
};
[
uuid(9A653086-174F-11d2-B5F9-00104B703EFD)
]
coclass WbemClassObject
{
143 / 168
[MS-WMI] — v20091104

interface IWbemClassObject;
};
[
uuid(C49E32C6-BC8B-11d2-85D4-00105A1F8304)
]
coclass WbemBackupRestore
{
interface IWbemBackupRestoreEx;
};
#define OPTIONAL in, unique
interface IWbemQualifierSet;
[
local,
restricted,
object,
uuid(dc12a681-737f-11cf-884d-00aa004b2e24)
]
interface IWbemClassObject : IUnknown
{
};
interface IWbemServices;
[
object,
restricted,
uuid(7c857801-7381-11cf-884d-00aa004b2e24)
]
interface IWbemObjectSink : IUnknown
{
HRESULT Indicate(
[in] long lObjectCount,
[in, size_is(lObjectCount)]
IWbemClassObject** apObjArray
);
HRESULT SetStatus(
[in] long lFlags,
[in] HRESULT hResult,
[in] BSTR strParam,
[in] IWbemClassObject* pObjParam
);
};
[
object,
restricted,
uuid(027947e1-d731-11ce-a357-000000000001)
]
interface IEnumWbemClassObject : IUnknown
{
HRESULT Reset();
144 / 168
[MS-WMI] — v20091104

HRESULT Next(
[in] long lTimeout,
[in] ULONG uCount,
[out, size_is(uCount), length_is(*puReturned)]
IWbemClassObject** apObjects,
[out] ULONG* puReturned
);
HRESULT NextAsync(
[in] ULONG uCount,
);
HRESULT Clone(
);
HRESULT Skip(
[in] long lTimeout,
[in] ULONG nCount
);
};
[
object,
restricted,
local,
uuid(44aca674-e8fc-11d0-a07c-00c04fb68820)
]
interface IWbemContext : IUnknown
{
};
[
object,
restricted,
uuid(44aca675-e8fc-11d0-a07c-00c04fb68820)
]
interface IWbemCallResult : IUnknown
{
HRESULT GetResultObject(
[in] long lTimeout,
[out] IWbemClassObject** ppResultObject
);
HRESULT GetResultString(
[in] long lTimeout,
[out] BSTR* pstrResultString
);
HRESULT GetResultService(
[in] long lTimeout,
[out] IWbemServices** ppServices
);
HRESULT GetCallStatus(
[in] long lTimeout,
145 / 168
[MS-WMI] — v20091104

[out] long* plStatus
);
};
[
object,
restricted,
uuid(9556dc99-828c-11cf-a37e-00aa003240c7),
pointer_default(unique)
]
interface IWbemServices : IUnknown
{
HRESULT OpenNamespace(
[in] const BSTR strNamespace,
[in] long lFlags,
[out, in, unique] IWbemServices** ppWorkingNamespace,
[out, in, unique] IWbemCallResult** ppResult
);
HRESULT CancelAsyncCall(
);
HRESULT QueryObjectSink(
[in] long lFlags,
[out] IWbemObjectSink** ppResponseHandler
);
HRESULT GetObject(
[in] long lFlags,
[out, in, unique] IWbemClassObject** ppObject,
);
HRESULT GetObjectAsync(
[in] long lFlags,
);
HRESULT PutClass(
[in] long lFlags,
);
HRESULT PutClassAsync(
[in] long lFlags,
);
146 / 168
[MS-WMI] — v20091104

HRESULT DeleteClass(
[in] long lFlags,
);
HRESULT DeleteClassAsync(
[in] long lFlags,
);
HRESULT CreateClassEnum(
[in] const BSTR strSuperclass,
[in] long lFlags,
);
HRESULT CreateClassEnumAsync(
[in] const BSTR strSuperclass,
[in] long lFlags,
);
HRESULT PutInstance(
[in] long lFlags,
);
HRESULT PutInstanceAsync(
[in] long lFlags,
);
HRESULT DeleteInstance(
[in] long lFlags,
);
HRESULT DeleteInstanceAsync(
[in] long lFlags,
);
HRESULT CreateInstanceEnum(
[in] long lFlags,
147 / 168
[MS-WMI] — v20091104

);
HRESULT CreateInstanceEnumAsync(
[in] long lFlags,
);
HRESULT ExecQuery(
[in] long lFlags,
);
HRESULT ExecQueryAsync(
[in] long lFlags,
);
HRESULT ExecNotificationQuery(
[in] long lFlags,
);
HRESULT ExecNotificationQueryAsync(
[in] long lFlags,
);
HRESULT ExecMethod(
[in] long lFlags,
[out, in, unique] IWbemClassObject** ppOutParams,
);
HRESULT ExecMethodAsync(
[in] long lFlags,
148 / 168
[MS-WMI] — v20091104

);
};
[
object,
restricted,
uuid(C49E32C7-BC8B-11d2-85D4-00105A1F8304)
]
interface IWbemBackupRestore : IUnknown
{
HRESULT Backup(
[in, string] LPCWSTR strBackupToFile,
[in] long lFlags
);
HRESULT Restore(
[in, string] LPCWSTR strRestoreFromFile,
[in] long lFlags
);
};
[
object,
restricted,
uuid(A359DEC5-E813-4834-8A2A-BA7F1D777D76)
]
interface IWbemBackupRestoreEx : IWbemBackupRestore
{
HRESULT Pause();
HRESULT Resume();
};
typedef enum _WBEM_REFR_VERSION_NUMBER {

WBEM_REFRESHER_VERSION = 2
} WBEM_REFR_VERSION_NUMBER;
typedef [v1_enum] enum _WBEM_INSTANCE_BLOB_TYPE {

WBEM_BLOB_TYPE_ALL = 2,
WBEM_BLOB_TYPE_ERROR = 3,
WBEM_BLOB_TYPE_ENUM = 4
} WBEM_INSTANCE_BLOB_TYPE;
typedef struct _WBEM_REFRESHED_OBJECT {

long m_lRequestId;
WBEM_INSTANCE_BLOB_TYPE m_lBlobType;
long m_lBlobLength;
[size_is(m_lBlobLength)] byte* m_pbBlob;
} WBEM_REFRESHED_OBJECT;
[
restricted,
uuid(F1E9C5B2-F59B-11d2-B362-00105A1F8177)
]
interface IWbemRemoteRefresher : IUnknown {
HRESULT RemoteRefresh(
[in] long lFlags,
149 / 168
[MS-WMI] — v20091104

[out] long* plNumObjects,
[out, size_is(,*plNumObjects)]
WBEM_REFRESHED_OBJECT** paObjects
);
HRESULT StopRefreshing(
[in] long lNumIds,
[in, size_is(lNumIds)] long* aplIds,
[in] long lFlags
);
HRESULT Opnum5NotUsedOnWire(
[in] long lFlags,
[out] GUID* pGuid
);
};
typedef struct {
IWbemRemoteRefresher* m_pRefresher;
GUID m_Guid;
} _WBEM_REFRESH_INFO_REMOTE;
typedef struct {
[string] wchar_t* m_wszNamespace;
} _WBEM_REFRESH_INFO_NON_HIPERF;
typedef enum
{
WBEM_REFRESH_TYPE_INVALID = 0,
WBEM_REFRESH_TYPE_REMOTE = 3,
WBEM_REFRESH_TYPE_NON_HIPERF = 6
}WBEM_REFRESH_TYPE;
typedef [switch_type(long)] union {

[case (WBEM_REFRESH_TYPE_REMOTE)]
_WBEM_REFRESH_INFO_REMOTE m_Remote;
[case (WBEM_REFRESH_TYPE_NON_HIPERF)]
_WBEM_REFRESH_INFO_NON_HIPERF m_NonHiPerf;
[case (WBEM_REFRESH_TYPE_INVALID)]
HRESULT m_hres;
} WBEM_REFRESH_INFO_UNION;
typedef struct {
long m_lType;
[switch_is(m_lType)] WBEM_REFRESH_INFO_UNION m_Info;
long m_lCancelId;
} _WBEM_REFRESH_INFO;
typedef struct {
[string] LPSTR m_szMachineName;
DWORD m_dwProcessId;
GUID m_guidRefresherId;
} _WBEM_REFRESHER_ID;
150 / 168
[MS-WMI] — v20091104

typedef enum {
WBEM_RECONNECT_TYPE_OBJECT = 0,
WBEM_RECONNECT_TYPE_ENUM = 1,
WBEM_RECONNECT_TYPE_LAST = 2
}WBEM_RECONNECT_TYPE;
typedef struct {
long m_lType;
[string] LPCWSTR m_pwcsPath;
} _WBEM_RECONNECT_INFO;
typedef struct {
long m_lId;
HRESULT m_hr;
} _WBEM_RECONNECT_RESULTS;
[
restricted,
uuid(2C9273E0-1DC3-11d3-B364-00105A1F8177)
]
interface IWbemRefreshingServices : IUnknown
{
HRESULT AddObjectToRefresher(
[in, string] LPCWSTR wszPath,
[in] long lFlags,
);
HRESULT AddObjectToRefresherByTemplate(
[in] IWbemClassObject* pTemplate,
[in] long lFlags,
);
HRESULT AddEnumToRefresher(
[in, string] LPCWSTR wszClass,
[in] long lFlags,
);
HRESULT RemoveObjectFromRefresher(
[in] long lId,
[in] long lFlags,
151 / 168
[MS-WMI] — v20091104

);
HRESULT GetRemoteRefresher(
[in] long lFlags,
[out] IWbemRemoteRefresher** ppRemRefresher,
[out] GUID* pGuid,
);
HRESULT ReconnectRemoteRefresher(
[in] long lFlags,
[in] long lNumObjects,
[in, size_is(lNumObjects)]
_WBEM_RECONNECT_INFO* apReconnectInfo,
[in, out, size_is(lNumObjects)]
_WBEM_RECONNECT_RESULTS* apReconnectResults,
);
};
[
restricted,
object,
uuid(423EC01E-2E35-11d2-B604-00104B703EFD)
]
interface IWbemWCOSmartEnum : IUnknown
{
HRESULT Next(
[in] REFGUID proxyGUID,
[in] long lTimeout,
[in] ULONG uCount,
[out] ULONG* puReturned,
[out] ULONG* pdwBuffSize,
[out, size_is(,*pdwBuffSize)] byte** pBuffer
);
};
[
restricted,
object,
uuid(1C1C45EE-4395-11d2-B60B-00104B703EFD)
]
interface IWbemFetchSmartEnum : IUnknown
{
HRESULT GetSmartEnum(
[out] IWbemWCOSmartEnum** ppSmartEnum
);
};
[
restricted,
object,
uuid(d4781cd6-e5d3-44df-ad94-930efe48a887)
]
152 / 168
[MS-WMI] — v20091104

interface IWbemLoginClientID : IUnknown
{
HRESULT SetClientInfo(
[in, unique, string ] LPWSTR wszClientMachine,
[in] long lClientProcId,
[in] long lReserved
);
};
[
object,
restricted,
uuid(F309AD18-D86A-11d0-A075-00C04FB68820),
pointer_default(unique)
]
interface IWbemLevel1Login : IUnknown
{
HRESULT EstablishPosition(
[in] DWORD reserved2,
[out] DWORD* reserved3
);
HRESULT RequestChallenge(
[out, size_is(16), length_is(16)] unsigned char* reserved3
);
HRESULT WBEMLogin(
[in, size_is(16), length_is(16), unique]
unsigned char* reserved2,
[in] long reserved3,
[in] IWbemContext* reserved4,
[out] IWbemServices** reserved5
);
HRESULT NTLMLogin(
[in, unique, string] LPWSTR wszNetworkResource,
[in, unique, string] LPWSTR wszPreferredLocale,
[in] long lFlags,
[out] IWbemServices** ppNamespace
);
};
[
restricted,
object,
uuid(541679AB-2E5F-11d3-B34E-00104BCC4B4A)
]
interface IWbemLoginHelper : IUnknown
{
HRESULT SetEvent(
[in] LPCSTR sEventToSet
);
153 / 168
[MS-WMI] — v20091104

};
154 / 168
[MS-WMI] — v20091104

7 Appendix B: Product Behavior
The information in this specification is applicable to the following product versions:
Microsoft Windows® 2000 operating system
Windows® XP operating system
Windows® XP 64-Bit Edition operating system
Windows® XP operating system Service Pack 1 (SP1)
Windows® XP operating system Service Pack 3 (SP3)
Windows Server® 2003 operating system
Windows Server® 2003 operating system with Service Pack 2 (SP2)
Windows Vista® operating system
Windows Server® 2008 operating system
Windows® 7 operating system
Windows Server® 2008 R2 operating system
This specification also covers Microsoft Windows NT® Server operating system behavior when it
interacts with WMI clients in one of the previously listed versions of Microsoft Windows®.
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 2.2.6: The prefix "__" is specific to Windows and is not a CIM standard.
<2> Section 2.2.13: A Windows client builds the IWbemContext object by using a set of specific
IWbemContext methods to add, delete, and enumerate properties with their respective values.
The IWbemContext methods are not used by the protocol at any time. They are used internally by
the client and the server to manage the content of the object.
<3> Section 2.2.13.4: 32-bit versions of Windows set the value to 4; however, 64-bit versions of
Windows set the value to 8.
<4> Section 2.2.13.4: 32-bit versions of Windows set the value to 4; however, 64-bit versions of
Windows set the value to 8.
<5> Section 2.2.14: This optimization technique is being used by Windows starting with
Windows XP and Windows Server 2003.
<6> Section 2.2.14: The value MUST be 0 for Windows communication.
<7> Section 2.2.21: Windows uses the m_dwProcessId as the process identifier.
155 / 168
[MS-WMI] — v20091104

<8> Section 3.1.1.1.3: Windows does not send progress information.
<9> Section 3.1.1.1.3: Windows tries to make the call at the highest authentication level,
RPC_C_AUTHN_PKT_PRIVACY. Windows gradually downgrades (decreasing the authentication level
by one level at every call) to RPC_C_AUTHN_NONE if the DCOM Remote Protocol (as specified in
[MS-DCOM]) is unable to use the current authentication level.
<10> Section 3.1.4.1.1: LocaleVersion is supported in Windows 7 and Windows Server 2008 R2
only. For Windows 2000, Windows XP, Windows Server 2003, Windows Server 2003 SP2,
Windows Vista, and Windows Server 2008, this parameter MUST be set to 0 when sent and MUST be
ignored on receipt.
<11> Section 3.1.4.1.2: Windows always returns this value.
<12> Section 3.1.4.1.3: Windows always returns this value.
<13> Section 3.1.4.1.4: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and
Windows Server 2008 fail the call if the locale name does not match one of the WMI locale formats,
as defined in WMI Locale Formats section 2.2.29, or if the locale name is not valid for that operating
system.
If the locale is in "MS_xxx" format as defined in 2.2.29 and the LCID is not valid for Windows 7,
Windows 7 fails the call. If the locale string is not in "MS_xxx" format and it is not a valid locale for
Windows 7, the locale is ignored.
<14> Section 3.1.4.1.4: Windows–based clients always set lFlags to zero. The server role of
Windows 2000 returns WBEM_E_INVALID_PARAMETER for a nonzero value of lFlags. The server
roles of Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008 allow lFlags
to be zero or any combination of the flags WBEM_FLAG_CONNECT_PROVIDERS and
WBEM_FLAG_CONNECT_REPOSITORY_ONLY.
<15> Section 3.1.4.1.4: Windows uses the system's locale as described in [MSDN-
GetSystemDefaultLangID].
<16> Section 3.1.4.2.1: The optimized asynchronous delivery is supported by Windows XP,
Windows Server 2003, Windows Server 2008, Windows 7, and Windows Server 2008 R2.
<17> Section 3.1.4.3.6: Windows does not ignore the amended qualifiers while it creates a CIM
class; however, it does ignore all the amended qualifiers while it updates a class. Because the
amended qualifiers are not ignored while Windows creates a CIM class, when this CIM class is
retrieved by using IWbemServices::GetObject or IWbemServices::GetObjectAsync (retrieved
even without using the WBEM_FLAG_USE_AMENDED_QUALIFIERS flag), the returned class contains
amended qualifiers.
<18> Section 3.1.4.3.7: Windows does not ignore the amended qualifiers while it creates a CIM
class; however, it does ignore all the amended qualifiers while it updates a class. Because the
amended qualifiers are not ignored while Windows creates a CIM class, when this CIM class is
retrieved by using IWbemServices::GetObject or IWbemServices::GetObjectAsync (retrieved
even without using the WBEM_FLAG_USE_AMENDED_QUALIFIERS flag), the returned class contains
amended qualifiers.
<19> Section 3.1.4.9.1: A WMI server in Windows 2000 and Windows XP signals a Windows kernel
event with the specified name. The valid values for the sEventToSet parameter of
IWbemLoginHelper::SetEvent are all the valid values for the lpName parameter to the
OpenEvent function, as defined in [MSDN-OpenEvent]. If the client can detect that the event is set
at the end of the IWbemLoginHelper::SetEvent method call, the client identifies that the server is
running in the same server. If the client and server are running on different machines, the Windows
156 / 168
[MS-WMI] — v20091104

event by the specified name will not be set on the client machine, and the client can then identify
that the server is running on another machine.
<20> Section 3.1.4.10.1: Windows Server requires an absolute file path that starts with a drive
letter.
<21> Section 3.1.4.10.1: Windows allows users that have the SE_BACKUP_PRIVILEGE privilege to
perform the backup operation.
<22> Section 3.1.4.10.2: Windows Server requires an absolute file path that starts with a drive
letter.
<23> Section 3.1.4.10.2: Windows allows users that have the SE_RESTORE_PRIVILEGE privilege to
perform the restore operation.
<24> Section 3.1.4.11: Windows implements the IWbemBackupRestoreEx interface in

Windows XP and Windows Server 2003.
<25> Section 3.1.4.12: The IWbemRefreshingServices interface is available only in Windows XP,
Windows Server 2003, Windows Server 2008, Windows 7, and Windows Server 2008 R2.
<26> Section 3.1.4.12.1: Windows 2000 sets the version number to 1. Windows XP, Windows
Server 2003, Windows Vista, Windows Server 2008, and Windows 7 set the version number to 2.
<30> Section 3.1.4.12.4: Windows does not implement this method and returns a
WBEM_E_NOT_AVAILABLE error code.
<33> Section 3.1.4.13: The IWbemRemoteRefresher interface is available only on Windows XP,
Windows Server 2003, and Windows Server 2008.
<34> Section 3.1.4.13.3: The Opnum5NotUsedOnWire method is not used by Windows and
therefore is not required for an implementation.
<35> Section 3.2.3: Windows 2000 and Windows XP clients obtain the IWbemLoginHelper
interface by using the IRemUnknown and IRemUnknown2 interfaces, as specified in [MS-DCOM]
sections 3.2.1.5.6 and 3.2.1.5.7, on the IWbemLevel1Login interface.
If the server returns an error during the attempt to use IRemUnknown and IRemUnknown2 to
obtain an IWbemLoginHelper interface, the client ignores the error. The client calls
IWbemLoginHelper::SetEvent to determine whether both the client and server are running on
the same machine.
157 / 168
[MS-WMI] — v20091104

The valid values for the sEventToSet parameter of IWbemLoginHelper::SetEvent are all the valid
values for the lpName parameter to the OpenEvent function as defined in [MSDN-OpenEvent]. If the
client can detect that the event is set at the end of the IWbemLoginHelper::SetEvent method
call, the client can identify that both the client and server are running on the same machine. If the
client and server are running on different machines, the Windows event by the specified name is not
set on the client machine, and the client can then identify that the server is running on another
machine.
<36> Section 3.2.4.1.1: Windows attempts to batch object delivery. The algorithm is complex;
however, the maximum batch size, in bytes, can be set by editing the registry value for
FinalizerBatchSize under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wbem\CIMOM registry
subkey. If FinalizerBatchSize is not specified, the default value, 262144 (0x40000), is used.
<37> Section 3.2.4.1.2: Windows does not send progress information.
<38> Section 4.2.2: In this context, Unoptimized Client behavior is client behavior under
Windows 2000 and Windows 2000 Server.
<39> Section 4.2.2: In this context, Optimized Client behavior is client behavior under Windows XP,
including Windows XP 64-Bit Edition, Windows XP SP1, and Windows XP SP3; and under Windows
Server 2003, Windows Server 2003 SP2, Windows Vista, Windows Server 2008, Windows 7, and
Windows Server 2008 R2.
<40> Section 4.2.2: In this context, Unoptimized Server behavior is server behavior under
Windows 2000 and Windows 2000 Server.
<41> Section 4.2.2: Optimized server behavior in this context is server behavior under
Windows XP, including Windows XP 64-Bit Edition, Windows XP SP1, and Windows XP SP3; and
under Windows Server 2003, Windows Server 2003 SP2, Windows Vista, Windows Server 2008,
Windows 7, and Windows Server 2008 R2.
<42> Section 5.1: Windows secures the access to each namespace and accepts only authenticated
calls made at least at the RPC_C_AUTHN_LEVEL_CONNECT level. Windows behavior across different
operating systems is specified in the following table.
Operating system version Minimum authentication level
Windows NT RPC_C_AUTHN_LEVEL_CONNECT
Windows 2000 RPC_C_AUTHN_LEVEL_CONNECT
Windows 2000 Professional SP3 RPC_C_AUTHN_LEVEL_PKT
Windows XP RPC_C_AUTHN_LEVEL_PKT
Windows Server 2003 RPC_C_AUTHN_LEVEL_PKT
Windows Vista RPC_C_AUTHN_LEVEL_PKT
<43> Section 5.2: In Windows, local administrators are implicitly granted all rights that are
specified in the table in section 5.2.
158 / 168
[MS-WMI] — v20091104

8 Change Tracking
This section identifies changes made to [MS-WMI] protocol documentation between September 2009
and November 2009 releases. Changes are classed as major, minor, or editorial.
Major changes affect protocol interoperability or implementation. Examples of major changes are:
A document revision that incorporates changes to interoperability requirements or functionality.
An extensive rewrite, addition, or deletion of major portions of content.
A protocol is deprecated.
The removal of a document from the documentation set.
Changes made for template compliance.
Minor changes do not affect protocol interoperability or implementation. Examples are updates to
fix technical accuracy or ambiguity at the sentence, paragraph, or table level.
Editorial changes apply to grammatical, formatting, and style issues.
No changes means that the document is identical to its last release.
Major and minor changes can be described further using the following revision types:
New content added.
Content update.
Content removed.
New product behavior note added.
Product behavior note updated.
Product behavior note removed.
New protocol syntax added.
Protocol syntax updated.
Protocol syntax removed.
New content added due to protocol revision.
Content updated due to protocol revision.
Content removed due to protocol revision.
New protocol syntax added due to protocol revision.
Protocol syntax updated due to protocol revision.
Protocol syntax removed due to protocol revision.
New content added for template compliance.
Content updated for template compliance.
159 / 168
[MS-WMI] — v20091104

Content removed for template compliance.
Obsolete document removed.
Editorial changes always have the revision type "Editorially updated."
Some important terms used in revision type descriptions are defined as follows:
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods)
as well as interfaces.
Protocol revision refers to changes made to a protocol that affect the bits that are sent over the
wire.
Changes are listed in the following table. If you need further information, please contact
[email protected].
Major
chang
Tracking number (if e
applicable) (Y or Revisio
Section and description N) n Type
1.3 39453 N Content

Protocol Overview (Synopsis) Removed mention of update.
Windows administrator.
1.7 39350 Y Product

Versioning and Capability Negotiation Removed product behavior behavior
note that stated "Server note
negotiation of locale removed
capabilities is supported in .
Windows Server 2008 R2
only".
2.2.15 39340 N Content

WBEM_REFRESHED_OBJECT Structure Specified that pointer update.
parameters must be set to
"NULL" as opposed to "0".
2.2.20 39453 N Content

_WBEM_REFRESH_INFO Structure Created a cross-reference update.
link for an instance of
WBEM_REFRESH_INFO_UNI
ON.
3.1.4 Specified the message- N Content

Message Processing Events and Sequencing Rules processing behavior in the update.
case where the output
parameter is set to NULL
upon input.
3.1.4.1.1 Merged this topic with a N Content

IWbemLevel1Login::EstablishPosition (Opnum 3) duplicate version. update.
3.1.4.1.1 39340 N Content

IWbemLevel1Login::EstablishPosition (Opnum 3) Specified that the reserved1 update.
pointer parameter must be
set to "NULL" as opposed to
160 / 168
[MS-WMI] — v20091104

Major
chang
"0".
3.1.4.1.1 39350 N Product

IWbemLevel1Login::EstablishPosition (Opnum 3) Updated product behavior behavior
note to say LocaleVersion is note
supported in Windows 7 and updated.
is not supported in Windows
XP or Windows Vista.
3.1.4.1.1 39341 N Content

IWbemLevel1Login::EstablishPosition (Opnum 3) Clarified the processing update.
rules for the LocaleVersion
parameter and return
values.
3.1.4.1.2 Clarified Windows versions N Product

IWbemLevel1Login::RequestChallenge (Opnum 4) in product behavior notes. behavior
note
updated.
3.1.4.1.2 39340 N Content

IWbemLevel1Login::RequestChallenge (Opnum 4) Specified that the reserved update.
pointer parameters must be
"0".
3.1.4.1.3 Clarified Windows versions N Product

IWbemLevel1Login::WBEMLogin (Opnum 5) in product behavior notes. behavior
note
updated.
3.1.4.1.3 39340 N Content

IWbemLevel1Login::WBEMLogin (Opnum 5) Specified that the reserved update.
pointer parameters must be
"0".
3.1.4.1.4 39342 N Content

IWbemLevel1Login::NTLMLogin (Opnum 6) Revised the server behavior update.
when the preferred locale is
NULL.
3.1.4.2.1 39350 N Product

IWbemObjectSink::Indicate (Opnum 3) Server details Added Windows 7 and behavior
Windows Server 2008 R2 to note
product behavior note. updated.
3.1.4.3.1 39453 N Content

IWbemServices::OpenNamespace (Opnum 3) Changed "set to" to "based update.
on".
3.1.4.3.2 39352 N Content

IWbemServices::CancelAsyncCall (Opnum 4) Specified the server update.
validation of the security
161 / 168
[MS-WMI] — v20091104

Major
chang
principal making the

CancelAsyncCall.
3.1.4.3.8 39344 N Content

IWbemServices::DeleteClass (Opnum 10) Specified that the server update.
must delete all instances of
the class and recursively
delete all derived classes.
3.1.4.3.9 39344 N Content

IWbemServices::DeleteClassAsync (Opnum 11) Specified that the server update.
must delete all instances of
the class and recursively
delete all derived classes.
3.1.4.3.16 39356 N Content

IWbemServices::CreateInstanceEnum (Opnum 18) Changed "strFilter" to update.
"strSuperClass".
3.1.4.3.17 39356 N Content

IWbemServices::CreateInstanceEnumAsync (Opnum Specified that the update.
19) strSuperClass parameter
MUST contain the name of
the CIM class for which the
client wants instances and
MUST NOT be NULL.
3.1.4.3.18 39345 N Content

IWbemServices::ExecQuery (Opnum 20) Specified that the update.
strQueryLanguage
parameter MUST be set to
"WQL" and removed product
behavior note for that
parameter.
3.1.4.3.19 39345 N Content

IWbemServices::ExecQueryAsync (Opnum 21) Specified that the update.
strQueryLanguage
parameter.
3.1.4.3.20 39357 N Content

IWbemServices::ExecNotificationQuery (Opnum 22) Changed "to receive events" update.
to "to deliver events
matching the query".
3.1.4.3.20 39345 N Content

IWbemServices::ExecNotificationQuery (Opnum 22) Specified that the update.
strQueryLanguage
162 / 168
[MS-WMI] — v20091104

Major
chang
parameter.
3.1.4.3.21 39345 N Content

IWbemServices::ExecNotificationQueryAsync (Opnum Specified that the update.
23) strQueryLanguage
parameter.
3.1.4.3.21 39358 N Content

IWbemServices::ExecNotificationQueryAsync (Opnum Specified that in all update.
23) circumstances, the server
MUST NOT call
IWbemObjectSink::SetStatu
s to send success or
operation progress
information.
3.1.4.7.1 39453 N Content

IWbemWCOSmartEnum::Next (Opnum 3) Specified that update.
IWbemWCOSmartEnum::Ne
xt must return the same
object array as
IEnumWbemClassObject::N
ext.
3.1.4.10.1 39348 N Content

IWbemBackupRestore::Backup (Opnum 3) Specified that the server update.
should verify that the
security principal making
the call is allowed to back
up the CIM database, and
added a product behavior
note.
3.1.4.10.2 39348 N Content

IWbemBackupRestore::Restore (Opnum 4) Specified that the server update.
should verify that the
security principal making
the call is allowed to restore
the CIM database, and
added a product behavior
note.
3.1.4.11.1 39453 N Content

IWbemBackupRestoreEx::Pause (Opnum 5) Added reference to "Timer update.
Events" section.
3.1.4.12 39345 N Product

IWbemRefreshingServices Interface Added Windows 7 and behavior
Windows Server 2008 R2 to note
the product behavior note. updated.
163 / 168
[MS-WMI] — v20091104

Major
chang
3.1.4.12.1 39349 N Content

IWbemRefreshingServices::AddObjectToRefresher Specified the security update.
(Opnum 3) restrictions on the security
principal.
3.1.4.12.2 39349 N Content

IWbemRefreshingServices::AddObjectToRefresherByTe Specified the security update.
mplate (Opnum 4) restrictions on the security
principal.
3.1.4.12.3 39349 N Content

IWbemRefreshingServices::AddEnumToRefresher Specified the security update.
principal.
3.1.4.12.4 39349 N Content

IWbemRefreshingServices::RemoveObjectFromRefresh Specified the security update.
er (Opnum 6) restrictions on the security
principal.
3.1.4.12.5 39349 N Content

IWbemRefreshingServices::GetRemoteRefresher Specified the security update.
principal.
3.1.4.12.6 39349 N Content

IWbemRefreshingServices::ReconnectRemoteRefresher Specified the security update.
principal.
3.2.3 39341 N Content

Initialization Clarified which locale lists update.
are unsupported.
4.2.2 Clarified Windows versions N Content

Synchronous Delivery of Result Sets in product behavior notes. . update.
4.2.2 Moved Windows version- N Product

Synchronous Delivery of Result Sets specific information into behavior
product behavior notes. note
updated.
4.2.2.1 Clarified references to N Content

Unoptimized Client and Unoptimized Server Windows versions. update.

Unoptimized Client and Optimized Server Windows versions. update.

Optimized Client and Optimized Server Windows versions. update.

Optimized Client and Unoptimized Server Windows versions. update.
164 / 168
[MS-WMI] — v20091104

Major
chang
6 39356 N Content
Appendix A: Full IDL Changed "strFilter" to update.
"strSuperClass".
N Editoriall
y
updated.
165 / 168
[MS-WMI] — v20091104

9 Index
_WBEM_RECONNECT_INFO structure 42 asynchronous delivery 135
_WBEM_RECONNECT_RESULTS structure 42 configuring refresher services 137
_WBEM_REFRESH_INFO structure 41 optimized asynchronous delivery 137
_WBEM_REFRESH_INFO_NON_HIPERF structure 43 overview 128
_WBEM_REFRESH_INFO_REMOTE structure 44 refresher interface 138
_WBEM_REFRESH_TYPE enumeration 43 semisynchronous operations 134
_WBEM_REFRESHER_ID structure 41 synchronous operations 129
ExecMethod method 88
A ExecMethodAsync method 90
ExecNotificationQuery method 86
Abstract data model ExecNotificationQueryAsync method 87
client 47 ExecQuery method 83
server 47 ExecQueryAsync method 84
AddEnumToRefresher method 112
AddObjectToRefresher method 110 F
AddObjectToRefresherByTemplate method 111
Applicability 13 Fields - vendor-extensible 13
Asynchronous delivery examples 135 Full IDL 142
B G
Backup method 106 GetCallStatus method 101

GetObject method 61
C GetObjectAsync method 63
GetRemoteRefresher method 114
CancelAsyncCall method 59 GetResultObject method 98
Capability negotiation 13 GetResultService method 100
Change tracking 159 GetResultString method 99
CIM path and namespace 21 GetSmartEnum method 102
Client Glossary 7
abstract data model 47
initialization 49 I
local events 119
timer events 119 IDL 142
timers 49 Implementer - security considerations 140
Clone method 96 Index of security parameters 140
Common data types 15 Indicate method 54
Configuring refreshing services examples 137 Informative references 9
CreateClassEnum method 70 Initialization 128
CreateClassEnumAsync method 72 client 49
CreateInstanceEnum method 80 server 49
CreateInstanceEnumAsync method 81 Introduction 7
IWbemClassObject 23
D IWbemLevel1Login::EstablishPosition (Opnum 3) 50
IWbemLevel1Login::RequestChallenge (Opnum 4)
Data model - abstract 51
client 47 IWbemLevel1Login::WBEMLogin (Opnum 5) 52
server 47
Data types 15 L
DeleteClass method 68
DeleteClassAsync method 69 Local events
DeleteInstance method 77 client 119
DeleteInstanceAsync method 79 server 119
E M
EstablishPosition method 50 Message processing

Examples client 49
166 / 168
[MS-WMI] — v20091104

server 49 Sequencing rules
Messages client 49
overview 15 server 49
transport 15 Server
abstract data model 47
N initialization 49
local events 119
Next method (section 3.1.4.4.2 94, section overview 46
3.1.4.7.1 103) timer events 119
NextAsync method 95 timers 49
Normative references 8 SetClientInfo method 104
NTLMLogin method 52 SetEvent method 105
SetStatus method 54
O Single result - synchronous delivery 130
Skip method 96
ObjectArray packet 34 Standards assignments 13
OpenNamespace method 58 StopRefreshing method 118
Opnum5NotUsedOnWire method 119 Synchronous delivery of a single result 130
Optimized asynchronous delivery examples 137 Synchronous delivery of result sets 130
Overview (synopsis) 9 Synchronous operations examples 129
P T
Parameters - security index 140 Timer events

Pause method 108 client 119
Preconditions 12 server 119
Prerequisites 12 Timers
Product behavior 155 client 49
PutClass method 64 server 49
PutClassAsync method 66 Tracking changes 159
PutInstance method 73 Transport - message 15
PutInstanceAsync method 75
V
Q
Vendor-extensible fields 13
QueryObjectSink method 60 Versioning 13
R W
ReconnectRemoteRefresher method 115 WBEM_BACKUP_RESTORE_FLAGS enumeration 28

References WBEM_CHANGE_FLAG_TYPE enumeration 25
informative 9 WBEM_CONNECT_OPTIONS enumeration 30
normative 8 WBEM_DATAPACKET_OBJECT packet 36
RefreshedInstances packet 40 WBEM_GENERIC_FLAG_TYPE enumeration 26
RefreshedSingleInstance packet 41 WBEM_INSTANCE_BLOB packet 40
Refresher interface examples 138 WBEM_INSTANCE_BLOB_TYPE enumeration 40
Relationship to other protocols 12 WBEM_QUERY_FLAG_TYPE enumeration 27
RemoteRefresh method 117 WBEM_RECONNECT_TYPE enumeration 42
RemoveObjectFromRefresher method 113 WBEM_REFRESHED_OBJECT structure 39
RequestChallenge method 51 WBEM_S_FALSE 23
Reset method 93 WBEM_S_NEW_STYLE 23
Restore method 107 WBEM_S_NO_ERROR 23
Result sets - synchronous delivery 130 WBEM_S_TIMEDOUT 23
Resume method 108 WBEM_STATUS_TYPE enumeration 27
WBEM_TIMEOUT_TYPE enumeration 27
S WBEMLogin method 52
WBEMOBJECT_CLASS packet 37
Security WBEMOBJECT_INSTANCE packet 37
implementer considerations 140 WBEMOBJECT_INSTANCE_NOCLASS packet 38
overview 140 WBEMSTATUS enumeration 28
parameter index 140 WQL event query 19
Semisynchronous operations examples 134 WQL query 15
167 / 168
[MS-WMI] — v20091104

WQL schema and data query 15
168 / 168
[MS-WMI] — v20091104

Windows Management Instrumentation Interface

Uploaded by

Copyright:

Available Formats

Windows Management Instrumentation Interface

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Windows Management Instrumentation Interface

Uploaded by

Copyright:

Available Formats

[MS-WMI]:

Windows Management Instrumentation Remote Protocol

Intellectual Property Rights Notice for Open Specifications Documentation

 Technical Documentation. Microsoft publishes Open Specifications documentation for

 Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

Date Revision History Revision Class Comments

07/20/2007 0.1 Major MCPP Milestone 5 Initial Availability

09/28/2007 0.2 Minor Updated the technical content.

10/23/2007 0.3 Minor Updated the technical content.

11/30/2007 1.0 Major Updated and revised the technical content.

01/25/2008 1.1 Minor Updated the technical content.

03/14/2008 2.0 Major Updated and revised the technical content.

05/16/2008 2.0.1 Editorial Revised and edited the technical content.

06/20/2008 3.0 Major Updated and revised the technical content.

07/25/2008 3.1 Minor Updated the technical content.

08/29/2008 4.0 Major Updated and revised the technical content.

10/24/2008 4.1 Minor Updated the technical content.

12/05/2008 4.2 Minor Updated the technical content.

01/16/2009 4.3 Minor Updated the technical content.

02/27/2009 4.4 Minor Updated the technical content.

04/10/2009 5.0 Major Updated and revised the technical content.

05/22/2009 6.0 Major Updated and revised the technical content.

07/02/2009 7.0 Major Updated and revised the technical content.

08/14/2009 7.1 Minor Updated the technical content.

09/25/2009 7.2 Minor Updated the technical content.

11/06/2009 8.0 Major Updated and revised the technical content.

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

3 Protocol Details ...................................................................................................... 46

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

4 Protocol Examples ................................................................................................ 128

5 Security ................................................................................................................ 140

6 Appendix A: Full IDL............................................................................................. 142

7 Appendix B: Product Behavior .............................................................................. 155

8 Change Tracking................................................................................................... 159

9 Index ................................................................................................................... 166

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

The following terms are defined in [MS-GLOS]:

The following terms are specific to this document:

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

1.2.1 Normative References

[DMTF-DSP004] Distributed Management Task Force, "Common Information Model (CIM)

[MS-DTYP] Microsoft Corporation, "Windows Data Types", January 2007.

[MS-ERREF] Microsoft Corporation, "Windows Error Codes", January 2007.

Copyright © 2009 Microsoft Corporation.

Release: Wednesday, November 4, 2009

[MS-WMIO] Microsoft Corporation, "Windows Management Instrumentation Encoding Version 1.0

[UNICODE] The Unicode Consortium, "Unicode Home Page", 2006, http://www.unicode.org/

1.2.2 Informative References

[DFS-R WMI] Microsoft Corporation, "DFSR WMI Classes", http://msdn.microsoft.com/en-

[MS-GLOS] Microsoft Corporation, "Windows Protocols Master Glossary", March 2007.

STRING-IDENTIFIER = ALPHA (ALPHA / DIGIT / (("_") ALPHA / DIGIT))