Integrate ManageEngine Endpoint Central with ServiceDesk Plus Complete Guide

Endpoint Central manages the endpoints — it inventories every computer, deploys software, pushes patches and can take remote control. ServiceDesk Plus manages the conversation — tickets, technicians, SLAs. The integration joins them in both directions, and it is worth knowing exactly what flows where before you switch it on.

1. Endpoint Central to ServiceDesk Plus: hardware and software inventory lands in the ServiceDesk Plus asset module and CMDB, so asset data stays current without manual entry.
2. Tickets from the machine itself: a user can raise a ticket from the Endpoint Central agent icon on their own PC, and the machine details travel with it.
3. Events become tickets: new hardware detected, new software detected, a licence expired, or prohibited software found can automatically open a ticket.
4. ServiceDesk Plus to Endpoint Central: from inside a ticket, the technician can start a remote session, deploy or remove software, and open system tools on that exact machine.

That last point is the one that changes daily work — the fix happens in the same window where the problem was reported.

The integration itself takes minutes. The failures almost always come from skipping these checks first.

1. Admin access on both products. You need administrator rights in Endpoint Central and in ServiceDesk Plus. The ServiceDesk Plus side uses a technician account with SDAdmin privileges for its API key — plan whose account that will be.
2. The servers must reach each other. Each product will call the other by server name, port and protocol. If one is on HTTPS with a certificate the other does not trust, the handshake fails — fix reachability before touching keys.
3. Names must match the reality. On multi-site and MSP-style setups, ManageEngine expects the site and office naming and the computer hierarchy to line up between the two products, or assets land in the wrong place.
4. Decide the account like it matters — it does. The integration runs day and night under one identity on each side. A dedicated account beats borrowing your own login, because when you change your password later, the integration should not break with it.

Authentication between the two servers is handled by API keys in both directions — one key per direction. Start on the Endpoint Central side.

1. Log in to the Endpoint Central console with an administrator account.
2. Generate the API key in Endpoint Central for the ServiceDesk Plus integration.
3. Copy it somewhere safe for the next step. Treat this key like a password — anyone holding it can talk to your endpoint server as the integration.

This key proves to ServiceDesk Plus that the data arriving really comes from your Endpoint Central server.

Now tell ServiceDesk Plus where Endpoint Central lives.

1. Log in to ServiceDesk Plus with admin credentials.
2. Open the Endpoint Central server settings (under Admin, Endpoint Central Server Settings).
3. Enter the server name, port number and communication protocol (HTTP or HTTPS, matching how your Endpoint Central server actually runs).
4. Paste the API key you generated in Endpoint Central.
5. Choose the features to integrate — asset data, help desk requests, software deployment and the rest — instead of switching everything on blindly.
6. Save. ServiceDesk Plus now knows your endpoint server and can authenticate to it.

Half done — and this is the half people forget. Communication from ServiceDesk Plus to Endpoint Central needs its own key, generated in ServiceDesk Plus and stored in Endpoint Central.

1. In ServiceDesk Plus, go to Admin → Users → Technicians.
2. Either edit an existing technician or add a new one for the integration. Enable login for the technician and give it administrator (SDAdmin) privileges.
3. Under API key details, generate the API key and copy it.
4. Switch to the Endpoint Central console: Admin → Integrations → ServiceDesk Plus settings.
5. Enter the ServiceDesk Plus server details and paste the copied API key, then Save.

Both directions are now authenticated. If you skip this step, one direction works and the other silently does not — the classic half-working integration.

Asset data syncing is only half the prize. For technicians to act from inside tickets, enable the UI integration.

1. In ServiceDesk Plus, click the gear icon at the top right.
2. Go to Apps and Add-ons → Integrations → Endpoint Central.
3. Confirm the Endpoint Central server name, port and protocol, and tick the checkbox to enable the Endpoint Central menu.
4. Then enable it per technician: Users → Technicians → edit the technician → tick Enable to access Desktop and MDM Plugin Functionality → Save.

One honest quirk, straight from ManageEngine's own documentation: you cannot enable this menu for your own account — another administrator has to do it for you. Every technician who gets Endpoint Central access in ServiceDesk Plus is also created as a user in Endpoint Central, so keep the technician list deliberate.

Do not declare success because the settings saved. Prove the integration with the three checks that matter.

1. Inventory check: confirm a known computer's hardware and software details now appear inside ServiceDesk Plus assets. Inventory syncs immediately when it is working.
2. Ticket check: raise a test ticket from a PC's agent icon and confirm it arrives in ServiceDesk Plus with the machine attached.
3. Action check: from that ticket, run one harmless action — open the machine's system details — and confirm it responds.

Know the rhythm of the sync so you do not chase ghosts later: inventory and deployment status update immediately, the currently logged-on user refreshes about every 30 minutes, approval requests every few minutes, and newly created software packages sync once every 24 hours or on demand. A package you created two minutes ago is not missing — it is simply not due yet.