3.3.1.2 Registry Keys (Public)

The Management Server uses the Windows registry to persistently store and retrieve the registry keys and values specified in section 2.2.3, and the persistent store is shared with [MS-CMPO], [MS-DTCO], [MS-DTCLU], and [MC-DTCXA]. The set of registry keys and values specified in section 2.2.3 MUST be exposed by the Management Server at a specified registry path via the Windows Remote Registry Protocol [MS-RRP] or Failover Cluster: Management API (ClusAPI) Protocol [MS-CMRP] depending on the registry protocol version, as specified in section 2.2.1.2. Each of these protocols can have a protocol-specific configuration that is not managed by OleTx Management Protocol.

The Management Server also uses the abstract data model elements specified in [MS-CMPO] section 1.3.2 and [MS-DTCO] section 3.2.1, and initialized by the MSDTC Connection Manager: OleTx Transports Protocol [MS-CMPO] and the MSDTC Connection Manager: OleTx Transaction Protocol [MS-DTCO], using the registry keys defined in sections 3.3.1.2.1, 3.3.1.2.2, 3.3.1.2.3, and 3.3.1.2.4. For each abstract data model element that is loaded from the registry, there is one instance that is shared by the Management Server and the protocol(s) that uses the abstract data model element. The abstract data model elements are immutable after the transaction manager service implementing the Management Server role has started. Any changes made to the registry keys will not be reflected in the abstract data model elements until the transaction manager service is stopped and restarted.

Sections 3.3.1.2.1, 3.3.1.2.2, 3.3.1.2.3, and 3.3.1.2.4 specify the registry keys and the abstract data model elements loaded from each key.