similar to: samba-ttol ntacl set usage

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, after adding a new GPO the ntacl sysvolcheck fails and i want wo repair with ntacl sysvolreset.... biut this fails aslo in the end with: connect_acl_xattr: setting 'inherit acls = true' 'dos filemode = true' and 'force unknown acl user = true' for service sysvol open: error=2 (No such file or directory) ERROR(runtime): uncaught exception - (-1073741823,

Can anyone explain what is happening when I run / usr / local / samba / bin / samba-tool ntacl sysvolcheck it and an error? ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO file /usr/local/samba/var/locks/sysvol/tdsfs01.net/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Scripts/scripts.ini

That's not a problem its just a ACL provisioning message as you can see the result was "DAG:DAD:PAI" but expected was "O:DAG:DAD:PAR" that's "normal" ;-) just ignore it or do a "samba-tool ntacl sysvolreset" Am 19.10.23 um 17:27 schrieb bd730c5053df9efb via samba: > Hi! > > I executed the command "samba-tool ntacl sysvolcheck"

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

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 >>>

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, installed winbind, smb and nmb from CentOS repos. My problem is after bringing up the second domain controller and successfully joining it

Hi! I executed the command "samba-tool ntacl sysvolcheck" on a DC and I got the following I pasted below. The first DC was provisioned migrating from a samba NT4 PDC with an LDAP backend using the classic upgrade procedure. I haven't detected any problem but I wanted to make sure there isn't any problem I might not be seeing yet. ERROR(<class

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, 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

I have a site with a working Samba4 AD domain with a single DC. It works. I've added three new DCs to the domain [using the SerNet packages for 4.0.21]. The intention is to then demote the old, original Samba4 DC. But problems exist for netlogon/sysvol. One of the new DCs - the second one added - works, clients can access netlogon & sysvol. However the other two DCs have ACL errors

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.

Hi, My Samba 3.6.6 file server isn't setting the security.NTACL extended attribute. It can set the user.DOSATTRIB without any issue. This appears to be an LXC container issue, as outside the container I can set this using the setfattr command without issue, whereas I can't do this inside. Despite this not being a Samba issue, I was wondering whether anybody has any encountered

Hi all; for few weeks I'm trying to implement a new samba PDC server for my school. It is based on debian squeeze and samba 3.5.6 with lDAP backend. I was able to join a computer into domain, LDAP is working, mapping home drive for users also. It seems that almost all works good but with one exeption. The one thing which is broken is roaming profile support. When user is logging into domain

Hello, Since I updated recently my samba DC's, I've noticed some werid behaviour on windows stations (seems random?) with some GPO's not being applied from time to time (reboot or even logoff-login usually does the trick). When policy is not applied and I run "gpupdate" on windows client  I'm getting output, that policy xxx (Default domain policy) could not be

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,

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. > > > >

This is my smb.conf root at DC02:~# cat /etc/samba/smb.conf # Global parameters [global] workgroup = CLINICAGUEMES realm = CLINICAGUEMES.COM.AR netbios name = DC02 server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate idmap_ldb:use rfc2307 = yes ldap server require strong

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

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