similar to: Changing Windows permissions runs very slow

Displaying 20 results from an estimated 10000 matches similar to: "Changing Windows permissions runs very slow"

2020 Oct 25
2
GPO fail and sysvol perm errors
On Sun, Oct 25, 2020 at 3:31 PM Rowland penny via samba <samba at lists.samba.org> wrote: > OK, if you look at the end of the permissions, there is a '+' sign, this > shows that extended acls set, to see these: > > getfacl /usr/local/samba/var/locks/sysvol The difference in acls is that the non-working domain includes: user:3000001:r-x user:3000002:rwx user:3000003:r-x
2020 Oct 28
1
GPO fail and sysvol perm errors
For completeness: The existing GPO: # samba-tool ntacl get --as-sddl \{07AF723D-5FFD-4807-B3C6-DFCE911B922A\}/ O:DAG:DAD:P(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;EA)(A;OICIIO;0x001f01ff;;;CO)(A;OICI;0x001f01ff;;;DA)(A;OICI;0x001f01ff;;;SY)(A;OICI;0x001200a9;;;AU)(A;OICI;0x001200a9;;;ED) The newly created GPO: # samba-tool ntacl get --as-sddl \{0C0B713E-EE65-4ACE-88AE-25125E2AAE00\}/
2020 Oct 25
2
GPO fail and sysvol perm errors
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
2020 Oct 25
3
GPO fail and sysvol perm errors
On 25/10/2020 20:37, Sonic wrote: > The reset allowed the current GPO to take effect, but right after > adding a new GPO (just named it, no editing, or linking) the > sysvolcheck fails: > # samba-tool ntacl sysvolcheck > ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception > - ProvisioningError: DB ACL on GPO directory >
2019 Aug 27
3
Permissions at the top of a Samba share
Am 2019-08-26 um 16:35 schrieb Rowland penny via samba: > On 26/08/2019 15:20, ? Peter Rindfuss via samba wrote: >> Hi, >> >> I have a question regarding permissions at the top of a share as seen >> from a Windows 10 client. >> >> We are using Samba 4.10.6-Debian (van Belle) on Debian 10 (Buster) with >> one AD controller and one file server. >>
2016 Jul 24
3
Samba 4.2.14 GPO issue
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
2013 Oct 09
2
GPO Permissions _AGAIN_
Hi all, I'm afraid I'm back to my old issue of GPO permissions. I have two ADDCs providing an AD Domain (internal.stmaryscollege.co.uk (short-name 'SMC')). Servers are called 'ad-01' and 'tainan'. ad-01 is 'Version 4.0.10' and tainan is 'Version 4.1.0rc4' (the latest version in the package repos of the respective OSs (arch and gentoo)) I have
2023 Oct 19
1
Error in samba-tool ntacl sysvolcheck
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
2016 Nov 26
2
Everyone ACL problem
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
2016 Jul 21
3
gpo not working with samba 4 migrated
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, but seem that some change are not applied, why and where I can find some information, in samba log anv event viewer any error is reported Also I have tried # samba-tool ntacl sysvolreset After this tried # samba-tool ntacl sysvolcheck
2014 May 13
1
GPO problems on a 4.1.6 AD, classicupgraded, uncaught exception
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
2014 Apr 08
1
Samba4 policies acl corruption
Hi everybody. One month ago me migrated from samba 3.6 classic domain to samba4. After solving some minor problems, we have found ourselves with a ACL corruption and we don't know how to deal with this. When accesing to our sysvol shared (for example, \\domain.local\sysvol) from both Samba or Windows clients, we are refused to connect. Domain=[VECTORSF] OS=[Unix] Server=[Samba 4.1.4]
2014 Jun 23
1
Command samba-tool ntacl sysvolcheck
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
2015 Oct 02
3
sysvol acl's broken beyond repair
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}
2016 Jul 22
2
gpo not working with samba 4 migrated
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 thanks for you answer, it seems that this can help, now some >> change
2016 Nov 26
1
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
2020 May 19
2
sysvolcheck and sysvolreset errors
I have a samba DC based on Debian Buster running samba 4.12.2 from Louis' repo. A second DC on Raspbian buster is running samba 4.12.0. I have sysvol replication working using rsync/unison as per the WiKi. I wasn't having any issues until I tried to edit a GPO and found that all the acl settings had disappeared. This may have happened when I upgraded the DCs from 4.11.x to 4.12.x
2017 Jun 21
3
Fwd: AD Policies are not applying properly
Hi, We have been consistently having issues with GPO and they are not consistent. We are using version 4.6.3 with BIND DNS Backend. As suggested in some of our previous communications, when we run the samba-tool ntacl sysvolcheck it results in the error as detailed below. [root at dc1 ~]# samba-tool ntacl sysvolcheck lp_load_ex: refreshing parameters Initialising global parameters rlimit_max:
2016 Apr 22
3
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
2016 Jul 24
3
Samba 4.2.14 GPO issue
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 controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). The