I'm employed as a web dev at a small internet marketing company and we're looking to get a network set up that meets the following requirements:
User information stored on a central server.
Users are able to log in on one workstation, save a file to their desktop (or wherever), log out of that machine, move to a different workstation, log in again, and see that same file. (i.e: user's files need to be centralized too)
I have some experience with Linux from setting web servers up, and I'm comfortable working with the command line. I'm confident that I can figure the set up out as long as someone can point me in the right direction.
If you've set up something similar before what did you use? What issues did you run in to? What would you recommend?
Thanks in advance to anyone who can be of help!
In my OS and Networking classes we are working with Active directory. To me it looks like it will work for your situation. We are working with Windows Server 2008 RC2, but I think there are linux alternatives.
You should take a look at [url=https://wiki.archlinux.org/index.php/Sshfs]sshfs[/url].
It will allow you to mount any folder from your server to any folder on your client.
[editline]asdf[/editline]
You'll have to install and configure ssh on your server for it to work however.
It would be useful to know what your clients are running and what your server is running.
[QUOTE=Boris-B;32029280]It would be useful to know what your clients are running and what your server is running.[/QUOTE]
Nothing is set in stone yet, but I believe we're going to be running ubuntu on everything for the time being. If there's anything else that'd be a better choice though I'm open to suggestions. :)
There's something great for this, but I'm not ringing any bells right now for some reason.
Damn.
NFS would be the usual way to do this. You can have /home be an NFS mount, so everyone's files live on the server. You'll need to have enough disk space on the server, of course, but it gives you a nice centralized place to do backups of everyone's files.
Active directory tied with the users profile paths, that's pretty much all you need.
Setting it up is not very hard, only issues that you need to look at are:
Space - Depending on the amount of users you might need a lot of it
Network speeds - Active Directory can take a huge chunk of the local area speeds if set up wrongly so Invest into proper network hardware.
LTSP. Does all 'dat fun shtuff.
Ended up using LDAP for the logins and NFS for the home directories. I'm working on setting up puppet to manage the configuration for all the client machines now.
Sorry, you need to Log In to post a reply to this thread.
