Export (0) Print
Expand All

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 released service packs:

  • Windows NT 4.0 operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system with Service Pack 1 (SP1)

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product 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.1: As specified in [MS-DMRP], the Windows implementation uses device names of the form \device\HarddiskNNN for hard disks. All Windows NT namespace device paths are created under \device for Windows. The disk number is the NNN in the Windows NT namespace device path.

<2> Section 1.7: Windows NT 4.0 SP3 and subsequent service packs, Windows 2000 and Windows Server 2003 implements version 2.0 of the protocol.

Windows XP implements client side of the version 2.0 of the protocol.

This protocol is not supported on versions of Windows Vista prior to Windows Vista SP1. Any attempt to use these methods on Windows Vista prior to SP1 causes a non-zero error code to be returned.

Windows Vista SP1 implements the client side of version 3.0 of the protocol.

Windows Server 2008 supports version 3.0 of the protocol.

Windows 7 implements the client side of the version 3.0 of the protocol

Windows Server 2008 R2 supports version 3.0 of the protocol.

<3> Section 1.8: Windows uses only the values in [MS-ERREF].

<4> Section 2.1: For Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, (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. The reason for this is to pick up changes in the cluster security descriptor, which could occur at any time through implementation-specific methods between servers.

<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 SP2, Windows Server 2008 and Windows Server 2008 R2.

<7> Section 2.2.2.13: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<8> Section 2.2.2.14: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<9> Section 2.2.2.15: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<10> Section 2.2.2.16: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<11> Section 2.2.2.17: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<12> Section 2.2.2.18: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<13> Section 2.2.2.19: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<14> Section 2.2.2.20: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<15> Section 2.2.2.21: Windows Server 2008 and Windows Server 2008 R2 do not support this object type.

<16> Section 2.2.3.3: The highest version value of 0x000100e0 is returned by a cluster of nodes that are running Windows NT 4.0 SP3.

This value is also returned by a cluster that is running both Windows NT 4.0 SP3 and Windows NT 4.0 SP4.

<17> Section 2.2.3.3: The highest version value of 0x000200e0 is returned by a cluster of nodes that are running Windows NT 4.0 SP4.

This value is also returned by a cluster that is running both Windows NT 4.0 SP4 and Windows 2000 Server.

<18> Section 2.2.3.3: The highest version value of 0x00030893 is returned by a cluster that is running Windows 2000 Server on all nodes.

This value is also returned by a cluster that is running both Windows 2000 Server and Windows Server 2003.

<19> Section 2.2.3.3: The highest version value of 0x00040ECE is returned by a cluster that is running Windows Server 2003 on all nodes.

<20> Section 2.2.3.3: The highest version value of 0x00051771 is returned by a cluster that is running Windows Server 2008 on all its nodes.

<21> Section 2.2.3.3: The higher version value of 0x00061DB0 is returned by a cluster that is running Windows Server 2008 R2 on all its nodes. This value is also returned by a cluster that is running both Windows Server 2008 R2 and Windows Server 2008 with SP2.

A cluster that is runningWindows Server 2008 R2 SP1 on all nodes sets dwClusterHighestVersion to 0x00061DB1. This value is also returned by a cluster that is running both Windows Server 2008 R2 and Windows Server 2008 R2 SP1.

<22> Section 2.2.3.3: The highest version value of 0x000723F0 is returned by a cluster that is running Windows Server 2012 on all its nodes.

<23> Section 2.2.3.3: The highest version value of 0x00082580 is returned by a cluster that is running Windows Server 2012 R2 on all its nodes.

<24> Section 2.2.3.3: The lowest version value of 0x000100e0 is returned by a cluster of nodes that are running Windows NT 4.0 SP3 or a cluster of nodes that are running Windows NT 4.0 SP4.

This value is also returned by a cluster of nodes that are running Windows NT 4.0 SP3 and Windows NT 4.0 SP4.

<25> Section 2.2.3.3: The lowest version value of 0x000200e0 is returned by a cluster of nodes that are running Windows 2000.

This value is also returned by a cluster that is running both Windows 2000 Server and Windows NT 4.0 SP4.

<26> Section 2.2.3.3: A lowest version value of 0x00030893 is returned by a cluster that is running Windows Server 2003 on all nodes.

This value is also returned by a cluster that is running both Windows Server 2003 and Windows 2000 Server.

<27> Section 2.2.3.3: A lowest version value of 0x00051771 is returned by a cluster that is running Windows Server 2008 on all nodes.

<28> Section 2.2.3.3: The lowest version value of 0x00061DB0 is returned by a cluster that is running Windows Server 2008 R2 on all its nodes. This value is also returned by a cluster that is running both Windows Server 2008 R2 and Windows Server 2008 R2 SP1. A cluster that is running Windows Server 2008 R2 SP1 on all nodes sets dwClusterLowestVersion to 0x00061DB1.

<29> Section 2.2.3.3: The lowest version value of 0x000723F0 is returned by a cluster that is running Windows Server 2012 on all its nodes.

<30> Section 2.2.3.3: The lowest version value of 0x00082580 is returned by a cluster that is running Windows Server 2012 R2 on all its nodes.

<31> Section 2.2.3.17.1: Windows NT, Windows 2000, and Windows Server 2003 do not permit dwType 0x0000000B (REG_QWORD). Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 do not permit dwType 0x00000000 (REG_NONE).

<32> Section 2.2.3.21: CLUSTER_CREATE_GROUP_INFO_RPC is only supported in Windows Server 2012 and Windows Server 2012 R2.

<33> Section 2.2.3.22: NOTIFY_FILTER_AND_TYPE_RPC is supported only in Windows Server 2012 and Windows Server 2012 R2.

<34> Section 2.2.3.23: NOTIFICATION_DATA_RPC is only supported in Windows Server 2012 and Windows Server 2012 R2.

<35> Section 2.2.3.29: CLUSTER_SHARED_VOLUME_STATE_INFO is only supported in Windows Server 2012 and Windows Server 2012 R2.

<36> Section 2.2.3.32: The CLUSTER_SHARED_VOLUME_STATE_INFO_EX structure is only supported in Windows Server 2012 R2.

<37> Section 3.1.1.2: Windows NT, Windows 2000, and Windows Server 2003 do not permit dwType 0x0000000B (REG_QWORD). Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 do not permit dwType 0x00000000 (REG_NONE).

<38> Section 3.1.3.1: For protocol version 2.0, the registrysubkey "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Cluster Server\ClusterInstallationState" is not set in the following versions of Windows: Windows NT.

<39> 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 may return a status value other than 0x00000004 (SERVICE_RUNNING) even though the cluster software is running.

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

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

<42> Section 3.1.4.1:

Unused opnums

Description

80

Used only locally by Windows, never remotely.

111

Used only locally by Windows, never remotely.

<43> Section 3.1.4.1.7: Windows NT and Windows 2000 Server do not support the Majority of Nodes quorum.

<44> Section 3.1.4.1.15: The resource ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<45> Section 3.1.4.1.48: The group ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<46> Section 3.1.4.1.86: The cluster network ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<47> Section 3.1.4.1.96: The cluster network interface ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<48> 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).

<49> Section 3.1.4.1.102: Windows NT 4.0 SP4 (and subsequent service packs) sets the lpwMajorVersion parameter to 0x0004.

<50> Section 3.1.4.1.102: Windows NT and Windows 2000 set this parameter to 0x0000.

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

<52> Section 3.1.4.1.102: Windows Server 2003 and Windows Server 2008 R2 set this value to "Microsoft(R) Cluster service".

<53> 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".

<54> 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).

<55> Section 3.1.4.1.104: Windows NT Server 4.0 does not support this method and returns 0x000006D1 (RPC_S_PROCNUM_OUT_OF_RANGE).

<56> 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).

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

<58> 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).

<59> 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).

<60> 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).

<61> Section 3.1.4.2: Servers running Windows Server 2008 do not return context handles that do not have "All" access.

<62> Section 3.1.4.2:

Unused opnums

Description

80

Used only locally by Windows, never remotely.

111

Used only locally by Windows, never remotely.

<63> Section 3.1.4.2.8: This value is not supported in Windows Server 2008.

<64> Section 3.1.4.2.15: The resource ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<65> Section 3.1.4.2.18: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<66> Section 3.1.4.2.19: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<67> Section 3.1.4.2.26: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<68> Section 3.1.4.2.48: The group ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<69> Section 3.1.4.2.50: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<70> Section 3.1.4.2.51: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<71> Section 3.1.4.2.52: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<72> Section 3.1.4.2.53: Group locked mode is supported in Windows Server 2012 and Windows Server 2012 R2.

<73> Section 3.1.4.2.66: Windows Server 2012 and Windows Server 2012 R2 return CLUSTER_CHANGE_CLUSTER_RECONNECT if notifications were dropped for the port.

<74> Section 3.1.4.2.74: Windows 8 and Windows 8.1 implementations always return ERROR_INVALID_FUNCTION.

<75> Section 3.1.4.2.74: Windows 8 and Windows 8.1 implementations always return ERROR_NOT_SUPPORTED.

<76> Section 3.1.4.2.74: The Windows 7 implementation returns ERROR_INVALID_FUNCTION.

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

<78> Section 3.1.4.2.86: The cluster network ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<79> Section 3.1.4.2.96: The cluster network interface ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<80> Section 3.1.4.2.101: dwType value CLUSTER_NODE_ENUM_GROUPS is supported in Windows 7, Windows 8, and Windows 8.1.

<81> Section 3.1.4.2.102: Windows Server 2008 sets the parameter to 0x0000, Windows Server 2008 R2 sets this parameter to 0x0001, Windows Server 2012 sets the parameter to 0x0002, and Windows Server 2012 R2 sets this parameter to 0x0003.

<82> Section 3.1.4.2.102: The following table lists the version-specific lpwBuildNumber values.

Windows Version

lpwBuildNumber

Windows Server 2008

0x1771

Windows Server 2008 R2 SP1

0x1DB1

Windows Server 2012

0x23F0

Windows Server 2012 R2

0x2580

<83> Section 3.1.4.2.102: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 set this value to "Microsoft(R) Cluster service".

<84> Section 3.1.4.2.102: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 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".

<85> Section 3.1.4.2.103: dwType value CLUSTER_RESOURCE_TYPE_ENUM_RESOURCES is supported in Windows 7, Windows 8, and Windows 8.1.

<86> 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).

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

<88> 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).

<89> 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).

<90> 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).

<91> 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).

<92> 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).

<93> 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).

<94> 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).

<95> 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).

<96> 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).

<97> 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).

<98> 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).

<99> 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).

<100> 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).

<101> 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).

<102> 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).

<103> 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).

<104> 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).

<105> 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).

<106> 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).

<107> 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).

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

<109> 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).

<110> 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).

<111> 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).

<112> 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).

<113> 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).

<114> Section 3.1.4.3.1.8: The resource ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<115> Section 3.1.4.3.1.14: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION.

<116> Section 3.1.4.3.1.20: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).

<117> Section 3.1.4.3.1.24: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION).

<118> Section 3.1.4.3.1.25: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION).

<119> Section 3.1.4.3.1.26: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION).

<120> Section 3.1.4.3.1.27: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION.

<121> Section 3.1.4.3.1.28: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).

<122> Section 3.1.4.3.1.29: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).

<123> Section 3.1.4.3.1.30: Windows NT does not support this control and returns 0x00000001 (ERROR_INVALID_FUNCTION)

<124> Section 3.1.4.3.1.31: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).

<125> Section 3.1.4.3.1.42: 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).

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

<127> 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).

<128> Section 3.1.4.3.1.48: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_STORAGE_GET_SHARED_VOLUME_INFO.

<129> Section 3.1.4.3.1.49: Windows Server 2008 R2 supports this method, but Windows Server 2008, Windows Server 2012, and Windows Server 2012 R2 fail this method with ERROR_INVALID_FUNCTION.

<130> Section 3.1.4.3.1.50: Windows Server 2008 R2 supports this method, but Windows Server 2008, Windows Server 2012, and Windows Server 2012 R2 fail this method with error ERROR_INVALID_FUNCTION.

<131> Section 3.1.4.3.1.51: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_SET_CSV_MAINTENANCE_MODE. Windows Server 2012 and Windows Server 2012 R2 fail this method using error code ERROR_INVALID_FUNCTION (0x00000001).

<132> Section 3.1.4.3.1.52: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_ENABLE_SHARED_VOLUME_DIRECTIO.

<133> Section 3.1.4.3.1.53: Windows Server 2008 returns ERROR_INVALID_FUNCTION (0x00000001) for CLUSCTL_RESOURCE_DISABLE_SHARED_VOLUME_DIRECTIO.

<134> 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 and Windows Server 2012 R2 fail this method using error code ERROR_INVALID_FUNCTION (0x00000001).

<135> Section 3.1.4.3.1.55: Server implementations on Windows Server 2008 and Windows Server 2008 R2 fail this method with error code ERROR_INVALID_FUNCTION (0x00000001).

<136> Section 3.1.4.3.1.56: Server implementations on Windows Server 2008 and Windows Server 2008 R2 fail this method with error code ERROR_INVALID_FUNCTION (0x00000001).

<137> 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).

<138> 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).

<139> Section 3.1.4.3.2.13: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION)

<140> Section 3.1.4.3.2.20: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION)

<141> Section 3.1.4.3.3.5: The group ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<142> 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 and Windows Server 2012 R2 do not support this control code and return ERROR_INVALID_FUNCTION.

<143> Section 3.1.4.3.5.5: The cluster network ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<144> Section 3.1.4.3.6.7: The cluster network interface ID returned by Windows is a Unicode string representation of a GUID in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

<145> Section 3.1.4.3.7.2: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).

<146> Section 3.1.4.3.7.11: Windows NT and Windows 2000 do not support this control and return 0x00000001 (ERROR_INVALID_FUNCTION).

<147> Section 3.2.1: Windows Vista SP1 and Windows Server 2008 clients do not maintain granted level of access.

<148> 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).

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

<150> 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).

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

<152> Section 3.2.4.5.1: A client should issue this method only when connected to a Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 server.

<153> 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

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

 
Show:
© 2014 Microsoft