Maester Packs
LowScript packFree

RKSolutions Intune Anomalies

Finds what needs attention in Microsoft Intune before it becomes a problem: devices that miss protection, drift out of compliance or fall out of management, and policies that still rely on outdated settings.

Version
0.1.2
Tests
8
Connectors
0
Published
26 Oct 2026

royklo · royklo.rksolutions-intune-anomalies · 0 stars · Open source · MIT

PowerShell 
Install-MtPack royklo/maester-pack-rksolutions/intune-anomalies

Install only packs from sources you trust. This pack is made by royklo, not by Maester. The site only indexes and scans it: Install-MtPack downloads it straight from github.com/royklo/maester-pack-rksolutions.

maester-packs.lock.json entry 
{  "Id": "royklo.rksolutions-intune-anomalies",  "Source": "royklo/maester-pack-rksolutions/intune-anomalies",  "Version": "0.1.2",  "Commit": "afa83af9cb197e96ba3c2571d8d26a67da3b6c9d",  "Digest": "sha256:2749b38eff701319ff21a3d7f3e93044c819052b2a64a8e3398edd11f56e69fe"}

← All tests

MP.RKS.IA.1006 Windows devices are registered in Windows Autopilot

Severity: LowGraph

Devices registered in Windows Autopilot (with a hardware hash or a corporate identifier for Autopilot device preparation) are recognised as company devices when they are reset, and enrol again on their own. A device that is not registered can be reset and set up as a personal device. The test lists physical Windows devices with neither a hardware hash nor a corporate identifier. Cloud PCs are left out.

Remediation action

  1. Upload the hardware hash of each device below (Get-WindowsAutopilotInfo), or add its corporate identifier.
  2. In the Microsoft Intune admin center, go to Devices > Enrollment > Windows Autopilot > Devices and import them.

Related links

%TestResult%