The goal is to have a custom home directory, as we need to migrate from /home, to a new volume, /people.
I've created a new test user, bilbo, yet the winbind service keeps assuming their home is at /home/bilbo instead of at /people/bilbo.
I am suspecting that Samba is not even reading the user's home directory path from Active Directory, as the results seem to indicate as such. Is there an smb.conf flag for that?
Steps taken to add new user, with a custom home directory path:
Create new user in AD, with extensions, used home directory path of "/people/bilbo"
On CentOS 7 host, I manually created /people/bilbo and contents, and tagged all files/directories with proper permissions.
However, upon initial login, the system created a new "/home/bilbo" instead of using the existing path!
What else I've tried:
Restart smb and winbind, and flushed cache (deleting *.tdb's too) - no good. Modified the local smb.conf, removing "template homedir = /home/%U" and restarted smb and winbind. - it then created a new one in /home/DEVELOPMENT/bilbo upon login, and did not attempt to look in /people at all.
Contents of smb.conf:
[global] security = ADS workgroup = DEVELOPMENT realm = DEVELOPMENT.mycompany.com client use spnego = yes server signing = auto server string = Samba Client winbind nss info = rfc2307 winbind enum users = yes winbind enum groups = yes winbind use default domain = yes winbind separator = + winbind refresh tickets = yes winbind offline logon = yes inherit acls = yes idmap config * : backend = tdb idmap config * : range = 10000-20000 template homedir = /home/%U force group = dev template shell = /bin/bash
Any suggestions, recommendations?