Share via

7 Appendix B: Product Behavior

  • Article

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 2000 Professional operating system

  • Windows XP 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 2000 Server operating system

  • Windows Server 2003 operating system

  • 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.1: Windows clients attempt to use RPC_C_IMP_LEVEL_DELEGATE, as specified in [MS-RPCE] section 2.2.1.1.9, and if that fails, attempt to use RPC_C_IMP_LEVEL_IMPERSONATE, as specified in [MS-RPCE] section 2.2.1.1.9.

<2> Section 2.1: Windows 2000 operating system and Windows XP clients first attempt to use Kerberos (for more information, see [MS-KILE]) and, failing that, attempt to use NTLM (for more information, see [MS-NLMP].

<3> Section 2.2.1.3: Applicable Windows Server releases internally maintain some of the tables in the catalog as a relational join of multiple internal tables. The amount of time that it takes to perform read operations on these tables can be greatly affected by the order in which the join is computed. Applicable Windows Server releases interpret the presence of this special option as a hint that the join should be computed in a particular order. Applicable Windows Server releases accept comparison values other than 1 for this special option, intended for local use only. These additional values are never sent by Windows clients.

<4> Section 2.2.1.4: The following versions of Windows support the 64-bit QueryCell marshaling format: Windows XP (x64 and Itanium Editions), Windows Server 2003 (x64 and Itanium Editions), Windows Vista (x64 Editions), Windows Server 2008 (x64 and Itanium Editions), Windows 7 (x64 Editions), Windows Server 2008 R2 operating system (x64 and Itanium Editions), Windows 8 (x64 Editions), and Windows Server 2012 (x64 and Itanium Editions).

<5> Section 2.2.1.8: The Windows 10 and earlier and Windows Server 2016 and earlier do not set the Write bit in cases that do not strictly require it.

<6> Section 2.2.1.8: Rather than ignoring the Read and Write bits, Windows 10 and earlier and Windows Server 2016 and earlier rely on them as hints when extracting data from these structures.

<7> Section 2.2.1.8: Windows 10 and earlier and Windows Server 2016 and earlier do not set the Read bit in cases that do not strictly require it.

<8> Section 2.2.1.8: Rather than ignoring the Read and Write bits, Windows 10 and earlier and Windows Server 2016 and earlier rely on them as hints when extracting data from these structures.

<9> Section 2.2.1.9: Windows uses this field as scratch space when constructing or processing TableDataFixed and TableDataFixedWrite structures, and in some cases sends these structures with this field set to a nonzero value for a null-valued property. This field is always ignored on receipt for a null-valued property.

<10> Section 2.2.1.9: Windows uses this field as scratch space when constructing or processing TableDataFixed and TableDataFixedWrite structures, and in some cases sends these structures with this field set to a nonzero value for a null-valued property. This field is always ignored on receipt for a null-valued property.

<11> Section 2.2.2.2: Windows also accepts local paths.

<12> Section 2.2.2.3: For more information on how the thread is selected for calls to MTA-hosted component instances on Windows, see [MSDN-ThreadMDLS].

<13> Section 2.2.2.3: For more information on how the thread is selected for calls to neutral-hosted component instances on Windows, see [MSDN-ThreadMDLS].

<14> Section 2.2.2.3.1: For more information on how Windows selects an STA thread to host the component instance, see [MSDN-ThreadMDLS].

<15> Section 2.2.2.13.1: On Windows, an ORBSpecificExceptionClassProperty is a Curly Braced GUID String Syntax ([MS-DTYP], section 2.3.4.3) representation of a CLSID, a ProgId, or a COM moniker (for more information, see [MSDN-COMMonikers]).

<16> Section 2.2.2.13.2: On Windows, an ORBSpecificModuleIdentifierProperty type is an assembly name for a managed assembly (for more information, see [MSDN-Assemblies]).

<17> Section 2.2.2.13.3: On Windows, an ORBSpecificTypeIdentifierProperty type is a class name of a class in a managed assembly (for more information, see [MSDN-Assemblies]).

<18> Section 2.2.2.13.4: On Windows, an ORBSpecificAlternateLaunchNameProperty is the service name of a Windows service (for more information, see [MSDN-WINSVC]).

<19> Section 2.2.2.13.5: On Windows, an ORBSpecificAlternateLaunchParametersProperty is service-specific command line string passed to a Windows service when starting it (for more information, see [MSDN-WINSVC]).

<20> Section 2.2.2.13.6: On Windows, an ORBSpecificCommandLineProperty is the lpCommandLine parameter of CreateProcess (for more information, see [MSDN-CreateProcess]). This property is intended to be used for debugging purposes, where the command line is modified to a value that runs the original system-provided command line under a debugger. Any other value produces undefined results.

<21> Section 2.2.2.13.7: On Windows, an ORBSpecificWebServerVirtualDirectoryProperty type is an Internet Information Services (IIS) virtual root (for more information, see [MSDN-IIS]).

<22> Section 2.2.2.13.8: On Windows, an ORBSpecificSubscriptionFilterCriteriaProperty type is a COM+ Event System filter criteria query (for more information, see [MS-COMEV] section 2.2.1).

<23> Section 2.2.2.13.9: On Windows, an ORBSpecificAlternateActivationProperty is a COM moniker (for more information, see [MSDN-COMMonikers]).

<24> Section 2.2.2.13.10: On Windows, an ORBSpecificProtocolSequenceMnemonicProperty type MUST be one of the values in the following table. The set of values considered valid by the COMA server on Windows is version-specific. The set of values representing RPC protocol sequences that are supported transports for DCOM on Windows is also version-specific and is not necessarily equal to the set of values considered valid by the COMA server. Those values that do not correspond to a supported RPC protocol sequences are simply ignored as possible transports by the DCOM protocol implementation on Windows.

Value

Description

Versions considered valid by COMA server

Versions supported protocol sequence for DCOM

*

Default System Protocols

Windows 2000

Windows XP

Windows Server 2003

Windows Vista

Windows Server 2008

Windows 7

Windows Server 2008 R2

Windows 8

Windows Server 2012

Windows 8.1

Windows Server 2012 R2

Windows 10

Windows Server 2016

None. For historical reasons, the COMA server on Windows accepts this as a valid value but it does not correspond to a valid RPC protocol sequence.

ncacn_ip_tcp

Connection-oriented TCP/IP

Windows 2000

Windows XP

Windows Server 2003

Windows Vista

Windows Server 2008

Windows 7

Windows Server 2008 R2

Windows 8

Windows Server 2012

Windows 8.1

Windows Server 2012 R2

Windows 10

Windows Server 2016

Windows 2000

Windows XP

Windows Server 2003

Windows Vista

Windows Server 2008

Windows 7

Windows Server 2008 R2

Windows 8

Windows Server 2012

Windows 8.1

Windows Server 2012 R2

Windows 10

Windows Server 2016

ncacn_http

Tunneling TCP/IP

Windows 2000

Windows XP

Windows Server 2003

Windows Vista

Windows Server 2008

Windows 7

Windows Server 2008 R2

Windows 8

Windows Server 2012

Windows 8.1

Windows Server 2012 R2

Windows 10

Windows Server 2016

Windows 2000

Windows XP

Windows Server 2003

Windows Vista

Windows Server 2008

Windows 7

Windows Server 2008 R2

Windows 8

Windows Server 2012

Windows 8.1

Windows Server 2012 R2

Windows 10

Windows Server 2016

ncacn_nb_tcp

Connection-oriented NetBIOS over TCP

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

ncacn_nb_ipx

Connection-oriented NetBIOS over IPX

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

ncacn_nb_nb

Connection-oriented NetBEUI

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

ncacn_np

Connection-oriented named pipes

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

Windows XP

Windows Server 2003

ncacn_spx

Connection-oriented SPX

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

Windows Server 2003 (x86 editions)

ncacn_dnet_nsp

Connection-oriented DECnet transport

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

Windows XP

Windows Server 2003

ncacn_at_dsp

AppleTalk DSP

Windows 2000

Windows XP

Windows Server 2003

Windows 2000

Windows XP

Windows Server 2003

ncacn_vnns_spp

Connection-oriented Vines SPP transport

Windows 2000

Windows XP

Windows Server 2003

None. For historical reasons, the COMA server on Windows 2000, Windows XP, and Windows Server 2003 accepts this value to represent Banyan Vines SPP instead of the value "ncacn_vns_spp" used by the RPC and DCOM protocol implementations on Windows. It does not represent a valid RPC protocol sequence.

ncadg_ip_udp

Datagram UDP/IP

Windows 2000

Windows XP

Windows Server 2003

None.

ncadg_ipx

Datagram IPX

Windows 2000

Windows XP

Windows Server 2003

None.

<25> Section 2.2.2.21.4:  Windows XP operating system Service Pack 2 (SP2), Windows XP operating system Service Pack 3 (SP3), Windows Server 2003 operating system with Service Pack 1 (SP1), Windows Server 2003 operating system with Service Pack 2 (SP2), Windows Vista through Windows 10 and Windows Server 2008 through Windows Server 2016  interpret NewVersionComponentDACLs.

<26> Section 2.2.2.21.4:  Windows Vista through Windows 10 and Windows Server 2008 through Windows Server 2016  interpret ComponentSACLs.

<27> Section 2.2.2.22: Applicable Windows Server releases do not enforce constraints on values of type DefaultAuthenticationLevelProperty. Windows clients never pass invalid values of this type.

<28> Section 2.2.2.23: Applicable Windows Server releases do not enforce constraints on values of type ActivationTypeProperty. Windows clients never pass invalid values of this type.

<29> Section 2.2.2.24: For more information about the software restriction property on Windows, see [MSDN-SOFTWRSTRPOLICY].

<30> Section 2.2.2.25: Applicable Windows Server releases do not enforce constraints on values of type DefaultImpersonationLevelProperty. Windows clients never pass invalid values of this type.

<31> Section 2.2.3: On Windows, "DllGetClassObject".

<32> Section 2.2.3: On Windows, a proxy/stub DLL. For more information about proxies and stubs on Windows, see [MSDN-MarshalDetails].

<33> Section 2.2.3: For information about type libraries on Windows, see [MSDN-TypeLibraries].

<34> Section 2.2.3: On Windows, "DllRegisterServer".

<35> Section 2.2.3: On Windows, "DllUnregisterServer".

<36> Section 2.2.4: For information about type libraries on Windows, see [MSDN-TypeLibraries].

<37> Section 3: In Windows, if an activation request for the COMA server object class is received in which the client context contains a transaction context property (see [MS-COM] section 2.2.2.1), the transaction will propagate to the COMA server object's client context. Windows clients never send such an activation request. To avoid inadvertently causing a situation in which the COMA server terminates a client application's transaction, it is recommended that COMA clients never send an activation request in which the client context contains a transaction context property.

<38> Section 3.1.1.1: In Windows, the COMA server configures COM+, also known as Component Services, on the server machine. For more information, see [MSDN-COM+].

<39> Section 3.1.1.1.1: In Windows, this is the transactional functionality of the COM+ protocol. For more information, see [MS-COM].

<40> Section 3.1.1.1.1: Windows provides this facility. For more information, see [MSDN-COM+].

<41> Section 3.1.1.1.2: Windows provides this facility, known as application pooling. For more information, see [MSDN-COM+].

<42> Section 3.1.1.1.2: Windows provides this facility, known as object pooling. For more information, see [MSDN-COM+].

<43> Section 3.1.1.1.3: Windows provides this facility. For more information, see [MSDN-COM+].

<44> Section 3.1.1.1.4: Windows provides this facility, known as COM+ events. For more information, see [MSDN-COM+].

<45> Section 3.1.1.1.5: Windows provides this facility. For more information, see [MSDN-COM+].

<46> Section 3.1.1.1.5: Windows provides this facility. For more information, see [MSDN-COM+].

<47> Section 3.1.1.1.6: Windows does not provide this facility natively, but supports this configuration for the Component Load Balancing feature of Microsoft Application Center. Note that Microsoft Application Center 2000 is only supported in Windows 2000, Windows XP, and Windows Server 2003.

<48> Section 3.1.1.1.7: Windows provides this facility. For more information, see [MSDN-COM+].

<49> Section 3.1.1.2.3: The following versions of Windows support the multiple-bitness capability:

  • Windows XP (x64 and Itanium Editions)

  • Windows Server 2003 (x64 and Itanium Editions)

  • Windows Vista (x64 Editions)

  • Windows Server 2008 (x64 and Itanium Editions)

  • Windows 7 (x64 Editions)

  • Windows Server 2008 R2 (x64 and Itanium Editions)

  • Windows 8 (x64 Editions)

  • Windows Server 2012 (x64 and Itanium Editions)

  • Windows 8.1

  • Windows Server 2012 R2

  • Windows 10

  • Windows Server 2016

<50> Section 3.1.1.2.7: Windows does this.

<51> Section 3.1.1.2.7: Windows does not enforce this for all internal properties.

<52> Section 3.1.1.2.9: Windows does this.

<53> Section 3.1.1.2.9: Windows does this.

<54> Section 3.1.1.2.9: Windows does this.

<55> Section 3.1.1.2.11: Windows does this.

<56> Section 3.1.1.3.1: On Windows platforms, this is the "CLSID" property of the components collection; see [MSDN-COMADMIN].

<57> Section 3.1.1.3.1: On Windows platforms, this is the "DLL" property of the components collection; see [MSDN-COMADMIN].

<58> Section 3.1.1.3.1: On Windows platforms, this is the "ThreadingModel" property of the components collection; see [MSDN-COMADMIN].

<59> Section 3.1.1.3.1: On Windows platforms, this is the "Name" property of the components collection; see [MSDN-COMADMIN].

<60> Section 3.1.1.3.1: On Windows platforms, this is the "Description" property of the components collection; see [MSDN-COMADMIN].

<61> Section 3.1.1.3.1: On Windows platforms, this is the "Bitness" property of the components collection; see [MSDN-COMADMIN].

<62> Section 3.1.1.3.1: On Windows platforms, this is the "VersionMajor" property of the components collection; see [MSDN-COMADMIN].

<63> Section 3.1.1.3.1: On Windows platforms, this is the "VersionMinor" property of the components collection; see [MSDN-COMADMIN].

<64> Section 3.1.1.3.1: On Windows platforms, this is the "VersionBuild" property of the components collection; see [MSDN-COMADMIN].

<65> Section 3.1.1.3.1: On Windows platforms, this is the "VersionSubBuild" property of the components collection; see [MSDN-COMADMIN].

<66> Section 3.1.1.3.1: On Windows platforms, this is the "InitializesServerApplication" property of the components collection; see [MSDN-COMADMIN].

<67> Section 3.1.1.3.1:  On Windows platforms, this is the "Transaction" property of the components collection; see [MSDN-COMADMIN].

<68> Section 3.1.1.3.1: On Windows platforms, this is the "Synchronization" property of the components collection; see [MSDN-COMADMIN].

<69> Section 3.1.1.3.1: On Windows platforms, this is the "IISIntrinsics" property of the components collection; see [MSDN-COMADMIN].

<70> Section 3.1.1.3.1: On Windows platforms, this is the "COMTIIntrinsics" property of the components collection; see [MSDN-COMADMIN].

<71> Section 3.1.1.3.1: On Windows platforms, this is the "JustInTimeActivation" property of the components collection; see [MSDN-COMADMIN].

<72> Section 3.1.1.3.1: On Windows platforms, this is the "ComponentAccessChecksEnabled" property of the components collection; see [MSDN-COMADMIN].

<73> Section 3.1.1.3.1: On Windows platforms, this is the "MinPoolSize" property of the components collection; see [MSDN-COMADMIN].

<74> Section 3.1.1.3.1: On Windows platforms, this is the "MaxPoolSize" property of the components collection; see [MSDN-COMADMIN].

<75> Section 3.1.1.3.1: On Windows platforms, this is the "CreationTimeout" property of the components collection; see [MSDN-COMADMIN].

<76> Section 3.1.1.3.1: On Windows platforms, this is the "ConstructorString" property of the components collection; see [MSDN-COMADMIN].

<77> Section 3.1.1.3.1: On Windows platforms, this is the "MustRunInDefaultContext" property of the components collection; see [MSDN-COMADMIN].

<78> Section 3.1.1.3.1: On Windows platforms, this is the "MustRunInClientContext" property of the components collection; see [MSDN-COMADMIN].

<79> Section 3.1.1.3.1: On Windows platforms, this is the "EventTrackingEnabled" property of the components collection; see [MSDN-COMADMIN]. The activity statistics collected for the component can be retrieved by a client via the COM+ Tracking Service (COMT) Protocol. For more information; see [MS-COMT].

<80> Section 3.1.1.3.1: On Windows platforms, this is the "LoadBalancingSupported" property of the components collection; see [MSDN-COMADMIN].

<81> Section 3.1.1.3.1: On Windows platforms, this is the "ConstructionEnabled" property of the components collection; see [MSDN-COMADMIN].

<82> Section 3.1.1.3.1: On Windows platforms, this is the "ObjectPoolingEnabled" property of the components collection; see [MSDN-COMADMIN].

<83> Section 3.1.1.3.1: On Windows platforms, this is the "ExceptionClass" property of the components collection; see [MSDN-COMADMIN].

<84> Section 3.1.1.3.1: On Windows platforms, this is the "IsEventClass" property of the components collection; see [[MSDN-COMADMIN].

<85> Section 3.1.1.3.1: On Windows platforms, this is the "PublisherID" property of the components collection; see [MSDN-COMADMIN].

<86> Section 3.1.1.3.1: On Windows platforms, this is the "MultiInterfacePublisherFilterCLSID" property of the components collection; see [MSDN-COMADMIN].

<87> Section 3.1.1.3.1: On Windows platforms, this is the "AllowInprocSubscribers" property of the components collection; see [MSDN-COMADMIN].

<88> Section 3.1.1.3.1: On Windows platforms, this is the "FireInParallel" property of the components collection; see [MSDN-COMADMIN].

<89> Section 3.1.1.3.1: On Windows platforms, this is the "TransactionTimeout" property of the components collection; see [MSDN-COMADMIN]. This is used to configure the timeout of COM+ transactions on a per-component basis. For more information, see [MS-COM] section 1.3.2.

<90> Section 3.1.1.3.1: On Windows platforms, this is the "IsEnabled" property of the components collection; see [MSDN-COMADMIN].

<91> Section 3.1.1.3.1: On Windows platforms, this is the "TxIsolationLevel" property of the components collection; see [MSDN-COMADMIN].

<92> Section 3.1.1.3.1: On Windows platforms, this is the "IsPrivateComponent" property of the components collection; see [MSDN-COMADMIN].

<93> Section 3.1.1.3.1: On Windows platforms, this is the "SoapAssemblyName" property of the components collection; see [MSDN-COMADMIN].

<94> Section 3.1.1.3.1: On Windows platforms, this is the "SoapTypeName" property of the components collection; see [MSDN-COMADMIN].

<95> Section 3.1.1.3.3: On Windows platforms, this is the "CLSID" property of the legacy components collection; see [MSDN-COMADMIN].

<96> Section 3.1.1.3.3: On Windows platforms, this is the "Bitness" property of the legacy collection; see [MSDN-COMADMIN].

<97> Section 3.1.1.3.3: On Windows platforms, this is the "Description" property of the legacy components collection; see [MSDN-COMADMIN].

<98> Section 3.1.1.3.3: On Windows platforms, this is the "ProgID" property of the legacy components collection; see [MSDN-COMADMIN].

<99> Section 3.1.1.3.3: On Windows platforms, this is the "InprocServer32" property of the legacy components collection; see [MSDN-COMADMIN].

<100> Section 3.1.1.3.3: On Windows platforms, this is the "InprocHandler32" property of the legacy components collection; see [MSDN-COMADMIN].

<101> Section 3.1.1.3.3: On Windows platforms, this is the "ThreadingModel" property of the legacy components collection; see [MSDN-COMADMIN].

<102> Section 3.1.1.3.3: On Windows platforms, this is the "DLL" property of the components collection; see [MSDN-COMADMIN].

<103> Section 3.1.1.3.3: On Windows platforms this is the "LocalServer32" property of the legacy components collection, see [MSDN-COMADMIN].

<104> Section 3.1.1.3.3: On Windows platforms, this is the "AppID" property of the legacy components collection; see [MSDN-COMADMIN].

<105> Section 3.1.1.3.3: On Windows platforms, this is the "ClassName" property of the legacy components collection; see [MSDN-COMADMIN].

<106> Section 3.1.1.3.3: On Windows platforms, this is the "RemoteServer" property of the legacy components collection; see [MSDN-COMADMIN].

<107> Section 3.1.1.3.3: On Windows platforms, this is the "LocalService" property of the legacy components collection; see [MSDN-COMADMIN].

<108> Section 3.1.1.3.3: On Windows platforms, this is the "ServiceParameters" property of the legacy components collection; see [MSDN-COMADMIN].

<109> Section 3.1.1.3.3: On Windows platforms, this is the "DllSurrogate" property of the legacy components collection; see [MSDN-COMADMIN].

<110> Section 3.1.1.3.3: On Windows platforms, this is the "RunAs" property of the legacy components collection; see [MSDN-COMADMIN].

<111> Section 3.1.1.3.3: On Windows platforms, this is the "Password" property of the legacy components collection; see [MSDN-COMADMIN].

<112> Section 3.1.1.3.3: On Windows platforms, this is the "ActivateAtStorage" property of the legacy components collection; see [MSDN-COMADMIN].

<113> Section 3.1.1.3.3: On Windows platforms, this is the "AccessPermissions" property of the legacy components collection; see [MSDN-COMADMIN].

<114> Section 3.1.1.3.3: On Windows platforms, this is the "LaunchPermissions" property of the legacy components collection; see [MSDN-COMADMIN].

<115> Section 3.1.1.3.3: On Windows platforms, this is the "AuthenticationLevel" property of the legacy components collection; see [MSDN-COMADMIN].

<116> Section 3.1.1.3.3: On Windows platforms, this is the "SRPTrustLevel" property of the legacy components collection; see [MSDN-COMADMIN].

<117> Section 3.1.1.3.4: On Windows platforms, this is the "CLSID" property of the WowInprocServers, WowLegacyServers, InprocServers, or LegacyServers collection; see [MSDN-COMADMIN].

<118> Section 3.1.1.3.4: On Windows platforms, this is the "InprocServer32" property of the WowInprocServers, WowLegacyServers, InprocServers, or LegacyServers collection; see [MSDN-COMADMIN].

<119> Section 3.1.1.3.4: On Windows platforms, this is the "LocalServer32" property of the WowLegacyServers or LegacyServers collection; see [MSDN-COMADMIN].

<120> Section 3.1.1.3.4: On Windows platforms, this is the "ProgID" property of the WowInprocServers, WowLegacyServers, InprocServers, or LegacyServers collection; see [MSDN-COMADMIN].

<121> Section 3.1.1.3.5: On Windows platforms, this is the "CLSID" property of the WowInprocServers, WowLegacyServers, InprocServers, or LegacyServers collection; see [MSDN-COMADMIN].

<122> Section 3.1.1.3.5: On Windows platforms, this is the "InprocServer32" property of the WowInprocServers, WowLegacyServers, InprocServers, or LegacyServers collection; see [MSDN-COMADMIN].

<123> Section 3.1.1.3.5: On Windows platforms, this is the "LocalServer32" property of the WowLegacyServers or LegacyServers collection; see [MSDN-COMADMIN].

<124> Section 3.1.1.3.5: On Windows platforms, this is the "ProgID" property of the WowInprocServers, WowLegacyServers, InprocServers, or LegacyServers collection; see [MSDN-COMADMIN].

<125> Section 3.1.1.3.6: Windows uses only the reserved container identifiers for protected conglomeration.

<126> Section 3.1.1.3.6: On Windows platforms, this is the "ID" property of the Applications collection; see [MSDN-COMADMIN].

<127> Section 3.1.1.3.6: On Windows platforms, this is the "Name" property of the Applications collection; see [MSDN-COMADMIN].

<128> Section 3.1.1.3.6: On Windows platforms, this is the "ApplicationProxyServerName" property of the Applications collection; see [MSDN-COMADMIN].

<129> Section 3.1.1.3.6: On Windows platforms, this is the "CommandLine" property of the Applications collection; see [MSDN-COMADMIN].

<130> Section 3.1.1.3.6: On Windows platforms, this is the "SeviceName" property of the Applications collection; see [MSDN-COMADMIN].

<131> Section 3.1.1.3.6: On Windows platforms, this is the "Identity" property of the Applications collection; see [MSDN-COMADMIN].

<132> Section 3.1.1.3.6: On Windows platforms, this is the "Description" property of the Applications collection; see [MSDN-COMADMIN].

<133> Section 3.1.1.3.6: On Windows platforms, this is the "IsSystem" property of the Applications collection; see [MSDN-COMADMIN].

<134> Section 3.1.1.3.6: On Windows platforms, this is the "Authentication" property of the Applications collection; see [MSDN-COMADMIN].

<135> Section 3.1.1.3.6: On Windows platforms, for conglomerations with Activation set to "Inproc", the Authentication property is constrained to the following values and has the special meanings described below.

Value

Special meaning for Activation set to FALSE

RPC_C_AUTHN_LEVEL_DEFAULT

Windows applies the creating process's authentication level for both incoming DCOM calls to and outgoing DCOM calls from instance containers associated with the conglomeration.

RPC_C_AUTHN_LEVEL_NONE

Windows applies the creating process's authentication level for outgoing DCOM calls from instance containers associated with the conglomeration. Windows accepts incoming DCOM calls to these instance containers at any authentication level. Furthermore, Windows allows calls to these instance containers to bypass the access check normally applied to incoming DCOM calls to the process.

<136> Section 3.1.1.3.6: On Windows platforms, this is the "ShutdownAfter" property of the Applications collection; see [MSDN-COMADMIN].

<137> Section 3.1.1.3.6: On Windows platforms, this is the "RunForever" property of the Applications collection; see [MSDN-COMADMIN].

<138> Section 3.1.1.3.6: On Windows platforms, this is the "Password" property of the Applications collection; see [MSDN-COMADMIN].

<139> Section 3.1.1.3.6: On Windows platforms, this is the "Activation" property of the Applications collection; see [MSDN-COMADMIN].

<140> Section 3.1.1.3.6: On Windows platforms, this is the "Changeable" property of the Applications collection; see [MSDN-COMADMIN].

<141> Section 3.1.1.3.6: On Windows platforms, this is the "Deleteable" property of the Applications collection; see [MSDN-COMADMIN].

<142> Section 3.1.1.3.6: On Windows platforms, this is the "CreatedBy" property of the Applications collection; see [MSDN-COMADMIN].

<143> Section 3.1.1.3.6: On Windows platforms, this is the "ApplicationAccessChecksEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<144> Section 3.1.1.3.6: On Windows platforms, this is the "ImpersonationLevel" property of the Applications collection; see [MSDN-COMADMIN].

<145> Section 3.1.1.3.6: On Windows platforms, this is the "AuthenticationCapabilities" property of the Applications collection; see [MSDN-COMADMIN].

<146> Section 3.1.1.3.6: On Windows platforms, this is the "CRMEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<147> Section 3.1.1.3.6: On Windows platforms, this is the "3GigSupportEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<148> Section 3.1.1.3.6: On Windows platforms, this is the "QueuingEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<149> Section 3.1.1.3.6: On Windows platforms, this is the "QCListenerEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<150> Section 3.1.1.3.6: On Windows platforms, this is the "EnableEvents" property of the Applications collection; see [MSDN-COMADMIN].

<151> Section 3.1.1.3.6: On Windows platforms, this is the "ApplicationProxy" property of the Applications collection; see [MSDN-COMADMIN].

<152> Section 3.1.1.3.6: On Windows platforms, this is the "CRMLogFile" property of the Applications collection; see [MSDN-COMADMIN].

<153> Section 3.1.1.3.6: On Windows platforms, this is the "DumpEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<154> Section 3.1.1.3.6: On Windows platforms, this is the "DumpOnException" property of the Applications collection; see [MSDN-COMADMIN].

<155> Section 3.1.1.3.6: On Windows platforms, this is the "DumpOnFailFast" property of the Applications collection; see [MSDN-COMADMIN].

<156> Section 3.1.1.3.6: On Windows platforms, this is the "MaxDumpCount" property of the Applications collection; see [MSDN-COMADMIN].

<157> Section 3.1.1.3.6: On Windows platforms, this is the "DumpPath" property of the Applications collection; see [MSDN-COMADMIN].

<158> Section 3.1.1.3.6: On Windows platforms, this is the "IsEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<159> Section 3.1.1.3.6: On Windows platforms, this is the "ConcurrentApps" property of the Applications collection; see [MSDN-COMADMIN].

<160> Section 3.1.1.3.6: On Windows platforms, this is the "RecyclingLifetimeLimit" property of the Applications collection; see [MSDN-COMADMIN].

<161> Section 3.1.1.3.6: On Windows platforms, this is the "RecycleCallLimit" property of the Applications collection; see [MSDN-COMADMIN].

<162> Section 3.1.1.3.6: On Windows platforms, this is the "RecycleActivationLimit" property of the Applications collection; see [MSDN-COMADMIN].

<163> Section 3.1.1.3.6: On Windows platforms, this is the "RecycleMemoryLimit" property of the Applications collection; see [MSDN-COMADMIN].

<164> Section 3.1.1.3.6: On Windows platforms, this is the "RecycleExpirationTimeout" property of the Applications collection; see [MSDN-COMADMIN].

<165> Section 3.1.1.3.6: On Windows platforms, this is the "QCListenerEnabled" property of the Applications collection; see [MSDN-COMADMIN].

<166> Section 3.1.1.3.6: On Windows platforms, this is the "QcAuthenticateMsgs" property of the Applications collection; see [MSDN-COMADMIN].

<167> Section 3.1.1.3.6: On Windows platforms, this is the "ApplicationDirectory" property of the legacy components collection; see [MSDN-COMADMIN].

<168> Section 3.1.1.3.6: On Windows platforms, this is the "SRPTrustLevel" property of the legacy components collection; see [MSDN-COMADMIN].

<169> Section 3.1.1.3.6: On Windows platforms, this is the "SRPEnabled" property of the legacy components collection; see [MSDN-COMADMIN].

<170> Section 3.1.1.3.6: On Windows platforms, this is the "SoapActivated" property of the legacy components collection; see [MSDN-COMADMIN].

<171> Section 3.1.1.3.6: On Windows platforms, this is the "SoapVRoot" property of the legacy components collection; see [MSDN-COMADMIN].

<172> Section 3.1.1.3.6: On Windows platforms, this is the "SoapMailTo" property of the legacy components collection; see [MSDN-COMADMIN].

<173> Section 3.1.1.3.6: On Windows platforms, this is the "SoapBaseUrl" property of the legacy components collection; see [MSDN-COMADMIN].

<174> Section 3.1.1.3.6: On Windows platforms, this is the "Replicable" property of the legacy components collection; see [MSDN-COMADMIN].

<175> Section 3.1.1.3.6: The replication client applications provided with Windows platforms do not replicate conglomerations whose Replicable property has a value of FALSE (0x00000000).

<176> Section 3.1.1.3.7: Windows adds a single entry with the Name property "Activators" to the PartitionRoles table for each partition created.

<177> Section 3.1.1.3.7: On Windows platforms, this is the "ID" property of the Partitions collection; see [MSDN-COMADMIN].

<178> Section 3.1.1.3.7: On Windows platforms, this is the "Name" property of the Partitions collection; see [MSDN-COMADMIN].

<179> Section 3.1.1.3.7: On Windows platforms, this is the "Description" property of the Partitions collection; see [MSDN-COMADMIN].

<180> Section 3.1.1.3.7: On Windows platforms, this is the "Changeable" property of the Partitions collection; see [MSDN-COMADMIN].

<181> Section 3.1.1.3.7: On Windows platforms, this is the "Deleteable" property of the Partitions collection; see [MSDN-COMADMIN].

<182> Section 3.1.1.3.8: On Windows platforms, this is the "Description" property of the LocalComputer collection; see [MSDN-COMADMIN].

<183> Section 3.1.1.3.8: On Windows platforms, this is the "TransactionTimeout" property of the LocalComputer collection; see [MSDN-COMADMIN].

<184> Section 3.1.1.3.8: On Windows platforms, this is the "ResourcePoolingEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<185> Section 3.1.1.3.8: On Windows platforms, this is the "IsRouter" property of the LocalComputer collection; see [MSDN-COMADMIN].

<186> Section 3.1.1.3.8: On Windows platforms, this is the "EnableDCOM" property of the LocalComputer collection; see [MSDN-COMADMIN].

<187> Section 3.1.1.3.8: On Windows platforms, this is the "DefaultAuthenticationLevel" property of the LocalComputer collection; see [MSDN-COMADMIN].

<188> Section 3.1.1.3.8: On Windows platforms, this is the "DefaultImpersonationLevel" property of the LocalComputer collection; see [MSDN-COMADMIN].

<189> Section 3.1.1.3.8: On Windows platforms, this is the "SecurityTrackingEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<190> Section 3.1.1.3.8: On Windows platforms, this is the "CISEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<191> Section 3.1.1.3.8: On Windows platforms, this is the "SecureReferenceEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<192> Section 3.1.1.3.8: On Windows platforms, this is the "InternetPortsListed" property of the LocalComputer collection; see [MSDN-COMADMIN].

<193> Section 3.1.1.3.8: On Windows platforms, this is the "DefaultToInternetPorts" property of the LocalComputer collection; see [MSDN-COMADMIN].

<194> Section 3.1.1.3.8: On Windows platforms, this is the "Ports" property of the LocalComputer collection; see [MSDN-COMADMIN].

<195> Section 3.1.1.3.8: On Windows platforms, this is the "DSPartitionLookupEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<196> Section 3.1.1.3.8: On Windows platforms, this is the "RpcProxyEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<197> Section 3.1.1.3.8: On Windows platforms, this is the "OperatingSystem" property of the LocalComputer collection; see [MSDN-COMADMIN].

<198> Section 3.1.1.3.8: On Windows platforms, this is the "LoadBalancingCLSID" property of the LocalComputer collection; see [MSDN-COMADMIN].

<199> Section 3.1.1.3.8: On Windows platforms, this is the "SRPRunningObjectChecks" property of the LocalComputer collection; see [MSDN-COMADMIN].

<200> Section 3.1.1.3.8: On Windows platforms, this is the "SRPActivateAsActivatorChecks" property of the LocalComputer collection; see [MSDN-COMADMIN].

<201> Section 3.1.1.3.8: On Windows platforms, this is the "PartitionsEnabled" property of the LocalComputer collection; see [MSDN-COMADMIN].

<202> Section 3.1.1.3.9: On Windows platforms, this is the "Name" property of the Roles collection; see [MSDN-COMADMIN].

<203> Section 3.1.1.3.9: On Windows platforms, this is the "Description" property of the Roles collection; see [MSDN-COMADMIN].

<204> Section 3.1.1.3.10: On Windows platforms, this is the "User" property of the UserInRole collection; see [MSDN-COMADMIN].

<205> Section 3.1.1.3.11: On Windows platforms, this is the "IID" property of the InterfacesForComponent collection; see [MSDN-COMADMIN].

<206> Section 3.1.1.3.11: On Windows platforms, this is the "Name" property of the InterfacesForComponent collection; see [MSDN-COMADMIN].

<207> Section 3.1.1.3.11: On Windows platforms, this is the "QueuingEnabled" property of the InterfacesForComponent collection; see [MSDN-COMADMIN].

<208> Section 3.1.1.3.11: On Windows platforms, this is the "QueuingSupported" property of the InterfacesForComponent collection; see [MSDN-COMADMIN].

<209> Section 3.1.1.3.11: On Windows platforms, this is the "Description" property of the InterfacesForComponent collection; see [MSDN-COMADMIN].

<210> Section 3.1.1.3.12: On Windows platforms, this is the "CLSID" property of the MethodsForInterface collection; see [MSDN-COMADMIN].

<211> Section 3.1.1.3.12: On Windows platforms, this is the "IID" property of the MethodsForInterface collection; see [MSDN-COMADMIN].

<212> Section 3.1.1.3.12: On Windows platforms, this is the "Index" property of the MethodsForInterface collection; see [MSDN-COMADMIN].

<213> Section 3.1.1.3.12: On Windows platforms, this is the "Name" property of the MethodsForInterface collection; see [MSDN-COMADMIN].

<214> Section 3.1.1.3.12: On Windows platforms, this is the "AutoComplete" property of the MethodsForInterface collection; see [MSDN-COMADMIN].

<215> Section 3.1.1.3.12: On Windows platforms, this is the "Description" property of the MethodsForInterface collection; see [MSDN-COMADMIN].

<216> Section 3.1.1.3.13: On Windows platforms, this is the "Name" property of the RolesForComponent collection; see [MSDN-COMADMIN].

<217> Section 3.1.1.3.14: On Windows platforms, this is the "Name" property of the RolesForInterface collection; see [MSDN-COMADMIN].

<218> Section 3.1.1.3.15: On Windows platforms, this is the "Name" property of the RolesForMethod collection; see [MSDN-COMADMIN].

<219> Section 3.1.1.3.16: On Windows platforms, this is the "AccountName" property of the PartitionUsers collection; see [MSDN-COMADMIN].

<220> Section 3.1.1.3.16: On Windows platforms, this is the "DefaultPartitionID" property of the PartitionUsers collection; see [MSDN-COMADMIN].

<221> Section 3.1.1.3.17: On Windows platforms, this is the "Name" property of the RolesForPartition collection; see [MSDN-COMADMIN].

<222> Section 3.1.1.3.17: On Windows platforms, this is the "Description" property of the RolesForPartition collection; see [MSDN-COMADMIN].

<223> Section 3.1.1.3.18: On Windows platforms, this is the "User" property of the UserInPartitionRole collection; see [MSDN-COMADMIN].

<224> Section 3.1.1.3.19: On Windows platforms, this is the "Name" property of the ApplicationCluster collection; see [MSDN-COMADMIN].

<225> Section 3.1.1.3.20: On Windows, this table is used to provide the list of server machines displayed in the Component Services MMC snap-in on the local machine.

<226> Section 3.1.1.3.20: On Windows platforms, this is the "Name" property of the ComputerList collection; see [MSDN-COMADMIN].

<227> Section 3.1.1.3.21: On Windows platforms, this is the "InstanceID" property of the ApplicationInstances collection; see [MSDN-COMADMIN].

<228> Section 3.1.1.3.21: On Windows platforms, this is the "Application" property of the ApplicationInstances collection; see [MSDN-COMADMIN].

<229> Section 3.1.1.3.21: On Windows platforms, this is the "PartitionID" property of the ApplicationInstances collection; see [MSDN-COMADMIN].

<230> Section 3.1.1.3.21: On Windows platforms, this is the "ProcessID" property of the ApplicationInstances collection; see [MSDN-COMADMIN].

<231> Section 3.1.1.3.21: On Windows platforms, this is the "IsPaused" property of the ApplicationInstances collection; see [MSDN-COMADMIN].

<232> Section 3.1.1.3.21: On Windows platforms, this is the "HasRecycled" property of the ApplicationInstances collection; see [MSDN-COMADMIN].

<233> Section 3.1.1.3.22: On Windows platforms, this is the "Application" property of the EventClassesForIID collection; see [MSDN-COMADMIN].

<234> Section 3.1.1.3.22: On Windows platforms, this is the "Bitness" property of the EventClassesForIID collection; see [MSDN-COMADMIN].

<235> Section 3.1.1.3.22: On Windows platforms, this is the "Name" property of the EventClassesForIID collection; see [MSDN-COMADMIN].

<236> Section 3.1.1.3.22: On Windows platforms, this is the "Description" property of the EventClassesForIID collection; see [MSDN-COMADMIN].

<237> Section 3.1.1.3.22: On Windows platforms, this is the "IsPrivateComponent" property of the EventClassesForIID collection; see [MSDN-COMADMIN].

<238> Section 3.1.1.3.23: The size of the Internal1 property is given as follows for different versions of Windows.

Windows version

Size of Internal1

Windows 2000

4

Windows XP (x86 Editions)

4

Windows XP (x64 and Itanium Editions)

8

Windows Server 2003 (x86 Editions)

4

Windows Server 2003 (x64 and Itanium Editions)

8

Windows Vista (x86 Editions)

4

Windows Vista (x64 Editions)

8

Windows Server 2008 (x86 Editions)

4

Windows Server 2008 (x64 and Itanium Editions)

8

Windows 7 (x86 Editions)

4

Windows 7 (x64 Editions)

8

Windows Server 2008 R2 (x86 Editions)

4

Windows Server 2008 R2 (x64 and Itanium Editions)

8

Windows 8 (x86 Editions)

4

Windows 8 (x64 Editions)

8

Windows Server 2012 (x86 Editions)

4

Windows Server 2012 (x64 and Itanium Editions)

8

Windows 8.1

4

Windows Server 2012 R2

8

Windows 10

4

Windows Server 2016

8

<239> Section 3.1.1.3.23: On Windows platforms, this is the "ID" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<240> Section 3.1.1.3.23: On Windows platforms, this is the "Name" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<241> Section 3.1.1.3.23: On Windows platforms, this is the "EventCLSID" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<242> Section 3.1.1.3.23: On Windows platforms, this is the "MethodName" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<243> Section 3.1.1.3.23: On Windows platforms, this is the "PerUser" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<244> Section 3.1.1.3.23: On Windows platforms, this is the "UserName" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<245> Section 3.1.1.3.23: On Windows platforms, this is the "Enabled" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<246> Section 3.1.1.3.23: On Windows platforms, this is the "Description" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<247> Section 3.1.1.3.23: On Windows platforms, this is the "MachineName" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<248> Section 3.1.1.3.23: On Windows platforms, this is the "PublisherID" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<249> Section 3.1.1.3.23: On Windows platforms, this is the "InterfaceID" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<250> Section 3.1.1.3.23: On Windows platforms, this is the "FilterCriteria" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<251> Section 3.1.1.3.23: On Windows platforms, this is the "SubscriberMoniker" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<252> Section 3.1.1.3.23: On Windows platforms, this is the "Queued" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<253> Section 3.1.1.3.23: On Windows platforms, this is the "EventClassPartitionID" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<254> Section 3.1.1.3.23: On Windows platforms, this is the "SubscriberPartitionID" property of the SubscriptionsForComponent collection; see [MSDN-COMADMIN].

<255> Section 3.1.1.3.24: On Windows platforms, this is the "Name" property of the PublisherProperties collection; see [MSDN-COMADMIN].

<256> Section 3.1.1.3.24: On Windows platforms, this is the "Value" property of the PublisherProperties collection; see [MSDN-COMADMIN].

<257> Section 3.1.1.3.25: On Windows platforms, this is the "Name" property of the SubscriberProperties collection, see [MSDN-COMADMIN].

<258> Section 3.1.1.3.25: On Windows platforms, this is the "Value" property of the SubscriberProperties collection, see [MSDN-COMADMIN].

<259> Section 3.1.1.3.26: On Windows platforms, this is the "ProtocolCode" property of the DCOM Protocols collection; see [MSDN-COMADMIN].

<260> Section 3.1.1.3.26: On Windows platforms, this is the "Order" property of the DCOMProtocols collection; see [MSDN-COMADMIN].

<261> Section 3.1.1.3.26: On Windows platforms, this is the "Name" property of the DCOM Protocols collection; see [MSDN-COMADMIN].

<262> Section 3.1.1.3.27: On Windows platforms, this is the "ApplicationFileName" property of the FilesForImport collection; see [MSDN-COMADMIN].

<263> Section 3.1.1.3.27: On Windows platform, this is the "FileName" property of the FilesForImport collection; see [MSDN-COMADMIN].

<264> Section 3.1.1.3.27: On Windows platforms, this is the "ApplicationName" property of the FilesForImport collection; see [MSDN-COMADMIN].

<265> Section 3.1.1.3.27: On Windows platforms, this is the "Description" property of the FilesForImport collection; see [MSDN-COMADMIN].

<266> Section 3.1.1.3.27: On Windows platforms, this is the "HasUsers" property of the FilesForImport collection; see [MSDN-COMADMIN].

<267> Section 3.1.1.3.27: On Windows platforms, this is the "IsProxy" property of the FilesForImport collection; see [MSDN-COMADMIN].

<268> Section 3.1.1.3.27: On Windows platforms, this is the "IsService" property of the FilesForImport collection; see [MSDN-COMADMIN].

<269> Section 3.1.1.3.27: On Windows platforms ,this is the "PartitionName" property of the FilesForImport collection; see [MSDN-COMADMIN].

<270> Section 3.1.1.3.27: On Windows platforms, this is the "PartitionDescription" property of the FilesForImport collection; see [MSDN-COMADMIN].

<271> Section 3.1.1.3.27: On Windows platforms, this is the "PartitionID" property of the FilesForImport collection; see [MSDN-COMADMIN].

<272> Section 3.1.1.4: On Windows, an alternate launch configuration is used to configure a Windows service.

<273> Section 3.1.1.4: On Windows, this maps to the dwStartType field of the QUERY_SERVICE_CONFIGW structure as specified in [MS-SCMR] section 2.2.15.

<274> Section 3.1.1.4: On Windows, this maps to the dwErrorControl field of the QUERY_SERVICE_CONFIGW structure as specified in [MS-SCMR] section 2.2.15.

<275> Section 3.1.1.4: On Windows, this maps to the lpDependencies field of the QUERY_SERVICE_CONFIGW structure as specified in [MS-SCMR] section 2.2.15.

<276> Section 3.1.1.4: On Windows, this maps to the ObjectName field for a service as specified in [MS-SCMR] section 3.1.1.

<277> Section 3.1.1.4: On Windows, this maps to the Password field for a service as specified in [MS-SCMR] section 3.1.1.

<278> Section 3.1.1.4: On Windows, this maps to the SERVICE_INTERACTIVE_PROCESS flag for the dwServiceType field of the QUERY_SERVICE_CONFIGW structure as specified in [MS-SCMR] section 2.2.15.

<279> Section 3.1.4: Different versions of Windows support the COMA interfaces as follows:

 

Windows 2000

Windows XP

Windows Server 2003

Windows Vista

Windows Server 2008

Windows 7

Windows Server 2008 R2

Windows 8

Windows Server 2012

Windows 8.1

Windows Server 2012 R2

Windows 10

Windows Server 2016

ICatalogSession

X

X

X

X

X

X

X

X

X

X

X

X

X

ICatalog64BitSupport

X

X

X

X

X

X

X

X

X

X

X

X

ICatalogTableInfo

X

X

X

X

X

X

X

X

X

X

X

X

X

ICatalogTableRead

X

X

X

X

X

X

X

X

X

X

X

X

X

ICatalogTableWrite

X

X

X

X

X

X

X

X

X

X

X

X

X

IRegister

X

X

X

X

X

X

X

X

X

X

X

X

X

IRegister2

X

X

X

X

X

X

X

X

X

X

X

X

IImport

X

X

X

X

X

X

X

X

X

X

X

X

X

IImport2

X

X

X

X

X

X

X

X

X

X

X

X

IExport

X

X

X

X

X

X

X

X

X

X

X

X

X

IExport2

X

X

X

X

X

X

X

X

X

X

X

X

IAlternateLaunch

X

X

X

X

X

X

X

X

X

X

X

X

X

ICatalogUtils

X

X

X

X

X

X

X

X

X

X

X

X

X

ICatalogUtils2

X

X

X

X

X

X

X

X

X

X

X

X

ICapabilitySupport

X

X

X

X

X

X

X

X

X

X

X

X

X

IContainerControl

X

X

X

X

X

X

X

X

X

X

X

X

X

IContainerControl2

X

X

X

X

X

X

X

X

X

X

X

X

IReplicationUtil

X

X

X

X

X

X

X

X

X

X

X

X

X

<280> Section 3.1.4.1: Applicable Windows Server releases support the following catalog versions.

Windows version

Catalog versions

Windows 2000

3.00

Windows XP (x86 Editions)

4.00

Windows XP (x64 and Itanium Editions)

4.00, 5.00

Windows Server 2003

4.00, 5.00

Windows Vista

4.00, 5.00

Windows Server 2008

4.00, 5.00

Windows 7

4.00, 5.00

Windows Server 2008 R2

4.00, 5.00

Windows 8

4.00, 5.00

Windows Server 2012

4.00, 5.00

Windows 8.1

4.00, 5.00

Windows Server 2012 R2

4.00, 5.00

Windows 10

4.00, 5.00

Windows Server 2016

4.00, 5.00

<281> Section 3.1.4.2: For Windows XP through Windows 10 and Windows Server 2003 through Windows Server 2016, the server supports capability negotiation for the 64-bit QueryCell (section 2.2.1.4) marshaling format capability.

<282> Section 3.1.4.3: On Windows XP through Windows 10 and Windows Server 2003 through Windows Server 2016, the client initiates, and the server supports, capability negotiation for the multiple-partition support capability.

<283> Section 3.1.4.4: On Windows XP through Windows 10 and Windows Server 2003 through Windows Server 2016, the client initiates, and the server supports, capability negotiation for the multiple-bitness support capability.

<284> Section 3.1.4.5: Opnums reserved for local use apply to Windows as follows:

Opnum

Description

3

Not used by Windows

4

Not used by Windows

5

Not used by Windows

6

Not used by Windows

<285> Section 3.1.4.7.1: Windows clients interpret this value as the CLSID of the COM class providing functionality appropriate for processing the table.

<286> Section 3.1.4.7.1: Windows clients interpret this value as the CLSID of the COM class providing functionality appropriate for processing the table.

<287> Section 3.1.4.7.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<288> Section 3.1.4.7.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<289> Section 3.1.4.7.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<290> Section 3.1.4.7.1: Applicable Windows Server releases allow additional queries for some tables, intended for local use only. These additional queries are never sent by Windows clients.

<291> Section 3.1.4.8.1: Windows COMA servers use multiple stores for the catalog. If these stores become out of sync with each other (for example, due to changes to one of the stores unrelated to this protocol) and the server detects such an error while performing a read, it provides additional error information about which property is mismatched.

<292> Section 3.1.4.8.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<293> Section 3.1.4.8.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<294> Section 3.1.4.8.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<295> Section 3.1.4.8.1: Applicable Windows Server releases allow additional queries for some tables, intended for local use only. These additional queries are never sent by Windows clients.

<296> Section 3.1.4.8.1: Applicable Windows Server releases accept additional special option values, intended for local use only. These additional special option values are never sent by Windows clients.

<297> Section 3.1.4.9.1: If a client attempts to make an invalid write (for example, attempts to move a component configuration into or out of a non-changeable conglomeration), Windows COMA servers provide additional information, when available, about which property write is invalid. In addition, Windows COMA servers use multiple stores for the catalog. If these stores become out of sync with each other (for example, due to changes to one of the stores unrelated to this protocol) and the server detects such an error while performing a write, it provides additional error information about which property is mismatched.

<298> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce that no adds are written to tables that do not support adds, although these invalid writes might fail during subsequent processing. Windows clients never send these invalid writes.

<299> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce that no adds are written to tables that do not support adds, although these invalid writes might fail during subsequent processing. Windows clients never send these invalid writes.

<300> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce that no adds are written to tables that do not support adds, although these invalid writes might fail during subsequent processing. Windows clients never send these invalid writes.

<301> Section 3.1.4.9.1: Applicable Windows Server releases allow additional queries for some tables, intended for local use only. These additional queries are never sent by Windows clients.

<302> Section 3.1.4.9.1: Applicable Windows Server releases use role-based security configuration for the System Application to determine authorization for writes to tables as follows.

Table

Allowed roles

ServerList table

"Administrator", "Reader"

All other tables

"Administrator"

<303> Section 3.1.4.9.1: If a client attempts to make an invalid write (for example, attempts to move a component configuration into or out of a non-changeable conglomeration), Windows COMA servers provide additional information, when available, about which property write is invalid. In addition, Windows COMA servers use multiple stores for the catalog. If these stores become out of sync with each other (for example, due to changes to one of the stores unrelated to this protocol) and the server detects such an error while performing a write, it provides additional error information about which property is mismatched.

<304> Section 3.1.4.9.1: Applicable Windows Server releases are able to generate multiple detailed errors, but do not guarantee that the detailed error results are complete.

<305> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce that no adds are written to tables that do not support adds, although these invalid writes might fail during subsequent processing. Windows clients never send these invalid writes.

<306> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce that no updates are written to tables that do not support updates, although these invalid writes might fail during subsequent processing. Windows clients never send these invalid writes.

<307> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce that no removes are written to tables that do not support removes, although these invalid writes might fail during subsequent processing. Windows clients never send these invalid writes.

<308> Section 3.1.4.9.1: Applicable Windows Server releases accept additional special option values, intended for local use only. These additional special option values are never sent by Windows clients.

<309> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce restrictions on the values of properties written to the tables. Applicable Windows Server releases do not enforce restrictions on the values of properties written to the tables. Windows clients never send these invalid writes. Windows clients never send these invalid writes.

<310> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce restrictions on the values of properties written to the tables. Applicable Windows Server releases do not enforce restrictions on the values of properties written to the tables. Windows clients never send these invalid writes. Windows clients never send these invalid writes.

<311> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce the restriction that read-only properties must not be written. Windows clients never send these invalid writes.

<312> Section 3.1.4.9.1: Windows does this for the Partitions table.

<313> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce the restriction that read-only properties must not be written. Windows clients never send these invalid writes.

<314> Section 3.1.4.9.1: Applicable Windows Server releases do not enforce the restriction that read-only properties must not be written. Windows clients never send these invalid writes.

<315> Section 3.1.4.9.1: Applicable Windows Server releases do this.

<316> Section 3.1.4.10: Opnums reserved for local use apply to Windows as follows.

opnum

Description

4

Just returns E_NOTIMPL. It is never used.

<317> Section 3.1.4.10.1: Applicable Windows Server releases return the ProgID of the component if it was able to determine this. Otherwise, they return the Curly Braced GUID String Syntax ([MS-DTYP] section 2.3.4.3) representation of the CLSID.

<318> Section 3.1.4.10.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<319> Section 3.1.4.10.1: Windows does not support a nonzero number of elements if any of the modules are managed (.NET) assemblies (for more information, see [MSDN-Assemblies]).

<320> Section 3.1.4.10.1: If any of the modules are managed (.NET) assemblies (for more information, see [MSDN-Assemblies]), Windows performs the registration procedure separately for each managed assembly as a separate transaction, failing the call if any of these operations fail. The remainder of the modules are then registered in a separate transaction, according to the transactional semantics specified.

<321> Section 3.1.4.10.1: Windows does this when a verification is being performed and one of the modules cannot be found.

<322> Section 3.1.4.10.1: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send UNC paths.

<323> Section 3.1.4.10.1: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send Universal Naming Convention paths.

<324> Section 3.1.4.11: Opnums reserved for local use apply to Windows as follows.

opnum

Description

6

Not used by Windows.

7

Not used by Windows.

9

Just returns E_NOTIMPL. It is never used.

<325> Section 3.1.4.11.4: Applicable Windows Server releases return the ProgID of the component if it was able to determine this. Otherwise, they return the Curly Braced GUID String Syntax ([MS-DTYP] section 2.3.4.3) representation of the CLSID.

<326> Section 3.1.4.11.4: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<327> Section 3.1.4.11.4: Windows does not support a nonzero number of elements if any of the modules are managed (.NET) assemblies (for more information, see [MSDN-Assemblies]).

<328> Section 3.1.4.11.4: If any of the modules are managed (.NET) assemblies (for more information, see [MSDN-Assemblies]), Windows performs the registration procedure separately for each managed assembly as a separate transaction, failing the call if any of these operations fail. The remainder of the modules are then registered in a separate transaction, according to the transactional semantics specified.

<329> Section 3.1.4.11.4: Windows does this when a verification is being performed and one of the modules cannot be found.

<330> Section 3.1.4.11.4: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send UNC paths.

<331> Section 3.1.4.11.4: Applicable Windows Server releases do not enforce this restriction when fREGISTER_VERIFYONLY is set in the dwFlags parameter. Windows clients do not pass names of non-existent files when calling this method.

<332> Section 3.1.4.11.4: Applicable Windows Server releases do not enforce this restriction when fREGISTER_VERIFYONLY is set in the dwFlags parameter. Applicable Windows Server releases use internal means to convey to Windows clients that a give file is not recognized as a module.

<333> Section 3.1.4.11.4: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send UNC paths.

<334> Section 3.1.4.12: Opnums reserved for local use apply to Windows as follows:

opnum

Description

5

Not used by Windows.

6

Not used by Windows.

<335> Section 3.1.4.12.1: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send UNC paths.

<336> Section 3.1.4.12.1: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send the UNC paths.

<337> Section 3.1.4.12.1: Applicable Windows Server releases allow additional values for this parameter, intended for local use only. These additional values are never sent by Windows clients.

<338> Section 3.1.4.12.2: Windows also allows local paths, intended for local use. Applicable Windows Server releases always send UNC paths.

<339> Section 3.1.4.13: Opnums reserved for local use apply to Windows as follows.

opnum

Description

4

Not used by Windows.

5

Not used by Windows.

<340> Section 3.1.4.14: Opnums reserved for local use apply to Windows as follows.

opnum

Description

4

Not used by Windows.

5

Not used by Windows.

6

Not used by Windows.

<341> Section 3.1.4.14.1: Applicable Windows Server releases export conglomerations to a Windows Installer [MSDN-WindowsInstaller] format, also known as MSI.

<342> Section 3.1.4.15.1: Applicable Windows Server releases export conglomerations to a Windows Installer [MSDN-WindowsInstaller] format, also known as MSI.

<343> Section 3.1.4.18.3: For Windows XP and later and Windows Server 2003 and later, servers do not verify that the source component is configured in the source conglomeration.

A call to AliasComponent in which the source component is configured in a conglomeration other than the specified source conglomeration has undefined behavior on these versions of Windows.

Windows COMA clients act as a pass-through and do not validate this requirement. It is the responsibility of Windows client applications to provide valid parameters when making such a request.

<344> Section 3.1.4.18.3: Windows uses an internal property in the ComponentsAndFullConfigurations table to associate the new CLSID with the original component.

<345> Section 3.1.4.18.6: Windows XP does not ignore this parameter.

<346> Section 3.1.4.18.6: Windows XP does not do this.

<347> Section 3.1.4.18.6: Windows XP does this.

<348> Section 3.1.4.19: Opnums reserved for local use apply to Windows as follows.

opnum

Description

5

Only used locally by Windows, never remotely.

6

Only used locally by Windows, never remotely.

9

Only used locally by Windows, never remotely.

<349> Section 3.1.4.20.3: Applicable Windows Server releases fix broken CLSID references from the component configuration. This is to support development of components locally on the server using Microsoft Visual Basic, which regenerates CLSIDs each time they are compiled.

<350> Section 3.1.4.21.4: For Windows XP and later and Windows Server 2003 and later, servers do not enforce this requirement; that is, a server will not fail the call if a client passes it an invalid/unknown container identifier.

Windows COMA clients act as a pass-through and do not validate this requirement. It is the responsibility of Windows client applications to provide valid parameters when making such a request.

<351> Section 3.1.4.21.7: Applicable Windows Server releases use the system event log.

<352> Section 3.1.4.22.4: Applicable Windows Server releases keep a local backup of files copied to target replication shares by replication client applications for the two most recent replications in which the server is a replication target. (This action also serves to provide a limited record of replication history). For the purposes of this backup, a replication begins with a call to IReplicationUtil::BeginReplicationAsTarget. If a replication client application either fails to call IReplicationUtil::BeginReplicationAsTarget or copies conglomerations to the server in any other manner except by copying the installer package files to a target replication share, backups might not provide an accurate record of replication history, and some files might not be in the location expected by client applications or administrators. However, this has no direct effect on COMA protocol behavior.

<353> Section 3.1.4.22.4: Applicable Windows Server releases do not attempt to perform any cleanup.

<354> Section 3.1.4.22.5: For Windows 2000 Professional and later and Windows 2000 Server and later, the COMA server does not fail the call if the conglomeration does not exist. 

Instead, they return a null value for ppvPassword. Windows clients never call this method with a ConglomerationId that was not previously verified to exist by reading the Conglomerations Table (section 3.1.1.3.6).

<355> Section 3.2.4.1: Windows clients support the following catalog versions.

Windows version

Catalog versions

Windows 2000

3.00

Windows XP (x86 Editions)

3.00, 4.00

Windows XP (x64 and Itanium Editions)

3.00, 4.00, 5.00

Windows Server 2003

3.00, 4.00, 5.00

Windows Vista

3.00, 4.00, 5.00

Windows Server 2008

3.00, 4.00, 5.00

Windows 7

3.00, 4.00, 5.00

Windows Server 2008 R2

3.00, 4.00, 5.00

Windows 8

3.00, 4.00, 5.00

Windows Server 2012

3.00, 4.00, 5.00

Windows 8.1

3.00, 4.00, 5.00

Windows Server 2012 R2

3.00, 4.00, 5.00

<356> Section 3.2.4.1: Windows XP clients support this range of catalog versions and enable configuration of multiple partitions on a server.

<357> Section 3.2.4.2: For Windows XP and later and Windows Server 2003 and later, the client attempts to perform capability negotiation for the 64-bit QueryCell marshaling format capability.

<358> Section 3.2.4.3: For Windows XP and later and Windows Server 2003 and later, the client initiates, and the server supports, capability negotiation for the multiple-partition support capability.

<359> Section 3.2.4.4: For Windows XP and later and Windows Server 2003 and later, the client initiates, and the server supports, capability negotiation for the multiple-partition support capability.