Revision Summary Date Revision History Revision Class Comments 3/2/2007 1.0 New Version 1.0 release 4/3/2007 1.1 Version 1.1 release 5/11/2007 1.2 Minor Version 1.2 release 6/1/2007 1.2.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.2.2 Editorial Changed language and formatting in the technical content. 8/10/2007 1.2.3 Editorial Changed language and formatting in the technical content. 9/28/2007 1.3 Minor Clarified the meaning of the technical content. 10/23/2007 2.0 Major Converted the document to unified format, and updated the technical content. 1/25/2008 2.1 Minor Clarified the meaning of the technical content. 3/14/2008 3.0 Major Updated and revised the technical content.
6/20/2008 4.0 Updated and revised the technical content. 7/25/2008 4.1 Minor Clarified the meaning of the technical content. 8/29/2008 5.0 Major Updated and revised the technical content. 10/24/2008 5.1 Minor Clarified the meaning of the technical content. 12/5/2008 5.2 Minor Clarified the meaning of the technical content. 1/16/2009 5.3 Minor Clarified the meaning of the technical content. 2/27/2009 5.4 Minor Clarified the meaning of the technical content. 4/10/2009 6.0 Major Updated and revised the technical content. 5/22/2009 7.0 Major Updated and revised the technical content. 7/2/2009 8.0 Major Updated and revised the technical content. 8/14/2009 8.1 Minor Clarified the meaning of
the technical content. 9/25/2009 8.2 Minor Clarified the meaning of the technical content. 11/6/2009 9.0 Updated and revised the technical content. 12/18/2009 10.0 Major Updated and revised the technical content. 1/29/2010 11.0 Major Updated and revised the technical content. 3/12/2010 11.1 Minor Clarified the meaning of the technical content. 4/23/2010 12.0 Major Updated and revised the technical content. 6/4/2010 13.0 Updated and revised the technical content. 7/16/2010 13.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 14.0 Major Updated and revised the technical content.
10/8/2010 15.0 Major Updated and revised the technical content. 11/19/2010 16.0 Major Updated and revised the technical content. 1/7/2011 17.0 Updated and revised the technical content. 2/11/2011 18.0 Updated and revised the technical content. 3/25/2011 19.0 Major Updated and revised the technical content. 5/6/2011 20.0 Updated and revised the technical content. 6/17/2011 20.1 Minor Clarified the meaning of the technical content. 9/23/2011 21.0 Major Updated and revised the technical content. 12/16/2011 22.0 Major Updated and revised the technical content. 3/30/2012 23.0 Major Updated and revised the technical content. 7/12/2012 24.0 Major Updated and revised
10/16/2015 27.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 27.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 27.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 28.0 Major Significantly changed the technical content.
specified in section 2.2.13.1. Unmarshaler This CLSID represents the unmarshaler CLSID that is supplied by the Windows Management Instrumentation Remote Protocol to the DCOM Remote Protocol and 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.18.6. For the IDL of these two IWbemContext interfaces, see , which contains the full 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. Structure requirements for marshaling a property. Structure requirements for marshaling a string. Structure requirements for marshaling an 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. The integer formats OCTET, UINT16, and UINT32 are encoded as defined in section 2.2.72. IWbemContextBuffer Marshaling Structure The IWbemContextBuffer data structure defines the wire format for buffer data that is used by this protocol. Its structure has the following encoding format (defined in notation as specified in ).
VT_BSTR VT_BOOL VT_UI1 VT_UI2 VT_UI4 VT_UNKNOWN VT_I1 If the 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. Property types Marshaling VT_BSTR MUST be marshaled as an IWbemContextString. VT_IUNKNOWN MUST be marshaled as a buffer for the 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, VT_BOOL MUST be marshaled as an array of 8 bytes with the first 2 bytes containing the 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 of 8 bytes with the first 4 bytes containing the value of the property, as specified in , a 4-byte floating-point format. VT_R8 MUST be marshaled in an 8-byte format as specified in [IEEE754]. VT_ARRAY | VT_* MUST be marshaled as an structure, as specified in 2.2.13.4. IWbemContextString Marshaling Structure The IWbemContextString data structure defines the wire format for the string data that is used by this protocol. Strings (property 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 . IWbemContextString has the following structure. IWbemContextString = StringLength *UnicodeCharacter StringLength MUST represent the length of the string as a character count. StringLength = UINT32 UnicodeCharacter = 2OCTET
Index _ 50 48 48 47 49 49 49 47 A Abstract data model 153 56 147 138 222 135 137 17 190 190 B 132 77 17 227 25 Client 153 153 161 159 159 154 159 161 161 161 153 55 153 161 153 121 Common data types 25 51 27 36 50 41 46 47 26 52 50 32 29 36 29 46 46 31 48 48 48 47 49 49 50 49 45 47 30 31 32 18 192 90 91 101 103 146 147 D Data model - abstract 153 56 Data types 25 51 27 36 50 41 46 47 26 52 50 32 29 36 29 46 46 31 48 48 48 47 49
64 Server 56 147 117 64 145 131 133 123 127 67 130 130 71 135 142 73 144 146 128 152 64 150 overview ( 55, 55) 64 151 63 130 131 51 72 145 122 17 222 143 52 165 Synchronous operations examples delivery of result sets 168 170 166 167 166 166 delivery traces 171 174 165 51 50 T Timer events 161 151 Timers 153 63 227 18 18 U 193 V 17 17 W 32 29 36 43 29 46 46 31 48 45 26 26 26 26 30 31 69 43 44 44 32 23 18 18