220.127.116.11 Cluster Registry
In order to access the cluster registry, a client MUST establish an RPC interface connection to an active node, as specified in section 3.2.3. Operations on the cluster registry begin with the client calling ApiGetRootKey (section 18.104.22.168.29 for protocol version 2, or 22.214.171.124.29 for protocol version 3) to open the cluster registry root key. After this key is opened, an RPC context handle is associated with this opened key, as specified in [MS-RPCE], and this handle is returned to the client. The client MAY then perform operations on this key, such as:
When enumerating keys or values, a client MAY first invoke ApiEnumKey (section 126.96.36.199.32 for protocol version 2, or 188.8.131.52.32 for protocol version 3) or ApiEnumValue (section 184.108.40.206.37 for protocol version 2, or 220.127.116.11.37 for protocol version 3) with the index set to 0. Then the client MAY continue calling ApiEnumKey or ApiEnumValue, incrementing the index on each call, until 0x00000103 (ERROR_NO_MORE_ITEMS) is returned.