|
Contents |
||||
|
|
||||
|
|
||||
Until recently, most discussions about Linux in the enterprise have focused on its role as a server platform. But with the launch of several new open-source operating systems -- including Red Hat Desktop, Novell Linux Desktop, and Sun's newly open sourced OpenSolaris environment -- the previously hypothetical idea of using open source operating systems on the desktop has taken on a new life. Many companies are seriously exploring the possibility of cobbling together free open-source desktops that use a variety of tools to integrate with existing proprietary applications.
Not surprisingly, the idea of supporting an open source desktop is likely to send shivers up the spines of IT managers who find it hard enough to manage a known, well-accessorised desktop based on Windows XP. Desktop Linux may be free, but for it to run smoothly technical staff must take on a steep learning curve, and install and use management tools providing similar remote management to those already available in Windows.
Leading Windows systems management firms, ranging from CA to HP and Novell, have already brought such tools to the table, although they tend to be less sophisticated than their Windows counterparts. Yet even with remote management handling functions such as image deployment and software updates, an open source desktop is likely to introduce a considerable support burden simply as users, unaccustomed to the ways and mores of the new environment, flood the help desk with calls for help.
Supporting an open source desktop inhouse can be done, says RTA's Carvouni, but it takes work: "In this registry, a lot of work was done to create an environment of managing," he says. "You discover it's not as easy as it first seems, and you have to do detailed business analysis to understand what [users are] doing."
| "Support is really about the mainstream products."
Laurie Wong, Sun Microsystems |
In the long run, companies weighing up strategies for open source adoption should look to existing vendors first, and if working with a VAR, they should make sure the VAR has both a track record of strong support and enough resources to provide adequate response times. Companies must also resist the urge to customise open source software: start changing and recompiling the code and you'll soon find the terms of your support arrangements changing considerably.
"Support is really about the mainstream products," says Laurie Wong, software business manager with Sun Microsystems. "If customers make changes to them, it becomes a consulting engagement." In other words, get carried away with open source and it could cost you an arm and a leg to support. Stick to top-shelf Linux brands and get familiar with online messaging boards for support on other open source applications and you should do OK.
This is the unspoken message underneath discussions about open source support, and it's one that should resonate with any technical or business manager contemplating the move.
Certainly, the growing number of support options for Linux make the open source option less risky than ever -- but it still has its potential pitfalls. Weigh up all the costs of support and your own requirements for support, and you'll be able to develop a hybrid in-house/outsourced support team capable of bringing your servers -- and your users -- smoothly into the world of open source.






I think this was a pretty negatively-focused article (e.g., starting with a case study of one person's bad experience). It discusses the issue of what are the pitfalls are of linux again and again yet provides little clue as to why people are interested in linux, i.e., the positives in using it. Successes are barely mentioned. What about the horror stories using windows that cause people to leave windows for linux? That is just as relevant to the author's story. And I have heard many horror stories of Microsoft's (and other propietary, non-open source vendor) support. Apache (open-source) is the most widely used web server software out there.