Hi Mosu,
thank You for Your very helpfull post.
Your answer considering the permissions of sysvol is spot on and I will check with facl-tools the permissions. My goal is to delegate permissions to a support user group and had not luck adding users to the existing groups on our UCS pdc.
In regards to the different sysvol-shares/-path:
We have a ucs@school setup with domain controllers at each site. With ucs@school 4.1 the netlogon folder was synced across the whole domain, e.g. logon scripts for one site were synced to every other pdc. This behaviour was changed with one minor upgrade to the 4.1 system, sysvol (w. path /var/lib/samba/sysvol//policies) gets still synced, but netlogon (and this now w. path /var/lib/samba/netlogon) does not.
Also: On our test systems (UCS 4.1-4) domain master and site pdc show with testparm
[netlogon]
comment = Domain logon service
path = /var/lib/samba/netlogon
case sensitive = No
read only = No
[sysvol]
path = /var/lib/samba/sysvol
case sensitive = No
acl xattr update mtime = Yes
read only = No
Output of grep -E -r ‘netlogon|scripts’ /etc/samba
/etc/samba/base.conf:[netlogon]
/etc/samba/base.conf: path = /var/lib/samba/netlogon
/etc/samba/smb.conf.debian:# in the [netlogon] share
/etc/samba/smb.conf.debian:# Un-comment the following and create the netlogon directory for Domain Logons
/etc/samba/smb.conf.debian:;[netlogon]
/etc/samba/smb.conf.debian:; path = /home/samba/netlogon
So where does the sysvol/ part come from?
I am just a simple samba3 guy, so maybe I am looking in the wrong places.
Regarding logs:
Thank You for Your help again. I hoped there would be some nice, clean logfiles considering failed logins with such a polished system as UCS :).
Thanks again for Your excellent post.
Martin