SysVol replication (DFS-R): Difference between revisions
From SambaWiki
m (/* remove line) |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 8: | Line 8: | ||
* [[Robocopy_based_SysVol_replication_workaround|Robocopy based SysVol replication workaround]] (Samba DCs -> Windows DCs): Quick set, easy to configure, uses MS robocopy |
* [[Robocopy_based_SysVol_replication_workaround|Robocopy based SysVol replication workaround]] (Samba DCs -> Windows DCs): Quick set, easy to configure, uses MS robocopy |
||
{{Imbox |
|||
| type = warning |
|||
| text = You need to sync <code>idmap.ldb</code> from the DC holding the PDC_Emulator FSMO role to all other DCS. This ensures that all DCs will use the same IDs. If you do not sync <code>idmap.ldb</code>, you can and will get different IDs on each DC. |
|||
}} |
|||
Revision as of 11:22, 9 March 2022
Samba in its current state doesn't support SysVol replication via DFS-R (Distributed File System Replication) or the older FRS (File Replication Service) used in Windows Server 2000/2003 for Sysvol replication.
We Currently advise administrators to use one of the following workarounds:
- Rsync based SysVol replication workaround (Samba DCs only): Quick setup, easy to configure.
- Bidirectional Rsync/Unison based SysVol replication workaround (Samba DCs only): More complex, requires third party script, each DC requires a cron job against each other DC
- Bidirectional Rsync/osync based SysVol replication workaround (Samba DCs only): More complex, requires third party script, each DC requires a cron job against each other DC
- Robocopy based SysVol replication workaround (Samba DCs -> Windows DCs): Quick set, easy to configure, uses MS robocopy
You need to sync idmap.ldb from the DC holding the PDC_Emulator FSMO role to all other DCS. This ensures that all DCs will use the same IDs. If you do not sync idmap.ldb , you can and will get different IDs on each DC. |