Lion - how does a network account actually work / look?

[sfatula]

On Lion server, if I setup some computer users with network accounts, what do they see when logged in? i.e., do they have any ability to still store something on the local HD? Is even the application folder stored on the server? If not, how do they install software?

Just trying to figure out what it really means, client wise.

 

[NorCalLights]

Only their home user folder is stored on the server. Other than that, everything else is exactly the same. Users have full access to the local machine, but obviously anything stored on the local HD won't be available if they log into another machine.

 

[Mattie Num Nums]

On Lion server, if I setup some computer users with network accounts, what do they see when logged in? i.e., do they have any ability to still store something on the local HD? Is even the application folder stored on the server? If not, how do they install software?

Just trying to figure out what it really means, client wise.

You have a few options.

Essentially in Open Directory or Active Directory when you create a user all you are doing is creating a container with metadata used for authentication. What you need to do is bind each computer manually or via a script to the authentication server (OD or AD server.) Once you are bound users can login to that machine with the credentials stored in AD/OD. Once authenticated you have the option: to store home folders on a Share, not necessarily the server hosting the OD environment, it can be on a NetApp or another server; or Mobile accounts which stores the Home folder locally on the machine with the option to sync to a server somewhere (also called roaming profiles.)