How do I support a home worker's personal computer?

Use an attended, on-demand session that the user starts and can end, and avoid installing a permanent agent. Where possible, keep corporate data on centrally-managed systems rather than cached on the personal device.

Can I fix a home worker's Wi-Fi remotely?

You can diagnose it, but you cannot administer their router and generally should not try. The practical remedies are moving the device closer, using a wired connection, or supplying a small adapter or extender.

Should home workers' laptops have unattended remote access?

For corporate-owned laptops, yes, it allows patching and fixes outside working hours. The usual constraints apply: named operator accounts, multi-factor authentication, session logging and a visible policy so staff know it exists.

What is the most common home-working IT problem?

Connectivity, by a considerable margin, followed by authentication and VPN access. Checking those first resolves the majority of tickets faster than starting with the application the user reported.

How-to guides · 7 min read

How to remotely support someone working from home

Written for: Helpdesk and IT teams supporting hybrid and fully remote staff on home broadband and mixed devices.

In short

Supporting a home worker is technically similar to supporting an office user and practically quite different. You have no control over the network, the device may be shared with a household, and you are working inside someone's home. The technical part is usually straightforward once you accept that connectivity, not the application, is the most likely cause.

Key takeaways

Assume connectivity first. Most home-working faults reported as application problems are network problems underneath.
You cannot administer a home router, so build diagnostics that work without it.
On a personal device, use attended access with visible consent, never a permanent agent.
Household context matters: shared bandwidth, other people's devices, and a lack of privacy on video calls are real causes of real tickets.
Peer-reviewed work on remote working consistently finds that effective IT support is a foundation of productive remote work, not a peripheral service.

Start with the connection

The single most useful question in home-worker support is whether the problem persists on a different network, such as a phone hotspot. It separates a genuine application fault from a connectivity fault in about a minute, and connectivity is the more common answer by a wide margin.

Home broadband contends with everything else in the house. A call that breaks up every afternoon is often a household pattern rather than a fault, and the honest answer is sometimes about scheduling or a wired connection rather than a configuration change.

Test on a phone hotspot to isolate the home network
Ask about distance from the router and whether the device is wired
Check whether the fault correlates with times other household members are online
Distinguish VPN problems from internet problems before changing anything

Corporate device or personal device

This distinction determines what you may do, not just what you can do. On a corporate laptop, a managed agent and unattended access are reasonable and let you patch and fix outside working hours. On a personally-owned machine, permanent access is disproportionate and creates a privacy problem your organisation does not want.

For personal devices, use attended sessions with explicit consent every time. National guidance on device security and personal devices at work makes a related point about data: keeping corporate information centrally held, rather than cached on the personal machine, limits what is exposed if that device is lost, sold or shared.

Working in someone's home

Remote support to a home is an unusually personal interaction. You may see personal files, family photographs, other people's names in a browser, and the state of a room on a video call. Treating that with obvious discretion is part of the job, and it strongly shapes whether people ask for help early or struggle silently.

Say what you are doing before you do it. Announce when you take control, narrate as you work, and confirm clearly when the session has ended. It costs nothing and it is the difference between support that feels helpful and support that feels intrusive.

Reducing the volume

The same handful of issues generate most home-working tickets: wireless quality, VPN or sign-in failures, peripherals not connecting, and confusion about which applications should be used for what. Each of those is addressable with a short, plainly-written self-help page and a consistent answer from every technician.

Track which problems recur per person as well as per category. A user who calls weekly about wireless drops usually has a house problem that no amount of software support will resolve, and a wired adapter is the actual fix.

A repeatable home-support routine

1. Confirm the device type first
Corporate or personal. It changes what access is appropriate and what you are permitted to change.
2. Isolate the network
Ask them to try a phone hotspot. This one test resolves an ambiguity that would otherwise take twenty minutes.
3. Check the VPN separately from the internet
Users report both as the internet being down. Establish whether general browsing works before touching the VPN client.
4. Start an attended session with clear consent
Explain what will appear on screen, and confirm they can see the session is active and can end it.
5. Narrate as you work
Say what you are doing and why. It reduces anxiety and often prevents the next call on the same subject.
6. Fix the underlying pattern where you can
If someone calls weekly about wireless, send a wired adapter. Repeat tickets are usually an environment problem, not a user problem.
7. Close the session visibly and follow up in writing
Confirm access has ended, then send a short summary of what changed so the user has a record.

Common mistakes

Installing a permanent agent on a personally-owned machine, which is a privacy and governance problem regardless of intent.
Debugging an application for half an hour when the home wireless was the cause all along.
Taking control without announcing it, in someone's home, on a machine with personal content on it.
Assuming a home user can change router settings, or should be asked to.
Treating repeat callers as difficult users rather than as evidence of an unfixed environmental problem.

Frequently asked questions

How do I support a home worker's personal computer?: Use an attended, on-demand session that the user starts and can end, and avoid installing a permanent agent. Where possible, keep corporate data on centrally-managed systems rather than cached on the personal device.
Can I fix a home worker's Wi-Fi remotely?: You can diagnose it, but you cannot administer their router and generally should not try. The practical remedies are moving the device closer, using a wired connection, or supplying a small adapter or extender.
Should home workers' laptops have unattended remote access?: For corporate-owned laptops, yes, it allows patching and fixes outside working hours. The usual constraints apply: named operator accounts, multi-factor authentication, session logging and a visible policy so staff know it exists.
What is the most common home-working IT problem?: Connectivity, by a considerable margin, followed by authentication and VPN access. Checking those first resolves the majority of tickets faster than starting with the application the user reported.

How this works in 247connect

247connect covers both halves of this: managed devices for corporate laptops that need out-of-hours patching, and on-demand sessions for personal machines where a permanent agent would not be appropriate.

Start a 14-day free trial See the feature list