---
title: "The tasks that make up a remote support week"
description: "Nearly every remote support task is a variation on one of two setups."
canonical_url: https://rmm247connect.app/how-to
section: "How-to"
product: 247connect
product_website: https://www.247connect.cloud/
site: "247connect Knowledge Hub"
author: "247connect Marketing Team"
date_published: 2026-02-02
date_modified: 2026-08-27
language: en-GB
license: Quotation and citation permitted with attribution to 247connect.
---

# The tasks that make up a remote support week

## Key figures

- **On-demand sessions:** Attended
- **Managed devices:** Unattended
- **File transfer:** Both ways
- **Reconnect after reboot:** Auto

## Two access models cover almost everything

Nearly every remote support task is a variation on one of two setups. Unattended access means an agent is installed once on a device you are responsible for, and you can reach it whether or not anyone is sitting there. That is the right model for servers, fixed workstations, kiosks and any machine you maintain rather than merely help with.

On-demand access means nothing is installed permanently: the person you are helping runs a small one-time application, you connect for the duration of the call, and it leaves nothing behind. That is the right model for a customer, a contractor, a personal device, or anyone outside your management boundary.

Choosing the wrong model is the root of a surprising number of problems. Unattended agents on devices you do not own creates a governance liability nobody signed up for. On-demand sessions for machines you maintain wastes minutes on every ticket and makes out-of-hours work impossible.

- Use unattended access for devices you own, maintain and can install software on
- Use on-demand access for anyone outside your boundary, or for one-off help
- Use wake-on-LAN with unattended access when maintenance happens out of hours
- Use file transfer rather than email or a shared drive for anything you need mid-session

## The habits that make sessions faster

Speed in remote support comes from preparation rather than from typing faster. Group devices before you need them, so finding the right machine is a search rather than a scroll. Agree with the user how a session starts, so the consent prompt is expected rather than alarming. Keep a short script or note for the three tasks you do most often, because doing them the same way each time makes them easier to hand over.

Where a task involves a reboot, plan for the reconnect before you start rather than after. And where a task involves a change someone might later question, note what you did in the ticket while the session is open. Both take seconds during and save a conversation afterwards.

## Doing it the same way every time

The guides below each cover one task end to end: the method, the places it usually goes wrong, and the questions people ask about it. They are written to be followed by someone who has not done that task before, which is also what makes them useful as team documentation rather than as reading material.

## Setting up remote support properly the first time

1. **Split the estate by access model** — List which devices get a permanent agent and which are helped on demand. This one decision determines your licensing, your policy and most of your day-to-day friction.
2. **Deploy agents to managed devices centrally** — Push the agent through your existing deployment tooling rather than machine by machine, and confirm it installs as a machine-level service so it survives reboots.
3. **Write the consent wording once** — Agree what an operator says before connecting and what the user sees. Consistency here is what makes remote support feel professional rather than intrusive.
4. **Rehearse the awkward cases** — Elevation prompts, reboots, multi-monitor layouts and slow links. Knowing how each behaves before a live ticket is the difference between a five-minute fix and a call-back.

## Frequently asked questions

### What is the difference between attended and unattended remote access?

Attended, or on-demand, access needs someone present at the device to start and consent to the session, and typically leaves nothing installed. Unattended access uses a permanently installed agent so an operator can connect whether or not anyone is there, which is what makes out-of-hours maintenance possible.

### Can you support someone without installing anything on their machine?

Yes. On-demand support uses a small one-time application the user runs for the duration of the call. It is the appropriate model for customers, contractors and personal devices, because it leaves no persistent access behind when the session ends.

### How do you reboot a remote machine without losing access?

Use the tool's reboot-and-reconnect function rather than restarting from inside the operating system. It signals the agent to expect the restart, so the session re-establishes automatically once the machine and its network stack are back rather than leaving you waiting and guessing.

### How do you transfer files during a remote session?

Use the session's own file transfer, in either direction, rather than email or a cloud share. It keeps the transfer inside the encrypted session, avoids attachment size limits, and leaves the transfer in the same audit trail as the rest of the session.

## Where 247connect fits

In 247connect these tasks share one console: managed agents for unattended devices, on-demand licences for one-off help, drag-and-drop transfer, chat, PowerShell and reboot with automatic reconnect.

---

Source page: https://rmm247connect.app/how-to
Product website: https://www.247connect.cloud/