Not every business has a rack, a server room, or even a cupboard with proper cooling. Plenty of UK offices, branches and small sites need datacentre-grade capability sitting under a desk or in the corner, running quietly enough not to annoy the people next to it. The Dell PowerEdge T560 is built for exactly that: a dual-socket tower with rack-class internals, generous drive bays and redundant power, in a chassis designed for an office rather than a data hall. This guide covers when a tower beats a rack server and how to spec the T560.
Why a tower at all
The case for a tower is environmental, not technical. A rack server expects cold aisle airflow, structured racking and a noise tolerance no office has. A tower like the T560 is engineered to draw air sensibly in an ambient room, run at acceptable noise levels, and sit on the floor without rails or a cabinet. For a single-site business or a branch office, that removes the hidden costs of building a mini data room just to host one or two servers.
Crucially, you give up very little in capability. The T560 is a genuine dual-socket platform with current Intel Xeon CPUs, full DDR5 memory, real hardware RAID options and redundant power, so it runs the same virtualisation, file, database and line-of-business workloads a comparable rack server would. The compromise is density and rack manageability, not raw capability, which is exactly the right trade for an office deployment.
Spec'ing the T560 for a branch or SMB
Start from the workload, as with any server. For a small virtualisation host, size cores and memory backwards from the VMs you will run, keep N+1 headroom so the box can be patched, and balance the DDR5 channels for full bandwidth. The same method we use for rack hosts applies here, just in a form factor that suits the room; read how to spec a server in 2026 for the underlying approach.
The T560's strengths are expansion and storage. Its tower chassis offers plenty of drive bays for capacity or a mix of fast and bulk storage, PCIe slots for networking and adapters, and headroom for an accelerator where a branch needs light GPU work. Specify dual power supplies and out-of-band iDRAC management even in an office; a server you cannot reach remotely, or that drops on a single PSU failure, defeats the point of buying enterprise hardware.
- •Right-size cores and RAM from the workload, with N+1 headroom for patching
- •Use the generous bays for a fast tier plus bulk capacity, on hardware RAID
- •Fit dual power supplies on separate feeds even in an office
- •Licence iDRAC for remote console so the branch box is manageable from afar
Storage and resilience for sites without IT staff
Branch and SMB sites rarely have hands on the ground, so resilience and remote management matter more, not less. Build storage on hardware RAID with a hot spare where the bay count allows, keep boot separate from data, and choose drive endurance that matches the write profile rather than defaulting to the cheapest option. Our SSD and NVMe range covers the fast tier and our wider components guidance the bulk capacity.
Out-of-band management via iDRAC is the single most valuable feature for an unstaffed site: it lets you power-cycle, re-image and troubleshoot the server without a site visit. Pair that with a sensible backup target and, ideally, an offsite copy, so a tower in a branch office is not a single point of failure for that location's data.
Tower vs rack: making the call
The decision is mostly about the room. If you have a rack, cooling and a tolerance for noise, a rack server is denser and easier to manage at scale. If you do not, a tower avoids the cost and complexity of building somewhere to put a rack server, and the T560 gives you rack-class capability without that overhead. A tower can usually be rack-mounted later with a conversion kit if your needs change, which de-risks the choice.
For multi-site organisations the answer is often a mix: rack servers in the core, towers like the T560 in branches. Build and price an exact T560 in our Dell configurator, browse the wider line on the Dell PowerEdge hub, and talk to us about a consistent build standard across your sites.