Hi-ho,

Up until I stopped consulting/slaving privately a couple of years ago I
was supporting about 200 users across 6 firms who did just this sort of
thing with Linux servers and mixed client networks.

What does it look like?  From my point of view to do what you asked:
 - Cyrus IMAP for mailbox storage (Don't let users store email locally)
 - postfix for inbound and outbound email, (Does internal as well)
 - mailman for internal mailing list management (Can do external as
well)
 - fetchmail to pickup mail if you're using a multi-pop email service.
 - zonedit.com dynamic DNS setup (don't like dyndns) if you want to get
external mail directly.
 - squid proxy for surfing.
 - Samba for windows client and old mac file access, native NFS for
linux and mac OS-X users.
 - rsync backup to another box if DR is required, and some sort of tape
drive (Was Dat, the last couple I did were super DLT) using generic
backup tools.

On a small site I'd do everything with one box, the busier or larger the
site the more machines would be used to split up the tasks..  Often not
from a performance perspective, but to keep the configuration of each
box simple and easier to maintain.  "Do it all" boxes tend to be complex
to support if they are busy, and are a PITA to upgrade or do maintenance
on as they take out the entire LAN if you typo something.
 
BUT...  When I stopped doing this work it took me 5 months to find a
competent firm to take over the sites and support them professionally.

If your firm has an in-house 'IT' guy (or girl) who is prepared to learn
the ropes it might be a good way to go, or if you have a good
relationship with a competent FOSS support vendor.

In my experience using FOSS on the server end in a small to medium sized
business is not a golden bullet for saving money, or fixing reliability
problems instantly.

Like any system it needs monitoring and maintenance, and time will
eventually show any flaws in the design and/or config of the setup.

The reality is that in SME's in New Zealand it can be difficult to get
access to linux/FOSS skills to give an appropriate level of risk
mitigation.

Unless you work for an IT company and IT is 'what you do' and using FOSS
your business direction, I would be very cautious about changing away
from SBS, it isn't all that bad for what it is....

At the very least talk to everyone in the business about what they do on
their PC.  Make a list, and play it back to them in your words,
explaining why FOSS will make things better, and how it will make things
worse.  (No golden bullet).

A few things that I've seen break due to unplanned and/or over-zealous
implementations of different server technologies in SME's over the
years:  (not a complete list, just a few off the top of my head...)

- Specialised printing services such as RIP boxes or large scale
copiers/MFD's refusing to talk to samba print queues.
- VPN traversal not working on linux firewall for the all important
vendor database that the sales folks forgot they used every day of the
week.
- Vendors refusing to support specialised software because a site 'Uses
linux servers' Even though it's just a network drive...  (ARGH!)
- Software requiring network based licensing services (AutoCad mech
desktop for e.g) having difficulty with the Samba domain emulation.
- Dynamic DNS on the linux side mis-reporting ADS/Windows specific
attributes, and barfing all over the windows security.
- After you've finished implementing a Linux server setup the accounting
department rolls up with the windows version of an accounting package
which requires Microsoft SQL.  They knew they were going to get the
'network' upgrade months ago, and assumed the new 'network' you've
installed would run "Dodgy network money 5.0".
- The CEO wants to sync his Titan PDA with your email system, because
the CEO at XZY Company can.  Just after you've disconnected the SBS
server and can't find the CD's.

Just my 2c worth, but I think it's important that people don't go out on
a limb with this sort of thing and put in a FOSS solution because they
personally feel it is a good idea.  Such things can tend to lead to
opening up your future opportunities faster than you thought might
happen.  (ie: you get the boot)

Unless you're working for a business full of geeks, make sure that
whatever you do has a good business fit first,  Appropriate technology
that delivers a reliable business solution is always a good way to go,
regardless of who's name is on the box, or how much it cost.

Cheers, Chris H.  (Damn, that's a long post for this time of night)

On Thu, 2008-02-28 at 21:15 +1300, John Hyde wrote:
> What would a linux / open source set-up look like and is anybody
> actually
> using such a set-up ?


Reply via email to