The Samba-Bugzilla – Bug 12037
RSAT does not create new user profile directory.
Last modified: 2018-07-05 22:57:22 UTC
AD does not create new user profile directory.
Steps to reproduce:
1. Create directory for profile SHARE on SAMBA AD-DC
2. Add Share definition to smb4.conf
3. Reload samba configuration
(smbcontrol all reload-config or service samba_server restart)
4. Apply ACLs on SHARE as described on SAMBA wiki for PROFILES or for USER home directories.
4. Create new user via RSAT with profile set to \\DC\SHARE\%username%
\\DC\SHARE\<username> is created,
No directory is created.
If the same SHARE is used to map that username's home directory then the user directory is created as expected.
There is no log entry that I can find relating to any event relating to the creating the user profile.
If the ACL on the PROFILES share is set to Everyone Full Control then the profile file is not created either. Nor can it be created by logging in to the domain as a user. Instead the local host reports that one is working with a temporary profile and that no settings will be saved.
However. If one moves (mv) the automatically create home directory from the USERS share to the PROFILES share; and renames the moved directory from USERNAME to USERNAME.V2 then Windows 7 Pro at least finds and uses the PROFILES share without a problem. Further, if one attempts to create a new user with the same PROFILE name then RSAT ADUC does report the existence of that directory.
In either case I can find nothing in the local hosts's Event Log or in any Samba related log file on the Samba host which reports why the PROFILE is not being created.
Created attachment 12297 [details]
log.smbd extract showing attempt to create roaming profile
This is a 2000 line extract from log.smbd showing the interaction of a Win7ProSP1 client logging on to a Samba-4.3 hosted AD-DC at debug level 10.
(In reply to James B. Byrne from comment #1)
Notwithstanding that the client finds a place to keep a roaming profile it cannot use it. So, there is no work-around discovered as yet.
This is not a samba bug, please consult the mailing list or https://www.samba.org/samba/support/