Slashdot Mirror


Reducing the TCO of IT with Linux?

Bil Simser asks: "I've been asked by upper management to look at the feasibility of replacing our current Windows IT infrastructure with Linux. Basically someone has said that Linux is free so now we're off to see how free that really means. A full replacement is probably impossible, but I can see some benefits coming from selective replacement of specific technologies (e.g. application servers, web servers) that might be feasible. This is both from a cost reduction standpoint and increasing productivity when it comes to system management. I've already looked at a few studies done on TCO reduction on this and they look good so now I'm turning to the Slashdot community to see if anyone has either practical experience or informative insight into a problem like this? The objective is to determine the TCO of deploying Linux as a core part of our operational environment so what does that mean in the sense of hardware, software, middleware and management impact?"

20 of 327 comments (clear)

  1. Changing from Windows to Linux... by Dot.Com.CEO · · Score: 5, Interesting
    ...basically means throwing away all your HR infrastructure, or retraining it. Windows servers administrators will be completely lost in a Unix environment (and vice-versa, of course).

    Also, before all the fanboys out there start screaming "Linux is better", consider this: the reason Windows server software is present at most companies is not because of IIS nor because it offers a secure server environment. It is because of Exchange. Although it has MANY shortcomings, it works, and even though it is perfectly feasible to use open protocols to accomplish most of what Exchange does, you will not have a clear upgrade path (something that is important to upper management, however irrelevant it might be in real life) and you will have to go through hell to do the transition.

    Basically, my opinion is the following: move your file servers, proxy servers and print servers to Linux. It should be fairly straightforward if you plan it well, or have a decent project manager. Leave Exchange for last and research the subject very well.

    Or post another Ask Slashdot :-D

    --
    Mother is the best bet and don't let Satan draw you too fast.
    1. Re:Changing from Windows to Linux... by Anonymous Coward · · Score: 0, Interesting

      In my exeperience, Unix admins on Windows are far less lost than Windows "admins" on Unix - the Unix admins tend to have some intelligence, and unix experience means that one can work out windows by "Here's how unix does it, here's the stupid kuldge that windows uses instead" - thus enabling a Unix admin to obtain a far deeper understanding of the various windows-admin-pitfalls than your average MCSE admin-monkey.

    2. Re:Changing from Windows to Linux... by Lumpy · · Score: 4, Interesting

      I got this idea because EACH Windows NT4.0 server only came with 5 user licenses.. and we were FORCED by microsoft to purchase a seat license for each workstation, for each of our 2 domains. that is a total of 3 licenses per workstation... The os, domain1, and domain2. we would have had to have MORE per workstation if we didnt convince them that the 3rd domain was for engineering only and noone outside engineering would use it.

      TCO for windows NT has been well over $500.00 per workstation here for JUST the OS and network licenses... and truth to be told, if we were audited I would bet that they would say that we needed to re-purchase the server licenses when we upgraded to W2K.

      so I got that idea from microsoft directly.... in our corperate wide license agreement.

      --
      Do not look at laser with remaining good eye.
    3. Re:Changing from Windows to Linux... by nolife · · Score: 2, Interesting

      I have been testing this on our network just this week. We use AD with a W2K PDC and BDC so I chose to add the Samba machine to the domain and add authorization via security=domain and use of the 'add user script' in smb.conf (new users get /bin/false for shell). I was going to try winbind but I really did not need the extra functionality it appears to provide. Our goal is to provide network printers that can provide document conversion to tiff, pdf and jpeg (via Ghostscript) by printing from the W2K workstations with PS drivers to the Samba machine. Everything currently works and I am now trying different methods of getting the resulting files back to the users, like via email, a web page or moving them to thier home directories on the various servers. I can't script my way out of a wet paper bag so this is the hard part for me. I have been having issues with the 'delete user script' in Samba as it appears to be deleting actual valid Linux accounts under certain conditions, like when someone tries to connect from a W2K machine that is not registered in the domain. The credentials get bounced off the PDC which sends back a fail and then Samba deletes the existing user account. I'll keep reading.
      To keep in context with the orignal story here, this has saved us money and reduced TCO on a small scale as we now have one less W2K server and did not have to buy a commercial closed source document conversion package that would need installed on everyones local workstation. I assume once this project is rolled out, the periodic maintenance will be negligable.

      --
      Bad boys rape our young girls but Violet gives willingly.
  2. Re:blunt by NeoEinstein · · Score: 5, Interesting

    Yeah in fact, you're true. But I think your conclusion (== Money) is little bit to fast.
    Changing a whole IT infrastructure from Windows to Linux is not simple, as any other migration, but ther can be a TCO reduction I think. Though it won't be fast, it's a long term saving and the visible money saving may come up only after a few years I think. When you realize that there isn't anymore licence upgrading.

    Another important thing that I would like to add, is that you will need a lot human resources and knowledge, at least for the start.

    Hope I could help and keep me up to date about the evolution, 'cause I'm also planning a similar migration.

    Best Regards

    NeoEinstein /*** Got the name, waiting for the brain ***/

    --
    n-e
  3. Who/What/How by jki · · Score: 3, Interesting
    I'm turning to the Slashdot community to see if anyone has either practical experience or informative insight into a problem like this? The objective is to determine the TCO of deploying Linux as a core part of our operational environment so what does that mean in the sense of hardware, software, middleware and management impact?"

    Without that information it is impossible to even try to guess the TCO. You should describe your environment, human resources and everything else in quite much detail to have beneficial input. As you might have read from some TCO reports, replacing things with Linux might have anything between a negative and very postive TCO impact. Anyway, I would suggest first trying with a dedicated group of individuals - then if it works, enlarge to one division (if your company has divisions). Take smaller steps. Or... do you already have results from tries like this?

  4. Transition of services by Alex+Belits · · Score: 4, Interesting

    If you will try to find the closest thing to what you have, you most likely will end with more headache than if you just list all the necessary functions and install whatever does them best.

    Say, you have email. There is Exchange equivalent for Linux (Samsung Contact), but if one can survive with moving meeting scheduling functionality to something else (or abandoning it -- people should not spend so much time at meetings that they need to mess with each other calendars to schedule it), Cyrus + sendmail with IMAP will outperform everything else UNLESS people like to send multi-megabyte attachments to giant lists instead of placing files on some HTTP server.

    Meeting scheduler and web server management programs can be installed separately (and nothing wrong will happen even if large attachment will get copied to 100 people, as long as it fits on the server's hard drive), but people should be aware that they are there. On the other hand, performance, security and flexibility of Internet connection will improve dramatically compared to Exchange.

    Same kind of "similat to what you had on Windows" vs. "what performs this function the best" dilemma exists for pretty much every other service.

    --
    Contrary to the popular belief, there indeed is no God.
  5. Insufficient information to go on... by Arimus · · Score: 3, Interesting

    Without knowing what application servers you're looking to replace it's abit hard to say anything.

    The general network infrastructure bits, file servers, mail servers (note: MAIL not the overblown nightmare known as Exchange), firewalls, dhcp servers, gateways, some router boxes then Linux will be of benifit.

    The one cost factor that is hard to calculate is the cost of retraining the IT support team - do you know how many already use linux at home or have used it in the past?

    --
    --- Users are like bacteria -> Each one causing a thousand tiny crises until the host finally gives up and dies.
  6. linux TCO by sega · · Score: 4, Interesting

    I've read a few things on the web about the topic. It seems to me that if you are involved with a small to mid sized business, there could be some decent savings on licensing fees etc. Also lots of people site support as being the great thing about windows products, well, if you actually look into it, it costs a heck of a lot for getting that support off microsoft each year. BUT, it's like what others have said, it depends a lot on just how much stuff can be painlessly transferred across to linux whilst maintaining the functionality and ease of use that is required.

  7. A few more by The+Original+Yama · · Score: 3, Interesting

    Sincere Choice
    Open Source Initiative
    Why Free Software's Long Run TCO must be lower
    Open Source is good for America - US military advised (This is about the military, but parts can also apply to business. Read the report linked at the end of that article.)

  8. This headline sounds funny to a Swede by Anonymous Coward · · Score: 1, Interesting
    There is a trade union in Sweden called TCO. This is mainly where social democratic people join. Since a trade union is more or less useless in a modern society, they have adopted other tasks to modivate the high number of people in their organization.

    One of these non-union tasks is probably known to you as the TCO-9x markings on your monitor.

    To me, the headline Reducing the TCO of IT with Linux? sounds like Linux is helping out in the fight against socialism.

  9. Awfully broad by thasmudyan · · Score: 4, Interesting

    I don't know but in my opinion a feasability and TCO study would definetely have to be based on the individual components of your infrastructure. Sadly this article doesn't say anything about what kind of solutions would have to be supported/replaced. Without that kind of information you simply can't do any cost analysis. You cannot just say that TCO with any specific system (even Linux) is going to be lower/higher *without* knowing the facts about the infrastructure.
    All that I CAN say based on recent experience is that a Linux server solution tends to be more stable, thereby saving costs in comparison to Windows servers with respect to reliability. Base installation costs for our shop has been equal to Windows, by the way, because it took our people more time to get things running in the first place. But that's only *our* experience.
    Again: without knowing the facts you cannot get meaningful conclusions for your specific situation.

  10. Yes, ... by Anonymous Coward · · Score: 2, Interesting

    although it doesn't eliminate them as the word "free" might suggest. However the costs get heavily reduced.
    At my current job they made the same decision time ago; we now run all remote customers stations, all local developing stations, all network management machines and nearly all servers under Linux. The only server we're still forced to run under Windows is the IIS/SQLServer one, but the port towards Apache/MySQL (or PostgreSQL - our network is rapidly growing) is already scheduled to start next year.

    The amount of money saved by using free software is enormous. No license fees per machine (A Windows + Office license saved for each machine does matter a lot when there are hundreds->thousands installs!), fast bug corrections, free and easy remote administration (desktop included), no time and bandwidth costs due to viruses or trojans (or windows .exe dialers downloaded from pr0n sites. Heh! One of our customers did that, and of course it didn't work;#)

    As other posters wrote, it may take some time and money to retrain the personnel to use Linux; that's true, but is definitely worth the effort. A mid-skilled sysadmin could also easily configure a basic window/desktop manager to be easier and safer to the user than Windows.

    YMMV of course, but in our case Linux was the best choice ever.

  11. My experience by chileno · · Score: 5, Interesting
    I'm the CIO of an insurance company. In 2000 I decided that linux was the way to go, so I hired an experienced Linux Engineer. We started with replacing mail, then proxy, web server, firewall, print servers, file servers, LDAP, net monitor (MRTG), basically everything that we called infrastructure. That took about a year, and in the middle, I trained my old windows guys with a mix of inhouse and outside efforts.

    At the beginning of 2001, we changed all development servers (with our testing Oracle 8i databases), and everything went sweet. So in april 2001 we changed our production server from a Sun Enterprise 5000 (4 Ultra Sparc processors) to a Quad Xeon. No more server crashes, no more high maintenance costs.

    • The final user is still using windows, so they didn't notice any change but more speed and more uptime.
    • The upper management is very happy with the savings so far (we reduced our spending by about 60%), and the uptime.
    • I am very happy with the solid performance of all our servers.


    Some interesting facts:
    • Our Company is one of the top ten in Venezuela.
    • Yes, we are in Venezuela.
    • We have only one windows server alive: it runs Metaframe.
    • No, I'm not an english native speaker. Corrections are welcome.


  12. Re:*Is* he changing from Windows? by Dot.Com.CEO · · Score: 4, Interesting

    He says they are using Windows IT infrastructure.

    --
    Mother is the best bet and don't let Satan draw you too fast.
  13. Stay away from Linux by Yuioup · · Score: 2, Interesting

    We're avoiding Linux like the plague. Why? Do you have any idea how hard it is to find Linux sysadmins? And if you do find them, do you have any idea the sort of salary they're likely to ask?

    In my opinion in the long run, the TCO of Linux fall higher than Microsoft. But this is just my opinion. I have no hard numbers and no, I'm not a Microsoft plant.

    Yuioup

    1. Re:Stay away from Linux by f00zbll · · Score: 2, Interesting
      Sure you can find tons of paper MIS/MCSE guys, but to be completely frank. 80% of them suck and end up creating more problems than they solve. This isn't something I've heard. It's first hand experience dealing with a half dozen small, medium and large ISP, as well as staff sysadmins.

      Give you an example of a real problem I know first hand. It's a bit dated, but it is still a valid example. ISP A a medium sized ISP in San Diego county with approximately 100K subscribers runs 80 linux boxes for the user homepages. ISP A is primarily a Solaris and linux shop. Their total sys admin staff for supporting 200 or so servers is a team of 5 guys. ISP B also in San diego has about 10K subscribers, but is primarily a windows shop. ISP B runs two dedicated exchange servers, but is unable to provide reliable service. In fact their email is down daily and they have a staff of 3 sysadmins. Not only that, their DNS server is also windows, it continually hiccups and results in "domain not found." In fact, every windows based ISP that I have ever worked with has a much larger staff to support the equal number of subscribers. In many cases, the staff was 2X the linux/solaris shops. Let's say an experienced junior sys admin goes for 55-65K and a equivalent microsoft junior admin goes for 35-45K. Keep in mind these are old numbers and aren't accurate for the current market. if it take 5 unix admins to support 100K subscribers and it takes 3 MS sysadmins to support 10K subscribers, it could take from 10-30 MIS sysadmin to support 100K subscribers.

      Therefore the TCO for 1 yr of unix staff for 100K subscribers would be about 450K including benefits and other costs. The equivalent for a microsoft shop could be as low as 500K and as high as 1.5million per year. Again, these are based on several years of experience with small, medium and large ISP's. In the end, every single ISP that starts out as a windows shop puts most of their critical components on a unix box. Things like email, firewall, dns, nntp and accounting are all on unix. Even ISP's that provide IIS hosting aren't pure windows. All of the big IIS hosting companies I know have unix for the critical functions.

    2. Re:Stay away from Linux by waferhead · · Score: 2, Interesting

      Can you please give us a hint where you work?

      (We don't want to accidentally work in a place run by drooling idiots)

      I have seen too many places where the one or two unix geeks, who in their spare time keep everything running, (has another primary job) is replaced by a horde of MSCEs and Windoze box, all thrashing wildly and never up.

      Makes you want to run screaming...

  14. Re:Use baby steps. by oconnorcjo · · Score: 3, Interesting
    Very true, but also try to figure out how much it would cost you to start using desktop Linux (and if that would be wise in yur situation) in situations where a group of desktop computers would be replaced and you would become subject to heavy new licencing

    I don't think this guy has any intention of replacing desktop computers and frankly Linux is not ready for the desktop yet. For two reasons: 1. average users HATE to learn how to use a computer and they already invested too much time into learning Windows and 2. Not all desktop applications that are standard in American bussiness are there yet for Linux.

    Linux still needs about five years to really get going in the desktop world.

    The server market is totally different. Bussinesses should look to Linux now as a server machine because it is widely TESTED and accepted system in that role with a lot of highly functional free and commercial products to work with it.

    --
    I miss the Karma Whores.
  15. Call us as a Reference. by DigitalAdrenaline · · Score: 2, Interesting
    I administrate a small Oil and Gas company.

    We moved to a completely Microsoft Free back end.

    We saved well over a hundred thousand dollars in the process, we have literally maintained 100% uptime since, and the users can see no difference.

    I could set you up to talk to either end users or management. Either would provide an excellent reference regarding their experience with using Linux servers instead of legacy Windows servers...

    mail me at consulting@myrealbox.com

    Kev.