Remote Work and Off-site Access
Turning the PC you left at the office into a machine you can reach: unattended setup, what breaks after updates or power cuts, and what this does not do.
Updated
Remote control for your own work is a different problem from supporting someone else.
The machine you are connecting to is yours. Nobody is sitting next to it, and nobody is going to click Accept for you. That single fact sets the direction for everything else.
Where this sits relative to the other two
| You connect to | Anyone there? | |
|---|---|---|
| Customer support | The customer’s machine | Yes, and they must approve |
| Internal IT operations | Company-managed endpoints | Sometimes |
| Remote work | Your own office machine | No |
So remote work has to run unattended — there is no second option. Setup is covered in unattended access.
Four things that actually stop you connecting
Most remote-work failures are not software problems. The machine simply is not there any more. Roughly in order of how often they happen:
One: the machine sleeps or hibernates. By far the most common. Before you leave, set the power plan so it does not sleep, or at minimum confirm the network adapter is allowed to wake it. Laptops sleep on lid close by default; desktops sleep by default too.
Two: it restarts after an update. Windows finishes an update, reboots, and stops at the login screen. Unless automatic sign-in is configured, the machine is powered on but the remote software has not started.
Three: power loss. A tripped breaker, someone unplugging it to vacuum. No software fixes this — what does is the “restore on AC power loss” setting in BIOS, which is worth setting before you need it.
Four: the network changed. New router, re-addressed subnet. WorksLink connects by device ID rather than IP and NAT traversal deals with private addressing, so this one usually takes care of itself (see what is NAT traversal).
Five minutes on the first three before you leave beats an hour of remote troubleshooting afterwards.
What it replaces
Most people were previously doing VPN plus Remote Desktop. Compared to that:
- No VPN account needed from IT — an individual can set this up
- No public IP requirement — home and office can both be behind NAT
- But it is not a VPN replacement: a VPN gives you the whole corporate network (file servers, internal applications); remote control gives you one machine. If your work spans several internal systems, the two are complementary rather than alternatives
What it does not do
Better said plainly than discovered later:
- No mobile client. iOS and Android are not released, so “control the office PC from my phone” is not available today. See platforms and download
- No Linux client. If your work machine runs Linux, there is no packaged client for it
- It is not file sync. You operate that machine remotely; you are not mirroring files locally. File transfer works, but for constant back-and-forth with large files a sync tool is the better shape
Individual or team
For personal use the free edition is enough.
What changes for teams is account governance: when someone joins or leaves, remote access should be granted and revoked in the same place as everything else, rather than living in individual accounts. That needs Team edition or above — differences are in enterprise deployment.