7 Appendix B: Windows Behavior
The information in this specification is applicable to the following versions of Windows:
- Windows 2000
- Windows XP
- Windows XP 64-Bit Edition
- Windows XP SP1
- Windows Server 2003
- Windows Server 2003 SP2
- Windows Vista
- Windows Server 2008
The specification also covers Windows NT Server behavior when interacting with WMI client in one of the above Windows versions.
Exceptions, if any, are noted as follows. 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.20: Windows uses the m_dwProcessId as the process identifier.
<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 with one 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: Windows does not implement this method.
<11> Section 3.1.4.1.1: The WBEM_S_NO_ERROR 0x00 value is returned by Windows Vista, Windows Vista SP1, and Windows Server 2008.
<12> Section 3.1.4.1.1: The E_NOTIMPL 0x80004001 value is returned by all versions of Windows except Windows Vista, Windows Vista SP1, and Windows Server 2008.
<13> Section 3.1.4.1.2: All versions of Windows return this value.
<14> Section 3.1.4.1.3: All versions of Windows return this value.
<15> Section 3.1.4.1.4: Windows 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 role of Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008 allows lFlags to be zero or any combination of the flags WBEM_FLAG_CONNECT_PROVIDERS and WBEM_FLAG_CONNECT_REPOSITORY_ONLY.
<16> Section 3.1.4.3.18: Under Windows, this value MUST be "WQL", as specified in section 2.2.1.
<17> Section 3.1.4.3.19: Under Windows, this value MUST be "WQL," as specified in section 2.2.1.
<18> Section 3.1.4.3.20: Under Windows, this value MUST be "WQL", as specified in section 2.2.1.
<19> Section 3.1.4.3.21: Under Windows, this value MUST be "WQL", as specified in section 2.2.1.
<20> Section 3.1.4.9.1: A Windows-based server signals a Windows kernel event by using a specified event name. This signal is used by the client process to identify whether the server and client are running on the same machine.
<21> Section 3.1.4.10.1: Windows Server requires an absolute file path that starts with a drive letter.
<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.11: Windows implements the IWbemBackupRestoreEx interface in Windows XP and Windows Server 2003.
<24> Section 3.1.4.12: The IWbemRefreshingServices interface is available only in Windows XP, Windows Server 2003, and Windows Server 2008.
<25> Section 3.1.4.12.4: Windows does not implement this method and returns WBEM_E_NOT_AVAILABLE error code.
<26> Section 3.1.4.13: The IWbemRemoteRefresher interface is available only on Windows XP, Windows Server 2003, and Windows Server 2008.
<27> Section 3.1.4.13.3: The Opnum5NotUsedOnWire method is not used by Windows and therefore is not required for an implementation.
<28> Section 3.2.4.1.2: Windows does not send progress information.
<29> Section 4.5: The optimized asynchronous delivery is supported by Windows XP, Windows Server 2003, and Windows Server 2008.
<30> 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 |
<31> Section 5.2: In Windows, local administrators are implicitly granted all rights that are specified in the table in section 5.2.
