Patch Tuesday at a 60-PC client office: without a distribution server, sixty computers pull the same updates across one small internet line, all morning. With one, the office downloads each file once and the rest happens at LAN speed. Here is how that piece of the MSP architecture works and when it pays for itself.
A Distribution Server is a lightweight component you install on one always-on machine inside the client's office. It synchronises the patch, software and configuration repositories with your central Endpoint Central MSP server at set intervals, and the agents in that office then collect everything from the distribution server over the local network instead of the internet. ManageEngine documents two management modes per remote office for a reason — direct and through distribution server — and choosing correctly per client is one of the biggest quality decisions an MSP makes.
Think of it as a local storeroom. Your central server holds the master copies of patches, software packages and configurations in the ManageEngine repository. The distribution server replicates the items its office needs, on a schedule. When an agent in that office is told to install a patch, it downloads the binary from the distribution server in the same building — fast, and free of internet cost. The agent still reports its status back so your console stays accurate. Nothing about the client's experience changes, except that deployments stop strangling their internet connection.
The host needs to be always on during working hours, wired to the LAN, and have enough free disk for the replicated repository — patch and software stores grow quietly. ManageEngine's published sizing guidance starts around a Core i3 class processor with 4 GB RAM for up to about 500 computers per distribution server, scaling up from there. A spare server is ideal; at small clients, the office file server or an always-on desktop that nobody uses for daily work is the usual honest choice. Do not put it on the receptionist's PC that goes home at six.
Three small habits keep distribution servers invisible, which is what you want. Let repository sync run off-peak so even that single download avoids office hours. Glance at the host's disk monthly — a full repository disk fails deployments in confusing ways. And when a client moves office or changes internet provider, revisit the mode choice: a site that grew from 8 to 80 PCs has outgrown direct mode even if nobody complained yet. The bandwidth savings are the client's money, which is exactly why this belongs in your monthly report conversation.
See Endpoint Central MSP running live — customers, offices and agents on one screen, step by step.
▶️ Watch Full VideoEach office that wants local distribution needs its own distribution server inside that office, because the point is LAN-speed delivery on site. Small offices can stay on direct communication, and you can mix modes freely — one client can have a distribution server at head office and direct mode at a tiny branch.
Yes. ManageEngine documents modifying the remote office's communication mode from the Customers screen. Install and start the distribution server first; until it is running, that office's computers cannot apply configurations.
Agents in that office cannot collect new patches, software or configurations until it is back, because their download source is local. Pick an always-on host, and treat a dead distribution server like a small outage in your monitoring routine.