2.3.1.6 NTDS Connection Object
Each NTDS connection object specifies a one-way replication connection from an Upstream Partner to the member object (section 2.3.1.3) containing this NTDS Connection Object. Each NTDS connection object for a DFS replica set MUST be stored in the domain naming context at the following RDN, within the NTFRS member object that is its parent:
"CN=connectionName"
Where connectionName is a Unicode string containing a unique name for this connection object.<23>
The attributes of this object Defined for FRS are:
enabledConnection: A Boolean value that MUST specify the state of the connection. If the connection is available for use, the value of the attribute MUST be TRUE. If the connection is not available for use, the value of the attribute MUST be FALSE.
fromServer: MUST be a Unicode string containing the DN of the responding member's nTFRSMember object.<24>
Schedule: Can specify the replication times for this connection. The format of this attribute MUST be as specified in section 2.3.1.2.
options: Options defines the priority of the connection.
-
The following MUST be used to retrieve the value of options.
-
0
1
2
3
4
5
6
7
8
91
0
1
2
3
4
5
6
7
8
92
0
1
2
3
4
5
6
7
8
93
0
1X
T
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
P
P
P
S
-
X = Do Not Care
-
P = Priority (3 bits for connection priority class)
-
S = FRS_IGNORE_SCHEDULE (1 – Ignore; 0 – Do Not Ignore)
-
T = NTDSCONN_OPT_TWOWAY_SYNC (1 – Two way; 0 – One way)
FRS_IGNORE_SCHEDULE flag MUST be used to indicate if the schedule has to be ignored or followed for the initial VVJoin.
NTDSCONN_OPT_TWOWAY_SYNC (force sync in opposite direction at end of sync) flag MUST be used in the following way: If the NTDSCONN_OPT_TWOWAY_SYNC flag is set on the connection, FRS MUST merge (bitwise OR) the schedule on this connection with the schedule on the corresponding connection, between these two servers, that is in the opposite direction and use the resultant schedule on the connection in the opposite direction.
The use of Priority is as specified in section 3.1.5.1.<25>
Exactly one NTDS connection object MUST exist for each computer that replicates to each member of a replica set. An NTDS connection object MUST be stored in the directory under the NTFRS member object to which it is inbound. The fromServer attribute of that object MUST point to the NTFRS member object to which it is outbound.
The NTDS connection object MUST use the schema definition provided by the nTDSConnection class definition, as specified in [MS-ADSC] section 2.204.