similar to: Everyone ACL problem

Yes, I have. But nothing change... Kevin Le 26/11/2016 à 12:08, Rowland Penny via samba a écrit : > On Sat, 26 Nov 2016 11:44:50 +0100 > Kévin GUERINEAU via samba <samba at lists.samba.org> wrote: > >> Hello list, >> >> I have problems with my PDC Samba Servers and all file servers. >> All DC Server have a compiled Samba 4.4.5. File servers have Samba

On Sat, 26 Nov 2016 11:44:50 +0100 Kévin GUERINEAU via samba <samba at lists.samba.org> wrote: > Hello list, > > I have problems with my PDC Samba Servers and all file servers. > All DC Server have a compiled Samba 4.4.5. File servers have Samba > Debian packages. > > In all shared folders, the ACL has the group "Everyone" and I can't > remove it.

Hello list, I have problems with my PDC Samba Servers and all file servers. All DC Server have a compiled Samba 4.4.5. File servers have Samba Debian packages. In all shared folders, the ACL has the group "Everyone" and I can't remove it. The biggest problem concern SYSVOL, I can't modify GPO, I have an error in MMC. I have tried to resolv the problem with the

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

Hello, I've en error again in the samba AD world. I use RSAT with the DOMAIN\administrator account to make some GPOs. Sometimes it doesn't work. So I have checked GPO ACL with 'gpo aclcheck' command, and this is the return : got OID=1.2.840.48018.1.2.2 ERROR: Invalid GPO ACL

Hi all, Some (then all) of our workstations were complaining about incorrect ACLs on GPOs and were unable to read the gpt.ini to apply the GPOs. So I did a sysvolcheck and sure enough I'd lost the ACLs when I moved our sysvol share to a new location on the server (whoops, mea culpa). I ran a sysvolreset which took a long time to return (some 5 minutes, please see my post on slow winbind

On Sun, Oct 25, 2020 at 4:02 PM Rowland penny via samba <samba at lists.samba.org> wrote: > What do you mean by 'working domain' and 'non-working domain' ? > Do you have two domains ? Different sites, different companies, not related. The working one was also a classic upgrade but earlier on, pre 4.6.x. Just using it to compare. > I am also trying to understand why

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

Hi all, We'er running a classicupgraded samba4 AD 4.1.6 sernet for a month or two now, and all is very well. :-) It has been classicupgraded using the same 4.1.6. Today I wanted to try GPO's and they are not applied. GPUpdate /force tells me: "Windows attempted to read the file blahblah\gpt.ini from a domain controller and was not successful". Taken from the mailinglist, I

I'm running rc6, but it's not a clean installation, it's samba3 upgraded to 4.0 in ages of beta2. samba-tool ntacl sysvolcheck dies with message about incorrect acl on gpo, but that acl is set by sysvolreset. lobus at sirius-a:~$ sudo samba-tool ntacl sysvolcheck ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO

Hi, Do you have any specific error message in Windows events log concerning GPO? Regards Le 24/07/2016 à 05:40, Min Wai Chan a écrit : > Dear All, > I've recently upgrade from samba 4.1.x to samba 4.2.14 and found that GPO > are having issue > > Specifically when I'm adding new using they *never *got the gpupdate > success fully. > > When I run samba-tool ntacl

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

On 25/10/2020 20:20, Sonic wrote: > On Sun, Oct 25, 2020 at 4:02 PM Rowland penny via samba > <samba at lists.samba.org> wrote: >> What do you mean by 'working domain' and 'non-working domain' ? >> Do you have two domains ? > Different sites, different companies, not related. The working one was > also a classic upgrade but earlier on, pre 4.6.x. Just

I'm not sure what are you deatiling, is a bug in progress taht can cause this random problems with some gpos or this error can be ignored? 2016-07-21 20:37 GMT+02:00 Trenta sis <trenta.sis at gmail.com>: > Hi, > > First of all thanks for you answer, it seems that this can help, now some > change made to gpo are applied and we are not receiving error in event > viewer,

I have upgraded Samba from a NT PDC to an AD DC about a week ago. Everything went pretty well until today. I've already configured about 25 GPO's (through RSAT on a Windows 10 machine) - but when I came to add more GPO's - it wouldn't let me with the above error message. My specs are: Samba 4.5.0 Slackware -current 64bit Kernel 4.4.20 The client machine is a Windows 10 Pro.

Dear All, I've recently upgrade from samba 4.1.x to samba 4.2.14 and found that GPO are having issue Specifically when I'm adding new using they *never *got the gpupdate success fully. When I run samba-tool ntacl sysvolcheck or samba-tool ntacl sysvolreset But don't seem to got it fix.. Any suggestion? Thank in advance. #samba-tool ntacl sysvolcheck Processing section

Hi everyone. I ran into notorios gpo error on windows clients. When I go to my dc controller and run samba-tool ntacl sysvolcheck I get an error: ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: DB ACL on GPO directory /usr/local/samba/var/locks/sysvol/tsnr.mtt/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}

Hi, That's look more like a gpupdate output than an event log entry :-) Le 24/07/2016 à 20:46, Min Wai Chan a écrit : > Hello Sébastien Le Ray, > > The PC reply the following... > > The processing of Group Policy failed. Windows could not resolve the user > name. This could be caused by one or more of the following: > a) Name Resolution failure on the current domain

On Thu, 24 Aug 2017 12:41:36 +0200 Sven Schwedas via samba <samba at lists.samba.org> 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: > > > >>> root at graz-dc-1b:~# samba --version > >>> Version 4.5.8-Debian > >>>

On 7/22/2016 3:37 AM, Rowland penny wrote: > On 21/07/16 22:18, Trenta sis wrote: >> I'm not sure what are you deatiling, is a bug in progress taht can cause >> this random problems with some gpos or this error can be ignored? >> >> 2016-07-21 20:37 GMT+02:00 Trenta sis <trenta.sis at gmail.com>: >> >>> Hi, >>> >>> First of all