similar to: Question on sysvol replication, GPOs and sysvolreset

Try: http://samba.bigbird.es/doku.php?id=samba:sync-sysvol I would recommend one way sync always from PDC FSMO owner, as this is the machine the GPOs get created in by default. And of course : http://samba.bigbird.es/doku.php?id=samba:sync-idmap.ldb Regards. LP On 5 Dec 2023 at 13:47 +0100, Jakob Curdes via samba <samba at lists.samba.org>, wrote: > Hello, > > I am wondering

Hi, In reading this list I see a lot of talk about samba-tool ntacl sysvolreset actually breaking things. Given the above How do I properly configure a 2nd AD DC or setup sysvol replication? For instance If I were to follow https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory In the Built-in Groups GID Mappings section the last thing it says to do is run samba-tool

Hi, I would like to know which the best way to replicate Sysvol between my DC Samba 4 is with Rsync/Osync, as per the article below? https://wiki.samba.org/index.php/Bidirectional_Rsync/osync_based_SysVol_replication_workaround I have 3 Samba 4 DC. Regards, M?rcio Bacci

On 22 November 2017 at 17:45, Rowland Penny <rpenny at samba.org> wrote: > On Wed, 22 Nov 2017 16:01:17 +0200 > Ian Coetzee via samba <samba at lists.samba.org> wrote: > > > Hi Guys, > > > > I have run into a very interesting problem using GPO's on our DC's. > > > > As you may (or may not) know, we have migrated to a pure Samba4 (Git >

Hi Guys, I have run into a very interesting problem using GPO's on our DC's. As you may (or may not) know, we have migrated to a pure Samba4 (Git stable branch checkout) AD network. I can't be happier. *Kudos to the Samba team* We are running to DC's, DC1 and DC2, both full fledged DC's, both running CentOS 6.9, fully up to date. For the sysvol partition I decided to run a

On 23 November 2017 at 14:16, Rowland Penny <rpenny at samba.org> wrote: > On Thu, 23 Nov 2017 14:01:03 +0200 > Ian Coetzee via samba <samba at lists.samba.org> wrote: > > > On 22 November 2017 at 17:45, Rowland Penny <rpenny at samba.org> wrote: > > > > > On Wed, 22 Nov 2017 16:01:17 +0200 > > > Ian Coetzee via samba <samba at

Hi Igor, Am 26.08.2016 um 13:23 schrieb Igor & Sandra: > I am part of a group of studies and learning samba 4. > The greatest difficulty is the language, many do not know English. > We set up a team to translate the documentation Samba 4 for our > language. > We would like to take the translation into Portuguese and make it > official. As said in my previous mail: Our

On Sun, 2 Oct 2016 11:45:15 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 02.10.2016 um 08:20 schrieb Trenta sis via samba: > > Hi, > > > > I have a samba 4.4.5 AD domain and is working perfect, but now I > > need to add a second samba 4 AD, I have found that in > >

I have observed 3 scenarios after I reboot the host with 2 guests (which are supposed to autostart after boot/reboot of the host): 1. Default network is created but I can not ping guests. Gests don't have assigned IP address or they both have IP address 192.168.122.100. 2. Default network is not created. 3. Default netork is properly created and everything works fine. In each case guests are

On the "Bidirectional Rsync/Unison based SysVol replication workaround" page. The title (as you can see) includes the word UNISON when in fact the "Unison" program is NOT being used for this replication anymore. As the instructions there actually use "Osync" then the word "UNISON" should probably need to be replaced with "OSYNC". (I looked

On 2016-08-26 10:59, Rowland Penny via samba wrote: > On Thu, 25 Aug 2016 06:08:16 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> On the "Bidirectional Rsync/Unison based SysVol replication >> workaround" page. The title (as you can see) includes the word UNISON >> when in fact the "Unison" program is NOT being

Dear Belle, That produce the similar situation. Thus I'm trying osync And the result are much present according to my test case And configuration are much streamline. However, I'm not sure how it can work with 2 DC or more... Thank You On Mon, Jun 22, 2015 at 9:05 PM, L.P.H. van Belle <belle at bazuin.nl> wrote: > Hai Min Wai Chan, > > I have tested it as shown in

Hi, I was thinking about bidirectional sync of sysvol and i've a question: ?What about DRBD?. You can create a disk partition in every node, create a DRBD cluster and then mount that partition on sysvol folder. The sincronization is bidirectional and in real time. For now i've not tested this option, but i've plans to start some tests. What is your opinion about this? Greetings!!

Dear Daniel, Klaus I've try that before But because of how samba work on the files. The Advise is No Without CTDB, you will just shoot yourself on the foot... On Thu, Jun 25, 2015 at 7:39 PM, Zerwes, Klaus <zerwes at rosalux.de> wrote: > Just some notes: > For master <-> master setup (bi-directional sync) you need AFAIK a cluster > filesystem. > I have no idea

Hello Min Wai Chan, ? Can you explain more about,, the DC1 will remove any emptey directory on DC1. tested it here, but that does not occure here. i can create empty directories on DC1, and these are synced to DC2. empty or not. ? ?DC1 will overwrite any users/group change on DC2? if setup correctly, your sysvol rights on DC1 and DC2 are the same.. ? i suggest you to the following. get the

2015-06-25 14:44 GMT+02:00 Daniel Carrasco Mar?n <danielmadrid19 at gmail.com>: > > > 2015-06-25 14:12 GMT+02:00 Min Wai Chan <dcmwai at gmail.com>: > >> Dear Daniel, Klaus >> >> I've try that before >> But because of how samba work on the files. >> >> The Advise is No >> Without CTDB, you will just shoot yourself on the

Hello all, Just to ask have anyone try osync before? https://github.com/deajan/osync And would you think that this will fix our issue on https://wiki.samba.org/index.php/SysVol_Bidirectional_Replication Where DC2 files or folder will be removed? Thank You.

I just setup replication of sysvol between my two DC's using the "Bidirectional Rsync/osync based SysVol replication workaround" and all went well with two exception. First, it seems that since an upgrade to Openssh version 7.0 that "dsa" key use is disabled by default by the Openssh team. There has been some questions for some time now regarding the security of

On Thu, 23 Nov 2017 14:01:03 +0200 Ian Coetzee via samba <samba at lists.samba.org> wrote: > On 22 November 2017 at 17:45, Rowland Penny <rpenny at samba.org> wrote: > > > On Wed, 22 Nov 2017 16:01:17 +0200 > > Ian Coetzee via samba <samba at lists.samba.org> wrote: > > > > > Hi Guys, > > > > > > I have run into a very

On Wed, 22 Nov 2017 16:01:17 +0200 Ian Coetzee via samba <samba at lists.samba.org> wrote: > Hi Guys, > > I have run into a very interesting problem using GPO's on our DC's. > > As you may (or may not) know, we have migrated to a pure Samba4 (Git > stable branch checkout) AD network. I can't be happier. *Kudos to the > Samba team* > > We are running