<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Intune on Phillip Büchler</title><link>https://922b9caf.blog-6cm.pages.dev/tags/intune/</link><description>Recent content in Intune on Phillip Büchler</description><generator>Hugo</generator><language>en</language><copyright>&amp;copy; 2022 &lt;a href="https://philipbuechler.ch/"&gt;Fime&lt;/a&gt;</copyright><lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://922b9caf.blog-6cm.pages.dev/tags/intune/index.xml" rel="self" type="application/rss+xml"/><item><title>Who Holds the Keys to Your Patching?</title><link>https://922b9caf.blog-6cm.pages.dev/posts/who-holds-the-keys-to-your-patching/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/who-holds-the-keys-to-your-patching/</guid><description>&lt;p&gt;On 21 October, details of two critical PHP flaws leaked to VirusTotal at 02:29 UTC. By 07:34, hosting providers were reporting active exploitation, and PHP released the fix at 13:52, &lt;a href="https://www.recordedfuture.com/blog/php2shell-vulnerability-exploitation"&gt;according to Recorded Future&lt;/a&gt;. Amazon later said the first exploitation attempts &lt;a href="https://www.bleepingcomputer.com/news/security/amazon-says-php2shell-exploitation-began-4-days-before-patches/"&gt;started on 17 October&lt;/a&gt;, four days before any patch existed.&lt;/p&gt;
&lt;p&gt;In &lt;a href="https://922b9caf.blog-6cm.pages.dev/posts/patch-less/"&gt;Patch Less&lt;/a&gt; I argued that the long tail of utilities on user devices should be patched automatically, with a third-party tool or Microsoft&amp;rsquo;s own catalogue. Timelines like this one are the reason. But that automation raises a question I keep coming back to: when you hand patching to a third-party tool, whose keys are you handing over?&lt;/p&gt;</description></item><item><title>Patch Less</title><link>https://922b9caf.blog-6cm.pages.dev/posts/patch-less/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/patch-less/</guid><description>&lt;h2 id="more-bugs-found-faster"&gt;More bugs, found faster&lt;/h2&gt;
&lt;p&gt;In 2025, &lt;a href="https://jerrygamblin.com/2026/01/01/2025-cve-data-review/"&gt;48,185 CVEs were published&lt;/a&gt;, about 21% more than in 2024. That&amp;rsquo;s roughly 130 a day, with a clear preference for Tuesdays. Not all of them are your problem. The biggest single source was a company that reports WordPress plugin bugs, and I&amp;rsquo;m fairly sure nobody runs WordPress on their CEO&amp;rsquo;s laptop.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;
&lt;p&gt;The direction matters more than the number, and AI is pushing it from both ends. Google&amp;rsquo;s Big Sleep agent &lt;a href="https://techcrunch.com/2025/08/04/google-says-its-ai-based-bug-hunter-found-20-security-vulnerabilities/"&gt;reported its first 20 vulnerabilities&lt;/a&gt; in August 2025, mostly in FFmpeg and ImageMagick. Those aren&amp;rsquo;t exotic projects. They sit inside a lot of desktop software your users run every day. On the other end, Mandiant&amp;rsquo;s &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/m-trends-2026"&gt;M-Trends 2026&lt;/a&gt; estimates the mean time to exploit at minus seven days. On average, exploitation now starts before the patch exists. And according to the &lt;a href="https://www.darkreading.com/threat-intelligence/verizon-dbir-enterprises-vulnerability-glut"&gt;Verizon 2026 DBIR&lt;/a&gt;, organisations took a median of 43 days to fix vulnerabilities, up from 32 the year before.&lt;/p&gt;</description></item><item><title>Newsletter Recommendations</title><link>https://922b9caf.blog-6cm.pages.dev/posts/newsletter-recommendations/</link><pubDate>Fri, 02 Dec 2022 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/newsletter-recommendations/</guid><description>&lt;p&gt;This week I subscribed to a newsletter. The author was hesitant to start one but was worried that his current distribution channel will not be there forever. Guess where he posts today?&lt;/p&gt;
&lt;p&gt;Anyway, newsletters had a renaissance for quite some time now. I subscribed and enjoyed a couple of them, related to my current line of work.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Intune Newsletter by Andrew Taylor&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Weekly collection of links around all sorts of Cloud based Endpoint Management topics.
&lt;a href="https://andrewstaylor.com/category/newsletter/"&gt;https://andrewstaylor.com/category/newsletter/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Running Microsoft iOS Applications on an M1 Mac</title><link>https://922b9caf.blog-6cm.pages.dev/posts/ios-applications-on-m1/</link><pubDate>Thu, 12 May 2022 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/ios-applications-on-m1/</guid><description>&lt;p&gt;With the introduction of the M1 processors for Apple Macs, there came the possibility to run iOS applications on your Mac. Would that allow users to use Microsofts Office applications on their Mac? And if so, would those apps respect App Protection policies that a company defines?&lt;/p&gt;
&lt;p&gt;The installation of iOS apps on Macs is straightforward. A good tutorial can be found on &lt;a href="https://readdle.com/blog/how-to-run-ios-apps-on-mac"&gt;the site of document tool creator Readdle&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Application developers can define if their applications should run on Mac, as there are some limitations, which might reflect badly on the users impression of an app. The Office applications, like Teams, Outlook, or OneDrive are not available with this method. Understandably, as Microsoft offers native Mac apps.
As with most things, there used to be simple workarounds, but as of now, Apple seems to have pulled the plug on the easy ones.&lt;/p&gt;</description></item><item><title>Was macht den modernen Client denn modern?</title><link>https://922b9caf.blog-6cm.pages.dev/posts/modern-client/</link><pubDate>Mon, 25 May 2020 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/modern-client/</guid><description>&lt;p&gt;Jede Veränderung in der Informatik&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; wird begleitet von neuen Begrifflichkeiten. Das Heer an Beratern und Produktherstellern muss ja Futter haben um auf Kundenfang zu geben. Ein sehr häufiger Begriff in meinem Alltag ist der &amp;ldquo;moderne Client&amp;rdquo;. Sei dies bezogen auf die Verwaltung von Endgeräten, Verteilung von Anwendungen oder die Kontrolle und Durchsetzung von Richtlinien - alles muss heute &lt;strong&gt;modern&lt;/strong&gt; sein. Doch was macht denn den Kübel auf dem Tisch plötzlich modern? Das ich darauf mit einem Stift kritzeln kann? Oder reicht es schon ohne LAN-Kabel mit dem Internet verbunden zu sein? Und wenn ich jetzt meine Geräteflotte mit MobileIron, Airwatch oder Intune verwalte, bin ich dann schon modern?&lt;/p&gt;</description></item><item><title>Windows 10 can't save pictures from the camera.</title><link>https://922b9caf.blog-6cm.pages.dev/posts/2019-09-24_camera-windows10-windowsinformationprotection/</link><pubDate>Tue, 24 Sep 2019 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/2019-09-24_camera-windows10-windowsinformationprotection/</guid><description>&lt;p&gt;That was the error that a user reported which eventually landed on my desk. In the project I am responsible for Intune Device Management and so the thinking was, that there must be a policy that blocks the Camera app.
There is not. But why this error then?&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://922b9caf.blog-6cm.pages.dev/img/wip-camera.png"&gt;&lt;figcaption&gt;
 &lt;h4&gt;Error Message with WIP&lt;/h4&gt;
 &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;Let me put the error here for Google to index:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Sorry — we weren’t able to save the photo.
If you nee it, here’s the error code:
0xA00F4253&lt;PhotoCaptureWriteFailed&gt; (0x80070005)&lt;/p&gt;</description></item><item><title>Office Custiomization Tool und eine Empfehlung zum Configuration Management</title><link>https://922b9caf.blog-6cm.pages.dev/posts/2019-04-15_office-custiomization-tool-und-eine-empfehlung-zum-configuration-management-efc4e6b9c9d3/</link><pubDate>Mon, 15 Apr 2019 00:00:00 +0000</pubDate><guid>https://922b9caf.blog-6cm.pages.dev/posts/2019-04-15_office-custiomization-tool-und-eine-empfehlung-zum-configuration-management-efc4e6b9c9d3/</guid><description>&lt;p&gt;Unternehmen haben beim Umstieg auf moderne Client Verwaltung oftmals Bedenken bei der Anpassung von Office. Klassischerweise werden viele Richtlinien im Office-Paket mitgegeben um es an die Anforderungen der Unternehmen anzupassen.&lt;/p&gt;
&lt;p&gt;Dabei gibt es in der modernen Client Verwaltung ein unbekannts Juwel — das “&lt;a href="https://config.office.com/"&gt;Office Customization Tool&lt;/a&gt;”. In der Weboberfläche werden die verschiedenen Konfiguration direkt vorgenommen. Diese Konfigurationen werden in einer XML-Datei gespeichert und können beim Setup so mitgegeben werden.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://cdn-images-1.medium.com/max/800/1*M9Q9zbj6hznBAyk_o9IoSA.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Schauen wir uns das doch mal näher an. Im Minimum, und dies bietet das Tool schon länger, besteht die Konfiguration aus den Produkten die Office installieren soll (bspw. Access integriert oder nicht, etc.). Dann wählt man die Architektur (32 oder 64bit) und in welcher Häufigkeit die Updates aus welcher Quelle installiert werden sollen.&lt;/p&gt;</description></item></channel></rss>