Slashdot Mirror
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?"
If programs would be read like poetry, most programmers would be Vogons.
The word is "samba." Samba will more or less allow a Linux server to fully integrate intoa Windows network. I would suggest that, if you are a Linux novice, you leave domain control on Windows and just use Linux as a workhorse. Time enough to move everything to Linux when you're more comfortable with Linux.
"He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
I've done similar things in the past and currently I run my print and file servers on Linux quite seamlessly. All of the Windows admins and users don't know any different.
Samba + PAM + CUPS gives you integrated authentication, SMB/CIFS file serving (Windows file sharing protocol), as well as SMB and IPP printing.
I don't know of any tutorials off the top of my head but Google gave me all I needed to figure it out.
You have, what, 50 users? Why deal with the licensing headaches from Win* server at all? Linux (running Samba) makes a great Domain Controller. Add another Linux/Samba for SAN/NAS. Throw in one more for a print server. I don't know too much about mail on Linux, but I hear postfix is nice.
In any event, your network is *way* too small to deal with Win* crap. Even if it's *donated* by MS, there's bound to be licensing issues at some point.
Deploy Linux in your server room and then migrate your users at a later date...if at all.
I'd rather you do it wrong, than for me to have to do it at all.
I know there are lots of free software bigots on this site and you can find lots of sites purporting to have easy configuration instructions for kerberos/AD set up, but I don't care. This product works, period. And it does it in an easy manner and it does it flawlessly, at least in our environment, which is a true 24x7 environment where uptime and accessibility matters -- a hospital.
Democrats and Republicans are like AIDS and Cancer, I want neither!
I work for an organization that provides tech support for non-profits. It's sad but true, non-profits have to live in the same world as commercial entities. They're subject to the same forces as anyone else -- they have momentum with existing Microsoft installations; there are custom legacy software that would require replacement, retaining, and conversation of data; they have users who only know Windows and (rightly or wrongly) would resist a switch to any other OS because it would mean they have to learn to use something slightly different.
You should be supporting the original poster's efforts to switch, not deriding him for not having already completed the task on every machine they have.
One thing we found when moving from 2000 to 2003 servers is that the terminal server licensing is not free. On a 2000 server each server had an unlimited TS License. On 2003, you have to purchase them. One extra cost to beware of.
If at first you don't succeed, so much for skydiving.
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.
If you have an application that requires Microsoft to run on the backend, then you are going to have trouble replacing said server with Samba. If it is an application that everyone uses, then even if you replace the other servers with Samba, you will still need the Microsoft CALs (client access license) to attach to the one remaning server. That is where the costs get you, not always the server software, but the CALs.
You can still make a case for migrating away from Microsoft at that point, but not based on software purchase price.
If you still need to buy software, have you seen this website? http://www.techsoup.org/ The nonprofit price for Microsoft software is very, very low.
And thus the answers you will get will be equally useless (crap in-crap out model....).
If you are more specific about what your servers are currently doing I am pretty sure people will help you out.
Now, for basic servics:
- File server and print server: Samba.
- Authentication servers: I believe Samba can act as a domain controller.
- DNS server: bind running in Linux.
- Web server: Apache.
- Dsta Base servers: MySQL.
- Backup server: Amanda.
- email: sendmail, postfix....
So, exactly which services are you aiming to provide???
IANAL but write like a drunk one.
This is an honest question, coming from a legitimate source, so all of those who think no one is out there stumbling along trying to understand all at once everything you have learned over the course of years need to take a deep breath.
To the question: Yes, you can phase out your Windows 2000/2003 server in favor of Linux servers. Whether it is worth it is up to you to determine - if you have a lot invested in your Windows server admin skills, and you don't have time to devote to raising your Linux server admin skills, this may not be for you. Both OS's require a degree of skill to manage, particularly for networks of desktops being employed by people who need the desktop to be perfect all the time (which is what my experience tells me small non-profit users expect).
If you are willing/able to meet the skill requirements for the system & network administration, and can translate that into desktop support that meets or exceeds that you deliver now, you need to come to an agreement with the organization about how best to deliver services using Linux. Some services can be moved off of Windows relatively transparently, but those which users seem to be most sensitive to generally aren't as easy to migrate.
If you are running Exchange, particularly if you are using group calendars, there isn't a terrific free-as-in-beer Linux solution. SuSE Openexchange Server offers what looks like a nice solution, but the pricing isn't a significant difference to the Microsoft non-profit pricings that I've experienced, and it comes with a recurring annual client license fee.
If you are extensively using Windows DFS for your file service, then the transition to a system that uses SAMBA, NFS, or DAV will be visible to the desktop user, with all the associated gnashing of teeth that brings. If you haven't implemented DFS, then the reproduction of home directories and shared directories with SAMBA should be simple and, with group policies, transparent.
Authentication of users against the Active Directory to Linux network services isn't as hard as it might seem. By installing the Microsoft Services for Unix (or whatever they are calling it this week) you will get POSIX fields in the Active Directory schema that can be used to write LDAP queries against for authentication via PAM, Apache modules, and PHP, Perl, and Java applications. Likewise, logins on Linux servers and workstations with AD credentials can be directed against the AD via LDAP, and SuSE has this option included in their default install process.
Finally, there are likely applications that are seen as critical to the success of the organization that are only supported on Windows. These niche applications will necessarily govern how much you can remove Windows from your back office.
In general, the introduction of a few Linux server into your back office is as painful as you want to make it. Moving user or customer facing services to Linux has to be an organizational decision, but it doesn't present a lot of technical problems. The biggest thing to remember is that you are meddling with the culture of the organization. These 50 people are doing something they consider very important, and they are not interested in what is cool to a bunch of geeks. If you thing Linux will save you enough money to buy 'IT goodies' then you shouldn't even bother, because it isn't the right motivation. Linux can save money, it can be more secure, and it can be more stable, but all of those things are irrelevant if they users are pissed off because 'it worked fine before you changed things'.
My advice is to use Linux to deploy new services, integrate it into the existing network, but only replace something that works when it is time to upgrade (since it will break anyway) or when it stops working. Be open and honest when you deploy something, when it breaks as well as when it works fine, and if you blow it up, take responsibility and don't blame someone else.
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...
Now for the application stack. I prefer using Novell's eDirectory 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 option is pretty enticing as well.
While we're on the topic of Novell and moving away from Windows on servers, look into GroupWise 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.
Not all non-profits are the EFF though.
Don't be a dickhead. You know who you are, AC. Now go put your fuzzy slippers on and get back to daytrading on your Mom's WebTV. It clear you don't have the social skills required to formulate a proper response anyway.
The idea that some other undersocialized loser modded you insightful just removed any hestancy I had in going off on you. Perfect.
Do what you will mods. I could care less if I have 'Excellent' karma with a room full of asshats like this.
If you never make mistakes, it's probably because you're not doing anything.
I toss down another gauntle that instead of whining about how they're wasing money running Windows, the AC troll above, and all Slashdot that can do 3 things.
1. Consider that this is someone who is looking into using something besides Windows, and not blindly spending money bacause "that the way it's always been done."
2. Sit there and HELP THEM DO IT! (Though above postings are doing a good job, so it may not be necessary).
and this is the most important one:
3. Go help a non-pprofit with their tech needs! They need us, and the community needs them. Time frequently means more than money, espically if they need tech help.
I have a group I'm helping locally to "fix up" their computers, and they have to run Windows in order to run some specific software required for them to obtain a grant. Think they should switch to no Microsoft? Not on your life. They get far more money from their grant than they pay to Microsoft, so it would be extremely wasteful to both their community and their donators if they were to "dump Microsoft." (Giving alternatives where appropriate, is another story entirely.) Think they can always count on being able to find a tech who can support linux? Nope. Most are volunteers who come and leave as they wish, and odds are they know Microsoft. Think they want to become part of a minority population? Turn down tech help because they run an OS that few are likely to know about? No. MS makes sense fror them, at least at the OS level, and definitely at the workstation level.
I am, and always will be, an idiot. Karma: Coma (mostly effected by
The Free Software Foundation?
A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
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? 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.
For most of the business end of the company that is. I work for a non-profit as well and I run everything in my power on Microsoft. Why? Because it is the most compatible with what is out there.
/. because apparently there is no help to be had.
I don't have time to sit around and learn an entire new infrastructure from such (apparently) great helpful linux zealots on
Windows works with the majority of the applications that are out there and if this person is purchasing through Dell as a vendor for their equipment in bulk they get a great deal of the Windows OS at cut-rate prices, including the server-end. Why would one not go for Windows? A non-profit has enough to keep up with without having to worry about a steep learning curve.
Also, the general turnaround for most non-profits as far as money goes is around 30%-40% to the donation. The rest goes to keeping the company going (employees, maintenance, bills, lease payments etc).
This person also didn't state where the donations were coming from. For all you pinheads know the money is coming from corporations who form partnerships with the non-profit. The general public might not even donate at all to this organization.
Confucius say better to remain silent than to open mouth and remove all doubt.
...instead of "go use Samba you fucktard".
I run a corporate AD forest that covers 3 countries. We have 3 primary AD controllers at the corporate office and a local AD controller at each major branch office. I've started integrating Linux into the mix, with an Oracle server, Mail server, DNS server, and a few application servers.
The hardest part has been getting Kerberos to properly authenticate with the AD tree. Basically, strip an off-the-shelf copy of Linux of anything related to Kerberos, then install a fresh copy of it from MIT. Once you've got that working, go pick up a copy of pam_krb5 and plug that into the PAM system. From then on out, all the linux services can authenticate with the AD tree through Kerberos.
If you want to share files, then you'll need to go the Samba route, but you don't have to start there. Plenty of Linux services (Courier IMAP, QMail, Bind, etc) work just fine on an AD forest without Samba.
I'm not sure if I'd trust my entire enterprise to Linux just yet. The time involved in figuring out which of the 5,000 configuration files I need to update to add a user isn't worth the ~$15 per user license of Windows. A single Windows 2003 server license plus users is very reasonable. It's the cost of 10+ server licenses that will kill you. Run a Windows AD controller and use Linux for the services on your network.
LOAD "SIG",8,1
LOADING...
READY.
RUN