Skip to main content
Remote Lock on Windows: locking without wiping, at last

This post is a translation of the Spanish original.

3 min read

Remote Lock on Windows: locking without wiping, at last

When someone calls saying they've left their work laptop on a train, the support conversation usually ends with the same awkward question: do we wipe it now or wait and see if it turns up? Until now, on Intune-managed Windows, the serious options were few and almost all of them involved wiping.

Microsoft has just opened a third way. It's called Remote Lock, it's in preview and it does exactly what the name promises: lock the device remotely without touching the data.

What exactly it does

According to Microsoft's preview documentation and what outlets like Help Net Security and TechSpot have published, when the administrator applies the lock Windows closes all active sessions, hides the sign-in options and shows a "Device Locked" screen. The device stays enrolled and managed in Intune, BitLocker stays active and the user's data stays where it was.

What's striking is how locked down it is. There's no local or offline unlock: no PIN, no password, no local admin, no web sign-in. Only IT, and only from Intune.

At this stage it's configured by hand, with a custom profile in Intune that sets LockState to 1 and is assigned to a dedicated group. To unlock, another profile with LockState set to 0 assigned to an unlock group. Functional, but quite handmade for something that will end up being a button.

What it doesn't do

Here's the fine print. Remote Lock doesn't prevent booting into the recovery environment, safe mode or from a USB stick. It doesn't change credentials or cut the network either. And the lock only arrives when the device checks in with Intune: if the laptop was already off or offline when you send it, it stays as is until it reconnects.

In plain terms: what protects the data on a stolen laptop is still BitLocker. Remote Lock is a locked door, but the real wall is encryption.

My reading from support

I like it. A lot, actually. Between "we do nothing" and "we wipe the device" there was a huge gap, and that gap is where many "lost" laptops live that later turn up in the car boot or in a station's lost-property office. Wiping is irreversible and costly in time: reinstalling, re-enrolling, the user recovering their stuff. Locking gives you room to decide calmly.

I see the best counter-argument clearly: someone may think this has it covered and relax on encryption. That would be a mistake. If a device without BitLocker falls into the wrong hands, Remote Lock changes little, because a boot USB is enough to read the disk. My view is that this feature only makes sense in fleets where BitLocker is already non-negotiable. Outside that, it gives a feeling of security that doesn't match reality.

I also have doubts about remote-only unlocking. For a theft it's perfect. For the false positive, the user who calls at eight in the morning with the laptop in their hands, it depends on the device having network access and on the check-in being fast. I haven't tried it yet, so I don't know how long it takes in practice, and a good part of its real usefulness depends on that.

What I would do right now, if you manage Intune: check what percentage of your fleet really has BitLocker enabled. That figure says more about your exposure to theft than any new feature.

I'm left with a question: when this leaves preview, will the default protocol for a lost device change from wipe first to lock first?

Sources

David González Lombraña

Apuntes, laboratorio y proyectos de IA, Linux y redes.