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 ...
Sandshark wrote:Just in case we are chasing the wrong cause, are you aware of anything else (like an OS upgrade) that happened between when the affected users were added to the AD and the unaffected were?
I caught the issue within about 10 minutes of enabling smb and deploying the GPO for the desktop shortcut, that is to say from when I deployed it to when I realized the issue, nothing major had changed.
Sandshark wrote:Do all the unaffected users have the same group GUID (32897) but a unique user GUID?
No. They are what looks to be sequential for the GUID, user GUID is listed as 32897 for every affected user, and "user" for unaffected users.
Sandshark wrote:What do you get from these commands:
id bsmith
id mwilliams
id 33397
cat /etc/group (just need entries 100 and above)
cat /etc/passwd (entries for at least bsmith, mwilliams, and 33397, if they exist)
id bsmith: (for privacy, AD security groups have been renamed as "ADsecgroupX" where applicable)
uid=35623(bsmith) gid=33281(domain users) groups=33281(domain users),35623(bsmith),33899(ADsecgroup1),32769(BUILTIN\users)
id mwilliams: (for privacy, AD security groups have been renamed as "ADsecgroupX" where applicable)
uid=33988(mwilliams) gid=33281(domain users) groups=33281(domain users),33988(mwilliams),36077(ADsecgroup2),33992(ADsecgroup3),32769(BUILTIN\users)
id 33397:
id: '33397':no such user
cat etc/group:
entries stop at "users:x100:"
everything else is <100
cat etc/passwd:
They do not exist. I suspect it's because of AD integration.
Sandshark wrote:BTW, do you have an inactive affected user that we can "mess with" without potentially disrupting your business flow?
I absolutely do.
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 admin
I'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.
Sorry, I replied to this but my reply just vanished, so here goes again.
The first line worked.As for the "Domain Users" and as an example of what I did verbatim, I just ran:
id mwilliams
noted the gid of 33281(domain users), and ran:chown -R mwilliams:33281 /home/DOMAIN/mwilliams
I will try the script after a bit.
Thank you so much for your time and patience.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
