<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Managing BIOS with Intune on Jon's Notes</title><link>https://www.configjon.com/series/intune-bios/</link><description>Recent content in Managing BIOS with Intune on Jon's Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.configjon.com/series/intune-bios/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing BIOS Passwords and Settings with Intune</title><link>https://www.configjon.com/bios-management-with-intune/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/bios-management-with-intune/</guid><description>&lt;p&gt;My Dell, HP, and Lenovo BIOS password and settings scripts have primarily been built for use with traditional device management tools like Microsoft Configuration Manager. This post introduces a new set of scripts designed specifically for Intune. These scripts are designed around the &lt;strong&gt;Intune Remediations&lt;/strong&gt; feature. The goal is to manage BIOS passwords and settings continuously, with no module dependencies, and no plain-text passwords.&lt;/p&gt;
&lt;p&gt;The scripts can be downloaded from my GitHub. &lt;strong&gt;&lt;a href="https://github.com/ConfigJon/Firmware-Management"&gt;https://github.com/ConfigJon/Firmware-Management&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Setting up BIOS password certificates in Intune</title><link>https://www.configjon.com/intune-bios-password-certificates/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/intune-bios-password-certificates/</guid><description>&lt;p&gt;This is the first deep dive in the &lt;strong&gt;&lt;a href="https://www.configjon.com/series/intune-bios/"&gt;Managing BIOS with Intune&lt;/a&gt;&lt;/strong&gt; series. The goal here is to get from nothing to &lt;strong&gt;password material that is ready to deploy&lt;/strong&gt; as an Intune remediation. That means three things, in order:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A document-encryption certificate, with its private key delivered to devices.&lt;/li&gt;
&lt;li&gt;BIOS passwords encrypted to that certificate as CMS files.&lt;/li&gt;
&lt;li&gt;Those CMS files embedded into a remediation script.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The actual password and settings remediations are covered in the next two posts. This one is everything that has to be in place first.&lt;/p&gt;</description></item><item><title>BIOS password management with Intune Remediations</title><link>https://www.configjon.com/intune-bios-password-management/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/intune-bios-password-management/</guid><description>&lt;p&gt;This is the second deep dive in the &lt;strong&gt;&lt;a href="https://www.configjon.com/series/intune-bios/"&gt;Managing BIOS with Intune&lt;/a&gt;&lt;/strong&gt; series. The first post, &lt;strong&gt;&lt;a href="https://www.configjon.com/intune-bios-password-certificates/"&gt;Setting up BIOS password certificates in Intune&lt;/a&gt;&lt;/strong&gt;, got the certificate onto devices and embedded the CMS-encrypted passwords into a deployable remediation script. This post details the password script logic and how to deploy the password scripts via an Intune remediation.&lt;/p&gt;
&lt;p&gt;This post assumes you&amp;rsquo;ve completed the certificate post and have built a remediation script (with the payload embedded) plus its matching detection script.&lt;/p&gt;</description></item><item><title>BIOS settings management with Intune Remediations</title><link>https://www.configjon.com/intune-bios-settings-management/</link><pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/intune-bios-settings-management/</guid><description>&lt;p&gt;This is the third deep dive in the &lt;strong&gt;&lt;a href="https://www.configjon.com/series/intune-bios/"&gt;Managing BIOS with Intune&lt;/a&gt;&lt;/strong&gt; series. It applies the same detection-and-remediation model from the &lt;strong&gt;&lt;a href="https://www.configjon.com/intune-bios-password-management/"&gt;password management post&lt;/a&gt;&lt;/strong&gt; to BIOS &lt;em&gt;settings&lt;/em&gt;. The goal is to keep devices at a desired BIOS configuration, detecting drift, and reporting on it.&lt;/p&gt;
&lt;p&gt;The deployment mechanics (creating the remediation, running as SYSTEM in 64-bit, assigning to a device group) are identical to the password post, so this post focuses on what&amp;rsquo;s different about settings: defining the desired state, the per-setting marker model, and the dependency on password management (and how to opt out of it).&lt;/p&gt;</description></item><item><title>BIOS management with Intune: reference and troubleshooting</title><link>https://www.configjon.com/intune-bios-reference/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.configjon.com/intune-bios-reference/</guid><description>&lt;p&gt;This is the reference post for the &lt;strong&gt;&lt;a href="https://www.configjon.com/series/intune-bios/"&gt;Managing BIOS with Intune&lt;/a&gt;&lt;/strong&gt; series. It is not part of the setup walkthrough. If you are deploying the solution, follow the deep-dive posts in order; come here when you need to look up a status line, understand the registry markers, decode a &lt;code&gt;FailReason&lt;/code&gt;, or troubleshoot a device that isn&amp;rsquo;t behaving as expected.&lt;/p&gt;
&lt;h3 id="the-registry-markers"&gt;The registry markers&lt;/h3&gt;
&lt;p&gt;A recurring remediation has to remember what it has done between runs, because the BIOS can only report &lt;em&gt;whether&lt;/em&gt; a password is set, not &lt;em&gt;which version&lt;/em&gt;. The scripts bridge that gap with registry markers under &lt;code&gt;HKLM:\SOFTWARE\ConfigJonScripts\FirmwareManagement\&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>