From f6aa1b67633f43c21b9c900e0ce92dc47a333da9 Mon Sep 17 00:00:00 2001 From: CBrasga <59372660+CBrasga@users.noreply.github.com> Date: Thu, 17 Apr 2025 08:23:00 -0700 Subject: [PATCH] Update device-remote-lock.md Currently, all Windows OSes are not supported. Windows 10 and Windows 11. --- intune/intune-service/remote-actions/device-remote-lock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/intune/intune-service/remote-actions/device-remote-lock.md b/intune/intune-service/remote-actions/device-remote-lock.md index d4ce5825f8c..2c85678f41a 100644 --- a/intune/intune-service/remote-actions/device-remote-lock.md +++ b/intune/intune-service/remote-actions/device-remote-lock.md @@ -50,7 +50,7 @@ When **Remote lock** is applied to a device that doesn’t have a PIN or passwor **Remote lock** isn't supported for: -- Windows 10 desktop +- Windows > [!NOTE] > For macOS devices, you set a 6-digit recovery PIN. When the device is locked, the **Device overview** displays the PIN until another device action is sent. Please make sure to write down the pin since it will only be available for 30 days after the remote lock command is sent. After the 30 days, Intune will no longer have the PIN. Also, you will see a failed status in reporting if you initiate this command again for the same device while the original pin has not been used to successfully unlock the device. You should only send this command once, write down the pin, and until you use it to get into the macOS device successfully, do not try to send this command to the same device again.