Currently Being ModeratedDec 26, 2012 5:22 AM (in response to Mtjoernelund)
I am building up my knowledge of OS X server (previous experience with Windows AD & Linux) so I am speaking from my current understanding (that is by way of disclaimer).
To answer your question, it is my understanding that you can, if the account type is a server 'local network user' type. If you choose/use this type then the user's home folder is hosted on the server.
As to whether OS X server can/will use a NAS for that I don't know. Try it to the server's directly attached HDD first.
Currently Being ModeratedDec 26, 2012 10:43 AM (in response to FromOZ)
I can set up a user with his home folder on the local HD just fine. The problem that I encounter is that if I set up a user with home folder located on a share mounted from my NAS the user cannot login. Hope that made my problem more clear?
Currently Being ModeratedDec 26, 2012 11:04 AM (in response to Mtjoernelund)
I would think at a minimum you'll need your NAS to be able to join/connect to your OD for the user account records. Is the user account able to authenticate with the NAS as user/password (rather than some other account to log into the NAS) and able to follow the same ACL rules as an OS X Server file share would?
For instance, if you have a user "jdoe" with an ID of 1035 it's going to need to connect to your NAS as user ID 1035 and the same password and then be able to write files to the NAS with owner ID 1035 etc in the directory you've designated as its home directory.
Currently Being ModeratedDec 26, 2012 11:59 AM (in response to infinite vortex)
The NAS is not joint with the OD, but seeing as I have tried to mount as a completely open nfs mount I did not think it would be an authentication issue.
Currently Being ModeratedDec 26, 2012 12:51 PM (in response to infinite vortex)
Success - sort of...
I believe that the answer was in the user ID. I set up a user on the server and on the NAS with the same user ID and credentials and created the folder structure of the users home on the NAS. Then I manually set the users home folder in workgroup manager to the afp-share on the NAS, and now I can sign in and the home folder syncs properly. Only concern now is, that if the user changes password, the password will not sync to the NAS. But for now I can live with that...
Currently Being ModeratedDec 26, 2012 12:58 PM (in response to Mtjoernelund)
In fact if all is well, you shouldn't even need to have created anything on the NAS drive. The moment you log in to the account it should autocreate itself. Whe it comes to passwords, this is why it's always best to use NAS drives that are capable of joining LDAP directories as user data will simoly come from the OD it connects to.
Currently Being ModeratedDec 27, 2012 4:55 AM (in response to Mtjoernelund)
Normally the NAS would need to be able to link to Open Directory so it can use the same user accounts for authentication. Unfortunately I am not aware of any NAS boxes that can do this despite the fact that nearly all NAS boxes run on Linux and 'real' Linux can do this via the same OpenLDAP software that Open Directory itself is based on.
I have personally suggested to NetGear that they should do this, they do already do this for Active Directory but not Open Directory.
There is a workaround that you could explore, historically, with NAS boxes to get round this you would tell the Mac Server to first connect to the NAS box via NFS, you would then 'reshare' the NAS box via AFP from the Mac server. So the clients would 'think' they are using a volume on the Mac server but the files would actually be stored on the NAS box.
Note: Even though Apple do not make it obvious, Mountain Lion can still act as both an NFS client (as will be used in this case) and an NFS server. In fact it supports a newer version of NFS than Snow Leopard.
You would have to manually setup an NFS mount at bootup to do this. A shellscript and a launchdaemon should be sufficient.
With some NAS boxes a very similar alternative would be to use iSCSI from the Mac server to the NAS box, some NAS boxes can act as an iSCSI server e.g. the NetGear ReadyNAS Pro range, but the Mac does not have an iSCSI client included as standard so you would have to buy a Mac iSCSI client/initiator.
Currently Being ModeratedDec 27, 2012 11:48 AM (in response to John Lockwood)
I have seen the discussions on connecting a readynas to OD, but seeing as this is for home use and I have a very limited number of users it seems manageable to handle it manually. But I definitely second the request to implement an OD client on the readynas box.
As to the suggestion using nfs I have tried that, and I can mount the NAS on the osx server, but when I try to use the nfs mount as location for the users home folder the users cannot sign in. Seems to be a problem getting access to e nfs mount from the clients, as they can also not see the share if I just true to connect to the server from another users profile. Also, I like using the afpshare directly, as this eliminates the need to pass all traffic through the server.
Currently Being ModeratedDec 27, 2012 3:17 PM (in response to Mtjoernelund)
It used to be officially supported to use NFS for clients to access their network home directories but with Lion (and Mountain Lion) this was no longer officially supported.
Therefore the need as I mentioned to 're-share' the volume via AFP. As you implied this does unfortunately impose an additional network overhead as traffic has to go as follows.
client ----> AFP ----> Server -----> NFS -----> NAS
What you could consider to help at least a little bit is to connect the server to the NAS on a totally separate network to the network the server uses to talk to the clients on. The main network would be between the server and clients, and you would use a second Ethernet connection just link the NAS and the server. As the clients will not need to talk directly to the NAS this will not be a problem. This would at least mean that each network only gets one set of traffic either AFP or NFS but not both and means the server can use both at full speed at the same time.
The Mac Pro still has two built-in 1Gbps Ethernet ports but you can also get either a USB3 Ethernet adaptor or a Thunderbolt to Ethernet adaptor (I have used one of these on a Mac mini server).
If you did not already have the NAS then people starting from new would be better off either getting a Thunderbolt RAID which can be directly attached to the Mac server, or at the higher-end go the traditional route of setting up a SAN and using an FDDI connection.
Note: You can now get Thunderbolt to FDDI interfaces.
Currently Being ModeratedJan 11, 2014 12:49 PM (in response to Mtjoernelund)
Dear Mtjoernlund, i am now in the process of reaching the same as you about a year ago. the exact same issue i have. trying to have the user home folder on the NAS and still keep the mac mini server as OD master. i get also the same issue for not being able to log in. Could you support on how to set this up?
Currently Being ModeratedFeb 10, 2014 6:17 AM (in response to raôul)
Best info I can give you is the explanation I gave in the post from Dec 26, 2012 12:51, i.e. manually adding users on both server and NAS ensuring username, credentials and UID are the same both places and then manually add the home location in workgroup manager. However as also stated above this is not preferred method and is vounarable as a password change by a user would render them unable to log in.
For now I am runing my users with small shares directly on the server and auto mounting their "secondary" home share from the NAS. Not an optimal solution but it will do until I can afford to set up a thunderbolt array of harddrives connected directly to the server.