OpusBUSINESS EXPERT

Three remote-control tools are installed on that PC. You can name one of them

Andy Shepherd5 min read

The desktop on the reception desk has three remote-control programs installed on it. Ask around the office and somebody can name one, usually the current IT company's, which is the one that is meant to be there. The other two are a printer engineer's session tool from some Tuesday two years ago, and whatever the accounts software's support desk talked a member of staff through installing when a report would not print.

Every one of them was reasonable on the day.

That is the part worth sitting with, because it explains why this is so common and why nobody in the building is at fault. Somebody needed help. The quickest way to get help was to let the helper see the screen. The tool went on, the fault got fixed, and the relationship with that supplier ended a year later without anyone connecting the two events. Taking it off again was not on a list, because it was nobody's job, and an unused remote-access agent makes no noise whatsoever. It looks precisely like one that is still in service.

The question is not whether remote access is dangerous

It is a normal way to fix a computer. We use it every day, and a business that refuses it altogether just pays more for somebody to drive over.

The useful question is narrower. Who can reach this machine, and does each of them still have a reason to?

Most firms have never been in a position to answer that, which is not the same as being exposed. It is the inventory that is missing, not necessarily the security.

Two kinds of access, and the difference matters more than the brand

Every one of these tools is one of two things, and the distinction is worth more than any argument about which product is better.

The first kind needs a person at the desk. Somebody reads a code down the phone or clicks a box that says allow, the session runs while they watch it, and access dies when the window closes. Nobody can connect to that machine while the office is empty, because there is nobody there to let them in.

The second kind runs as a service. It starts with the computer, signs itself in to the supplier's console, and waits. Whoever holds an account on that console can connect whenever they like, including at two in the morning with the building locked.

Both have their place. The second is how any provider does maintenance out of hours, ours included, and a firm that bans it ends up having its updates applied in the middle of the working day instead.

An unattended agent is a key to the building. There is nothing wrong with a supplier holding one. There is something wrong with nobody knowing how many are out there.

An afternoon's work, not a project

  1. 01List what is installed on each machine, and what starts up with it
  2. 02For each remote-control tool, work out who it connects to: which company, which account
  3. 03Check that company is still a supplier, and that whoever held the account still works there
  4. 04Remove what has no owner, through the supplier where one still exists
  5. 05Write down what is left and who holds it

The installed-programs list and the startup entries will find most of it. The fastest route is usually simpler than either, which is to ask the people who sit at the machines what they remember agreeing to. The archaeology lives in their memory more reliably than it does anywhere on the disk, and somebody will say "oh, that was the man who came about the scanner", which answers a question the software cannot.

Fifteen machines is an afternoon. It is tedious and it is not technical, and it produces the one document that nobody has.

Do not simply delete them

Where the supplier has disappeared, or will not reply to two emails, that is itself a decent answer about whether their agent should stay on your computers.

Set the rule once, for whoever asks next

Per-session consent by default. Somebody wants to see a screen, a person sits at that screen while they look, and the session ends when the call does.

Unattended access becomes a decision with a name on it. Which supplier, which account, written down, and looked at again when the contract changes or the engineer who held it leaves.

Two lines in a document covers it. The value is not in the policy, it is that the next engineer who asks gets the same answer as the last one, rather than whichever answer the person nearest the phone happens to give.

The same test applies to us

This is the uncomfortable half, and it would be dishonest to leave it out. One of the tools on that PC is probably the incoming provider's, and the question does not get gentler because the relationship is new.

An IT company that cannot tell you which of its tools can take your screen while you are at lunch has told you something. The answer should arrive the same day and in writing: the tool, whether it needs you to be sitting there, and which people in the firm can use it. We put the same four questions to ourselves that we suggest you put to any provider, and this one is the first of them in practice.

If you have just changed IT provider, or there is an icon in the system tray that nobody in the office recognises, we can go through the machines with you. It is a better conversation to have on a quiet Thursday than after somebody connects to a computer at a weekend and you cannot work out who.


We work with businesses across Knutsford, Alderley Edge, Wilmslow, Altrincham, Stockport and Warrington, and remotely for clients anywhere in the UK.

If any of this sounds like your business, we will tell you plainly whether we can help.

We would like to use analytics cookies to understand how this site is used, advertising cookies to measure our ads, and to load our office map from Google. None of them loads on its own unless you accept — though Google Tag Manager itself loads either way, with every category switched off. The map also has a button of its own. Read our cookie policy