<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mdm on MicroMDM</title><link>https://micromdm.io/tags/mdm/</link><description>Recent content in Mdm on MicroMDM</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 10 Jun 2021 12:00:00 -0700</lastBuildDate><atom:link href="https://micromdm.io/tags/mdm/index.xml" rel="self" type="application/rss+xml"/><item><title>Tinkering with Declarative Management</title><link>https://micromdm.io/blog/wwdc21-declarative-management/</link><pubDate>Thu, 10 Jun 2021 12:00:00 -0700</pubDate><guid>https://micromdm.io/blog/wwdc21-declarative-management/</guid><description>&lt;p>Amongst the many announcements at Apple&amp;rsquo;s WWDC21 was &lt;a href="https://developer.apple.com/news/?id=y3h32xgt">declarative management&lt;/a>. I would highly recommend &lt;a href="https://developer.apple.com/videos/play/wwdc2021/10131/">watching the WWDC session &amp;ldquo;Meet declarative device management&amp;rdquo;&lt;/a> to get a a general idea of what it is and how it works.&lt;/p>
&lt;p>I wanted to tinker with the new capabilities and created some initial support for it and wanted to share how you can try this out, too. My hope is that, if you&amp;rsquo;re inclined, you can get these tools and start playing with it.&lt;/p>
&lt;p>Note this is a mostly technical how-to to get up and running and testing Declarative Management with NanoMDM. I hope to write more about the conceptual/paragidm changes DM brings as well more broad thinking in how to implement this protocol in a server. See the bottom for links to further discussion. Also note this is all really early stuff, based on beta software and documentation priovided by Apple and of course is all subject to major breaking changes.&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><item><title>About Software Updates in Big Sur</title><link>https://micromdm.io/blog/big-sur-softwareupdate/</link><pubDate>Thu, 17 Dec 2020 00:00:00 +0500</pubDate><guid>https://micromdm.io/blog/big-sur-softwareupdate/</guid><description>If you work with Apple in some capacity, you know that they&amp;rsquo;re not very likely to admit mistakes. I&amp;rsquo;m not aware of Apple publishing postmortems after outages or providing details about known issues. So it&amp;rsquo;s up to the developer and admin communities at large to help each other learn about outages and potential causes. With the release of macOS 11.1 this week I&amp;rsquo;ve been debugging a new issue with the Mac software update process, one which will affect most enterprise users.</description></item><item><title>WWDC20: What's new in managing Apple devices</title><link>https://micromdm.io/blog/wwdc20-what-s-new-in-managing/</link><pubDate>Tue, 30 Jun 2020 00:00:00 +0500</pubDate><guid>https://micromdm.io/blog/wwdc20-what-s-new-in-managing/</guid><description>Here are some of my opinions about Mobile Device Management (MDM) related changes announced last week. SimpleMDM did a great job of summarizing the announcements, so I won&amp;rsquo;t repeat the same list here. Instead, I&amp;rsquo;ll focus on a few things which are interesting to me. Before I get into that, I have to mention this isn&amp;rsquo;t a well-balanced editorial. It&amp;rsquo;s in my nature to skip over accomplishments and focus on things that still need attention.</description></item><item><title>Five years behind, Five years ahead</title><link>https://micromdm.io/blog/wwdc20-v2/</link><pubDate>Mon, 22 Jun 2020 00:00:00 +0500</pubDate><guid>https://micromdm.io/blog/wwdc20-v2/</guid><description>Apple MDM is over 10 years old today. Initially, MDM was a protocol to manage iPhones, but later expanded to the growing range of Apple devices. MicroMDM started about five years ago, when a few of us in the MacAdmin community became curious about what the MDM could do. We were intrigued by the &amp;ldquo;zero touch&amp;rdquo; deployment, which was brand new at the time. Lots of things were different. Almost nobody was using MDM and Apple Business Manager for the Mac.</description></item><item><title>Updating to Mojave?</title><link>https://micromdm.io/blog/os_update/</link><pubDate>Tue, 16 Oct 2018 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/os_update/</guid><description>Earlier this year Apple updated the MDM Protocol Reference document to add a previously undocumented key to the AvailableOSUpdates command.
Key Content IsMajorOSUpdate Set to true if this is a major OS update (e.g. 10.13.x to 10.14). macOS only. This got a few of us in the #mdmdev channel on MacAdmins Slack talking. We&amp;rsquo;ve tried scheduling OS Updates in the past, and MicroMDM has had support for all these commands for years.</description></item><item><title>Surviving the Kextpocalyse, Round 0</title><link>https://micromdm.io/blog/kext-whitelist/</link><pubDate>Mon, 13 Nov 2017 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/kext-whitelist/</guid><description>There&amp;rsquo;s an understandable sense of urgency in the MacAdmin community around MDM and Kernel extensions these days. If you&amp;rsquo;ve been paying attention you know that in order to be able to reliably deploy kernel extensions in an enterprise environment, DEP and MDM are becoming a requirement. Apple is likely not going to stop there, and both MDM and DEP will become a requirement for Mac management over the next year or two.</description></item><item><title>How to troubleshoot your DEP/MDM Enrollments</title><link>https://micromdm.io/blog/troubleshoot-dep/</link><pubDate>Mon, 06 Nov 2017 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/troubleshoot-dep/</guid><description>The Device Enrollment Program(DEP) allows enterprises to configure their Macs to auto-enroll into a Mobile Device Management(MDM) server of their choice. DEP makes it possible to ensure that a new Mac becomes managed during the unboxing process, reducing the need for Netboot and complex imaging workflows. Of course, as any workflow that depends on the network, this enrollment process can fail, and it&amp;rsquo;s important for an administrator to know how to troubleshoot it.</description></item><item><title>Understanding MDM Certificates</title><link>https://micromdm.io/blog/certificates/</link><pubDate>Thu, 11 May 2017 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/certificates/</guid><description>&lt;p>Apple Mobile Device Management (MDM) requires the use of various digital certificates for its operation. But exactly which certificates and the various ways in which they are generated, acquired, signed, used, exported, imported, and managed within an MDM product may not be so clear. Generally speaking a commercial MDM product or service manages most of the complexity related to these certificates for you but in the case of an open source MDM much of that responsibility will land on you. In this post I hope to bring a better understanding of these certificates with the aim that you&amp;rsquo;ll be managing at least a few of them yourself.&lt;/p></description></item><item><title>The business side of MDM - Do you know your DUNS Number?</title><link>https://micromdm.io/blog/accounts/</link><pubDate>Sat, 06 May 2017 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/accounts/</guid><description>&lt;p>Getting started with MDM is hard enough, but the toughest part is not technical, it&amp;rsquo;s getting approval to create all the accounts with Apple in order to begin. I recently went through the whole process for my company and thought it would be useful to others if I blogged about it. Below is infromation about what accounts you might need, and how you might go about acquiring them.&lt;/p></description></item><item><title>What's next for MicroMDM</title><link>https://micromdm.io/blog/welcome/</link><pubDate>Mon, 24 Aug 2015 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/welcome/</guid><description>&lt;p>I first &lt;a href="https://groob.io/posts/mdm-experiments/">wrote&lt;/a> about experimenting with MDM at the end of 2015. Since then, Apple has made the MDM specification &lt;a href="https://developer.apple.com/library/content/documentation/Miscellaneous/Reference/MobileDeviceManagementProtocolRef/3-MDM_Protocol/MDM_Protocol.html">public&lt;/a>, many administrators are looking to swap imaging devices for a DEP workflow, and even commercial vendors &lt;a href="https://simplemdm.com/2017/03/07/deploy-munki-apple-dep-mdm/">are taking notice&lt;/a> of the &lt;a href="http://blog.eriknicolasgomez.com/2017/03/08/Custom-DEP-Part-1-An-Introduction/">needs&lt;/a> of our community. One thing has become increasingly clear — MDM will play a critical role in the future of managing Apple devices in the enterprise. And with the renewed interest in MDM from the macadmin community, it&amp;rsquo;s only fair to be asked — What is the future of the MicroMDM project?&lt;/p></description></item></channel></rss>