Endpoint Central Agent Shows Offline in Console Fix
The user is sitting at the computer, working normally — but your console insists the machine is offline. The agent and the server have stopped talking, and this page reconnects them.
✍️ Technical Anshu🪟 Windows Clients⏱️ 10 minute fix
🎥 Watch the agent install and come online in the full installation video
An Endpoint Central agent reports in on a schedule and answers the console on demand. When the console shows a machine as offline (or it never came online after installation), one link in that chain is broken: the agent service is stopped, the network path to ports 8020 or 8383 is blocked, the server address changed, or the agent install is damaged. Check them in this order — do not uninstall anything yet.
Endpoint Central — Agent — Computers
HR-LAPTOP-12Online
HR-LAPTOP-13Offline — last contact 3 days ago
HR-LAPTOP-14Online
The last contact time tells you whether the machine died suddenly or never reported in at all
1
Check the Obvious — Machine On and Clock Right
Confirm the PC is actually powered on and the user is logged in or at least at the sign-in screen
Check the PC clock. A clock that is hours or days wrong breaks secured agent communication and makes reporting look stale
Note the last contact time in the console. Offline since a known event (office move, server IP change, firewall change) points straight at the cause
2
Restart the Agent Service on the Client
On the client PC, open services.msc
Find the ManageEngine agent service — current builds list it as ManageEngine UEMS - Agent; older installs say Desktop Central - Agent. Also check the ManageEngine UEMS - Remote Control service
If either is stopped, start it and set the startup type to Automatic. If it starts and stops again, note the error — that usually means a damaged install, which Fix 4 handles
Wait a few minutes and refresh the Computers view in the console
3
Test the Road From Client to Server
The agent initiates the conversation, so test in the direction the agent travels:
On the client, open a browser and try http://SERVERNAME:8020. The console login page should load
Or run Test-NetConnection -ComputerName SERVERNAME -Port 8020 in PowerShell and look for TcpTestSucceeded : True. Repeat with port 8383 for secured communication
False on both usually means a firewall between the client and server, the server service stopped, or the agent still pointing at an old server name or IP after a server migration
The client cannot even open the road to the server — no agent setting will fix this. Check the firewall path and the server service.
False here means fix the network or the server first, not the agent
4
Repair or Reinstall the Agent ⭐
If the service runs and the ports test True but the machine stays offline, the agent registration is likely damaged — uninstall the agent from that PC and push it again fresh from Scope of Management
Exclude the agent folder C:\Program Files (x86)\ManageEngine\UEMS_Agent from antivirus scans — security products quarantining agent files is a real and recurring cause of agents that install and then vanish
After the reinstall, confirm the machine shows Online and run one manual scan from the console to prove on-demand tasks also work
⚠️ Whole office offline at once? That is never 200 broken agents. It is the server: service stopped, server IP changed, or a firewall rule removed. Fix the server side before touching a single client.
🎥 Watch a Healthy Install Come Online
The video shows the agent installation and the console view of managed computers.
The agent shows offline only for laptops. Desktops are fine. Why?
Laptops sleep, roam between office Wi-Fi, home networks and VPN, and are often off when the console checks. A laptop that was online yesterday and offline on a work-from-home day is usually behaviour, not damage. Check the last contact pattern before repairing anything.
Can a wrong time on the PC really make the agent look offline?
Yes. Secured communication and status reporting both depend on sane timestamps. A dead CMOS battery or a broken time sync can leave a PC permanently out of step with the server. Fix the time source and the agent usually recovers on its own.
The agent service keeps stopping by itself. What now?
Look at what is stopping it: antivirus quarantining agent files (add the UEMS_Agent folder exclusion), a corrupted install (clean reinstall), or another admin tool removing it. The Windows Event Viewer on the client will usually name the culprit.
This guide is based on the Technical Anshu video on Endpoint Central installation • Stuck on a step? Ask in the video comments and you will get a reply 🙏