We have two file servers for home directory space, with six separate quota-enforced trees depending on what project you're on. They're serving files via smb or nfs. If you belong to project1, your path would look like server/a1/username; for project2 it would be server/a2/username, etc.
On Linux, if a user logs in this home directory gets an nfs mount like /h/server/a1/username. For windows, a network drive is mapped via samba at \\server\username.
I cannot seem to get the Windows path to work the same way it works for us on our current setup. I have a share, with qtrees at a1, a2, etc. And I can copy the current data to those paths, to preserve the current directory trees. But if I browse the Windows SMB share, it comes up as \\server\[a1-6]\ instead of \\server\username.
I guess the two things I'm looking for is a way to hide the directory project tree and make it so the files for which the user has access to can be shown as though they are the first level path (\\server\username) instead of the secondary path (\\server\aX\username)
I experimented with home directories, and user mapping, and I can't seem to get anywhere close to getting this behavior out of the netapp. Any idea where I'm going wrong...?
Well, maybe I'm going about this the wrong way. I can get a home directory share set up, but I can't mount the share in solaris, which means copying the existing data can't be done. There's also the question of %w vs. %d, because we are using the samba protocol for Windows domain accounts, but %w sounds like local accounts to me instead.
Should I just create my usual structure, then convert the subdirectories into home directories later? My understanding is conversion will NOT map the current (copied) directories to the existing users, but will instead create new directories for those users who login after conversion.