Setting up a network in a small business environment entails some specialised considerations to ensure an optimum implementation. Key design factors include careful topology planning, IP addressing, proper data segregation, and licensing issues.
Microsoft hit a home run with Windows Small Business Server. It's becoming increasingly difficult to find small business servers not running the economically priced Windows operating system. The Windows Server 2003 platform provides stability, while the Exchange and SQL engines provide scalability. Wizards, meanwhile, simplify administration.
When deploying Windows Small Business Server, or any small business network, most implementations can be optimised if you keep the following 10 elements in mind.
1: Servers aren't always necessary
AMI Research reports that of 68.5 million small businesses
worldwide, more than 21 million have multiple PCs but no server. That figure
can be found in Microsoft promotional materials designed to help IT consultants
understand the small business space and sell servers. But the fact is, many
organisations don't have servers because they don't need them. Other
organisations have servers because an IT professional or consultant sold them
one, but they don't actually require it.
I've encountered customers whose previous IT consultants sold them US$4,000 servers (with dual-Intel Pentium CPUs, no less) that do nothing but fulfil DHCP services. That's a waste. While technology professionals should always work to deploy the best technologies for clients or organisations in which they work, IT pros have a responsibility to ensure the correct technologies are deployed.
If a company employs fewer than 10 employees and isn't forecasting aggressive growth, it's likely a peer-to-peer network of Windows XP Professional systems will meet the organisation's needs. Should the organisation grow, the investment in XP Pro systems can still be leveraged. When exceeding 12 or so employees, though, organisations are typically better off with a server.
One easy but all-too-common mistake can be easily avoided; never deploy Windows XP Home systems in office or business workgroup environments. The consumer OS doesn't offer the security controls Windows XP Professional boasts, nor can Windows XP Home join a Small Business Server-powered domain (should the organisation grow to the point that it requires centralised administration).
2: Good topology is planned, not accidental
Poorly configured networks are everywhere. The number of
three- and four-hop networks I encounter as an IT consultant is mind numbing.
Adding four- and five-port routers/switches here and there isn't the proper way
to connect networks. Although it's an easy approach, performance inevitably
becomes a problem.
Thus, it comes as no surprise when a small business with nine systems and four switches approaches me complaining of poor network performance. Worse yet, many of these networks often possess multiple 192.168.x.y and 10.0.x.y subnets.
Replacing three four-port switches with a single 16-port switch typically introduces dramatic performance improvements. Even with only 10 or 12 employees, the additional ports often prove handy for providing a single interface for all client systems, a server if it's present, and firewall and DSL or T1 connectivity.
It's easy to fall into the trap of simply adding switches as a network expands, but before you add a second switch, plot the network on paper. Count the number of hops a connection must navigate before reaching the gateway. Often, you'll find investing in a few extra cable drops (to avoid requiring an additional switch in a quickly expanding office) provides performance gains that more than justify the expense.
Whenever you prepare to add new systems or are prepping a new network, consider its topology carefully. Work to minimise the number of hops data must travel, even if investing in a switch with more ports or new cable drops is required.
3: Network equipment deserves investment
The average lifespan of a network switch or firewall is
probably four to five years. Others may tell you three years is the average,
but let's be honest -- most organisations try to maximise their investments by
running equipment longer.
If you try to save funds by purchasing cheaper network equipment, you'll almost certainly pay the price down the road. Less expensive switches, firewalls, VPN appliances, and routers are available, sure. But they're made with lesser quality materials. That means the power supplies are less robust. Ports are more likely to fail. Cheap fans are more likely to malfunction, thereby resulting in failure due to overheating.
When designing or "re-architecting" a small business network, budget funds appropriately for commercial-class network equipment. Buy the best the organisation can afford. Although there are no moving parts, and the equipment is likely parked in a closet where no one will ever see it to appreciate it, most aspects of an organisation's data and communications will run through the equipment. If there's ever an element that justifies purchasing quality components, that's it.
3%
2%
