One remote desktop tool per client, one spreadsheet per office, passwords in a chat window — that is how most small IT service providers start, and it breaks the day the fifth client signs up. Endpoint Central MSP is built for exactly that moment: every customer, every office and every computer inside a single console, with walls between clients and proof of work for every bill.
If you provide IT support to several companies, your real problem is not tools — it is separation and scale. Each client needs its own computers, its own policies and its own reports, but your team needs one login and one routine. That is the exact job of the MSP edition of ManageEngine Endpoint Central. This guide explains the structure first — customers, remote offices, agents and distribution servers — then the daily work: onboarding, patching, technician access and the monthly reports that justify your invoice. Prices and licence counts change, so this page never prints a number for them; check ManageEngine's current MSP licensing page or ask for a quote before you commit.
Endpoint Central MSP organises everything in three levels. At the top is your server — one installation that your whole team logs into. Below it sits a Customer for every client company you serve. Inside each customer you create Remote Offices — one for every physical location that client has, like a head office and a warehouse. Computers belong to a remote office, remote offices belong to a customer, and almost every action in the console — a patch job, a software push, a report — is aimed at one of these levels. Get this map right on day one and the console stays clean for years; mix two clients into one customer and you will be untangling reports forever.
Small offices can let every agent talk directly to your central server over the internet. Bigger sites should get a Distribution Server — one always-on PC or server inside that office. The distribution server keeps local copies of the patch, software and configuration repositories, syncs them with your central server at intervals, and hands the files to agents over the fast local LAN. The same 500 MB patch then crosses the client's internet line once, not forty times. ManageEngine's published sizing for a distribution server starts modestly — roughly a Core i3 class machine with 4 GB RAM for up to 500 computers, growing with the load. When in doubt, start direct for tiny sites and add distribution servers where bandwidth hurts.
Every managed computer runs the lightweight Endpoint Central agent. Push it from the console, install it manually, or let the distribution server deploy it inside the office. Installed agents appear under that remote office in the Scope of Management. Keep the scope honest: remove machines the client has scrapped, because reports, patch percentages and — depending on your licence — billing counts all follow the scope. A bloated scope makes a healthy client look badly patched and makes your monthly report a lie.
The MSP console holds the keys to every client's network, so access control is not decoration. The Administrator role sees everything. Below it, create Technician users with defined roles — read, write or full control per module — and, critically, a scope: a technician can be limited to specific remote offices or custom groups. Your junior who supports two schools should not even see the hospital client's machines. Scope-limited technicians also cannot touch global settings such as patch test groups or system health policies, which stay with full administrators. Set this up before the team grows, not after the first awkward question from a client.
The daily MSP routine in this console is simple to say and powerful in practice: patch in staggered rings per client (a test group first, the rest a few days later), deploy software per customer so one client's licensed package never lands on another's machines, and use remote control for support without travelling. Because automated patch deployment, software deployment and configurations can all be scoped per customer or per remote office, one engine does the work of ten separate installations — and a mistake stays inside one client's boundary instead of spreading everywhere.
MSP clients rarely complain about the work — they complain that they cannot see the work. Schedule per-customer reports: patch status, inventory, software compliance and system health, generated separately for each client and sent on a fixed date. Endpoint Central also lets you mask personal data in report settings, so a report shared with a client does not leak end-user details it should not carry. Attach the report to your invoice and the conversation changes from “what did you do this month?” to a two-minute review. That reporting habit, more than any single feature, is what turns the MSP edition from a tool into a business.
See Endpoint Central MSP running live — customers, offices and agents on one screen, step by step.
▶️ Watch Full VideoThe regular edition manages one company's computers. The MSP edition adds the customer layer on top — many client companies in one console, each with its own remote offices, agents, technician scopes and reports, so a service provider runs every client from a single installation.
No. Small sites can use direct communication between agents and your central server. A distribution server earns its place where an office has many computers or a slow internet line, because patches and software then download once to the office and spread over the LAN.
Licensing is sold by ManageEngine for the MSP edition based on the endpoints and technicians you manage across customers, and the exact packs and prices change over time. This guide deliberately prints no price — check ManageEngine's current MSP licensing page or request a quote for your endpoint count before budgeting.