Changing a Windows Network to Linux?

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"

Comments

A basic strategy:

[TripMaster Monkey]

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?

Not to sound condescending here, but honestly...if you've never even installed Linux, much less used it long-term, you really have no idea what you're letting yourself in for.

My advice would be to install Linux on your home system in a dual-boot configuration with your existing Windows install. Then, use the Linux system exclusively. If something comes up that you don't know how to do in Linux, don't boot into Windows...figure out how to do it on Linux. Only switch to Windows if you have no other option, and if you do, keep a detailed record of the transgression in a notebook (hereafter referred to as the 'Book of Shame'). Also, remember to try to do things your users at work will be expected to be able to do...after all, you're evaluating the feasibility of Linux in your workplace as well as your home. After you've figured out how to do something you couldn't do previously, check off its entry in the Book of Shame.

After a few weeks (months?) of this, sit down with your Book of Shame and see what you've learned. How many entries do you have? How many were subsequently checked off? At this point, you should have a good idea of whether or not deploying Linux in the workplace is a viable option for you.

One more thing...use the resources available to you. Here's a good link to some online Linux courses...you might want to check them out for starters. Also, the Web and the newsgroups usually have good information about whatever question you might have, if you have the patience to dig deeply enough, and the self-esteem to withstand the few elitist jerks who scoff and call you a n00b. Finally, read those man pages!

I'm looking forward to seeing what you find out...please remember to let us know. ^_^

Windows vs Linux

[ka9dgx]

There is a heavy percieved bias against Windows, for various reasons here on /., and this story points out the difference between that perception and the reality of the situation.

While many of us don't like Microsoft, for various reasons, we still use it, many of us exclusively. The network you manage is more important than you realize. You're being paid to reduce uncertainty for the users. It's not fair to your users to increase that uncertainty by orders of magnitude unless there is a massive benefit to the users. Replacement of Office with equivalent functionality is NOT a benefit, as it will only frustrate your users everytime anything unexpected happens. The users will also then have you to personally blame when ANYTHING goes wrong, reguardless of its relevance to the OS switch.

If you want to learn some Linux, get an older machine, put two newer NICs in it, and set up an IPcop firewall. You can use a web browser to configure it once it's installed, and peek around inside it via the console. This gives you the benefit of helping to protect the users, while giving you a linux box to manage.

Don't subject your users to your whim. It may suck for you, but Windows is what the users expect, and can cope with, slashdot bias be damned.

Feel free to ignore my advice, but you might want to update your resume if you do so.

--Mike--