Slashdot Mirror

← Back to Stories (view on slashdot.org)

Changing a Windows Network to Linux?

Posted by Cliff on from the OS-defectors-anonymous dept.

Charli125 asks: "I have been a Windows administrator ever since I got into the tech industry. I have no working experience with any other OS except for those from Apple. I am currently working with a small company that has 1 server and around 15 workstations. I would like to faze out all of the Windows software, in order to avoid having to deal with viruses, save money, and learn how the other half lives. Since I have never so much as installed Linux, I am looking for resources or advice on how to get started, and how to plan the change over. Can anyone help me?" "My current setup is like this:
Server-Windows Small Business Server 2003, Symantec Antivirus Corporate Edition(and for Exchange)

Workstations-Windows XP Pro, Office 2003 or XP, Symantec Antivirus, IE for most of the browsers (Firefox for mine and a few others). The main apps used are like every other office, Word and Excel.

I have OpenOffice installed on my home computer, and it works fine. I do see a problem with non-tech types saving in the default format though, which would result in other users not being able to read the documents/spreadsheets.

Yeah, I know, I'm so MSFT, I'm everything you guys hate about the IT world, but I would really appreciate anything that would help me get started.

Thanks"

4 of 150 comments (clear)

  1. Faze versus Phase by Anonymous Coward · · Score: 0, Informative

    I would like to faze out all of the Windows software ...

    From the MacOS Dictionary application:

    USAGE NOTE faze, phase
    Faze = disconcert; daunt. Phase (verb) = carry out (a plan, program, etc.) in stages. Phase for faze is an increasingly common blunder--e.g.: "Others said they had weathered so many rumors that nothing phased [read fazed ] them anymore." ( Boston Globe; June 6, 1995.) The opposite error ( faze for phase) also occurs, but more rarely--e.g.: "All that while shooting guard Art Mlotkowski, shadowed all over the court by Northport senior Rob Sanicola, was fazed [read phased ] out of the offense." ( Newsday [New York]; Feb. 26, 1995.) -- BG

  2. Good advice by benjamindees · · Score: 3, Informative

    I'd add:

    Of course start with your home machine. If you can't use Linux, you can't support it. Try at least two distros.

    Also, since you're completely green, you'll have to switch in stages. Take small steps. It'll take longer, but you'll be better off for it.

    Buy and read at least three Linux books. Start with a general one to give you an overview and some basics. Maybe get one on Samba, perhaps another on whatever e-mail or groupware server you decide on.

    Stop upgrading your Windows software. Standardize on what you have now, and don't buy a new Dell with Office 2005 whenever it comes out. It will only cause more hassle. Standardize on Firefox immediately. Decide if you need to use Office and Crossover on Linux or if you can switch some or all users to OpenOffice.org. If you can switch, start now.

    Once you're completely comfortable using and configuring Linux for yourself (this will take you six months), start by replacing the Windows server. If you do it correctly, your users won't even notice. That's the goal.

    From there, switch your worst user to a Linux desktop. Explain to him how Linux works, that it's open source, and that any problems he encounters should be reported and fixed. Make sure this user tears Linux apart. Make it clear this is only a test, and that you want to find problems. Use this time to get acquainted with the bug reporting tools.

    Switching to Linux, even in a small network, is a long term project. Problems will crop up along the way. You may need to modify your intended path. Linux comes with lots of options. That's okay. Don't be afraid to try different options as long as you end up with the best configuration for your application. The benefits are definitely worth it.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  3. Migration Assistance by Mike+Sheffey · · Score: 2, Informative
    The company that I work for, Versora, focuses on helping customers who aren't Linux experts with their migration. We provide software and services for Windows to Linux desktop and server migration. Have a look at our products:

    http://www.versora.com/products/

    and services page:

    http://www.versora.com/services/

    We have also published various white papers on some of the technical issues associated with migrating from Windows to Linux:

    http://www.versora.com/support/documentation.php

  4. Re:Obviously retarded by 51mon · · Score: 2, Informative

    "if you don't change everything back so I can get my email in the next 30 minutes"

    Outlook is quite capable of spontaneously stopping people from reading their email for half an hour without any help from Linux servers (or Exchange).

    I seem to remember several versions do quite a good job of this when you get more than 2^16 email in one folder. Then there is Microsofts idea of "security" which is to make it so complex to use certain sorts of attachments no one will ever try.

    Heck I sent my boss an email with a text inline part before an HTML inline part, and Outlook just hid the text part - cool.

    If the guy is looking to lose the grief of Microsoft software Outlook, and Outlook Express, are my idea of low hanging fruit. Heck I moved a guy at the Office to Thunderbird because he needed IMAP4 (yeah right Outlook supports IMAP4 - meanwhile back in the real world....).