similar to: Samba 4.4.2 "samba-tool ntacl sysvolreset" is not working correctly

Samba 4.4.2 I was doing some maintenance work and I noticed that sysvolcheck gave some error. I ran "samba-tool ntacl sysvolreset". Running sysvolcheck again still gives errors. I tried with several sysvol backups and the result is always the same. The affected policies are always "Default Domain Policy" and "Default Domain Controllers Policy". These policies

On my small, one DC AD setup, where I just followed the wiki and did not (!) make any other changes except for working on the AD through the RSAT, I ran samba-tool ntacl sysvolcheck and got the following output: --------------------snip-------------------- ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO directory

Hi, I got same problem describe in [1] python error end with File "/usr/lib/python2.7/site-packages/samba/ntacls.py", line 162, in setntacl so I edited ntacls.py [2] and one line before the error (line 161 in this case) I add print(file) and I found default domain policie {31B2F340-016D-11D2-945F-00C04FB984F9} was gone from file system (the error is pretty clear "no such file

Hi I'm with this problem? Version: Samba 4.3 (4.2 upgrade) S.O .: Ubuntu 4.14 samba-tool ntacl sysvolreset open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823, 'Undetermined error') File "/opt/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File

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

piggybacking on the "Syncing Sysvol" thread ... I had thought that the conventional wisdom was that ntacl sysvolreset should be mostly avoided once relative stability achieved and additional GPO's created. https://wiki.samba.org/index.php/Sysvolreset Has this changed recently? Kris Lou klou at themusiclink.net

On 18/07/2019 14:11, Jonathan Hunter via samba wrote: > On Wed, 17 Jul 2019 at 17:58, Rowland penny via samba > <samba at lists.samba.org> wrote: >> On 17/07/2019 17:43, Kris Lou via samba wrote: >>> I had thought that the conventional wisdom was that ntacl sysvolreset >>> should be mostly avoided once relative stability achieved and additional >>>

On Mon, 13 Nov 2017 09:59:23 +0100 Sina Owolabi via samba <samba at lists.samba.org> wrote: > Hi List! > > I am working my way through getting familiar with samba and I have two > domain controllers now with an additional samba file server. > The servers are CentOS 7.4.1708; > the domain controllers are built from source with samba-4.7.1; > and the file server,

Mandi! Rowland Penny via samba In chel di` si favelave... > The error you are getting is usually caused by adding GPOs to the first > DC and then NOT copying them to the second DC before running > 'sysvolreset'. The GPOs are also stored in AD, 'sysvolreset' reads AD > to find where the GPOs are supposed to be, but if it cannot find any, > it errors out.

OK, I've traced this a little further on now. I think I have followed the trail via the following items that call or refer to each other in turn: - python samba-tool ntacl sysvolreset - source3/smbd/pysmbd.c: SMB_VFS_FSET_NT_ACL( fsp, security_info_sent, sd); - source3/include/vfs_macros.h:#define SMB_VFS_FSET_NT_ACL smb_vfs_call_fset_nt_acl - source3/smbd/vfs.c:NTSTATUS

Hi Version 4.1.0pre1-GIT-957f9fa openSUSE 12.2 After running samba-tool ntaclreset These are the ACE's produced: getfacl sysvol/ # file: sysvol/ # owner: root # group: wheel # flags: s-- user::rwx user:root:rwx group::r-- group:wheel:r-- group:3000000:r-- group:3000001:r-- group:3000002:r-- mask::rwx other::--- I got the group names from wbinfo. The group numbers correspond to: 3000000

> On Tue, 11 Sep 2018 01:16:16 +0100 > niya via samba <samba at lists.samba.org <https://lists.samba.org/mailman/listinfo/samba>> wrote: > > >/hi everyone />//>/installed and joined a second dc following the instructions at />/https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory > />/both version are 4.8.2 />/when i try

Hi, I am finally revisiting my sysvol share (GPOs haven't been working for me for quite some time) and trying to get permissions sorted properly on it. For many years, "samba-tool ntacl sysvolreset" has always failed for me with errors that I have been unable to solve. Previously I have used guidance from Louis and got things working, but my sysvol is currently in a broken state.

On 03/10/15 16:03, Carlos A. P. Cunha wrote: > I compiled with these options for the wiki samba "recommended". You only require them if you are having major problems. > > samba -V > Version 4.3.0 > > samba -b | grep [S]TATEDIR | awk '{print $NF}' > /opt/samba/var/locks > OK, that looks correct. Have you altered smb.conf ? Rowland

hi everyone installed and joined a second dc following the instructions at https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory both version are 4.8.2 when i try to reset t the Sysvol folder's file system access control lists on the new dc i get the following error sudo samba-tool ntacl sysvolreset open: error=2 (No such file or directory) ERROR(runtime):

Or if you want to maintain the 'log level = 2' you can set just the 'vfs' log level to 1 eg: log level = 2 vfs:1 This way you are just silencing the bit that needs to be silenced, not the whole of samba. If that's what you want, of course. On 16 June 2017 at 07:06, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Thu, 15 Jun 2017 20:00:42 -0300 >

Hi, On Thu, 18 Jul 2019 at 14:27, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 18/07/2019 14:11, Jonathan Hunter via samba wrote: > > For me, at least, "ntacl sysvolreset" is definitely broken and has > > been for the last few years. It's on my list of things I really need > > to fix as soon as possible, but I just haven't had

Hi Rowland I removed the winbind lines, and added the 'idmap_ldb:use rfc2307 = yes' line to the second DC, and rebooted the servers, but the error does not go away. First DC: [global] dns forwarder = 8.8.8.8 netbios name = TESTBOX realm = SAMDOM.TESTING.COM server role = active directory domain controller workgroup = SAMDOM idmap_ldb:use

On Wed, 17 Jul 2019 at 17:58, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 17/07/2019 17:43, Kris Lou via samba wrote: > > I had thought that the conventional wisdom was that ntacl sysvolreset > > should be mostly avoided once relative stability achieved and additional > > GPO's created. > > > >

Hi, After making progress with my scripts for software installation (thanks, Rowland!) I am on a bit of a mission to get things working again. I found that permissions on my sysvol share were somehow incorrect (group ownership was root, etc.) so I ran 'samba-tool ntacl sysvolreset'.. however this now fails with the following error. (I'm on Samba 4.5.0) user at dc2:~ $ sudo