NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Home Folders won't deploy for already created users
Model: ReadyNas 3220 Firmware: 6.10.5 Hotfix 1 Environment: Win10 20H2-21H1 | Domain I'm having an issue where after I've enabled Home Folders, already present user profiles on client machines ...
OK, so mwilliams' personal folder is assigned to user 33397, which does not exist, and group 32897, which probably doesn't either.
drwx------ 1 33397 32897 0 Jan 30 2020 mwilliams
His proper user GUID is 33988 and his group is 33281:
uid=33988(mwilliams) gid=33281(domain users)
So I think chown -R mwilliams:33281 mwilliams from the .home share should fix the problem.
If not, then chown -R 33988:33281 mwilliams.
If the first one works, then this script should do it for all:
cd /home
for dir in */; do chown -R "${dir%?}:33281" "$dir"; done
chown -R admin:admin adminI'm using the GID for the group because I'm not entirely sure how to handle the group name "domain users" with a space in it.
If you have to use the UID instead of the name to make it work, then it'll take a lot more to get that info, and it's probably easier to just do it manually unless hou have a huge number of affected users.
I think that would be a very bad idea as a first try. First off, user directories are not just directories, they are BTRFS subvolumes. And I don't know whether or not they would be automatically created a second time. If they are, I don't know why they wouldn't suffer from the same issue.
For non-domain users, a user has to actually log in for the home folder to be created. I assume the same is true of a domain user.
Can you paste in an actual couple of listings from the ls-all command from /home instead of re-creating it? One that shows both at least one properly working and one not would help the most. The one you listed has a couple things that confuse me. First, it looks like a combination of one for a directory and one for a file. And second "domain users" as a "user name" that includes a space. And is domain actually the name of your domain, or literally the work "domain"?
It may also help if you take a look at the results of getent passwd and see if it prints the names of domain users as well as local ones. There will be a lot of system reserved "users" with GUIDs below 100 that you can just ignore. No need to post that for now, just see if they show up and if anything looks different between a user with a working and non-working home folder other than their own GUID.
Thanks for the reply.
Sandshark wrote:I think that would be a very bad idea as a first try. First off, user directories are not just directories, they are BTRFS subvolumes. And I don't know whether or not they would be automatically created a second time. If they are, I don't know why they wouldn't suffer from the same issue.
I found this out shortly after I posted. Decided not to go down that road.
Here is a copy/paste, as root, from ls -all from /home/DOMAIN where "DOMAIN" is my domain name:
drwx------ 1 bsmith domain users 56 Aug 17 15:09 bsmith
drwx------ 1 33397 32897 0 Jan 30 2020 mwilliams
The mwilliams would be an affected user.
It just says "domain" for working users, not the actual domain name.
getent passwd lists no end-users as far as I can tell:
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/bin/sh
bin:x:2:2:bin:/bin:/bin/sh
sys:x:3:3:sys:/dev:/bin/sh
sync:x:4:99:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/bin/sh
man:x:6:12:man:/var/cache/man:/bin/sh
lp:x:7:7:lp:/var/spool/lpd:/bin/sh
mail:x:8:8:mail:/var/mail:/bin/sh
news:x:9:9:news:/var/spool/news:/bin/sh
uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
proxy:x:13:13:proxy:/bin:/bin/sh
www-data x:33:33:www-data:/var/www:/bin/sh
backup:x:34:34:backup:/var/backups:/bin/sh
list:x:38:38:Mailing List Manager:/var/list:/bin/sh
irc:x:39:39:ircd:/var/run/ircd:/bin/sh
systemd-timesync:x:40:49::/run/systemd:/bin/false
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
systemd-network:x:42:51::/run/systemd/netif:/bin/false
systemd-resolve:x:43:52::/run/systemd/resolve:/bin/false
systemd-bus-proxy:x:44:53::/run/systemd:/bin/false
_apt:x:45:99::/nonexistent:/bin/false
clamav:x:46:54::/var/lib/clamav:/bin/false
mysql:x:47:55::/nonexistent:/bin/false
media:x:71:99::/var/cache/forked-daapd:/bin/false
statd:x:79:99::/var/lib/nfs:/bin/false
libuuid:x:80:80::/var/lib/libuuid:/bin/sh
sshd:x:82:99::/var/run/sshd:/usr/sbin/nologin
messagebus:x:83:83::/var/run/dbus:/bin/false
avahi:x:84:84::/var/run/avahi-daemon:/bin/false
nut:x:85:85::/var/lib/nut:/bin/false
snmp:x:86:86::/var/lib/snmp:/bin/false
klog:x:89:89::/home/klog:/bin/false
syslog:x:91:91::/home/syslog:/bin/false
ReadyNAS:x:96:96::/var/lib/timemachine:/bin/false
ftp:x:97:97::/var/ftp:/bin/false
admin:x:98:98::/home/admin:/bin/false
guest:x:99:99:nobody:/nonexistent:/bin/false
nobody:x:99:99:nobody:/nonexistent:/bin/false
Thanks again for your time.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
