Ret. World Bank CTO on Desktop Linux TCO Facts 345
comforteagle writes "W. McDonald Buck, retired CTO of World Bank, believes we need to take a more honest and frank look at the Cost Analyses it will take to put Linux on the corporate desktop. In Part I of Corporate Desktop Linux - The Hard Truth he begins with one of the most common misconceptions... that a business can buy a computer without Windows and save money in the transaction."
Bring it on. (Score:1, Insightful)
Yeah, but it's not a one time purchase (Score:4, Insightful)
When a user bought Windows 3.1, they also unwittingly bought Windows 98, Windows 98SE, Windows ME, and Windows XP. This is planned obsolescense for no other reason except to keep Micorsoft shareholders happy.
With Linux, you avoid that ridiculous problem.
More Fodder for Anti-Trust? (Score:3, Insightful)
huhhuh????? (Score:3, Insightful)
i think he should take a good look at his support contracts and then figure out just what's wrong with his reasoning here. that's right, his reasoning would be ok IF he was arguing about home desktopts - but he isn't, so what does the initial ten or twenty bucks mean?
of course, maybe the final chapter will be "linux just can't compete.. because linux can't give me huge discounts if i would have said that ms sucks".
Re:Bring it on. (Score:2, Insightful)
Well it might not look good to start when you can buy a windows dell for $400 but the same Linux dell costs $420
But DUH you can buy the Windows dell for $400 and install linux FOR FREE ON IT
Even then if you needed to deploy a hundred of them through all a company then you can make one main install of linux and mirror it everywhere.
So Linux actually can never be more expensive than windows even if windows is the 'cheapest' to buy from the store.
The best mac support on the wed [tribbles.org]
Re:Well he ignores one big fact (Score:3, Insightful)
He's talking about corporate purchases; where the company buys off the shelf, simply re-buying "their standard configuration" each time another cubicle needs filling. These kinds of customers don't build their PC from bits, you fool!
And they DO worry about tiny differences in price; because they get multiplied out by the hundreds of boxes getting bought by the whole company.
Get a brain before using your keyboard, FFS.
Re:Well he ignores one big fact (Score:4, Insightful)
I think the conclusion ... (Score:2, Insightful)
My two cents
Re:Bring it on. (Score:5, Insightful)
And it's hardly a win for Linux to say that Linux is not more expensive than Windows. If we can't show a cost savings for Linux, it's a win for Redmond.
Re:Well he ignores one big fact (Score:3, Insightful)
The title of the article is Corporate Desktop Linux. Corporations don't piece their systems together.
So he purposely misstates any facts and says that windows is cheaper because some pricey manufacturers choose to sell windows for less than linux installed machines. This is silly too because you can just buy the chjeaper windows default install and put linux on it with a burned CD you downloaded for no cost. And then throw away the Windows CD!
No, he's stating the facts correctly. Theoretically, buying an N-series from Dell should be cheaper, because they are not including a Windows license in that price. But it's not.
If you want it without a particular option, the price should be less than an identical system that includes that option.
Just like buying a car without a radio. It should cost less than an identical car with a radio. Not more.
Re:Well he ignores one big fact (Score:3, Insightful)
I would probably go with Dell/HP/IBM because it is actually a better value because your time and the staffs time costs money too and you also need to save your butt from management if something goes wrong.
Re:I'm a programmer at a bank.... (Score:3, Insightful)
But the point of the article, and my post, is about linux on the desktop and how difficult that could be to implement (in a large company). I was specifically talking about how most vendor products used in my bank (or any large bank) don't include desktop components that run on Linux. It's different when IBM comes out and says "Were moving to linux!" since they are a technology company. They have the knowledge and resources to make that shift. A bank has NO interest in the progress of technology. They want to use off-the-shelf technology to meet their business needs. Most large non-technology businesses are like that.
Cost of viruskiller, spyware cleaners, downtime? (Score:3, Insightful)
-cost of Anti-Virus software (that slows the system down)
-cost of anti-spyware solutions. Typically you need two or more cleaners to get the most common ones.
-cost of downtime. Typical desktop PC in a business is down for most of a day many times a year.
-cost of the forced upgrade cycle.
-On top of that, Windows comes with NOTHING bundled. Everything costs extra. Just managing the licenses in a corporate environment is pain!
Add to this the much bigger probability of data loss and theft, and the Windoze solution does not seem like a solution at all.
Bandaid over duct tape. Legacy crap is what keeps people using Win32, there are no other sane reasons.
Re:Dumbass, Your'e a Banker or a MS shill? (Score:3, Insightful)
Re:I'm a programmer at a bank.... (Score:3, Insightful)
I would agree that most industries don't look to change platforms or migrate software packages. All it would take is for the demand to exist for the supply of strongly-supported apps to be developed.
Another thought is that with web-enablement of apps, platform independence is that much closer to being an option. And web apps have *definitely* come a long way to providing much of the functionality we have had for some time in regular apps.
Give it a few years, and those web apps will make desktop platform indpendence a reality. You can still program however you choose, and your servers can be whatever you need them to be.
Very true (Score:3, Insightful)
It can be difficult to get pre-installed Linux desktop.
Servers, though, a totally different matter. Here you can make really large savings. Especially when you consider that you don't need all those CALs. Compare a Windows Server 2003 running Windows Terminal Server and having 20 Windows XP desktops connecting to it, to a completely Linux Desktop OS and Linux Server OS solution, and you're biggest saving is in the server area. Heck, according to this article the Linux Server / Windows Desktop would be the cheapest solution!
Re:Well he ignores one big fact (Score:5, Insightful)
Anyway... have you ever worked for a large company, say, a bank or large corporate office, with procurement policies? I think you haven't, otherwise you would know that just telling them "Just buy a couple hundred motherboards, HDD's, CPU's, RAM sticks, cases, monitors, keyboards and mice and have your techie guy working in the basement put them together for you over your lunch break and install Linux on them." just ain't gonna fly. They are large companies, they do business, their business is not computers, but they need computers to run their business, so they look for other large companies that assure them that they are getting solid computers that will get the job done. They're going to buy Dell, or HP, or IBM. They are *not* going to show up at Bob's Discount Linux Shop and order a couple hundred desktops. And they are not going to give their one IT guy back in the server room a pile of components. They are going to go with a large supplier who will deliver a bunch of pre-built, pr-econfigured machines that they can plug into their network, put their username and password in, and get to work.
As for mom and dad and grandma, you try telling them to buy the components and build it themselves. Or telling them to go to Bob's Discount Linux Shop when they can get the same computer with an OS they allready know, and often for a couple hundred dollars less thanks to the discounts the big companies offer that small shops just can't match. They want a computer thay can buy, plug in, and start sharing pictures. They don't know, or care, about Linux or wether it's better/cheaper/sexier. They didn't buy a windows machine. They bought a Dell.
The point the guy makes in the article is completely valid: Unless and until large suppliers like Dell/HP/IBM make computers preconfigured with some flavour of Linux available, and make them cheaper than a comparable Windows box, then Linux will never be 'cheaper' or 'free' to the 99% of people out there who aren't geeks like us.
As a bit of background on me, I also work with Windows 2000-2003 *and* Linux servers for a living, in an environment where we have all our outward-facing machines running Linux and acting as webservers/webapp servers/firewalls/VPN server, and inside the network itself we've got several Windows 2000 and 2003 servers running Active Directory, Exchange, and several proprietary apps that require a server component running on a Windows NT-variant, and a client component running on a Windows desktop. Point is, I work with both Windows and Linux servers and desktops on a daily basis, I have some idea what I'm talking about.
The HR cost... (Score:2, Insightful)
Hey, if you can sell the idea to the bean counters more power to you but I don't think Linux will be cost effective for enterprise any time soon.
The price of "change" (Score:3, Insightful)
WHAAAAAT?!! YOU'RE TAKING AWAY MY POWERPOINT?!!
People grow up with these programs. They devote time and personal resources becoming proficient with them. They don't want that background to become obviated. They don't want to start over. We who work in technology are just the opposite by our very nature. We like change. We like the challenge and adventure of learning new (and better) things. That nature is one of the things that drove is into a technical field.
I personally think the only practical migration is to first migrate to F/OSS apps on Windows, gradually. Then, migrate all those apps to Linux. So that, to the user, Linux is just another application migration.
Re:Bring it on. (Score:2, Insightful)
I guess there are a couple of points that have to be considered in all this.
First : If the cost of a PC with windows is $400 and the same PC with Linux is $420, you have to realize that actually a PC with either Windows or Linux or BSD costs $400, because you can install whatever you feel like on that PC. After that, the cost of additional software for basic things also has to be considered. Windows is an obvious loser in that area (consider antivirus/basic editors/remote mgmt/whatever and the bill starts to grow).
Second: If you really think that for medium-large companies it's a hassle to have to re-install the machines with Linux if they have shipped with Linux, I guess that's not a problem. Actually, PCs where I work are being reinstalled anyway with the corporate image, so that time of reinstalling has to be counted on the TCO for both Linux and Windows.Then again, those images are more expensive for similar functionality with windows, than a similar image based on linux (and we have both where I work). Of course, maintenance of windows machines tend to be a little, well, harder and problematic, so it all adds on the TCO. \P>
He's doing it like a typical CTO (Score:3, Insightful)
Any IT worker with half a brain knows that you can deal with your primary reseller. I can get really good HP business desktops sans Windows XP or a Windows XP license for about $500 (dx2000's fully loaded, $400 not). That should be the starting point of pricing for the desktop itself. This guy is spending too much money any way you look at it. Has he never heard of a reseller?
Next you look at the cost of licensing. If you want Microsoft's "Assurance", or whatever they call it these days (in which you can upgrade without fee the next time around), a company my size would have to spend about $300,000. The other option is buy each individual XP license at $176 a pop. Neither of these options include any kind of support. Going with Linux, lets say Novell's Desktop Linux (Suse 9.2 Pro with the LDAP client preinstalled and a shiny Gnome configuration), I'm looking at $80 a license. This includes a little bit of support, and an active community on Novell's official forums.
Anyways, from here you have to figure out how to get around the Microsoft Office lock-in, and decide whether you want to go with Citrix or Codeweavers. But that's an entirely different discussion.
Re:Windows OEM shop prize (Score:1, Insightful)
It looks to me, however, like the Microsoft monopoly has such a stranglehold on the tier 1 manufacturers that it is now not possible for a corporate shopper to save money by avoiding Windows unless they are prepared to go outside the first tier (which brings another whole set of buying issues in organizations with strong procurement rules), or unless the size of the deal is large enough to merit special treatment.
Re:Bring it on. (Score:5, Insightful)
a VERY large company can get much better pricing without windows and from DELL.
He may be a smart guy but he is making some really DUMB mistakes trying to get TCO information.
NO corperation on this planet goes to Dell's website and configures up a computer, and presses the "order 10,000" button. you call a personal Sales Associate.
That is what I did, his first quote was in line with the article until I threw the quote back at them saying, "not good enough, HP is mre than willing to do what it takes to get our business, that includes not charging us for windows."
The quote came back over $250.00 per machine lower and the line that mentioned XP pro was actually removed from the quotation.
The machines arrived with no OS.
Maybe when the author of the article starts thinking and acting like how a company will get their PC's then we will get a fail TCO.
Until then he is acting like joe-blow off the street looking for 1 pc, and this is not the way to get a fair TCO.
Support! Investment in support! (Score:2, Insightful)
If you want to look at the cost of any software, Linux or others, in the corporate envrionment you have to considered three main points; managed support costs, unmananged support costs, investment costs. Before you get your undies in a bunch, yes there are other costs but if you slice up all the costs these three can average nearly 75% of the pie.
Managed Support Costs are the things budgeted for. Help Desk technicians, maintenance contracts and such. The cost of a Windows based support person is less than a Linux based support person. There are more Windows people (greater supply). Umanaged Support Costs are those things that are costs generated by unplanned/budgeted items. For example, I sit at my desk and monkey around with getting something to work for an hour. That is a cost to the company both from a resource time spent perspective and from a loss of productivity perspective. THESE COSTS ARE HUGE!
Finally there are investment costs which are things the business will have to do to switch. Imagine a business with a 10 person support desk that is primarily Windows. There are documents, procedures, how-tos, along with the expertise the individuals have built up. Now you come in and say switch to Linux. The business will have to throw away a lot of that list and then spend even more money re-building it for Linux.
Even if Windows and Linux cost exactly the same to support/manage it is a tough sell to a CIO on the topic of Investment Costs. It will cost to much money to switch and for a period of time 1-2 years it puts the infrastructure at risk (new software, unknown problems, etc).
I'm a huge fan of Linux! I have to CPUs at work one is pure SuSE 9.2 and the other is W2K. Even on the W2K I spend my time in SuSE inside of VMware. I am very anti-MS but this is not about MS vs. Linux, this is about costs and risks to switching.
Re:Bring it on. (Score:4, Insightful)
Nonsense.
We just have to point out the fact that most larger businesses throw away the bundled OEM-XP-home licenses anyway because they have their own licenses (which of course would no longer be needed if you have Linux).
And of course smaller businesses tend to buy whitebox or cheap systems which can be often had without Linux.
Re:A golden opportunity (Score:3, Insightful)
Re:Why branded? (Score:3, Insightful)
Quality Control.
I've had whole labs of PCs bought from white-box vendors, and whole labs bought from Dell etc.
We had a white-box lab of 700mhz slot-A athlon systems. after 6 months of running, we had just about every CPU fan die within a 3 week span. The machines were somewhat unstable, mostly due to poor ram compatability. When it came time to cycle the lab, we ended up having to dumpster about 1/2 of them because of problems. (the rest were distributed among grad students who still had PPro200 systems)
Because of volume, Dell/etc can simply do a better job of quality testing before releasing a box.
Re:Bring it on. (Score:4, Insightful)
However, since we have a corporate volume license from $PARENT, and we have an image we've built with our software load, we essentially pay for Windows TWICE - once on the pre-install which we don't use, then software rental on the corporate install.
The other TCO problem with Windows is in imaging. With a Windows image, all the machines have to be identical for the image to work or you get all sorts of interesting driver issues. Manufacturers keep changing their specs. You can get the same model of PC from HP and find it has a different NIC and a different chipset and a different video card even though it's apparently the same. With a Linux image, it seems so long as you've got the module, it just works without complaining. With a Windows image, the best you get is many "Found new hardware" dialogues (and the driver install may or may not work, and you have to sometimes feed it disks which is kind of missing the point of a hard disk image). Sometimes you get a machine that won't even boot. Windows is a royal pain for machines built from hard disk images unless you can make sure all your machines are identical.
Re:But the OS is just the starting point (Score:3, Insightful)
I wonder how you could come to this conclusion, but must assume you haven't been around many medium- to large corporate Windows networks. I have, and let me tell you - - scheduling in Outlook, not only for meetings, but also for resources (like conference rooms) and employee vacations, training, etc., was one of the most heavily used feature sets in Exchange. Many companies and small offices rely on the free/busy scheduling facility so much that all employees are REQUIRED to keep their calendars up to date so that management will know the availablity of any colleague at a glance. And I can assure you that, if it weren't for this functionality in Exchange, OSS mail and calendar software would have penetrated much more deeply into corporate American than it has thus far. I've been able to bring Apache, PHP, and MySQL to my current employer's server room, but they will NEVER break away from Outlook/Exchange in the course of my career, I'm sure.
Re:Flawed Logic (Score:2, Insightful)
Also, if you're concerned enough about ongoing costs to use old PII workstations across the board, then you should also take into account the electricity these machines burn when compared to a modern PC with better power saving. Granted, P4 workstations are going to burn more electricity, but where I work I think the average workstation is a PIII 1-1.4Ghz machine... relatively low power consumption. Then there's the heat the machines output which must be combated with air conditioning. OK... so you save a little money on the heating bill...
For a corporation, it also comes down to SUPPORT. Your solution is a one-person vendor solution and therefore would be unacceptable to any corporation with any significant size. Where I work we buy Dell workstations because if they break the company can turn to Dell and ask them WTF. We buy HP servers because we happen to think they're the best, and we can turn to HP and ask WTF. We also have UNIX systems which are IBM running AIX... because we can turn to IBM and ask WTF.
Linux has made some inroads... we have VMware ESX servers in our R&D and prodution environments, mostly used in our "production dev" environment... but workstations? Unlikely:
I did run a project about a year ago where I installed Linux on my laptop to show that we could get all of our work done on a Linux machine without worrying about Windows licenses. I did... I was at least AS efficient as I was before (as were others working on it), but in the end it came down to the ability to turn to Microsoft and ask WTF. Until we can meet or exceed this requirement in the open source community, Microsoft will remain on the desktops.
I applaud this guys review... it's part 1. I'll wait and see where he's going with this, but I do suspect Linux is going to do OK in this comparison...
Re:Bring it on. (Score:3, Insightful)
Dell is also a good company for this. You're probably thinking, why should I buy an agreement like this from Microsoft when I have no choice but to pay for the Windows license from Dell? Dell will work with you. Once they verify you have a VLA with Microsoft, they will deduct the cost of the Windows license(s) form your order.
Now speaking from experience, all preloaded machines are CRAP! Dell loads all kinds of "tools" on their default install (this also means never use their restore cd's either). Take 2 machines, load one by hand with a vanilla XP cd and load the other with the Dell XP cd. Once in Windows check out the Services list. Surprised? There's a lot of unnecessary services and also programs preinstalled, which over time, will make the system unstable. I learned the hard way. I started off using the Dell loads until I noticed a pattern in BSOD's and crashes. Then I started a standardized imaging system with the base images being done by hand with a vanilla XP cd. No more random crashes...
I have noticed, however, that sometimes the DellTech will ask you to boot to the Diag partition (a supersmall FAT partiton they put at the beginning of the hard drive with diagnostic utilities) for error codes and such. Blow that partition away. You don't need it. I've made it a habit that before I call a DellTech, I boot to the Diagnostic cd for that system (each system has it's own (GX260, GX270, Latitude D600, etc.)) and write down every error code it spits out. This will greatly speed up your call time and get your machine fixed very quickly.
If nothing else, I hope people who have to work with such machines have learned 2 things:
Re:Flawed Logic (Score:3, Insightful)
Don't forget the additional cost of the requisite anti-virus system for every PC, and possibly a commercial anti-spyware solution too. Oh, and since the anti-virus slows the system down by X %, you'll need to buy all systems X% more powerful than you need.
Re:Is this REALLY a problem? (Score:2, Insightful)
With that said, I don't really see Linux becoming all that big on the desktop. Because most of the office users won't start using it at home, simply because 8/10 users plays with their computers in a very different way of what the more geeky types does.
I know plenty of office workers who only know as much about computers as they need to for work. They only have windows with office because that is what they use at work. If businesses started installing linux, then new employees would most likely use it at home, to help be familiar and compatible with work. There are also those people I know who know only the keystrokes and mouse clicks they need to run 1 application, who call the help desk if a window pops up in the way, and they cant close it.
Re:Cost of viruskiller, spyware cleaners, downtime (Score:3, Insightful)
Re:Bring it on. (Score:3, Insightful)
Guess what. Large businesses do install their systems from scratch. It's called imagining. Did you really think they drop, for example, an HP system with all those additional HP OS 'enhancements' cold onto the network, or sit in front of each box in a 1000 computer shipment with install discs? All Buck demonstrated was that he didn't spend any time talking to IT departments, which is hardly 'trying' to do a fair analysis in my book. In fact his article was so slovenly I question if he's really a Linux devote at all.
Re:Article before the slashdot effect kicks in... (Score:2, Insightful)
If I'm a corporation and I am going to buy, say, 100 desktops, I don't go to the website for the purchase. I call Dell or IBM or HP or Gateway directly and get a sales rep for pricing and options.
After the options and prices are set, I would ask how much does the price drop if no Windows licenses are included. I'd probably have a much better chance of getting what I want at that point.
It's one thing to turn down $500. It's another to turn away $25,000.
- Tony
Re:Bring it on. (Score:3, Insightful)
The other thing to watch in TCO calculations is how cost tradeoffs are measured. If you're not tracking actual costs through the entire life cycle, the numbers are bullshit. And both training costs and estimates of improved or lost productivity are notoriously imprecise and sensitive to initial assumptions.
In fact, when I consult, I advise my clients to be wary of TCO calculations. The main reason is that the number that matters most to business is not TCO but return on investment (ROI). That's benefits minus costs. TCO comparisons assume equal benefits for the alternative approaches. But the goal of IT in a business is not just to reduce costs: if that were true, you could save a lot of money by ripping all your computers out. The goal is to maximize productivity. So ease of integration, stability of systems, ability to deploy new solutions in a controlled manner, all add to operational flexibility and are benefits. It's fallacious to look at IT solely as a cost center, and by allowing the debate to shift in that direction you're giving up a lot of winning arguments for Linux.
Re:I'm a programmer at a bank.... (Score:2, Insightful)
We are in the "software business", with one client. Ourselves. We write most of our trading software, in house, from scratch. It runs on Linux serves, with the clients being either Solaris or Windows.
Owning your code when it comes to trading systems is a fairly obvious necessity. First for reliability reasons. Can you imagine having a trading system go down and not be able to fix it yourself ? Relying on some vendor to fix would be insane when you realize how much money is at stake.
Second, we need to build new models quickly in order to trade new markets as we develop them. If you wait for some software vendor to decide what is a commercially viable product, you will be at the tail end after all the other banks have made all the money.
Third, many of our models are proprietary. We think them up, write the math, code it and use them to give us an "edge".
Now of course there are plenty of places that we use software written by a vendor, but the point is that if you don't write and maintain your own code for trading systems, it's because you're pretty much a third tier player and can't afford to.
Other places we happen to be going backwards. For instance we recently switched email to Exchange/Outlook across the Firm. But the rumors from the IT folks suggest that the decison to switch has to do more with "reciprocity" (Microsoft is a big client, pays big fees, and demands that we use their software as much as possible) then with TCO / reliability, etc. I've been told that it took over a year to get the Firm comfortable that the Exchange / Outlook that we run is secure enough, that the code we run has been heavily modified for us and is not the same as the code in the retail or other corporate versions.
Throw windows out with the packaging (Score:3, Insightful)
So you have to reinstall... so what (Score:3, Insightful)
But isn't that what most big companies do anyway? Even if you run Windows, you never want the stock installation that Dell put on there. You reinstall the machine with the corporate standard version of Windows (if your IT people have any clue, this will be fully automated).
So I don't see that inability to get Linux preinstalled is a big deal. The main reason to buy a machine which comes with Linux is as a guarantee that all the components have Linux drivers - but you can check that separately.
Re:Article before the slashdot effect kicks in... (Score:3, Insightful)
If that's a correct summary, then he's urging acceptance of what is likely to be a highly volatile status quo. That seems simultaneously fatalistic and a bit silly.