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.
Are you comfortable wiith the Linux command prompt via SSH? If so, go to the home folder and see if those users' folders belong to the:
cd /home
ls -all
The listing for User1 should look like:
drwx------ 1 User1 users 22 Nov 6 2019 User1
Then go into one of the users' folders and see about the file ownership:
cd <username>
ls -all
A file should look like:
-rw-r--r-- 1 User1 users 136364 Nov 16 2010 MyPic.jpg
This is assuming your default group is users and all are a member of that group. If anything is wrong, you can use Linux commands to fix it. If you need help, come back and paste in some results and we can give you the appropriate commands. It will still take some of your time, but not nearly as much as copying the files back and forth.
If you have a whole lot of users, a command script could be written to do it all.
Okay, I'm a bit new at Linux, but was able to get this far with few issues.
Permissions appear to be the same drwx------ on all user accounts within /home/DOMAIN, where the profile folders exist for Home Folders.
The only differences I see are that the affected users are missing information for columns "User1", and the column that would normally list "domain", and the very next column that should say "users" only lists a number "32897".
Sorry, I couldn't figure out a Format-Table equivalent for Linux that would work. Columns 3,5, and 6 if I were to guess.
I've bolded the columns in question:
Affected Users:
drwx------ 1 emptycolumn 33397 emptycolumn 32897 0 Jan 30 2020 username
Made-up example of a Working Profile:
drwx------ 1 username 33397 domain users 2.3K Sep 20 2021 username
There are no files in the affected user directories.
Do I need to manually change these columns?
I think we are on the right track, but I don't have an AD system, and it's obviously different in that case, so can't tell you how to fix it.
Linux will use the GUID for a user or group if it can't resolve it into a name, so that's what those numbers are. That definitely seems to be a part of the puzzle, though I'm surprised that the ones that work also seem to have an undefined user name.
Working users have usernames populated; I should have written a better example, that's on me.
A better example:
drwx------ 1 johnsmith 33397 domain users 2.3K Sep 20 2021 johnsmith
Anyway, I appreciate your response. I think I'm going to experiment with deleting the user directories in question and see if a relog doesn't re-create them.
Can you tell me, how does ReadyNas populate the Home Folder directories? Is it just creating directories for any AD Users it finds when Accounts>Authentication is ran, or does the end user need to authenticate to the ReadyNas and that's when the directory is created for that user?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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
