Ask Slashdot: How To Start With Linux In the Workplace?

An anonymous reader writes "Recently my boss has asked me about the advantages of Linux as a desktop operating system and if it would be a good idea to install it instead of upgrading to Windows 7 or 8. About ten boxes here are still running Windows XP and would be too old to upgrade to any newer version of Windows. He knows that i am using Linux at work on quite outdated hardware (would have gotten a new PC but never requested new hardware — Linux Mint x64 runs quite well on it) and i always managed to get my stuff done with it. I explained to him that there are no licensing issues with Linux, there is no anti-virus software to deal with and that Linux is generally a bit more efficient on old hardware than operating systems from Microsoft. The boss seems interested." But that's not quite the end; read on for this reader's question. "Since I am the only guy with Linux experience I would have to support the Linux installations. Now the problem is what works perfectly fine for me may be a horrible experience for some of my coworkers, and even if they would only be using Firefox, Thunderbird and LibreOffice I don't know if I could seriously recommend using Linux as a desktop OS in a business. Instead I want to set up one test machine for users to try it and ask THEM if they like it. The test machine should be as easy and painless to use as possible and not look too different compared to Windows. Which distro and what configuration should I choose for this demo box?"

Comments

Themes...

[Anonymous Coward]

KDE can be configured to look identical to windows.

(X)Ubuntu

[Anonymous Coward]

I would recommend plain ol' Ubuntu since, imho, they have made the most polished Linux desktop experience for those with no prior linux experience. If you're worried that Unity may be sensory overload for some of your users -- consider installing Xubuntu and doing a little customization to give it the same general feel that your user's XP desktop would have.

Replace the backend first

[Anonymous Coward]

You will save yourself a lot of trouble by migrating the backend (servers, database) to linux first, and only then start on the frontend (workstations, user interface). You will also enjoy a larger benefit immediately, as the backend is where linux will really save you time and effort (once you have it configured).

Don't start on the desktop

[MAXOMENOS]

In my experience it's much easier to get Linux in the workplace as a server, and here there's lots of areas where it's as good as or better than Windows. Start with a LAMP server for internal web; use it to host a Wiki for documentation.

First step: Audit

[nine-times]

If you want to know how to start, your first step would be to audit all the software that people use to get their jobs done. Once you have a complete list, ask these questions for each piece of software:

1. Does that software run on Linux?
2. If not, is there a comparable piece of software that would have all the functionality we need?
3. If not, can we live without the missing functionality?

If you get to the end of those questions and the answer is "no", then you should probably cut your losses and accept that you'll have to stick with Windows. If you can answer "yes" to at least one of these questions for every piece of software on your list, then select some users to be in a pilot program. You should find at least a couple semi-influential but fairly patient power users and set up a new test machine for them.

Re:The department gives the hint.

[houghi]

Isn't Mint a distribution? So you should be able to make ity look like anything out there. I believe XFCE would look the most familiar.

For the user, look at the desktop. For the admin, look at the distribution.

As an admin, I would probably use something like SUSEStudio.com, because it would mean I would be able to easily make an installable image that looks likeI would want it with the programs I desire.

A bit of extra work and you have something that is really tailord for your company. You can make two images. One for clients and one for servers. Or go evebn further and edit YaST so you have only one image for several options. Portable, desktop, software selections per department, ...

Obviously the work you put will depend on how large the company is.

No.

[Burz]

As soon as they scratch the thinnest surface they will get very confused. In my experience, configuring KDE like Windows results in rejection after an initial period of brief comfort.