Getting rid of your server in a small business environment

Question

In a small business environment, is it still necessary to have a central server?

Speaking for my own company (a small charity with about 12 employees) we use our server (Windows Server 2003) for the following:

• Email via Microsoft Exchange
• Central storage
• Acting as a print server
• User authentication / Active Directory

There are significant costs associated with running a server like this:

• Electricity, first for the server itself then for the air conditioning required (this thing pumps out a lot of heat)
• Noise (of which there is a lot)
• IT support bills (both Windows Server and Exchange are pretty complicated, and there are many ways they can go wrong)

I've found ways to replace many of these functions with cheaper (better?) alternatives:

• Google Apps / GMail is a clear win for us: we have so many spam related problems it's not even funny, and Outlook is dog slow on our aging computers
• You can buy networked storage devices with built in print servers, such as the Netgear ReadyNAS™ RND4210 that would allow us to store/share all of our documents, and allow us to access printers over the network

The only thing that I can't figure out how to do away with is the authentication side of things - it seems to me that if we got rid of our server, you'd essentially have a bunch of independent PCs that had no shared pool of user accounts / no central administrator. Is that right? Does that matter? Am I missing any other good reasons to keep a central server?

Does anybody know of any good, cost-effective ways of achieving the same end but without the expensive central server?

Answer 1

We keep a server in our office for the reasons you stated, primarily for centralized authentication and managing access to shared resources (storage, printers, etc.). We used to run Exchange as well and moved our e-mail to another mail system for the same reasons you stated as well (Exchange was just a pain to manage for such a small group of users). As for the other concerns with electricity and noise, I would recommend downgrading your server. If the one server is generating sufficient heat and noise as to require its own A/C unit, then it's time to get something smaller and quieter. DELL produces some decent low-end tower servers which are very quiet and do not pump out a lot of heat which are made for use in offices and will run Windows Server for a small workgroup without any trouble.

Answer 2

Just because you have a server doesn't mean it has to be some expensive, powerful beast of a machine. You can just as easily use a workstation or common desktop for the Domain, file and print sharing. However you do need to consider backups as they are one of the things often lost if you drop down to some type of NAS/print server.

Also I completely agree that running exchange yourself for a small business is probably an unnecesary complication. GMail is OK to a point, but if you do need more functionality you can get online managed exchange services.

Answer 3

Back 3 years ago, when we moved everything to the cloud in our school, it became apparent that a small company does not need a server. We have a bunch of computers and the only thing they need to share is a printer.

The fact is that MS sold us the idea that one needs a server, and it may have been true in the past before the cloud was a winner. Today we run our docs and email services on Google for free. If our school burns, we can go and work next door or next city without losing one bite of information.

Next January we are launching a new school. The question of the server is out once more in the planning.

It's cheaper to administrate a bunch of user accounts in multiple PCs than to administrate a server, not forgetting the expertise requiered and the multiple issues associated with running one.

I give all this advice, coming from an MS "expert" with a long tradition of managing server environments in extremely complex networks. Now that I look at our network from a business perspective, running a server in an SMB environment is totally overkill.

Save yourselves the money.

The main teaching here is that one needs to grow and adapt. We will happy to run our new network with no servers attached.

Diego Bronstein Partner at Wizard Colombia wizardcolombia.com

Answer 4

Most modern printers could easily be equipped with a network interface, without the need for a printserver. However, you need to individually install the printer on each PC, which is a little more difficult to administrate.

As for your concern regarding the active directory, there must be hosting companies that offers VPS / virtual machine instances with only VPN access. If you just have a medium-level firewall that can hold a VPN-tunnel up then you would be good to go.

We have an inhouse vritualization server that runs a few development machines, aswell as an instance of server 2008 R2 for our AD. This approach should be easily leveregable with outsourcing.

I however doesn't have any suggestions on hosting companies. Whats your location? Country wise?

This was the first one I found that seems to offer a "private network" feature: http://www.fasthosts.co.uk/dedicatedservers/private-lan/

Answer 5

You can go to any number of service providers who offer "Hosted Exchange" for a monthly fee per mail box. You can keep the familiarity without the hassle of administration. Then just buy an inexpensive Work Group server from Dell for File and Print serving. You could probably get away with spending under $1000 (including licensing).

My question is, how old is your server to be running that load and hot??

Answer 6

Assuming you licensed Windows Server 2003 as either Full Packaged Product or Volume License you could just move it to a new desktop machine w/ mirrored SATA drives and continue using it. Personally, I like having a Windows Server machine with Windows desktops for even small numbers of client computers.

Samba can do domain authentication, but there are no open source alternatives that will give you the convenience and simplicty of managing PCs with Group Policy. There also isn't an offering that does what WSUS does in the open source world.

To my mind you're trading one set of problems for another: You're going to increase your PC support costs by doing away with the server computer (though with a network that small, I'd argue that your IT provider doesn't know what they're doing if IT support costs are an issue anyway-- that's a small network and should cost well under $2,000.00 / yr in support expense).

If you don't like what Exchange is doing for you jettison it. Personally, I like it, but it sounds like your IT provider isn't doing a good job of supporting it if, in an network that small, it requires any amount of attention at all.