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.
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.