Linked by Thom Holwerda on Mon 12th Nov 2007 21:48 UTC
Thread beginning with comment 284359
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.




Member since:
2007-02-17
Firstly - you had a full year of full support, how come you didn't test it then? Why did you muck with it after that year, causing it to come down? Didn't you already say - If it ain't broke, don't fix it?
If you are going to count downtime and associated costs versus support costs ... then you need to count it for Windows as well. Your $3999 for Windows doesn't include support, or downtime from virsuses (which are in the vast majority WINDOWS virsues), or virus protection software, or as I pointed out CALs, or whatever.
If you have a million an hour riding on downtime, then you are certain to be up for a huge cost in paying CALs, and paying RedHat for support for the full seven years is way, way cheaper than trying to keep Windows server licensed and supported for the same period.
You just simply aren't comparing apples with apples. If you did that and were honest with yourself and your employers, then any viable Linux or BSD or OpenSolaris server option would win on TCO every time, by a huge margin, over Windows server.
If your CEO were at all clued in, he would be far more likely to fire you for buying Windows, exposing the company to security risks, costing the company money the time for removing viruses, rootkits, botnet zombies & the like, costing the company money through having a requirement have staff to keep track of licenses, costing the company money for downtime every "patch tuesday", exposing the company to risk through leaking of its data, exposing the company to unnecessary legal risks arising from licensing audits, and costing the company money bigtime for locking them in to a single and abusive supplier.