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 Service Pack 3 (SP3)
Windows 2000 operating system
Windows XP operating system
Windows NT 4.0 operating system Service Pack 4 (SP4)
Windows Vista operating system with Service Pack 1 (SP1)
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 4.0 SP3
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 1.8: Windows uses only the values in [MS-ERREF].
<2> Section 2.1: Only Windows NT 4.0 SP3 and subsequent service packs, Windows 2000, and Windows Server 2003 implement ClusAPI Protocol version 2. Windows XP implements the client side of ClusAPI Protocol version 2. Windows Server 2008 and later implement ClusAPI Protocol version 3.0.
The following versions of Windows implement only the client side of ClusAPI Protocol version 3:
Windows Vista SP1
Note: Any attempt to use these methods on Windows Vista operating system prior to SP1 causes a nonzero error code to be returned.
Windows 7
Windows 8
Windows 8.1
Windows 10
<3> Section 2.1: For ClusAPI Protocol version 3.0, Windows also validates client authorization for any methods that do not require that a context handle be acquired in a previous method. Thus, any method could be the first method called after establishing the RPC connection. This picks up changes in the cluster security descriptor, which could occur at any time through implementation-specific methods between servers.
<4> Section 2.2.1.11: The HGROUPSET_RPC context handle is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<5> Section 2.2.2.4: In Windows, CLUS_CHAR_LOCAL_QUORUM is returned by protocol version 2.0 servers only when the resource being queried for its characteristics is of type "Local Quorum".
<6> Section 2.2.2.6: This enumeration is supported by Windows Server 2003 operating system with Service Pack 2 (SP2), Windows Server 2008, and Windows Server 2008 R2.
<7> Section 2.2.2.11: The CLUSTER_OBJECT_TYPE_SBL_DEVICE enumeration value is not available in Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.
<8> Section 2.2.2.11: The CLUSTER_OBJECT_TYPE_CERT enumeration value is not available in Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016.
<9> Section 2.2.2.11: Windows 10 v1909 operating system and earlier and Windows Server v1909 operating system and earlier operating systems do not support this object type.
<10> Section 2.2.2.13: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<11> Section 2.2.2.14: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<12> Section 2.2.2.15: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<13> Section 2.2.2.16: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<14> Section 2.2.2.17: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<15> Section 2.2.2.18: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<16> Section 2.2.2.19: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<17> Section 2.2.2.20: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<18> Section 2.2.2.21: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.
<19> Section 2.2.2.23: The S2DCACHE_MODE enumeration is not available in Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.
<20> Section 2.2.2.24: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 do not support this object type.
<21> Section 2.2.2.25: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 do not support this object type.
<22> Section 2.2.2.26: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 do not support this object type.
<23> Section 2.2.3.3: The following table lists the dwClusterHighestVersion values that are returned by a cluster and the corresponding Windows version(s) on which all of the nodes in the cluster are running.
|
dwClusterHighestVersion value returned |
Applicable Windows Server releases on which all nodes are running |
|---|---|
|
0x000100e0 |
Windows NT 4.0 SP3 or both Windows NT 4.0 SP3 and Windows NT 4.0 SP4 |
|
0x000200e0 |
Windows NT 4.0 SP4 or both Windows NT 4.0 SP4 and Windows 2000 Server |
|
0x00030893 |
Windows 2000 Server or both Windows 2000 Server and Windows Server 2003 |
|
0x00040ECE |
Windows Server 2003 |
|
0x00051771 |
Windows Server 2008 |
|
0x00061DB0 |
Windows Server 2008 R2 or both Windows Server 2008 R2 and Windows Server 2008 operating system with Service Pack 2 (SP2) |
|
0x00061DB1 |
Windows Server 2008 R2 operating system with Service Pack 1 (SP1) or both Windows Server 2008 R2 and Windows Server 2008 R2 SP1. |
|
0x000723F0 |
Windows Server 2012 |
|
0x00082580 |
Windows Server 2012 R2 or both Windows Server 2012 R2 and Windows Server 2016. This value also is returned by a cluster that is running Windows Server 2016 on all nodes, but previously had a node running Windows Server 2012 R2, and has not incremented its operational version as specified in section 3.1.4.3.7.18. |
|
0x00090003 |
Windows Server 2016 and either no node running Windows Server 2012 R2 has previously been a member of this cluster or the cluster operational version has been incremented as specified in section 3.1.4.3.7.18. |
|
0x000a0001 |
Windows Server operating system |
|
0x000a0003 |
Windows Server 2019 |
|
0x000b0001 |
Windows Server operating system |
|
0x000b0003 |
Windows Server 2022 |
|
0x000c0004 |
Windows Server 2022, 23H2 operating system |
|
0x000c0006 |
Windows Server 2025 |
<24> Section 2.2.3.3: The following table lists the dwClusterLowestVersion values that are returned by a cluster and the corresponding Windows version(s) on which all of the nodes in the cluster are running.
|
dwClusterLowestVersion value |
Applicable Windows Server releases on which all nodes are running |
|---|---|
|
0x000100e0 |
Windows NT 4.0 SP3 and/or Windows NT 4.0 SP4 |
|
0x000200e0 |
Windows 2000 Server or both Windows 2000 Server and Windows NT 4.0 SP4 |
|
0x00030893 |
Windows Server 2003 or both Windows Server 2003 and Windows 2000 Server |
|
0x00040ECE |
Windows Server 2003 operating system |
|
0x00051771 |
Windows Server 2008 |
|
0x00061DB0 |
Windows Server 2008 R2 or both Windows Server 2008 R2 and Windows Server 2008 R2 SP1. |
|
0x00061DB1 |
Windows Server 2008 R2 SP1 |
|
0x000723F0 |
Windows Server 2012 |
|
0x00082580 |
Windows Server 2012 R2 or both Windows Server 2012 R2 and Windows Server 2016. This value is also returned by a cluster running Windows Server 2016 that had a node running Windows Server 2012 R2 on which the operational version was not incremented as specified in section 3.1.4.3.7.18. |
|
0x00090003 |
Windows Server 2016 and either no node was running Windows Server 2012 R2 or its cluster operational version was incremented as specified in section 3.1.4.3.7.18. |
|
0x000a0001 |
Windows Server operating system |
|
0x000a0003 |
Windows Server 2019 |
|
0x000b0001 |
Windows Server operating system |
|
0x000b0003 |
Windows Server 2022 |
|
0x000c0004 |
Windows Server 2022, 23H2 |
|
0x000c0006 |
Windows Server 2025 |
<25> Section 2.2.3.17.1: ClusAPI Protocol version 2.0 does not permit dwType 0x0000000B (REG_QWORD). ClusAPI Protocol version 3.0 does not permit dwType 0x00000000 (REG_NONE).
<26> Section 2.2.3.21: The CLUSTER_CREATE_GROUP_INFO_RPC structure is not supported in Windows NT 4.0 operating system, Windows 2000, Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2.
<27> Section 2.2.3.22: The NOTIFY_FILTER_AND_TYPE_RPC structure is not supported in Windows NT 4.0, Windows 2000, Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2.
<28> Section 2.2.3.23: The NOTIFICATION_DATA_RPC structure is not supported in Windows NT 4.0, Windows 2000, Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2.
<29> Section 2.2.3.29: The CLUSTER_SHARED_VOLUME_STATE_INFO structure is not supported in Windows NT 4.0, Windows 2000, Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2.
<30> Section 2.2.3.32: The CLUSTER_SHARED_VOLUME_STATE_INFO_EX structure is not supported in Windows NT 4.0, Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.
<31> Section 2.2.3.34: The CLUSCTL_RESOURCE_NETNAME_CHECK_OU_PERMISSIONS_INPUT structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<32> Section 2.2.3.35: The CLUSCTL_RESOURCE_NETNAME_CHECK_OU_PERMISSIONS_OUTPUT structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<33> Section 2.2.3.36: The SR_RESOURCE_TYPE_QUERY_ELIGIBLE_LOGDISKS structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<34> Section 2.2.3.37: The SR_RESOURCE_TYPE_ELIGIBLE_DISKS_RESULT structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<35> Section 2.2.3.38: The SR_RESOURCE_TYPE_QUERY_ELIGIBLE_TARGET_DATADISKS structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<36> Section 2.2.3.39: The SR_RESOURCE_TYPE_QUERY_ELIGIBLE_SOURCE_DATADISKS structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<37> Section 2.2.3.40: The SR_RESOURCE_TYPE_REPLICATED_DISK structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<38> Section 2.2.3.41: The SR_RESOURCE_TYPE_REPLICATED_DISKS_RESULT structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<39> Section 2.2.3.42: The CLUSTER_MEMBERSHIP_INFO structure is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<40> Section 2.2.3.43: The OS_AND_OS_VERSION_INFO structure is not available in Windows NT 4.0, Windows 2000 operating system, Windows XP operating system, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10 v1507 operating system, and Windows 10 v1511 operating system.
<41> Section 2.2.3.44: The CLUS_DISK_NUMBER_INFO structure is not available in Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and Windows 10 v1507.
<42> Section 2.2.3.45: The CLUS_PARTITION_INFO_EX2 structure is not available in Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and Windows 10 v1507.
<43> Section 2.2.3.46: The NodeUtilizationInfo structure is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10, and Windows Server 2016.
<44> Section 2.2.3.50: The CLUS_PHYSICAL_DISK_INFO_HEADER structure is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and Windows Server 2016.
<45> Section 2.2.3.52: The CLUS_STRING_NAME_INFO structure is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<46> Section 2.2.3.54: The CLUS_SBL_DISK_STATE structure is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<47> Section 2.2.3.56: The CLUS_SBL_DISK_HEALTH_STAT structure is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<48> Section 2.2.3.60: The CLUS_CREATE_INFRASTRUCTURE_FILESERVER_OUTPUT is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and Windows Server 2016.
<49> Section 2.2.3.61: The ClusterUtilizationInfo structure is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and Windows Server 2016.
<50> Section 3.1.1.1.4: Group locked mode is not supported in Windows NT 4.0, Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.
<51> Section 3.1.1.1.5: Group Sets are not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<52> Section 3.1.1.2: On servers running ClusAPI Protocol version 2.0, dwType 0x0000000B (REG_QWORD) is not permitted. On servers running ClusAPI Protocol version 3.0, dwType 0x00000000 (REG_NONE) is not permitted.
<53> Section 3.1.1.5: Storage replication is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<54> Section 3.1.3.1: For protocol version 2.0, the registry subkey "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Cluster Server\ClusterInstallationState" is not set in Windows NT operating system.
<55> Section 3.1.3.2: In Windows NT, Windows 2000, and Windows Server 2003, it is possible for the cluster software to run but not as a Windows service as specified in [MS-SCMR]. In this case, the QueryServiceStatus method can return a status value other than 0x00000004 (SERVICE_RUNNING) even though the cluster software is running.
<56> Section 3.1.4.1: For Protocol Version 2.0, Windows NT 4.0 and Windows 2000 implementations do not indicate to the RPC runtime that it is to perform a strict NDR data consistency check at target level 5.0, as specified in [MS-RPCE] section 3.
<57> Section 3.1.4.1: For Protocol Version 2.0, Windows NT 4.0 and Windows 2000 implementations do not indicate to the RPC runtime by means of the strict_context_handle attribute that it is to reject the use of context handles that are created by a method of an RPC interface that is different from this one, as specified in [MS-RPCE] section 3.
<58> Section 3.1.4.1.7: Windows NT and Windows 2000 Server do not support the Majority of Nodes quorum.
<59> Section 3.1.4.1.15: The resource ID returned by Windows is a GUIDString.
<60> Section 3.1.4.1.48: The group ID returned by Windows is a GUIDString.
<61> Section 3.1.4.1.86: The cluster network ID returned by Windows is a GUIDString.
<62> Section 3.1.4.1.96: The cluster network interface ID returned by Windows is a GUIDString.
<63> Section 3.1.4.1.102: Windows NT 4.0 SP3 does not support this method and returns 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<64> Section 3.1.4.1.102: Windows NT 4.0 SP4 (and subsequent service packs) sets the lpwMajorVersion parameter to 0x0004.
<65> Section 3.1.4.1.102: Windows NT and Windows 2000 set this parameter to 0x0000.
<66> Section 3.1.4.1.102: Windows NT 4.0 SP4 (and subsequent service packs) sets this parameter to 0x00E0. Windows 2000 sets this parameter to 0x893.
<67> Section 3.1.4.1.102: Windows Server 2003 and Windows Server 2008 R2 set this value to "Microsoft(R) Cluster service".
<68> Section 3.1.4.1.102: Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000 Server, Windows Server 2003, and Windows Server 2008 R2, set this Value to a null-terminated Unicode string that is constructed as follows: "Service Pack X", where X is replaced by an integer service pack number. For example, if the server operating system has Service Pack 3 installed, the server would set this parameter to the null-terminated Unicode string "Service Pack 3".
<69> Section 3.1.4.1.103: Windows NT 4.0 SP3 does not support this method and returns 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<70> Section 3.1.4.1.104: Windows NT Server 4.0 operating system does not support this method and returns 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<71> Section 3.1.4.1.105: Windows NT Server 4.0 does not support this method and returns 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<72> Section 3.1.4.1.106: Windows NT Server 4.0 does not support this method and returns 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<73> Section 3.1.4.1.107: Windows NT and Windows 2000 do not support this method and return 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<74> Section 3.1.4.1.108: Only Windows Server 2003 supports this method. Windows NT and Windows 2000 return 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<75> Section 3.1.4.2: Windows Server 2008 supports only "All" access and determines client access the same as Protocol Version 2.0 servers (see section 3.1.4.1).
<76> Section 3.1.4.2: Servers running Windows Server 2008 do not return context handles that do not have "All" access.
<77> Section 3.1.4.2.8: This value is not supported in Windows Server 2008.
<78> Section 3.1.4.2.15: The resource ID returned by Windows is a GUIDString.
<79> Section 3.1.4.2.48: The group ID returned by Windows is a GUIDString.
<80> Section 3.1.4.2.66: Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 return CLUSTER_CHANGE_CLUSTER_RECONNECT if notifications were dropped for the port.
<81> Section 3.1.4.2.74: Windows 8, Windows 8.1, and Windows 10 implementations return ERROR_INVALID_FUNCTION.
<82> Section 3.1.4.2.74: Windows 8, Windows 8.1, and Windows 10 implementations return ERROR_NOT_SUPPORTED.
<83> Section 3.1.4.2.74: Windows 7 implementations return ERROR_INVALID_FUNCTION.
<84> Section 3.1.4.2.74: Windows Server v1909 and earlier, and Windows 10 v1909 and earlier do not send or process this control code.
<85> Section 3.1.4.2.74: Windows Server v2004 operating system and earlier operating systems do not send or process this control code.
<86> Section 3.1.4.2.84: Windows removes any preceding and trailing space (Unicode 0x20) characters from lpszNetworkName prior to checking for name uniqueness and setting the name.
<87> Section 3.1.4.2.86: The cluster network ID returned by Windows is a GUIDString.
<88> Section 3.1.4.2.96: The cluster network interface ID returned by Windows is a GUIDString.
<89> Section 3.1.4.2.101: dwType value CLUSTER_NODE_ENUM_GROUPS is not supported in Windows Vista SP1.
<90> Section 3.1.4.2.102: Windows Server 2008 operating system with Service Pack 2 (SP2) through Windows Server 2012 R2 operating system set lpwMajorVersion to 0x0006 and Windows Server 2016 through Windows Server 2022 set lpwMajorVersion to 0x000a.
<91> Section 3.1.4.2.102: The following table lists lpwMinorVersion values for additional Windows versions:
|
Windows Version |
lpwMinorVersion |
|---|---|
|
Windows Server 2008 |
0x0000 |
|
Windows Server 2008 R2 |
0x0001 |
|
Windows Server 2012 |
0x0002 |
|
Windows Server 2012 R2 |
0x0003 |
|
Windows Server 2016 |
0x0000 |
|
Windows Server operating system |
0x0000 |
|
Windows Server 2019 |
0x0000 |
|
Windows Server v1903 operating system |
0x0000 |
|
Windows Server v1909 |
0x0000 |
|
Windows Server v2004 |
0x0000 |
|
Windows Server v20H2 operating system |
0x0000 |
|
Windows Server 2022 |
0x0000 |
|
Windows Server 2025 |
0x0000 |
<92> Section 3.1.4.2.102: Applicable Windows Server releases running ClusAPI Protocol version 3 set this value to "Microsoft(R) Cluster service".
<93> Section 3.1.4.2.102: Applicable Windows Server releases running ClusAPI Protocol version 3 set this value to a null-terminated Unicode string that is constructed as follows: "Service Pack X", where X is replaced by an integer service pack number. For example, if the server operating system has Service Pack 3 installed, the server would set this parameter to the null-terminated Unicode string "Service Pack 3".
<94> Section 3.1.4.2.103: dwType value CLUSTER_RESOURCE_TYPE_ENUM_RESOURCES is not supported in Windows Vista SP1 or Windows Server 2008.
<95> Section 3.1.4.2.106: Windows 10 v1909 and earlier and Windows Server v1909 and earlier operating systems do not send or process this control code.
<96> Section 3.1.4.2.116: Windows Server 2008 does not support this method and fails the method call with a return value of 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).
<97> Section 3.1.4.2.117: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<98> Section 3.1.4.2.118: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<99> Section 3.1.4.2.119: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<100> Section 3.1.4.2.120: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<101> Section 3.1.4.2.121: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<102> Section 3.1.4.2.122: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<103> Section 3.1.4.2.123: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<104> Section 3.1.4.2.124: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<105> Section 3.1.4.2.125: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<106> Section 3.1.4.2.126: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<107> Section 3.1.4.2.127: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<108> Section 3.1.4.2.128: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<109> Section 3.1.4.2.129: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<110> Section 3.1.4.2.129: Windows Server 2012 R2 and earlier operating systems do not support this value.
<111> Section 3.1.4.2.129: Windows Server 2016 and earlier operating systems do not support this value.
<112> Section 3.1.4.2.129: Windows Server v1909 and earlier operating systems do not support this value.
<113> Section 3.1.4.2.130: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<114> Section 3.1.4.2.131: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<115> Section 3.1.4.2.131: Windows Server v1909 and earlier operating systems do not support this value.
<116> Section 3.1.4.2.132: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<117> Section 3.1.4.2.133: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<118> Section 3.1.4.2.134: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<119> Section 3.1.4.2.134: Windows Server 2016 and earlier operating systems do not support this value.
<120> Section 3.1.4.2.134: Windows Server v1909 and earlier operating systems do not support this value.
<121> Section 3.1.4.2.135: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<122> Section 3.1.4.2.135: Windows Server 2016 and earlier operating systems do not support this value.
<123> Section 3.1.4.2.137: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<124> Section 3.1.4.2.138: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<125> Section 3.1.4.2.138: For FilterAndType.FilterFlags value CLUSTER_CHANGE_SHARED_VOLUME_STATE_V2, Windows Server 2012 sets the buffer to a PROPERTY_LIST (section 2.2.3.10) containing one or more Property Values (section 2.2.3.10.1) of type binary value, with each binary data value representing a CLUSTER_SHARED_VOLUME_STATE_INFO (section 2.2.3.29) structure.
<126> Section 3.1.4.2.139: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<127> Section 3.1.4.2.140: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<128> Section 3.1.4.2.141: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<129> Section 3.1.4.2.142: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<130> Section 3.1.4.2.143: Windows Server 2008 and Windows Server 2008 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<131> Section 3.1.4.2.144: ApiAddNotifyResourceV2 is not available in Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10 v1507, and Windows 10 v1511.
<132> Section 3.1.4.2.145: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 do not support this method and fail calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<133> Section 3.1.4.2.146: The ApiCreateGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<134> Section 3.1.4.2.147: The ApiOpenGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<135> Section 3.1.4.2.148: The ApiCloseGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<136> Section 3.1.4.2.149: The ApiDeleteGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<137> Section 3.1.4.2.150: The ApiAddGroupToGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<138> Section 3.1.4.2.151: The APIRemoveGroupFromGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<139> Section 3.1.4.2.152: The APIMoveGroupToGroupSet method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<140> Section 3.1.4.2.153: The APIAddGroupSetDependency method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<141> Section 3.1.4.2.154: The ApiAddGroupToGroupSetDependency method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<142> Section 3.1.4.2.155: The ApiNodeGroupSetControl method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<143> Section 3.1.4.2.156: The ApiGroupSetControl method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<144> Section 3.1.4.2.157: The ApiSetGroupDependencyExpression method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<145> Section 3.1.4.2.158: The ApiRemveClusterGroupDependency method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<146> Section 3.1.4.2.159: The ApiSetGroupSetDependencyExpression method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<147> Section 3.1.4.2.160: The ApiRemoveGroupSetDependency method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<148> Section 3.1.4.2.161: The ApiRemoveClusterGroupToGroupSetDependency method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<149> Section 3.1.4.2.162: The ApiCreateGroupSetEnum method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<150> Section 3.1.4.2.163: The ApiSetGroupDependencyExpression method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<151> Section 3.1.4.2.164: The ApiChangeCsvStateEx method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<152> Section 3.1.4.2.164: Windows Server 2008 does not support this method and fails calls with RPC_S_PROCNUM_OUT_OF_RANGE (0x000006D1).
<153> Section 3.1.4.2.165: The ApiAddGroupToGroupSetEx method is not supported in Windows Server v1803 operating system and earlier, and Windows 10 v1803 operating system and earlier.
<154> Section 3.1.4.2.166: Windows Server v2004 and earlier operating systems do not send or process this method.
<155> Section 3.1.4.2.167: The ApiClusterNativeUpdateControl method is available on Windows 11, version 24H2 operating system but returns an error if called.
<156> Section 3.1.4.3.1.8: The resource ID returned by Windows is a GUIDString.
<157> Section 3.1.4.3.1.14: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION.
<158> Section 3.1.4.3.1.20: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<159> Section 3.1.4.3.1.24: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION).
<160> Section 3.1.4.3.1.25: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION).
<161> Section 3.1.4.3.1.26: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION).
<162> Section 3.1.4.3.1.27: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION.
<163> Section 3.1.4.3.1.28: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<164> Section 3.1.4.3.1.29: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<165> Section 3.1.4.3.1.30: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION)
<166> Section 3.1.4.3.1.31: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<167> Section 3.1.4.3.1.42: Only Windows Server 2003 operating system with Service Pack 1 (SP1) and Windows Server 2003 SP2 support this control. Windows NT 4.0 with Service Pack 3 or higher installed, Windows 2000, Windows XP, and Windows Server 2003 return 0x00000001 (ERROR_INVALID_FUNCTION).
<168> Section 3.1.4.3.1.43: No type of maintenance mode is supported by Windows NT. Simple maintenance mode is supported by Windows 2000 and Windows Server 2003.
<169> Section 3.1.4.3.1.43: Only Windows Server 2003 with SP1 and Windows Server 2003 SP2 support this control. Windows NT 4.0 with Service Pack 3 or higher installed, Windows 2000, Windows XP, and Windows Server 2003 return 0x00000001 (ERROR_INVALID_FUNCTION).
<170> Section 3.1.4.3.1.48: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_STORAGE_GET_SHARED_VOLUME_INFO.
<171> Section 3.1.4.3.1.49: Only Windows Server 2008 R2 supports this method.
<172> Section 3.1.4.3.1.50: Only Windows Server 2008 R2 supports this method.
<173> Section 3.1.4.3.1.51: Only Windows Server 2008 R2 supports this method.
<174> Section 3.1.4.3.1.52: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_ENABLE_SHARED_VOLUME_DIRECTIO.
<175> Section 3.1.4.3.1.53: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_DISABLE_SHARED_VOLUME_DIRECTIO.
<176> Section 3.1.4.3.1.54: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_SET_SHARED_VOLUME_BACKUP_MODE. Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 fail this method using error code ERROR_INVALID_FUNCTION (0x00000001).
<177> Section 3.1.4.3.1.55: Implementations on Windows Server 2008 and Windows Server 2008 R2 fail this method with error code ERROR_INVALID_FUNCTION (0x00000001).
<178> Section 3.1.4.3.1.56: Implementations on Windows Server 2008 and Windows Server 2008 R2 fail this method with error code ERROR_INVALID_FUNCTION (0x00000001).
<179> Section 3.1.4.3.1.57: CLUSCTL_RESOURCE_CLOUD_WITNESS_UPDATE_TOKEN is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<180> Section 3.1.4.3.1.58: The CLUSCTL_RESOURCE_NETNAME_CHECK_OU_PERMISSIONS resource control code is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<181> Section 3.1.4.3.1.59: CLUSCTL_RESOURCE_NETNAME_CHECK_AD_STATE is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<182> Section 3.1.4.3.2.6: Windows NT, Windows 2000, and Windows Vista do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<183> Section 3.1.4.3.2.12: The resource types configured by default in Windows do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<184> Section 3.1.4.3.2.13: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION)
<185> Section 3.1.4.3.2.20: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION)
<186> Section 3.1.4.3.2.32: CLUSCTL_CLOUD_WITNESS_RESOURCE_TYPE_VALIDATE_CREDENTIALS is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<187> Section 3.1.4.3.2.33: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_ELIGIBLE_LOGDISKS is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<188> Section 3.1.4.3.2.34: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_ELIGIBLE_TARGET_DATADISKS is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<189> Section 3.1.4.3.2.35: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_ELIGIBLE_SOURCE_DATADISKS is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<190> Section 3.1.4.3.2.36: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_REPLICA_VOLUMES is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<191> Section 3.1.4.3.2.37: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_LOG_VOLUME is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<192> Section 3.1.4.3.2.38: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_REPLICATED_DISKS is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<193> Section 3.1.4.3.2.39: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_RESOURCE_GROUP is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<194> Section 3.1.4.3.2.40: CLUSCTL_RESOURCE_TYPE_REPLICATION_GET_LOG_INFO is not available in Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10 v1507, and Windows 10 v1511.
<195> Section 3.1.4.3.3.5: The group ID returned by Windows is a GUIDString.
<196> Section 3.1.4.3.3.19: The CLUSCTL_GROUP_SET_CCF_FROM_MASTER control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, and Windows Server 2016.
<197> Section 3.1.4.3.3.20: The CLUSCTL_GROUP_GET_PROVIDER_GROUPS control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<198> Section 3.1.4.3.3.21: The CLUSCTL_GROUP_GET_PROVIDER_GROUPSETS control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<199> Section 3.1.4.3.4.6: For protocol version 2.0, only Windows Server 2003 supports this control; Windows NT and Windows 2000 return 0x00000001 (ERROR_INVALID_FUNCTION). For protocol version 3.0, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 do not support this control code and return ERROR_INVALID_FUNCTION.
<200> Section 3.1.4.3.4.17: The CLUSCTL_NODE_GET_CLUSBFLT_PATHS control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<201> Section 3.1.4.3.4.18: The CLUSCTL_NODE_GET_CLUSBFLT_PATHINFO_EX control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<202> Section 3.1.4.3.4.19: The CLUSCT_NODE_STORAGE_GET_PHYSICAL_DISK_INFO_EX control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<203> Section 3.1.4.3.4.20: The CLUSCTL_NODE_GET_SBL_DISK_STATE_EX control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<204> Section 3.1.4.3.4.21: The CLUSCTL_NODE_GET_SBL_CACHE_CONFIG_EX control code is not available in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<205> Section 3.1.4.3.4.22: The CLUSCTL_NODE_SCALEOUTNODE_PLACEMENT_UPDATE control code is not supported in Windows Server v1803 and earlier, and Windows 10 v1803 and earlier.
<206> Section 3.1.4.3.5.5: The cluster network ID returned by Windows is a GUIDString.
<207> Section 3.1.4.3.6.7: The cluster network interface ID returned by Windows is a GUIDString.
<208> Section 3.1.4.3.7.2: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<209> Section 3.1.4.3.7.11: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).
<210> Section 3.1.4.3.7.18: The CLUSCTL_CLUSTER_UPGRADE_CLUSTER_VERSION control code is not implemented in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<211> Section 3.1.4.3.7.19: The CLUSCTL_CLUSTER_CLEAR_UPGRADE_IN_PROGRESS control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<212> Section 3.1.4.3.7.20: The CLUSCTL_CLUSTER_IS_READY_FOR_UPGRADE control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<213> Section 3.1.4.3.7.22: The CLUSCTL_CLUSTER_SET_DNS_DOMAIN control code is not supported in Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10 v1507, and Windows 10 v1511.
<214> Section 3.1.4.3.7.23: The CLUSCTL_CLUSTER_GET_OS_AND_OS_VERSION_INFO control code is not supported in Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10 v1507, and Windows 10 v1511.
<215> Section 3.1.4.3.7.24: The CLUSCTL_CLUSTER_NODE_REPLACEMENT control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<216> Section 3.1.4.3.7.25: The CLUSCTL_CLUSTER_GET_CLUSTER_UTILIZATION control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<217> Section 3.1.4.3.7.26: The CLUSCTL_CLUSTER_REMOVE_INFRASTRUCTURE_FILESERVER control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<218> Section 3.1.4.3.7.27: The CLUSCTL_CLUSTER_NOTIFY_INFRASTRUCTURE_SOFS_CHANGED control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, or Windows Server 2012 R2.
<219> Section 3.1.4.3.7.28: The CLUSCTL_CLUSTER_CREATE_INFRASTRUCTURE_FILESERVER control code is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, or Windows Server 2012 R2.
<220> Section 3.1.4.3.8: The ApiGroupSetControl (Opnum 174) method is not supported in Windows NT 4.0 SP3, Windows NT 4.0 SP4, Windows 2000, Windows XP, Windows Server 2003, Windows Vista SP1, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2.
<221> Section 3.2.1: Windows Vista SP1 and Windows Server 2008 clients do not maintain granted level of access.
<222> Section 3.2.3.3: Windows NT does not retry the ApiGetClusterName (section 3.1.4.1.4 for protocol version 2, or 3.1.4.2.4 for protocol version 3) method if it fails with error 0x000006BF (RPC_CALL_FAILED_DNE).
<223> Section 3.2.4.1.2: Clients running Windows NT do not perform the procedure that is specified in this section for version 2.0 of the protocol.
<224> Section 3.2.4.1.2: Clients running Windows 2000 perform step 2 of the version 2.0 procedure only if the registry value in step 1 is set to 2 (eClusterInstallStateConfigured) or 3 (eClusterInstallStateUpgraded).
<225> Section 3.2.4.1.2: Only clients running Windows Server 2003 perform step 3 of the version 2.0 procedure, as specified in this section.
<226> Section 3.2.4.5.1: A client issues this method only when connected to a server running Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2.
<227> Section 3.2.4.6: Windows versions that implement version 2.0 protocol clients differ in the error codes that trigger a reconnect. The following table specifies the error codes that are used in each Windows version that implements version 2.0 of this protocol.
|
Value |
Symbol |
Windows NT |
Windows 2000 |
Windows XP and Windows Server 2003 |
|---|---|---|---|---|
|
6 |
ERROR_INVALID_HANDLE |
Yes |
Yes |
Yes |
|
1115 |
ERROR_SHUTDOWN_IN_PROGRESS |
No |
Yes |
No |
|
1255 |
ERROR_SERVER_SHUTDOWN_IN_PROGRESS |
No |
Yes |
No |
|
1702 |
RPC_S_INVALID_BINDING |
No |
Yes |
Yes |
|
1717 |
RPC_S_UNKNOWN_IF |
Yes |
Yes |
Yes |
|
1722 |
RPC_S_SERVER_UNAVAILABLE |
Yes |
Yes |
Yes |
|
1723 |
RPC_S_SERVER_TOO_BUSY |
Yes |
Yes |
Yes |
|
1726 |
RPC_S_CALL_FAILED |
Yes |
Yes |
Yes |
|
1727 |
RPC_S_CALL_FAILED_DNE |
No |
Yes |
Yes |
|
1747 |
RPC_S_UNKNOWN_AUTHN_SERVICE |
No |
Yes |
Yes |
|
1753 |
EPT_S_NOT_REGISTERED |
No |
Yes |
Yes |
|
1775 |
RPC_X_SS_IN_NULL_CONTEXT |
No |
Yes |
Yes |
|
5072 |
ERROR_CLUSTER_NODE_NOT_READY |
No |
Yes |
Yes |
|
5073 |
ERROR_CLUSTER_NODE_SHUTTING_DOWN |
Yes |
Yes |
Yes |
<228> Section 3.2.4.6: Windows Vista SP1 and Windows Server 2008 clients do not maintain the level of access granted and behave as protocol version 2.0 clients during the reconnect procedure.