Slashdot Mirror


Migrating Your Office from Windows to Linux?

bastiji asks: "I work at a mid-sized company, around 50 people and 90% M$ shop (10% being the Sun server doing our backups). Most of my users are using Office 85% of the time with some specialized apps thrown in for good measure. With the upcoming licensing changes from M$ my finance guys are worried about increased spending on even the software that we already own. I've been to told to look for alternatives and I'm asking for your help. How does one begin to do migration from a totally dependent M$ shop to the least expensive options. Are there any examples for mid-sized firms taking this route and any public examples of cost-savings?"

8 of 677 comments (clear)

  1. Before you switch... by whizzird · · Score: 5, Insightful

    I'd suggest having the users (or leads or whatever) try the windows version of star office. Make sure they can do what they need to do, before you switch them. Otherwise you'll be forced to switch back, and they'll have a negative view of Linux.
    Also make a list (you can't plan something like this too much) of all the apps they're using, and what features they're using, and make sure you can provide all of those features before you switch.

    And put lots of pictures of Tux around the place. His cute smile will calm everyone's fears. :)

    1. Re:Before you switch... by Fjord · · Score: 5, Insightful

      Similarily, get people using Mozilla instead of IE. Using the Windows versions of the Linux applications they will be using will make the transition much easier.

      Also check the how well specialized applications under wine. Don't just read the ranking in the codewearvers database: actually use it.

      --
      -no broken link
  2. Cost of retraining? by essdodson · · Score: 5, Insightful

    Have your finance people taken into account that the majority of the employees know Microsoft products fairly well and would have to be retrained for such a migration. The problem getting Linux or other OSS into the office isn't cost or a technical issue. Its a people issue, plain and simple people know MS Products, they've been using them for years. A move to a completely different operating system and business suit will leave the employees feeling abandoned and useless and will more than likely hurt productivity.

    Something to consider. This is probably the biggest reason that OSS has had such a hard time infiltrating the office.

    --
    scott
    1. Re:Cost of retraining? by mckayc · · Score: 5, Insightful

      Put your average Windows user in front of a Linux box and ask them to do something they can do in Windows like change the background. Watch them panic when they can't do it, or don't know where the C Drive is. It's not because they're stupid, they're just not used to the differences between the two OSes.

      If you ignore the issue of retraining because "Linux Windows Managers are an easy transition" you're quite simply dimwitted.

  3. Not sure if this works but... by T3kno · · Score: 5, Insightful

    If I were doing this I would create a "I want that" sort of environment. What I mean is pick a Linux distro that has a lot of eye candy and cool features, ala SuSE or Mandrake, and give it to some of your more advanced users, those willing to experiment a little bit. Let them play around with it, and give them some freedom to customize as much as they want. Once they start to really make the GUI look nice, and playing with some of the stuff that is just not available with out of the box Windows/Office they will start to attract other users. Have them tell the rest of the staff that this is the "future" and they are beta testing for the optimal environment. It wouldn't hurt if you got them new machine, or monitors, give a users some incentive to learn and use Linux.

    With KDE 3 it's really not that hard to learn the OS, how many Windows users use a CMD shell, the same will be true for the average run of the mill Linux user if the GUI is setup right. I have been using KDE3 for a while now and it is at least as easy if not easier than Windows to do just about anything.

    If you allow fairly unrestricted Internet access I would make sure that all of the multimedia apps are working correctly, and that flash is working as well. These are big things for the weenies, they want the bells and whistles that Windows provides, and with a good distro they're all there, but they may need some tweaking to get them running flawlessly.

    Just my $0.02, but that is what I would do.

    --
    (B) + (D) + (B) + (D) = (K) + (&)
  4. Not so simple (you forgot the BSA) by sterno · · Score: 5, Insightful

    It does seem like it should be that simple but you neglect the existence of the BSA audit. If you go that route you can expect to hear from the BSA before too long offering an amnesty if you buy the latest versions of the software. If you don't, of course, they'll take you to court and they'll get you for that one or two pieces of software you didn't license. Every company has one or two pieces of software they didn't license. That's all they need to get you for the software costs and legal fees. Fun, non?

    My suggestion is that if you choose not to go the Microsoft route make a point of either:

    1) purging every vestige of microsoft's sofware from your office

    2) making sure everything is in pristine order for when the BSA comes along

    --
    This sig has been temporarily disconnected or is no longer in service
  5. Re:Good Luck by soloport · · Score: 5, Insightful

    Diferentiate between quick-learners and, uh, reluctant-learners, first. If you can't figure this out intuitively, ask. "Would you like to try something new?"

    Entice even *one* person to try a new, alternative Office suite (start with an MS-Windows install of TOS Office). Ask for their feedback. Observe their learnning experience and learn from it, yourself. Then take it to the next level.

    Teach a half-dozen people -- in your spare time. Grow your "install base". Always return to the original group(s) and make sure they're not feeling abandoned, etc.

    Next, introduce *one* new person to a "pretty" desktop (Grome/KDE). Show them all the ease-of-use options first. Then help them understand the details as they walk through the learning curve. Every newbie will be diferent. But every newbie needs encouragement; A reason to stay the course.

    By all means, show them the same app. they used on MS-Windows (e.g. TOS Office) running on the new desktop! Help them make "familiarity connections".

    Be methodical, plodding, patient and open-minded. You'll succeed far sooner than you ever dreamed! The initial newbies, if you employ them, will help newer newbies. And the love will spread...

    Do I sound like I've done this before? ;-)

  6. Simplify the task bar, menus, desktop by mikosullivan · · Score: 5, Insightful
    Linux can be made a lot friendlier just by configuring the desktop for really easy use.

    This is a small change to the way KDE and Gnome look, but I think it's an important change: the typical Gnome taskbar along the bottom is three times as big as Windows users are used to, and is cluttered with a bunch of useless toys. Get rid of everything except the buttons that indicate which programs are running, and of course the button that users think of as the "start" button.

    The default menus in most distros are also way too extensive. They tend to have the same thing several times in several places. Pick the dozon or so programs your users generally need and put them in the main "start" menu. Hide the rest in a single "advanced" menu, or even get rid of the menu items altogether.

    Put icons for the most important programs right on the desktop: Spreadsheet, Word Processor (not "Text Document" like Open Office says), etc.

    By default, don't allow multiple desktops. Users who are advanced enough to understand the concept will know to ask you for it.

    Finally, sit and watch users play with the system. Note any place that they frown and get confused. Don't believe self-deprecatory excuses that they just don't know what they're doing and they're sure the system is fine: if they don't know how to do something it's the systems' fault for not being easy enough.

    --
    Miko O'Sullivan