Rowland Penny
2025-Jul-09  15:04 UTC
[Samba] SYSVOL replication Windows to Samba, 2025 best practices
On Wed, 9 Jul 2025 14:51:07 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote:> Try this > > http://samba.bigbird.es/doku.php?id=samba:sync-sysvol > > You need to replicate by manually copying > > You need to do a sysvol reset once you have copied the contents.It all sort of depends on what is going to happen to the Windows DC. If the Windows DC is going to remain as part of the domain, then using one of the methods that can be found on the Samba wiki can be used, but it would probably required modifications because of the Windows DC If it is a 'one off' sync, then you could use anything, you could even connect to the sysvol share via 'connect to server' and just copy it across, just ensure you get everything and then run sysvolreset. Rowland
CED Ing. Damiano Bolla
2025-Jul-11  05:56 UTC
[Samba] SYSVOL replication Windows to Samba, 2025 best practices
Thanks Rowland Further investigation finds the following rsync server that can be run on Windows https://www.itefix.net/cwrsync/server I will try to have a periodic rsync client connect to Windows rsync server (PDC FSMO) and see how it goes If it works, it may be worth to be included in the documentation Il 2025-07-09 5:04 PM, Rowland Penny via samba ha scritto:> On Wed, 9 Jul 2025 14:51:07 +0100 > Luis Peromarta via samba <samba at lists.samba.org> wrote: > >> Try this >> >> http://samba.bigbird.es/doku.php?id=samba:sync-sysvol >> >> You need to replicate by manually copying >> >> You need to do a sysvol reset once you have copied the contents. > It all sort of depends on what is going to happen to the Windows DC. > > If the Windows DC is going to remain as part of the domain, then using > one of the methods that can be found on the Samba wiki can be used, but > it would probably required modifications because of the Windows DC > > If it is a 'one off' sync, then you could use anything, you could even > connect to the sysvol share via 'connect to server' and just copy it > across, just ensure you get everything and then run sysvolreset. > > Rowland >