similar to: Proper sysvol permissions

Displaying 20 results from an estimated 2000 matches similar to: "Proper sysvol permissions"

2018 Jul 24
3
Force set group id on samba domain member
2018-07-24 23:26 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Tue, 24 Jul 2018 22:50:16 +0200 > Michal <Michal67M at seznam.cz> wrote: > > > 2018-07-24 16:53 GMT+02:00 Rowland Penny via samba > > <samba at lists.samba.org>: > > > > > > Do the users have a gidNumber attribute containing the gidNumber of > > >
2018 Jun 22
1
Proper sysvol permissions
(I am not getting emails from the samba list (I do not know why), this is copy from web archive, sorry :-( )<br><br>On Fri, 22 Jun 2018 16:07:39 +0200 Michal via samba <<a href='https://lists.samba.org/mailman/listinfo/samba'>samba at lists.samba.org</a>> wrote: >><i> Samba 4.8.2 as AD controller, installed from scratch (no upgrade).
2018 Jul 25
2
Fwd: Force set group id on samba domain member
On Wed, 25 Jul 2018 22:40:25 +0200 Michal via samba <samba at lists.samba.org> wrote: > ---------- Forwarded message ---------- > From: Majkl Majkl <themajklthe at gmail.com> > Date: 2018-07-25 22:28 GMT+02:00 > Subject: Re: [Samba] Force set group id on samba domain member > To: Rowland Penny <rpenny at samba.org> > Cc: "samba at lists.samba.org"
2018 Jul 09
1
Fwd: classicupgrade questions
 Does anybody know any answer in this topic, please?  Michal ---------- Původní e-mail ---------- Od: Michal via samba <samba at lists.samba.org> Komu: samba at lists.samba.org Datum: 4. 7. 2018 8:58:45 Předmět: [Samba] classicupgrade questions "I am trying to do a classicupgrade.  (This is not 1st try, I went through it once time already; then I deleted all data and trying it
2018 Jul 04
5
classicupgrade questions
I am trying to do a classicupgrade.  (This is not 1st try, I went through it once time already; then I deleted all data and trying it again, with questions now.) Command samba-tool domain classicupgrade --dbdir=/etc/samba.PDC/ --realm=ad.nemuh.cz --dns-backend=BIND9_DLZ /etc/samba.PDC/smb.PDC.conf Problem a) ... init_sam_from_ldap: Entry found for user: pc0027$ init_sam_from_ldap: Failed to
2018 Jun 25
2
Proper sysvol permissions
(sorry for not threading, still getting no mails from  samba list) Ad rights on samba directories: # rm -rf /usr/local/samba.ad # cd /usr/src/samba-4.8.2 # make install (no dirs in /usr/local/samba.ad/var/locks/ at this point) # /usr/local/samba.ad/sbin/samba-tool domain provision --use-rfc2307 -- interactive       realm: NEMUH.CZ       netbios: UHN    ... # ll
2018 Jul 25
0
Fwd: Force set group id on samba domain member
---------- Forwarded message ---------- From: Majkl Majkl <themajklthe at gmail.com> Date: 2018-07-25 22:28 GMT+02:00 Subject: Re: [Samba] Force set group id on samba domain member To: Rowland Penny <rpenny at samba.org> Cc: "samba at lists.samba.org" <samba at lists.samba.org> 2018-07-25 9:19 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: >
2018 Jul 25
0
Fwd: Force set group id on samba domain member
2018-07-25 22:57 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Wed, 25 Jul 2018 22:40:25 +0200 > Michal via samba <samba at lists.samba.org> wrote: > > > ---------- Forwarded message ---------- > > From: Majkl Majkl <themajklthe at gmail.com> > > Date: 2018-07-25 22:28 GMT+02:00 > > Subject: Re: [Samba] Force set group id on
2018 Jul 10
0
My terrible fail - started AD together with NT4 domain. Help needed
I am in a process of moving from NT4 domain to AD domain. And I did exactly what should not be done, I run AD on the production network. Now clients (Win7 and Win10) can not see old NT4 domain controller. What exactly I did:   - exported production LDAP data of our  domain called "NIS" and started new LDAP server with that data on new linux server, called ad1   - copied samba config
2018 Jul 24
5
Force set group id on samba domain member
Samba DM config below. Directories with setgid: $ll /home4/group total 32 drwxrws--- 7 NIS\nisadmin NIS\audio 4096 Jul 24 14:14 audio drwxrwx--- 2 NIS\nisadmin NIS\dok-sprava 4096 Jul 21 09:23 dok-sprava drwxrwx--- 2 NIS\nisadmin NIS\poj 4096 Jul 23 08:38 poj drwxrwx--- 2 NIS\nisadmin NIS\projekty 4096 Jul 23 09:14 projekty When user creates file/dir directly on linux, the
2018 Jul 24
3
Force set group id on samba domain member
2018-07-24 16:53 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Tue, 24 Jul 2018 15:57:46 +0200 > Michal <Michal67M at seznam.cz> wrote: > > > For being honest, in my previous tests this user's (user test1) new > > files was created with NIS\audio group as extected; but other user's > > files (user amistest) was created with
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:
2018 Jul 10
0
classicupgrade questions
Am Mittwoch, 4. Juli 2018, 08:55:19 CEST schrieb Michal via samba: My mailer (kmail) is broken... > b) After upgrade, a lot of imported users in AD have "account > disabled". One of them, as far as I can remember, was user "anger": > dn: uid=anger,ou=People,dc=nspuh,dc=cz > objectClass: shadowAccount > objectClass: person > objectClass: inetOrgPerson >
2017 Jun 22
0
Fwd: AD Policies are not applying properly
Hi, No solutions to get out of this? -- Thanks & Regards, Anantha Raghava On 21/06/17 7:05 PM, Anantha Raghava wrote: > 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
2019 Jun 21
0
GPO ACL
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
2013 Jan 10
1
ACL on GPO directory does not match expected value from GPO object. AGAIN.
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
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
2023 Oct 19
1
Error in samba-tool ntacl sysvolcheck
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"
2015 Nov 16
0
samba-tool ntacl sysvolcheck and sysvolreset
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
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