Skip to content

Managed service providers

Remote access for managed service providers

Looking after other organisations' computers means many machines, several technicians and customers who expect you to be careful. RFDesk's team features cover rollout, control and the paper trail.

  • Silent install that enrols each computer
  • Policies and device groups per customer
  • Usage reports by computer and by person

Roll out without touching every machine

Make an enrolment key in the team, with an expiry, a limit on how many computers may use it and the address-book folder new machines are filed under. The key comes with a silent install command for the Windows installer. Run it as administrator or hand it to the deployment tool the customer already uses. RFDesk installs without showing anything, starts at sign-in and joins the team by itself.

Keep customers apart and settings consistent

Structure matters once you look after more than a handful of machines.

  • Device groups sort a team's computers, and each group can lock rules of its own.
  • The shared address book has folders and tags, so a technician finds the right machine by customer or site.
  • A team policy locks settings on or off on every enrolled computer: file transfer, clipboard, recording, restart, unattended access and more.
  • Idle limits end a session after a set number of minutes without input.

Decide who can reach what

Access rules on a computer restrict connections to listed accounts or listed devices, to allowed hours and to allowed networks. The server enforces them before the computer is told that anyone asked. For unattended machines, give each technician their own access with their own password and a time window, instead of one shared secret. Their sessions appear under their own name.

A front door for customers

Each team can open a help page at its own link. A customer describes the problem and waits in a queue, a technician claims the request and connects, and the customer still approves on their own screen. Requests that are finished are listed with the team's notes.

Show the work

Signed-in sessions are kept in a history with the technician's note. Usage reports show sessions with a team's computers by period, by computer and by the person who connected. Technicians can protect their accounts with two-step sign-in.

Good to know

  • Policies apply to computers enrolled in a team, not to devices that only appear in its address book.
  • A computer that is already linked to an account or another team does not join with an enrolment key.
  • The tools a session offers on a customer's machine depend on what that machine and its policy allow.
  • Plans state whether commercial use is included. See pricing.

FAQ

Questions and answers

Can I separate one customer's computers from another's?

Yes. Use device groups and address-book folders inside a team, or a team per customer, depending on how separate they need to be.

What happens if an enrolment key leaks?

Revoke it and make another. Computers that already joined with it stay in the team.

Can a customer's staff still approve each session?

Yes. A connection made with the one-time password always needs approval at the computer. Unattended access is a separate, deliberate setting.

Can I prove who connected to a machine?

Sessions are recorded in the history with the account that connected, and access given to named people shows their name on the computer and in its history.

Ready when you are

Connect from this browser now, or get the app for the computer you want to reach.