A user calls on a Sunday. A server-room PC needs a restart, three laptops are missing a critical patch, and you are nowhere near your desk. With the Endpoint Central mobile app, all of it is handled from the phone in your pocket — if the setup is done properly and safely.
First, one honest sentence that this whole guide stands on: the phone does not manage your PCs — the Endpoint Central server does. The mobile app is a window into that server. It lets you see the fleet, approve patches, start remote control sessions and fire instant actions from anywhere. It does not replace the server, and it does not replace the web console for heavy work. Set it up with that picture in mind and it becomes the most useful tool an office admin carries. This page covers the complete working setup — install, safe connection, login, and the daily routine.
Endpoint Central works in three layers. The server sits in your office (or on a machine you control) and holds the database, policies and schedules. An agent on every PC talks to that server. The mobile app is simply a third way of talking to the server — alongside the web console on your desk. ManageEngine says it plainly in its own app documentation: the app extends the web console, it does not replace it. Every action you take in the app — a restart, a patch approval, a remote session — is executed by the server and the agent, exactly as if you had clicked it at your desk. So the real setup questions are never about the phone. They are about the server being healthy, reachable and protected.
Install the app named Endpoint Central by ManageEngine from Google Play or the Apple App Store — nothing else. On first launch it asks for three things:
8020 is the standard console port used for this connectionThen sign in with your normal Endpoint Central username and password. The same account, the same permissions, the same audit trail — the app creates no back door and no separate login system. If the connection fails at this stage, the problem is almost never the app: it is reachability, which the next step deals with honestly.
Inside the office Wi-Fi, the app usually connects immediately because the phone can already reach the server. The moment you step outside, the server must be reachable from the internet — and this is where setups go wrong. Never port-forward the Endpoint Central console straight onto the public internet. A management console that can restart, wipe and remote-control every PC in the company is the single worst thing to leave open to the whole world. The safe routes are the boring ones: connect the phone to the office through a VPN first and then open the app, or use ManageEngine's Secure Gateway Server — the vendor's own edge component that sits between the internet and your server for exactly this job. Both routes are explained in full in the companion page on safe connections.
A phone with fleet control is a master key, so treat it like one. Keep a strong screen lock on the phone — fingerprint plus a real PIN, not a four-digit guess. Turn on two-factor authentication for console logins if your setup offers it. Sign in to the app with your own named account, never a shared admin login, so every action stays attributable to a person. And decide today what happens if the phone is lost: the kill routine (revoke the account session from the web console, change the password, wipe the phone remotely) is written up in its own page in this set. Security set up in advance takes minutes; improvising it during a loss takes hours.
With the connection safe, the daily pattern settles quickly. Morning: open the app, glance at system health and the list of computers with missing patches. Approve the patches that are due — the app supports approve and decline directly, and you can watch automated deployment tasks progress. During the day: when a user calls, find their computer in the app, start a remote control session (the user can be asked for permission first — keep that setting on), or open a command prompt on the machine for a quick fix. Machines that are off can be woken with Wake on LAN; machines that must go down can be shut down or restarted remotely. New computers joining the office can be added and agent installation tracked from the same app. That is the honest shape of the job: monitoring and instant response on the phone, heavy configuration at the desk.
The complete live demo — connecting the app, taking remote control and running a full fleet from a phone — is in the full video.
▶️ Watch Full VideoNo — and ManageEngine itself says so. The app is a companion for monitoring and instant response: approvals, remote control, quick actions. Configuration, deployment planning and reporting belong on the web console, where the screens and options are complete.
Three things: the server name or IP address, the port (8020 is the standard port for this connection) and the mode — choose HTTPS. After that you sign in with your normal Endpoint Central username and password.
Yes, if the connection route is safe: through your office VPN, or through ManageEngine's Secure Gateway Server. It is not safe if the console itself has been port-forwarded onto the open internet — that exposes the tool that controls every PC you manage.