← cd ~/learn
// learning path · beginner to intermediate
Intune for Windows, start to finish
Apps, scripts, local admin passwords and compliance, in the order most teams roll them out.
0 of 6 read · about 12 minutes in total
- 01Packaging Win32 apps for Intune: detection rules and return codesMost Win32 app failures in Intune come down to two things: a detection rule that doesn't match reality, and return codes Intune doesn't understand.2 min✓ read
- 02Intune Remediations: find and fix problems before users noticeRemediations pair a detection script with a fix script and run them on a schedule. It's one of the most useful and underused features in Intune.2 min✓ read
- 03Windows LAPS with Intune: unique local admin passwords in minutesIf every PC shares the same local administrator password, one compromised machine means all of them. Windows LAPS fixes that, and it's built into Windows and Intune.2 min✓ read
- 04Why Edge suddenly switched language on a whole officeUsers in one office reported Edge and LinkedIn appearing in another language. Nobody had touched Edge. The cause was an Intune app assignment.2 min✓ read
- 05Rolling out "require compliant device" without a flood of ticketsRequiring a compliant device is one of the strongest Conditional Access controls you can apply. It's also one of the easiest to get wrong. A step-by-step rollout.2 min✓ read
- 06Intune in September: deployment rings, faster compliance and stricter automationFive recent Intune changes that affect how you roll out, how quickly devices become compliant, and whether your automation keeps working.2 min✓ read
Progress is saved in this browser only. A post counts as read once you've scrolled most of the way through it.