Linux Workstations in a Windows Domain?
gsperling asks: "As Windows licensing costs are gradually increasing, and options for those licenses are decreasing, I am forced to investigate Windows alternatives. I am trying to begin rolling out Linux as an alternative desktop solution to my enterprise. I am an IT Manager for a company of approximately 65 users. We are incorporating a second company into ours in the next six months, and that 65 number will grow to well over 150. This is a solution that I need to start working on TODAY. We currently have a Windows 2000 Server. It is primarily used as a file and printer sharing server, along with maintaining all of the user accounts domain-wide. I would like to know how it is possible to get a Linux Workstation to authenticate against the user database in our Windows 2000 Server. I have exhaustively Google'd, read thousands of mailing list archives, and have still come up short. After I receive my results, I plan on publishing a whitepaper on how this is done, of course giving credit where credit is due." For those of you using Linux in the Enterprise, how have you managed to get Windows to play nice with any Linux boxen in your domain?
The person is probably not going to be the one to mess it up. He is looking for information on how to implement things, and will be running a test case to see how it works. He has stated his reasons(money, and since he's on slashdot: dislikeing of MS) and is looking for the best solution that there is available to him.
He is not switching his whole server over to Linux with Samba and auth on it, he is moving some client systems over. Major difference in the disruption level if things don't work out.
On Arrakis: early worm gets the bird. Magister mundi sum!