Cisco IT Manager Targeting 70% Linux
RMX writes "LinuxWorld Australia has an
interesting article discussing Linux Desktop adoption in Cisco.
Cisco "already converted more than 2,000 of its engineers to Linux desktops...plans to move many laptop users to the platform over the next few years...the driver for Linux on the desktop is not cost savings, but easier support. Manning estimates that it takes a company approximately one desktop administrator to support 40 Windows PCs, while one administrator can support between 200 and 400 Linux desktops.'"
Ha, 40:1 ratio for desktop support personell for windows? Tell that to alot of IT managers, in particular, my former employer. Try 200:1
Don't Tread on Me
That is the worst support ratio in history. I hate Windoze, but no large support org has that bad of ratios. Mine are approx. 250:1 for a Win2k shop, which is pretty average.
- Erst kommt das Fressen, dann die Moral
because Cisco is now a security company?
So, Linux TCO is greater, eh?
Now Balmer is going to get on a plane and install Ad-Aware and SP2 on their machines to help with tech support.
What gets me is that what they describe could be done with Active Directory and group policies.
I wonder if those microsoft studies that show Windows' TCO better than Linux's account for the "productivity" of a linux engineer...
What i'm sure it doesn't show is that a linux engineer handling 200 computers can provide a much better service (due to the fact that more is "known and controllable" in linux than windows) than a windows sysadmin handling the same amount of computers, resulting in lower costs of security, less costs related to spywares, viruses, user support calls, etc.
There are two kinds of people in the world: Those with good memory.
I am sure they (CISCO) have some Mozilla/Firefox on these PCs. Question is: How have they decided o manage it? Central managing of Mozilla/Firefox is still not [officially] possible now. Any ideas?
They obviously don't know their own department. I worked as a contractor for them a couple years ago. I was the only onsite tech support person for two sites with a total of 250 users, with 99% of those being windows. I was also part of the support teams initial Linux push, and I can tell you that the biggest driver from a customer (end user) perspective was the idea of using cheap Opteron workstations instead of uber expensive Sun stations. A Sun dual CPU workstation at the time with 12GB of ram was over $50k dollars, whereas an Opteron station with more cpu power and the same amount of ram was under $10K. That is a huge difference in price. The biggest factor stopping it from becoming a reality was the fact that at the time the Clearcase tool chain and support tools weren't fully functional under Linux. So I doubt the driver was so much lower desktop support costs as it was lower equipment costs.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
"... the driver for Linux on the desktop is not cost savings, but easier support. Manning estimates that it takes a company approximately one desktop administrator to support 40 Windows PCs, while one administrator can support between 200 and 400 Linux desktops."
Isn't this still Cost Savings, when you don't need to hire as many admins?
We're typically 1:30 for local areas which is basically admin of the LAN, user applications, etc. Add to that central security, networking, hardware support, and we're down to 1:15.
Including in-house bespoke application support (specialist programmers emplyed under an IT remit, rather than technically able and active users) and you're down to 1:6 in some areas. On the other hand we have specialist terminals (with high maintainence requirements as well as user training etc) which are more like 1:90.
Inefficiency abounds in some companies.
the driver for Linux on the desktop is not cost savings, but easier support. Manning estimates that it takes a company approximately one desktop administrator to support 40 Windows PCs, while one administrator can support between 200 and 400 Linux desktops.'
And this does not represent a cost savings?
You see? You see? Your stupid minds! Stupid! Stupid!
Apart from the ease of creating a company software update ftp (apt-get, yeast, swaret, slapt-get, etc), I really think the license and CD administration to be a pain in the Windows admin's butt.
My Windows co-workers often need a CD either because they need new software, or due to their computer requesting a CD due to some function not already installed. Finding the RIGHT CD (they are like 1000 cd's every month, and they are neatly marked in INVISIBLE, but very fancy, writing) is a total pain. Then, there is the issue of which key is used for this one (oh, you used the english version!) really turns this into a nightmare.
Folks running windows run all kinds of different versions of their software. Why, upgrading costs time and money. On my Slackware machines, swaret has done all upgrades for me, totally automatically! Just upgraded one PC from Slackware 9.0 to 10.1 - swaret --upgrade wait for a while (was a 200mhz...) and reboot when all is done. No keys, no CDs, no cost. Totally brilliant!
A clever person solves a problem. A wise person avoids it. -- Einstein
Little if any functionality of most worms requires root privileges. They could run just fine as a user process.
about the worst thing that can happen is the home directory to be wiped out
Which is usually the only directory on a workstation that contains any information of value.
Delete all your home directories, rsync or rdiff your backup in and magically things just work.
You could restore the entire filesystem on any computer to achieve the same thing.
There are many factors that make Linux less worm-prone than windows. Taken together, they add up to a huge disparity in malware prevalence between the two OSes. However, no single factor is a magic bullet, and that includes the relative difficulty of running with root privileges. It's just one small piece of the puzzle.
but usually patches for OSS vulnerabilities are not bundled along with all sorts of other updates. This means that far less testing is usually needed for OSS security patches. (Or, that's the theory, anyway.)
HAND.
.. and I have to say that their Linux Workstations are extremely well deployed and managed. The desktops themselves are Dual-CPU 3G boxes running a customized version of Red Hat Enterprise Linux. Red Carpet is used to manage packages, supported by really nice internal mirrors providing fast access to everything you need to get the job done. The default install even includes acess to Microsoft Office and Internet Explorer. Not sure if this is through Crossover or something -- it is so well integrated that I've never had to look under the covers to see how it is done. Having worked at other networking companies where Linux is the default engineering desktop, I have to say that Cisco really gets it when it comes to desktop linux.
lists and you'll find that most vulnerabilities are either buffer overflows or string format vulnerabilities. There are very few circumstances where fixing those with a one-liner patch would change behavior in a way that other code depends on. If there were any such code then that in itself indicate possible data corruption bugs in the currently running software.
In short: When you don't bundle fixes you typically have one-line fixes which don't break code which isn't already broken (by relying on buggy behavior). Hence, testing time is minimized.
HAND.
I work on the Unix/Linux side of one of the IT departments at my work. We have about 25 admins for 180+ servers and 900+ workstations, plus a beowulf cluster and associated SAN/NAS devices. And we actually have free time to work on other projects (like in-house software development/support, training, and learning/developing new technologies to roll-out). The PC group has about 80 people to support ~700 PC's and 70 servers. Do the math...
We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
I think that if we bought products from the company of every CEO that has slept in the Lincoln Bedroom, we'd have more prosperity, fewer terrorists, better return on our investment dollars, and higher executive bonuses that would trickle down to all layers of our economy, especially at American-staffed Mercedes and Lexus auto dealerships. So stay away from that Linux corruption. It's bad, very BAD!!!
DT
Is this thing on? Hello?
Ok, so someone explain to me why Cisco's web-based and desktop-based management tools are almost always Windows-only? Not only Windows-only, but frequently don't run right under anything but Internet Explorer.
Guess I'll continue to stick to CLI and console cables for configuration and management.
"Tell me doctor, with all of your defenses, are there any provisions for an attack by killer bees?"