7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

The terms "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section.

Windows Client

• Windows NT 4.0 operating system

• Windows 2000 Professional operating system

• Windows XP operating system

• Windows XP 64-Bit Edition operating system

• Windows Vista operating system

• Windows 7 operating system

• Windows 8 operating system

• Windows 8.1 operating system

• Windows 10 operating system

• Windows 11 operating system

Windows Server

• Windows NT Server operating system

• Windows 2000 Server operating system

• Windows Server 2003 operating system

• Windows Server 2003 operating system with Service Pack 2 (SP2)

• Windows Server 2008 operating system

• Windows Server 2008 R2 operating system

• Windows Server 2012 operating system

• Windows Server 2012 R2 operating system

• Windows Server 2016 operating system 

• Windows Server operating system

• Windows Server 2019 operating system

• Windows Server 2022 operating system

• Windows Server 2025 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product 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.12: Windows interprets the flags as follows:

WBEM_FLAG_CONNECT_REPOSITORY_ONLY: The connection is established to operate only on the static data (classes and instances) stored in the CIM 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.

<3> 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.

The following Windows versions support the context properties in the table: Windows XP operating system Service Pack 1 (SP1), Windows Server 2003 operating system with Service Pack 1 (SP1), Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating system. Prior versions of Windows ignore these values.

<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.13.4: 32-bit versions of Windows set the value to 4; however, 64-bit versions of Windows set the value to 8.

<6> Section 2.2.14:  This optimization technique is being used by Windows starting with Windows XP and Windows Server 2003.

<7> Section 2.2.21: Windows uses the m_dwProcessId as the process identifier.

<8> Section 2.2.30.1: Windows 2000 Professional and later and Windows Server 2003 and later do not return errors using the return value of the GetSD CIM method. Errors are returned as an error in the IWbemServices interface method call.

<9> Section 2.2.30.2: Windows 2000 Professional and later and Windows Server 2003 and later do not return errors using the return value of the GetSD CIM method. Errors are returned as an error in the IWbemServices interface method call.

<10> Section 2.2.30.3: On Windows NT 4.0, Windows 2000 Professional, Windows 2000 Server, Windows Server 2003, Windows XP, and Windows XP SP1, the RequiresEncryption qualifier is ignored.

<11> Section 2.2.32: In Windows, the security descriptor of a namespace can be specified explicitly in an MOF file, using the NamespaceSecuritySDDL qualifier. The qualifier is a string in the security descriptor definition language (SDDL) format. If no NamespaceSecuritySDDL qualifier is present, the server initializes the security descriptor for the namespace to the default value.

<12> Section 3.1.1: In Windows, the limit is 5000.

<13> Section 3.1.1: In Windows, the security descriptor of a namespace can be specified explicitly in an MOF file, using the NamespaceSecuritySDDL qualifier. The qualifier is a string in the security descriptor definition language (SDDL) format. If no NamespaceSecuritySDDL qualifier is present, the server initializes the security descriptor for the namespace to the default value.

The security groups refer to the values defined in [MS-DTYP] section 2.4.2.4.

Starting with Windows Vista, the default security groups are:

• AUTHENTICATED_USERS

• LOCAL_SERVICE

• NETWORK_SERVICE

• BUILTIN_ADMINISTRATORS

In Windows Server 2003, Windows XP, Windows 2000 Server, Windows 2000 Professional, and Windows NT 4.0, the default security groups are:

• BUILTIN_ADMINISTRATORS

• LOCAL_SERVICE

• NETWORK_SERVICE

• EVERYONE

The default access permissions for the AUTHENTICATED_USERS, LOCAL_SERVICE, and NETWORK_SERVICE are:

• WBEM_METHOD_EXECUTE

• WBEM_FULL_WRITE

• WBEM_ENABLE

<14> Section 3.1.1: "WQL:References" is used in Windows NT Server, Windows NT 4.0, and Windows 2000 Server only. 

<15> Section 3.1.1.1.3: Windows does not send progress information.

<16> Section 3.1.1.1.3: Windows tries to make the call at the highest authentication level, RPC_C_AUTHN_PKT_PRIVACY. If UnsecAppAccessControlDefault is set to false, 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. The minimum authentication level for Windows 2000 Professional and Windows 2000 Server is RPC_C_AUTHN_LEVEL_CONNECT. In Windows 2000 Professional and Windows 2000 Server, Windows XP, and Windows Server 2003, the server does not check for the AllowAnonymousCallback flag prior to making anonymous callbacks to the client.

In Windows Vista and later and Windows Server 2008 and later, the AllowAnonymousCallback value will be retrieved from registry location HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\AllowAnonymousCallback. In Windows 2000 Professional and Windows XP, the server does not check for the UnsecAppAccessControlDefault flag prior to downgrading the authentication level.

In Windows Server 2003 and later and Windows Vista and later, the UnsecAppAccessControlDefault value will be retrieved from registry location HKLM\Software\Microsoft\WBEM\CIMOM\UnsecAppAccessControlDefault.

<17> Section 3.1.3: In Windows 2000 Professional, Windows 2000 Server, Windows XP, and Windows Server 2003, this value is set to True.

<18> Section 3.1.4: The following Windows versions support ordered array types:

• Windows NT operating system

• Windows NT 4.0

• Windows XP 64-Bit Edition

<19> Section 3.1.4: 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.

<20> Section 3.1.4: Windows NT Server and Windows NT 4.0 do not allow the static properties to be modified.

<21> Section 3.1.4: Windows allows providers to do the impersonation or do additional authentication and authorization checks based on the security principal of the caller.

<22> Section 3.1.4: On Windows NT 4.0, Windows 2000, Windows Server 2003, Windows XP, and Windows XP SP1, the RequiresEncryption qualifier is ignored.

<23> Section 3.1.4: In Windows Server 2008 and Windows Server 2008 R2, if the number of active IWbemService objects for root\virtualization namespace is more than 4096, the server returns WBEM_E_QUOTA_VIOLATION.

<24> Section 3.1.4:  Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 do not use this.

<25> Section 3.1.4:  Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 do not use this.

<26> Section 3.1.4: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 do not set this option. Windows 8 and later and Windows Server 2012 and later set this option when WMI C-Client APIs are used but not when the IWbemServices COM interface is used.

<27> Section 3.1.4.1.1: If the server accepts as a locale parameter for the IWbemLevel1Login::NTLMLogin method all locales valid for Windows Vista as defined in Appendix A of [MS-LCID], the server returns WBEM_S_NO_ERROR for IWbemLevel1Login::EstablishPosition.

<28> Section 3.1.4.1.1: If the server returns WBEM_E_INVALID_PARAMETER for any valid Windows Vista locales as specified in Appendix A of [MS-LCID] that has been passed as a locale parameter to the IWbemLevel1Login::NTLMLogin method while all other parameters are valid, the server returns E_NOTIMPL for IWbemLevel1Login::EstablishPosition.

<29> Section 3.1.4.1.4: In Windows, it is the Windows system locale of the server.

<30> Section 3.1.4.1.4: Windows 2000 and later and Windows XP and later fail the call and return 0x80041008 (WBEM_E_INVALID_PARAMETER) if the locale name does not match one of the WMI Locale Formats (section 2.2.29), or if the locale name is not valid for that operating system.

If the locale name is in the "MS_xxx" format but refers to an LCID, Windows Vista and later and Windows Server 2008 and later fail the call and return 0x80070057 (E_INVALIDARG).

If the locale is in "MS_xxx" format as defined in section 2.2.29 and the LCID is not valid for Windows 7, Windows Server 2008 R2, Windows 8, or Windows Server 2012, Windows fails the call and returns E_INVALIDARG. If the locale string is not in "MS_xxx" format and it is not a valid locale for Windows 7 and later and Windows Server 2008 R2 and later, the locale is ignored.

<31> Section 3.1.4.1.4: Windows clients always set lFlags to 0. The server role of Windows 2000 returns WBEM_E_INVALID_PARAMETER for a nonzero value of lFlags. The server roles of Windows XP and later and Windows Server 2003 and later allow lFlags to be 0 or any combination of the flags WBEM_FLAG_CONNECT_PROVIDERS and WBEM_FLAG_CONNECT_REPOSITORY_ONLY.

<32> Section 3.1.4.1.4: The following Windows client versions do not enforce a limit:

• Windows NT 4.0

• Windows NT Server 4.0 operating system

• Windows 2000 Professional

• Windows 2000 Server

• Windows XP

• Windows XP SP1

• Windows XP operating system Service Pack 2 (SP2)

• Windows Server 2003

• Windows Server 2003 with SP1

The following versions of Windows enforce a query string limit of 8173 characters (WBEM_MAX_PATH -19, where WBEM_MAX_PATH = 0x2000 and the 19 characters represent the length of the string __namespace.name=""):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<33> Section 3.1.4.1.4: Windows uses the system's locale as described in [MSDN-GetSystemDefaultLangID].

<34> 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.

<35> Section 3.1.4.3.6: Windows client versions Windows NT 4.0, Windows 2000 Professional, Windows XP, and server versions Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003, and Windows Server 2003 with SP1 do not enforce a limit.

The following versions of Windows enforce a query string limit of 4096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<36> 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.

<37> Section 3.1.4.3.7: Windows client versions Windows NT 4.0, Windows 2000 Professional, Windows XP, and server versions Windows NT Server 4.0, Windows 2000 Server, Windows Server 2003, and Windows Server 2003 with SP1 do not enforce a limit.

The following versions of both client and server enforce a query string limit of 4096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<38> Section 3.1.4.3.8: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

The following Windows versions enforce a query string limit of 4096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<39> Section 3.1.4.3.9: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

The following Windows versions enforce a query string limit of 4,096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<40> Section 3.1.4.3.10: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 4096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<41> Section 3.1.4.3.11: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 4096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<42> Section 3.1.4.3.12: Windows client versions Windows NT 4.0, Windows 2000 Professional, Windows XP, and server versions Windows NT Server 4.0, Windows 2000 Server, Windows Server 2003 and Windows Server 2003 with SP1 do not enforce a limit.

The following versions of both client and server enforce a query string limit of 8192 characters (WBEM_MAX_PATH = 0x2000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<43> Section 3.1.4.3.13: Windows client versions Windows NT 4.0, Windows 2000 Professional, Windows XP, and server versions Windows NT Server 4.0, Windows 2000 Server, Windows Server 2003, and Windows Server 2003 with SP1 do not enforce a limit.

The following versions of Windows enforce a query string limit of 8,192 characters (WBEM_MAX_PATH = 0x2000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<44> Section 3.1.4.3.14: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 8192 characters (WBEM_MAX_PATH = 0x2000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<45> Section 3.1.4.3.15: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 8,192 characters (WBEM_MAX_PATH = 0x2000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<46> Section 3.1.4.3.16: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 4096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<47> Section 3.1.4.3.17: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 4,096 characters (WBEM_MAX_IDENTIFIER = 0x1000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<48> Section 3.1.4.3.18: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 16384 characters (WBEM_MAX_QUERY = 0x4000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<49> Section 3.1.4.3.18: Keysonly is not available in the following products: Windows 95 operating system, Windows NT 4.0, Windows 98 operating system, Windows Millennium Edition operating system, and Windows 2000.

<50> Section 3.1.4.3.18: Keysonly is not available in the following products: Windows 95, Windows NT 4.0, Windows 98, Windows Millennium Edition, and Windows 2000.

<51> Section 3.1.4.3.19: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows XP 64-Bit Edition

• Windows XP SP1

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 16,384 characters (WBEM_MAX_QUERY = 0x4000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<52> Section 3.1.4.3.20: In the following versions of Windows, the interval is first converted to a double, then multiplied by 1000, and then converted to a 32-bit unsigned integer. This has the effect of truncating out-of-range values without generating an error.

• Windows 2000

• Windows 2000 Server

• Windows XP

• Windows 7

• Windows Server 2008

• Windows Server 2008 R2

• Windows 8

• Windows Server 2012

<53> Section 3.1.4.3.20: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 16384 characters (WBEM_MAX_QUERY = 0x4000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<54> Section 3.1.4.3.21: The following Windows versions do not enforce a limit:

• Windows NT 4.0

• Windows 2000

• Windows XP

• Windows Server 2003

• Windows Server 2003 with SP1

These Windows versions enforce a query string limit of 16,384 characters (WBEM_MAX_QUERY = 0x4000):

• Windows Server 2003 SP2 and later

• Windows Vista and later

<55> Section 3.1.4.3.21: In the following versions of Windows, the interval is first converted to a double, then multiplied by 1000, and then converted to a 32-bit unsigned integer. This has the effect of truncating out-of-range values without generating an error.

• Windows 2000

• Windows 2000 Server

• Windows XP

• Windows 7

• Windows Server 2008

• Windows Server 2008 R2

• Windows 8

• Windows Server 2012

<56> Section 3.1.4.8.1: Applicable Windows Server releases record lClientProcId for debugging purposes.

<57> 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 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.

<58> Section 3.1.4.10.1: Applicable Windows Server releases require an absolute file path that starts with a drive letter.

<59> Section 3.1.4.10.1: Windows allows users that have the SE_BACKUP_PRIVILEGE privilege to perform the backup operation.

<60> Section 3.1.4.10.2: Applicable Windows Server releases require an absolute file path that starts with a drive letter.

<61> Section 3.1.4.10.2: Windows allows users that have the SE_RESTORE_PRIVILEGE privilege to perform the restore operation.

<62> Section 3.1.4.11: This interface is not supported in Windows NT 4.0 and Windows 2000.

<63> Section 3.1.4.12: The IWbemRefreshingServices interface is not available in Windows NT 4.0, Windows 2000, or Windows 2000 Server.

<64> Section 3.1.4.12.1: Windows 2000 sets the version number to 1.

<65> Section 3.1.4.12.2: Windows 2000 sets the version number to 1.

<66> Section 3.1.4.12.3: Windows 2000 sets the version number to 1.

<67> Section 3.1.4.12.4: Windows 2000 sets the version number to 1.

<68> Section 3.1.4.12.4: Windows does not implement this method and returns a WBEM_E_NOT_AVAILABLE error code.

<69> Section 3.1.4.12.5: Windows 2000 sets the version number to 1.

<70> Section 3.1.4.12.6: Windows 2000 sets the version number to 1.

<71> Section 3.1.4.13: The IWbemRemoteRefresher interface is not available in Windows NT 4.0, Windows 2000, or Windows 2000 Server.

<72> Section 3.1.4.13.3: The Opnum5NotUsedOnWire method is not used by Windows and therefore is not required for an implementation.

<73> Section 3.1.4.17:  Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 do not use this.

<74> Section 3.1.4.17:  Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 do not use this.

<75> Section 3.1.4.17.11: In Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008, the default is IN when IN/IN,OUT/OUT is not specified for a method parameter.

<76> Section 3.1.4.18.1: Windows initializes the security descriptor for the namespace to the following values.

Starting with Windows Vista, the default security groups are:

• Authenticated Users

• LOCAL SERVICE

• NETWORK SERVICE

• Administrators (on the local computer)

In Windows Server 2003, Windows XP, Windows 2000 and Windows NT 4.0, the default security groups are:

• Administrators

• LOCAL SERVICE

• NETWORK SERVICE

• Everyone

The default access permissions for the Authenticated Users, LOCAL SERVICE, and NETWORK SERVICE are:

• Execute Methods

• Full Write

• Enable Account

<77> Section 3.2.3: Windows clients pass the client process ID in the lClientProcId parameter.

<78> 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.1.1.5.6 and 3.1.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.

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.

<79> Section 3.2.3: If the return value from IWbemLevel1Login::EstablishPosition is WBEM_S_NO_ERROR and LocaleVersion is set to 0, the client filters out locale lists that are not supported in Windows Vista, as specified in [MS-LCID].

<80> Section 3.2.4: Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Windows 7 do not set the option. Windows 8 does set the option when WMI C-Client APIs are used but not when the IWbemServices COM interface is used.

<81> 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.

<82> Section 3.2.4.1.2: Windows does not send progress information.

<83> Section 4.2.2: In this context, unoptimized client behavior is client behavior in Windows 2000 and Windows 2000 Server.

<84> Section 4.2.2: In this context, optimized client behavior is client behavior in the following Windows versions:

• Windows XP 64-Bit Edition

• Windows XP SP1

• Windows XP operating system Service Pack 3 (SP3) and later

• Windows Server 2003

• Windows Server 2003 SP2 and later

<85> Section 4.2.2: In this context, unoptimized server behavior is server behavior in Windows 2000 and Windows 2000 Server.

<86> Section 4.2.2: Optimized server behavior in this context is server behavior in the following Windows versions:

• Windows XP 64-Bit Edition

• Windows XP SP1

• Windows XP SP3 and later

• Windows Server 2003

• Windows Server 2003 SP2 and later

<87> 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.

<88> Section 5.2: In Windows, local administrators are implicitly granted all rights that are specified in the table in section 5.2.