search for: sysvolreset

...ersion 4.7.3-Debian root at dc3:/etc/samba# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.2 (stretch) Release: 9.2 Codename: stretch Did you upgrade, if so, from .. To ... Samba version ? No upgrades. And why was running : samba-tool ntacl sysvolreset needed? I tried the sysvolreset, as I applied a gpo to a printer deploy, but it did not appear to the user. I did as I always did and it worked, but this time it failed. On Wed, Mar 14, 2018 at 9:32 AM, L.P.H. van Belle via samba < samba at lists.samba.org> wrote: > Hai, > > No,...

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

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

...eu Almeida da Silveira <edson.tadeu at gmail.com> wrote: > > > Can you tell me what are correct permissions to set at sysvol in > > order to work and how to solve that problem with 'Domain admins' uid ? > > It isn't really a 'uid' problem, it is a 'sysvolreset' problem, giving > Domain Admins a gidNumber only makes it worse. > How to fix it ? Remove the GPO and then add it again, then NEVER use > sysvolreset again. > > > > > I´m using samba 4.4.6 and i will upgrade to 4.4.10 but i´d like to > > correct this issue before....

hi folks, After run *samba-tool ntacl sysvolreset *the below error occurs. I not remember of make any modification directly on the server. I only manager via rsat. root at dc3:/etc/samba# samba-tool ntacl sysvolreset *open: error=40 (Too many levels of symbolic links)* ERROR(runtime): uncaught exception - (-1073741823, '{Operation Failed} The...

On 1/11/2018 10:45 AM, Carlos via samba wrote: > Hi > > Any ? > > Regards; > > > On 10-01-2018 15:11, Carlos wrote: >> >> Every 5 minutes. >> >> This moment(before sysvolreset,) machine is ok . This comend is valid >> now ? >> >> *In DC01 Problem does not exist with sysvol. >> >> Regards; >> >> >> >> On 10-01-2018 14:51, lingpanda101 via samba wrote: >>> On 1/10/2018 11:42 AM, Carlos via samba wrote: >&gt...

Hi, another tipp for further debugging. Just run the sysvolreset in debug mode to see on which file it has problems to reset the permissions: samba-tool ntacl sysvolreset -d 10 2>&1 | grep "called for file" Then check the last listed file if this might be a symlink loop. If not just run it without grep and maybe a lower debug level of 3-4 to s...

...ngel via samba wrote: > Hi all, > > thanks a lot for the new release, the feature list definitely sounds > promising. > One question I have regarding this one: > > Am Donnerstag, 12. Juli 2018, 10:47:31 CEST schrieb Karolin Seeger via samba: > > > samba-tool ntacl sysvolreset is now much faster > > ----------------------------------------------- > > > > The 'samba-tool ntacl sysvolreset' command, used on the Samba AD DC, > > is now much faster than in previous versions, after an internal > > rework. > > Does that imply that...

...e all pieces together for a scenatio with two DCs and GPOs being used. Obviously the GPOs need to be replicated between DCs, I use "osync" as per the samba wiki (https://wiki.samba.org/index.php/Bidirectional_Rsync/osync_based_SysVol_replication_workaround). In that documentation the sysvolreset command is issued every time on the second DC after a successful sync. On the other hand, the page https://wiki.samba.org/index.php/Sysvolreset claims that one should never run sysvolreset or even sysvolcheck (!?) in such a scenario. So what is the correct advice? I would assume that I do not n...

...; wrote: > >> On 2017-08-24 12:27, Rowland Penny via samba wrote: >>> On Thu, 24 Aug 2017 12:03:42 +0200 >>> Sven Schwedas via samba <samba at lists.samba.org> wrote: >>> >>>> >>>> Where does the error come from, and why doesn't sysvolreset fix it? >>>> >>> >>> Mainly because (from my testing) sysvolcheck/sysvolreset is broken. >>> I do not write 'C' code and the problem seems to be in set_nt_acl >>> from source3/smbd/posix_acls.c >>> It doesn't set the correct ACL....

...a scenatio with > two DCs and GPOs being used. > Obviously the GPOs need to be replicated between DCs, I use "osync" as > per the samba wiki > (https://wiki.samba.org/index.php/Bidirectional_Rsync/osync_based_SysVol_replication_workaround). > > In that documentation the sysvolreset command is issued every time on > the second DC after a successful sync. > > On the other hand, the page https://wiki.samba.org/index.php/Sysvolreset > claims that one should never run sysvolreset or even sysvolcheck (!?) in > such a scenario. > So what is the correct advice? I wo...

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. > > > > https://wiki.samba.org/index.php/Sysvolreset > > > > Has this changed recently? > > Well, to my knowledge, the problem hasn't been fixed yet, but...

On Tue, Mar 7, 2017 at 9:32 AM, Rowland Penny via samba < samba at lists.samba.org> wrote: > It isn't really a 'uid' problem, it is a 'sysvolreset' problem, giving > Domain Admins a gidNumber only makes it worse. > How to fix it ? Remove the GPO and then add it again, then NEVER use > sysvolreset again. > > Hang on, can you explain this a little further? I thought that Domain Admins was issued gidNumber 512 by default. In...

I run the sysvolreset by without it when I duplicate the gpo (rsync) problems occurs later on windows machines perform the same on the DC that received the copy .... Regards.... Em 16-06-2017 15:08, Rowland Penny via samba escreveu: > Mine looks similar, but I am/was trying to get samba-tool to work > correc...

Sorry, my english is not very good !!! 'gpupdate /force' Before sysvolreset permission error occurs in loading some gpo, after running sysvolreset the problem has not occurred anymore, but every rsync I run sysvolreset. Regards; On 11-01-2018 13:51, lingpanda101 via samba wrote: > On 1/11/2018 10:45 AM, Carlos via samba wrote: >> Hi >> >> Any ? &...

...017-08-24 12:27, Rowland Penny via samba wrote: > On Thu, 24 Aug 2017 12:03:42 +0200 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >>> root at graz-dc-1b:~# samba --version >>> Version 4.5.8-Debian >>> root at graz-dc-1b:~# samba-tool ntacl sysvolreset && echo "no error" >>> no error >>> root at graz-dc-1b:~# samba-tool ntacl sysvolcheck >>> ERROR(<class 'samba.provision.ProvisioningError'>): uncaught >>> exception - ProvisioningError: DB ACL on GPO >>> directory /var/l...

.... move you domain folder out of the /var/lib/samba/sysvol folder. mv /var/lib/samba/sysvol/intern.domain.tld to_somewhere else. mkdir /var/lib/samba/sysvol/intern.domain.tld <<<<<<<<<< you must have an empty folder for the next command. And run samba-tool ntacl sysvolreset ---- Good luck, if you need more help, you know where to find us. ;-) ( ps, when its all done, DONT run samba-tool ntacl sysvolreset again, never ever ) Until this bug is fixed. ( more GPO tips, google: https://www.google.nl/search?q=samba+L.P.H.+van+belle+GPO&source=lnt&tbs=qdr:y&am...

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 /usr/local/samba/bin/samba-tool ntacl sysvolreset set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_BUFFER_TOO_SMALL. ERROR(runtime): uncaught exception - (-1073741789, 'Buffer too small'...

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. Most recent example (samba 4.10.1, just now) is below: # samba-tool ntacl sysvolreset set_nt_acl_conn: init_...

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 >>> GPO's created. >>> >>> https://wiki.samba.org/index.php/Sysvolreset >>> >>> Has this changed recently? >> Well, to my knowledge, the problem hasn't be...