2.3.11 msDFSR-Connection
Each object of this class represents a directional connection between two machines only.
The following attributes of this object are relevant to DFS-R:
objectGUID: The connection GUID. This attribute MUST exist.
FromServer: DN of the inbound partner (other msDFSR-Member object). MUST exist.
msDFSR-Enabled: Boolean that specifies whether this connection is enabled or disabled.
msDFSR-Schedule: A binary attribute that contains the replication schedule, as defined below.
msDFSR-Keywords: A string to be used in an implementation-dependent manner.<16>
msDFSR-RdcEnabled: Enable or disable RDC transfers on a connection.
msDFSR-RdcMinFileSizeInKB: Minimum size threshold for enabling RDC transfers.
msDFSR-Options: Bit flags to control certain behavior. The following bits are used:
0x1: Controls how the schedule is interpreted. If 0, the schedule is interpreted in UTC time zone. If 1, the schedule is interpreted in the local time zone.
All other bits are ignored and SHOULD be set to 0.
Each msDFSR-Connection object MUST NOT use the same msDFSR-Member object as the client and server.
The schema definition for this object is as specified by the msDFSR-Connection class definition in [MS-ADSC] section 2.106.
A Schedule is a binary attribute of size 336 bytes (2*24*7) that represents a schedule for a week. Each hour is represented as a 16-bit integer. Every hour is divided into four quarters, each of which occupies 4 bits. A schedule starts out specifying the time windows, starting from Sunday midnight in either UTC or system local time.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sun 00:00 |
Sun 01:00 |
||||||||||||||||||||||||||||||
|
02:00 |
02:15 |
02:30 |
02:45 |
Sun 03:00 |
|||||||||||||||||||||||||||
|
Sun 04:00 |
Sun 05:00 |
||||||||||||||||||||||||||||||
|
Sun 06:00 |
Sun 07:00 |
||||||||||||||||||||||||||||||
|
Sun 08:00 |
Sun 09:00 |
||||||||||||||||||||||||||||||
|
Sun 10:00 |
Sun 11:00 |
||||||||||||||||||||||||||||||
|
Sun 12:00 |
Sun 13:00 |
||||||||||||||||||||||||||||||
|
Sun 14:00 |
Sun 15:00 |
||||||||||||||||||||||||||||||
|
Sun 16:00 |
Sun 17:00 |
||||||||||||||||||||||||||||||
|
Sun 18:00 |
Sun 19:00 |
||||||||||||||||||||||||||||||
|
Sun 20:00 |
Sun 21:00 |
||||||||||||||||||||||||||||||
|
Sun 22:00 |
Sun 23:00 |
||||||||||||||||||||||||||||||
|
Mon 00:00 |
... |
||||||||||||||||||||||||||||||
The 4 bits that store the schedule data for each quarter hour contain one of the 16 values ranging from 0x0 to 0xF. A value of 0x0 indicates that the replication schedule is off for that quarter-hour in the schedule. A value of 0xF indicates that replication is on for that quarter-hour in the schedule with full bandwidth. The levels in between are used in an implementation-defined way.<17>