Slashdot Mirror
How One Small Business Switched to Ubuntu
firenurse writes to point out a story in The Inquirer about how one small business switched to Ubuntu. It describes a maddening comedy of errors, a series of circular screw-ups among Microsoft, HP, and a RAID vendor. From the article: "You never quite wrap your head around how anti-consumer Microsoft's policies are until they bite you in the bum. Add in the customer antagonistic policies of its patsies, HP in this case, and vendors like Promise, and you have quite a recipe for pain. Guess what I did today?"
That would have been disappointing even if you got it working.
Big name vendor + non-supported hardware. Any system consultant with a few years of experience should be able to tell you "don't do that".
Actually the guy in the article didn't know what he was doing and tries to blame Microsoft and HP for the mess that his lack of knowledge created.
If he had done this for even once in the past, he would have known what would happen. Very nice of him to practice with his clients' systems.
I joined two users too late.
The difference here is that you were having LEGITIMATE TECHNICAL ISSUES, as opposed to issues created by pencil pushers. Every problem the guy ran into was caused by either a total lack of thought on the manufacturers end (exe and no drivers), or intentional/malicious limiation (F6 driver install disabled, Windows Key issues).
I'm sorry your attempt with Ubuntu didn't work (I had a similar problem with old hardware and the fix was to use LILO instead of GRUB, btw).
However what's interesting is the *differences* between your problems with Ubuntu and what TFA describes as problems with proprietary vendors. With the proprietary vendors, they basically said 'either you use our configuration or screw off'... The hardware, software, and so forth were all designed to work one single way, and if you want to deviate from that, you're on your own.
Your experience with Ubuntu was just the opposite: dozens of people (apparently) gave you lots of different suggestions for what might be wrong and how to fix it. It looks like in your case it didn't work out in the end, but it is certainly interesting how much free support you received for a product you didn't pay for.
First of all, its called using the right tool for the right job. When you buy an OEM desktop you get OEM windows, you *CAN* buy the CD for an extra 10-20 bucks with most places and if you register as a reseller you can get much more. (If you're a microsoft partner you can just sell another license through your partner advantage program and use your own cd's/media for install) (free to join program). Finding Media is probably the easiest job of any techie.
Secondly, don't use Windows XP to be a server. It really isn't much more and sometimes cheaper to get a system pre-installed with SBS 2003 R2 and you get Exchange and other features built in not to mention a true comparison against Linux resource/functionality wise.
Terribly inaccurate and to say the least a very inept technician and company at work here.
My biggest selling "managed service" for small/medium sized businesses isn't my linux solution but my sbs 2003 r2 solution because for most people it not only saves money but provides tons of features from easy to configure remote access to sharing in sharepoint to cenralized ad administration/logins/access restrictions to built in exchange and with the advanced version sql server access.
I would never sell someone a desktop as a server solution simply because your selling yourself short. If cost savings was an issue buy a refurb server system and put whatever linux you want on it.
I have been bitten by every single problem mentioned in that article. Bad OEM "revogery disks" and MS licensing restrictions that prevent one from using an alternative install disks are one of the biggest single problems facing those of us that support very small businesses professionally. Say what you want about Dell... at least they include real windows install disks.
However, I have to question the judgement of the author. First of all, what kind of consultant deploys branch offices "weekly" and didn't know about these problems in advance? Anyone with much experience would know about (a) how difficult it is to move windows from one storage subsystem to another, (b) that HP uses bad recovery disks, and (c) that RAID installs require a floppy.
In addition, I question the use of Linux in this situation... perhaps it was his only way out of a bad recommendation to a client, but the problem is that there are *very* few Linux-savv consultants servicing businesses this size. For this reason alone I don't deploy Linux solutions... I can't find subcontractors who can back me up when I'm on vacation or sick, and should I stop working with a client, I don't want to leave them high and dry. Most consultants I know replace Linux servers with windows because they simply can't support it.
Finally, there's a much better way to do what he's trying to do: a NAS appliance. If all you need is some shared storage, printer sharing and the occasional backup, one of the many small business NAS devices out there (Infrant, Snap / Adaptec, Buffalo, etc...) will do so with greater reliability and less complexity than a PC-based server.
-R
Anyone who confuses "support" with proprietary software is not working in their client's best interests. Proprietors drop software maintenance to get users on the upgrade treadmill. Proprietors ostensibly act motivated by profit, but users can find computers that do their job well after the hardware is no longer profitable. Consultants ought to promote the use of free software drivers and firmware (or, preferably, no firmware needed at all) so that their clients can leverage the talents of a free market of developers to improve and maintain the software needed to make all hardware work with any system. Separating users from their freedom is not fiscally sound for users.
Digital Citizen
Let me quickly relate a recent experience. I installed Slackware on this machine a little while back. It took me two days, including one day to figure out how to set up Apache with a load of modules and Twiki. Kernel compiled, Apache compiled, ready to go.
More recently I had to install Windows XP Pro from an SP1 disk. It took me two days to set up Windows XP Pro with administrator and user accounts and get all my apps updated and working properly (or close enough with some apps running escalated privileges) in user mode.
My conclusion: Both Slackware and Windows are very difficult systems to build from scratch. If people had to install Windows themselves they would be as smart as Linux geeks.
"Will future ages believe that such stupid bigotry ever existed!" -- Ivanhoe
Does your incredibly snide and degrading tone get you far in life? Because it doesn't work on the internet. Maybe you think you're being witty or something but you just come across as an angry jerk.
in a decade of using linux I've never come across a more helpful and patient community than Ubuntu. If you ask questions politely and provide the information that's requested, instead of acting like you are smarter than everyone else and you don't think their question is relevant, you might find you get a little bit more useful information. Just a tip.
This comment is fully compliant with RFC 527.