From this, I do think this method could allow me to move more slowly, due to
Hi, I was looking around for Linux active directory support and found an article on ms services for UNIX. Which apparently allows Linux clients to authenticate to ad as if it was a nis and nfs server. My questions, would this be a good direction to take for active directory migration? By that I mean the following... 1 Setup ms services for UNIX, use the server for nfs and to authenticate Linux boxes with ad user accounts as if it was a nis server 2 Deploy Linux desktops, set up nis and nfs on the clients. 3 Migrate ad user accounts to a real nis and nfs server, ensuring to implement a secure channel for nis and nfs to travel over. How to do this yet I don’t know. Main reason for this idea of migration is the xp pcs requirement of group policy, I couldn't move over to samba/nfs/nis until there were no xp pcs. proprietary software holding me back. Waiting for successmaker to come out with cross platform capabilities, which I've been told they are working on.
From step 2, how would be best to go about altering the users environment in KDE? Can kiosk allow you to alter an home directory of a test user that can be used as a default profile like how xp works? Sorry for the comparison, but I can only work with what I know. I would also like to make the menu locked for students, so would that be a case of read only-ing their menu folder. Also can you prevent someone from using sudo? Im still contemplating my distro for here and am seriously considering mepis because of how slick it is and that it using true debian repositories. Unlike some distros I know...
Does freenx have to co-exist with ltsp in order for thin clients to benefit from freenx? As it seems it's not a thin client in itself. Sorry if I got the wrong end of the stick on this one, Im still learning. Many Thanks Alan Loughlin -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.9 - Release Date: 11/06/2005