The user is staring at an error. You are standing in a corridor with only your phone. Two minutes later you are looking at their screen, fixing the problem yourself. This is the session, step by step.
Remote troubleshooting is a headline feature of the Endpoint Central app: take control of a managed computer, see its screens — including multiple monitors, which the app detects automatically — and work as if you were sitting at the desk. The steps are simple. The professionalism is in the details around them: permission, communication and closing properly.
Call or message the user first whenever the situation allows it. A screen that starts moving on its own frightens people and, in many offices, breaks policy. Confirm which computer is theirs — the app lets you take control of a user session or the computer session, and picking the right one matters on shared machines. Most importantly, keep the app's user permission prompt enabled: Endpoint Central can ask the user to accept before you connect. That single setting turns remote control from something done to users into something done with them, and it is your protection if a session is ever questioned.
Open the app and connect to your server (through the VPN or gateway if you are outside). Find the computer in the list, open it, and choose the remote control action from the tools. Accept the permission flow, and the user's desktop appears on your phone. If the user has two monitors, the app detects and displays them — switch between displays rather than fighting a shrunken view of both. Give the screen a moment to settle on slower connections; the first seconds of any remote session are the laggiest, and judging the connection by them leads to unnecessary restarts of the session.
Phone remote control rewards a different technique than desk remote control. Zoom into the area you are working in instead of reading the whole desktop at thumbnail size. Use the on-screen controls for right-clicks and key combinations rather than improvising gestures. For fixes that are really two commands, skip the screen entirely — the app also offers a command prompt (and terminal on Linux) for managed machines, which is faster and kinder to mobile data. And know the honest limit: a long, fiddly job — a big settings hunt, a spreadsheet-side diagnosis — is better finished at the console. Start it on the phone if someone is blocked; move it to the desk if it grows.
When the fix is done, tell the user what you changed in one sentence, then end the session explicitly rather than letting it time out, and confirm with the user that their screen is back in their hands. If you restarted anything remotely, wait and confirm the machine came back and the user can log in. These closing courtesies take twenty seconds and are the difference between an IT department users trust with remote access and one they fear. Trust, once earned, makes every future session faster — users accept the permission prompt immediately instead of calling their manager first.
The full video shows remote control taken from the app on a real fleet — the fastest way to learn the flow.
▶️ Watch Full VideoYes — and they should. Endpoint Central can prompt the user for permission before a session starts, and the session is a visible event on their machine. Keep that setting on; silent access destroys trust and may break your office policy.
Yes. The app automatically detects and displays multiple monitors, and you can switch between them during the session instead of squinting at both squeezed onto one small screen.
Stabilise the user if they are blocked, then finish the long work from the web console. For quick command-level fixes, use the app's command prompt tool instead of the full screen — it is far lighter on a slow connection.