AutopilotQR
Microsoft introduced QR-based Device Association for Windows Autopilot Device Preparation, but how do you actually scan the QR code and associate the device with your tenant? AutopilotQR makes it simple. Open the website on your phone, sign in with your Microsoft Entra ID account, scan the QR code, and associate the device directly with Intune. No CSV exports, USB drives, or PowerShell required.
What it does
- Scans Device Association QR codes generated during Windows OOBE
- Signs in to your own Microsoft Entra tenant using multitenant authentication
- Lists available Windows Autopilot Device Preparation policies
- Associates devices directly with your Intune tenant using Microsoft Graph
- Verifies successful device pre-association before continuing Windows OOBE
- 100% browser-based with delegated permissions. No backend infrastructure or customer data storage
MacPPPC
Building a Privacy Preferences Policy Control profile by hand means writing XML you’d rather not write, and the usual shortcut is a tool that assumes you run Jamf. MacPPPC generates macOS PPPC profiles in the browser and can push them straight into Intune — no XML, no JSON, nothing to install.
What it does
- Builds PPPC profiles for permissions like Full Disk Access, Screen Recording and Input Monitoring
- Deploys directly to Intune through Microsoft Graph using your own Entra ID sign-in
- Or download a
.mobileconfigor Settings Catalog JSON and upload it yourself - Unlisted app? Drop in its
Info.plist, or a zipped.appbundle and it reads the bundle identifier for you - Enforces Apple’s actual rules — Camera and Microphone can only be denied, so the tool won’t let you build a profile macOS will ignore
- 100% client-side. Nothing is proxied through a server, because there isn’t one
MSIinfo
Getting a ProductCode out of an MSI usually means installing something, running Orca, or trusting an upload site with a vendor installer. Drag the MSI onto MSIinfo instead and it reads the properties you actually need for a Win32 detection rule — in the browser, in a second.
What it does
- Drag and drop an MSI, get its properties immediately
- ProductCode, ProductVersion, UpgradeCode and the rest of what detection rules and packaging need
- No Orca, no PowerShell, no admin rights — works on a locked-down client
- The file is parsed locally and never uploaded, which matters when the installer is a customer’s
WinMedia Builder
UEFI boots from FAT32, FAT32 stops at 4 GB, and a current Windows install.wim doesn’t. The fix is DISM, oscdimg and a partitioning routine you have to look up every time. WinMedia Builder wraps all of it in one GUI: point it at an ISO, get media that actually boots.
What it does
- Takes a Windows ISO,
install.wimorinstall.esdas source - Splits an oversized
install.wiminto.swmparts so it fits on FAT32 - Rebuilds a bootable ISO from the result
- Optionally prepares a USB drive with a FAT32 boot partition and an NTFS data partition
- Live progress log, background processing, and settings remembered between runs
- Your source media is never modified — but USB preparation wipes the target drive, so pick it carefully
Found a bug, or want something added?
All my tools are free and open source, and I keep improving them based on real-world feedback. Open an issue on GitHub, or write to me at simon@simsen.dk.