<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Softwareupdate on MicroMDM</title><link>https://micromdm.io/tags/softwareupdate/</link><description>Recent content in Softwareupdate on MicroMDM</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 17 Dec 2020 00:00:00 +0500</lastBuildDate><atom:link href="https://micromdm.io/tags/softwareupdate/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>