Integrating Linux into a Windows Network?

Di0medies asks: "I work for a some-what small non-profit organization that uses a windows-based network. We currently have 6 servers supporting about 25 local domain users and about 25 remote users and we're planning on migrating from Server 2000 to Server 2003 in a month or so. Being a non-profit, we're always a little tight on cash and considering Microsoft charges ungodly amounts of money for server software, migrating portions of the network to Linux leaves more cash available for other IT goodies (like a new high-capacity file server!) and also adds more stability and security to the network. All of this depends on how well a Linux server will work on a Windows network. Does anyone have any suggestions regarding Linux integration? Can Windows and Linux be made to play well together? Is there anything out there to add limited Active Directory support to Linux?"

How this even got posted?

[aralin]

Seriously? Just tell the poster to go to Samba [samba.org] and leave space for more interesting questions.

Linux + Samba (+OpenVPN) = Goodbye MS

[samdu]

Unless you're running software that requires Windows on the server, you shouldn't have any problems replacing all those Windows servers with Linux boxes running Samba. I don't do Active Directory using Samba, but I've heard that it's possible and that the next version of Samba will have full AD support. I just haven't found any compelling reason to use AD.

And if you need remote VPN access, check out OpenVPN. It's SSL based, easy to configure (comparitavely), and stable. There are clients for Windows, Linux, and Mac.

Windows is sometimes free

[parvenu74]

You work for a non-profit organization and it's shelling out contribution money for Microsoft products?

Just because an organization is running Windows servers doesn't mean they have to pay for it. For some organizations Microsoft will donate software and coordinate with a local .NET users group to develop "line-of-business" applications unique to the non-profit. Case in point, the local (Kansas City) .NET users group developed an internal application to allow the Salvation Army (SA) to coordinate donations and logistics getting items to/from the SA warehouse. Those who contributed to development were given copies of Visual Studio -- for the duration of the project, of course -- and server licenses were given to the SA by the local MS office.

Usually, Microsoft software is not free, but sometimes it is...

A lot of choices

[rsax]

It all depends on your budget. It sounds weird but do you want to go the opensource way and not pay at all or do you have some funds set aside for this change? I'm mainly referring to using commercial Linux distros like RHEL [redhat.com] or SUSE [novell.com]. Both subscriptions, the basic options, can be bought for roughly $350 per year. That will get you a stable platform which doesn't change a lot for five years. If you don't want to pay for RHEL or SUSE support and don't mind supporting yourself with the help of a community then I would suggest going with a RHEL clone operating system like CentOS [centos.org]. It's based on RHEL, the developers use the same SRPM packages provided by Red Hat so you still get some of the benefits.

Now for the application stack. I prefer using Novell's eDirectory [novell.com] as opposed to Microsoft's Active Directory. It'll run on Linux so that's one less Windows server right there. The price is based on a per user basis which comes up to $2 per user! Not a bad price. Tie that in with all your Linux services such as Samba, IMAP server, Postfix with eDirectory using the LDAP protocol. Their password self-service [novell.com] option is pretty enticing as well.

While we're on the topic of Novell and moving away from Windows on servers, look into GroupWise [novell.com] as a messaging server instead of MS Exchange. Again, it runs on Linux as well a bunch of other platforms and has cross platform clients so you're not limited to Windows for end users either.

Devils Advocate, have you *asked* MS?

[millisa]

I know the original question was 'how do I dump MS for Linux', but I highly suggest you choose the right tool for the job. Yes, Linux is great. Samba is great. Administering it, well, it depends on *you* really. As most are guessing, it doesn't sound like you've heard of samba, so it is likely you are fairly new to the Linux scene. Great. Welcome.

Now, you really need to decide if it is the right tool and if you can make it the right tool. Before doing that, consider your current setup and your current upgrade path. Is MS wrong for you? Maybe not. Do you qualify for Non-profit MS licensing? [microsoft.com] Yes, it is evil and I should be lashed for suggesting it. However, it is important to know that the option exists. If you do qualify, you are not going to get a better licensing option from MS at your size in all liklihood. Small Business Server 2k3 is definitely targetted at your size organization; find out what pricing you can get for it from the MS marketroids. Let them even give their TCO arguments to you. Remember them, write them down, you'll need them.

Once you have that info, you have the ammunition to help justify your linux proposal. Or you won't and you'll have at least chosen the Evil Empire with thought...

Don't make the switch just because the zealots are pushing you to. Make the switch when it is the right economical, business & technical supportable option. Learn Samba. Prove it works to yourself. Bring in a workstation with it and prove it works to the non-profit. Prove the TCO argument. You *will* win if they really listen.