Moving Small Organizations from Windows to Linux?
chris1646 asks: "Currently we are a small organization that is entirely a Windows shop. Next year much of the server and desktop hardware we run will need replacing. I am looking for creative ways to introduce Linux as my desktop and server OS of choice, however a couple of our core applications run exclusively on Windows. Has anyone had any success hosting Windows applications via terminal server while using Linux as the client OS? Has anyone handled a AD to open source LDAP migration?"
As always, there's not enough information. Why do you want to do this? What are you trying to accomplish? What apps? How critical are they? If you want to switch just for the sake of switching, then really, you should be fired.
Absolutely 100% correct. If you have a small company, and applications that require Windows. You don't switch to Linux.
The problem with businesses is that they are not very open to OS theology; businesses just want to do what they are doing, and if the job requires computers and OS and apps and stuff, well - that's just the cost of doing business. It will cost money to run a Linux shop, and it will be probably *more expensive* to run a Linux shop, considering that every Windows app -- that normally would be "install and run" on any Windows box -- becomes a WINE nightmare, to see where it crashes and how to work around those crashes. Do you really want to buy a $20,000 app (there are plenty of specialty apps in this price range, all mission-critical) just to find out that no, it won't run under WINE, and no, vendor support in such environment is not provided. Do you want to lose the support on such an expensive app? You are risking not just your job, you are risking jobs of your coworkers too - if the company loses a contract because of OS troubles then some employees may need to be laid off, starting with you, of course.
If you have dreams about using RDP for those few apps that you must have on Windows, it depends on what those apps are. Some apps do not permit running under RDP because that would be inviting to buy one copy of an app and then have the whole company to access the server and run the thing. I personally know of some examples, so check before you buy into it. And other posters already said that the cost of a terminal license is as high as WinXP, and you have all the eggs in one basket (server.) Server dies - the whole company stops; are you OK with that?
Again, businesses don't want anything that deviates from tried, tested and true path. Cost is not a concern here; labor and apps cost uncountably more than the OS. If you want to migrate, you still can do that; I tried myself, starting with a 3-man company, and guess what eventually happened? Once we started growing, the total cost of maintenance of a mixed network shot through the roof (and disappeared among the stars.) Now we stick to Linux on firewalls, and Windows XP everywhere else. We do use Linux on our embedded systems, and it's perfect there. Desktops are a different matter.
Ok, I'll be the first to admit that there is a tremedous lure to FOSS software and have rolled it out myself in a number of situations, but not to desktops. I've replaced web servers, database servers and Windows file servers with servers running Apache, PostgreSQL and Samba. However, before I considered something like this in my current environment, I'd need to do a serious cost analysis that went way beyond licensing costs. For example, what will this mean to the user that has been using Windows and MS Office for 10 years? And, you mentioned that some of your core applications are Windows-only affairs. Sure, you can use RDP/Citrix to run these apps, but then you're throwing the Windows licensing costs into the mix. Not to mention the possibility that your apps won't like running in this way.
So, how much is your infrastructure *really* costing you?
How much would retraining cost?
How much would it cost to possibly have to give up your core vendor support due to running in an potentially unsupported configuration?
This may sound like I'm anti-FOSS. Actually, I'm not - I love FOSS in the right situation. WHat I AM against is FOSS for the sake of FOSS. While I "grew up" on the IT side of the house, I'm a big believer in the business needs dictating IT's role and responsiblity rather than the other way around.
My advice: Think this through before you put a lot of time into it. You may end up saving a whole lot more (not just money) by sticking with what works.
The plural of anecdote is not data -- Frank Kotsonis
<anecdote>
Now, here are the facts as they're found in ONE PREVIOUS PLACE OF WORK:
We had roughly 150 people working in a branch office, 110 of which were a mix of hardware and software engineers. The rest were either support or upper management.
We had roughly twice as many computers as people, with the computers in the lab area shared among many people depending on who was using a bench on any particular day.
About 80% of the computers were running a couple of Unix variants, mostly Solaris. The rest of the computers were running Windows.
We had 3 full time IT people who had to support all the workstations, servers, and communications equipment.
</anecdote>
I have yet to talk to anybody who has actually experienced a situation where Windows support and development costs were less than Unix (or Linux) support and development costs for the same staff at the same location. I figure these places must exist, because SEVERAL INDEPENDENT RESEARCH INSTITUTES seem to stumble over them all the time. I'm glad I've never worked at any of them though.
Oh, and when putting machines out for testing you have a good opportunity to help manipulate the users.
Make the test machines pretty spiffy. Get some flat panel displays for example, if you haven't already got them deployed. Draw lots for who gets the 'first upgrades' rather than allocating it out like it's work.
Properly set up (if your office is anything like mine just set the default screensaver to the 3D matrix one and make them dual screen machines) you will get huge enthusiasm for 'the upgrade' rather than bitching about how everything is now insignificantly different.
Beep beep.
Having said that, you might be able to run your critical apps under WINE, and use Linux X clients to run it via SSH.
... after making sure with your software/support provided that this is a supported configuration. Otherwise, they might use it as an excuse when something breaks (even if it's not a wine issue) to wiggle out of fixing a particularly difficult problem (if they are anything like the provider of a company I used to work with, they probably sold you the Windows licenses and might not be tickled pink to see the OS upgrade revenue going away).
Don't rush things. Break in the users nice and calm. Set up sample workstations for each environment and ask them to give them a try and get their feedback. That way you'll be prepared to deal with the little (yet annoying) issues or even better, you'll be able to avoid them. For example, in Windows, the U.S. International keyboard layout differs slightly from the Linux version in the way they handle the entering of special characters. It's no big deal, but for a fast touch typist, it can really wreck your pace while you retrain your finger memory.
Good luck. If you do succeed, please post your story and let us know.
No sig
Ok. You're right. That means that 2 hours of employee time make up for the cost of one Windows XP license.
Please don't misunderstand - F/OSS provides LOTS of great software, but I don't see any way you can pencil the cost of Linux as a desktop replacement for Windows. Linux makes just about everything possible. (FWIW, I have been a daily Linux user since 1994.) Just because it's possible doesn't make it a good idea. Just because it's cool doesn't make it make any business sense, either.
All of the software/hardware vendors work their butts off to make sure that Windows compatibility is met. This doesn't mean that they do it well, but they don't care about any other OS. You can care, and if you select peripherals well, it won't be any issue at all. What happens when one of your "important" users goes out and finds a great deal on a digital camera/printer/trackpad/some other device which is completely unsupported in Linux?
It's not worth fighting the battle for the desktop. Linux is not complete enough yet for non-technical users to have. Linux on the server makes great sense, and I highly recommend it. (Although at home I just migrated all of my services to OS X.)
Respectfully,
Anomaly
But Herr Heisenberg, how does the electron know when I'm looking?
Hold up, there, cowboy. That is the wrong question to ask.
The systems and servers aren't your personal plaything. They are there to meet the needs of your employer. The small organization. The all-Windows shop.
There are often reasons for choosing the proprietary app. The predominant OS for a business of your size or type or location. Reasons that are not always narrowly technical, not always narrowly economic.
I actually don't work for the group in charge of maintaining the systems, but I know a few things about how they are maintained. Basically, all systems have the same exact same RH4 image and sync up against an internal yum repository for software updates. There is basically zero maintenance for each machine besides that. Users can't write to the hard drive, all data is stored on netapp filers. When you are hired, you get really basic classes on how to use KDE, the internal wiki, Open Office, get on mailing lists, etc. A caveman could pass these classes.
We have over 7000 linux machines and 4 people to maintain them, plus 1000+ technical and non technical employees. Using Linux saves us millions of dollars, which pays for a couple of those netapps. The thing is, Linux just works, not to mention the vast amount of free software that is available for it.
Truthfully, and its a sad truth for some people, anyone who says Linux isn't ready for the corporate world has no idea what they are talking about. Its been there for while.