<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nanomdm on MicroMDM</title><link>https://micromdm.io/tags/nanomdm/</link><description>Recent content in Nanomdm on MicroMDM</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Aug 2026 04:27:17 +0000</lastBuildDate><atom:link href="https://micromdm.io/tags/nanomdm/index.xml" rel="self" type="application/rss+xml"/><item><title>Organization-linked Activation Lock &amp; Bypass</title><link>https://micromdm.io/blog/organization-activation-lock/</link><pubDate>Wed, 19 Aug 2026 04:27:17 +0000</pubDate><guid>https://micromdm.io/blog/organization-activation-lock/</guid><description>&lt;p>To quote our friends over at Iru (formerly Kandji):&lt;/p>
&lt;blockquote>
&lt;p>Activation Lock is a theft-deterrent feature found in &lt;a href="https://support.apple.com/HT201365">iOS and iPadOS devices&lt;/a> and modern &lt;a href="https://support.apple.com/HT208987">Mac computers&lt;/a> (with the Apple T2 Security chip and Apple silicon).&lt;/p>
&lt;/blockquote>
&lt;p>NanoMDM and NanoDEP now have direct support for organization-linked Activation Lock, the flavor of Activation Lock that is &lt;em>not&lt;/em> tied to a user&amp;rsquo;s Apple Account (i.e. not &amp;ldquo;Find My&amp;rdquo;). NanoDEP (as of &lt;a href="https://github.com/micromdm/nanodep/releases/tag/v0.7.0">v0.7.0&lt;/a>) can &lt;strong>lock&lt;/strong> a device to your organization using the Apple DEP API, and NanoMDM (as of &lt;a href="https://github.com/micromdm/nanomdm/releases/tag/v0.9.0">v0.9.0&lt;/a>) can &lt;strong>unlock&lt;/strong> a device using Apple&amp;rsquo;s Escrow Key Unlock endpoint. Both sides revolve around the humble Activation Lock Bypass Code. Below we&amp;rsquo;ll walk through both, step by step.&lt;/p></description></item><item><title>MicroMDM v1 project maintenance mode</title><link>https://micromdm.io/blog/micromdm-v1-maintenance-mode/</link><pubDate>Fri, 20 Jun 2025 14:10:00 -0700</pubDate><guid>https://micromdm.io/blog/micromdm-v1-maintenance-mode/</guid><description>&lt;p>The MicroMDM project in its current form—what I refer to as MicroMDM “v1”—has effectively been in maintenance mode for years now. Development effort has been almost entirely focused on &lt;a href="https://github.com/micromdm/nanohub">NanoMDM&lt;/a> and the &lt;a href="https://github.com/micromdm?q=nano">“Nano”-suite of projects&lt;/a>. This post serves to merely confirm and formalize the current situation: MicroMDM “v1” is indeed in maintenance mode.&lt;/p></description></item><item><title>Introducing NanoMDM</title><link>https://micromdm.io/blog/introducing-nanomdm/</link><pubDate>Sun, 30 May 2021 11:45:00 -0700</pubDate><guid>https://micromdm.io/blog/introducing-nanomdm/</guid><description>&lt;p>I’d like to introduce &lt;a href="https://github.com/micromdm/nanomdm">NanoMDM&lt;/a>. From the project’s &lt;a href="https://github.com/micromdm/nanomdm/blob/main/README.md">README&lt;/a>:&lt;/p>
&lt;blockquote>
&lt;p>NanoMDM is a minimalist Apple MDM server heavily inspired by MicroMDM.&lt;/p>
&lt;/blockquote>
&lt;p>Which is a rather minimalist description itself. To expand a bit: NanoMDM is a fully functional (yet scope-limited) &amp;ldquo;core&amp;rdquo; Apple MDM protocol server written in Golang. &lt;em>Another&lt;/em> small open source MDM server, you ask? Yes! Doesn&amp;rsquo;t that also describe MicroMDM, too? Well, yes it does. So what gives? Why a new project?&lt;/p>
&lt;p>I hope to explain how this project came about, why I think it has a place here, and a little about how it differs from MicroMDM. I think this will give some insight into the goals and design of NanoMDM along the way as well. Finally, I hope to recruit your help with this new open source project.&lt;/p></description></item></channel></rss>