<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Device Management on libcom.de</title>
		<link>https://www.libcom.de/en/tags/device-management/</link>
		<description>Recent content in Device Management on libcom.de</description>
		<generator>Hugo</generator>
		<language>en-GB</language>
		
		
		
		
			<lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.libcom.de/en/tags/device-management/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Device Management for the Linux Desktop: The Gap We Close Ourselves</title>
				<link>https://www.libcom.de/en/blog/device-management-for-the-linux-desktop/</link>
				<pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://www.libcom.de/en/blog/device-management-for-the-linux-desktop/</guid>
				<description>&lt;p&gt;Name a platform, and I&amp;rsquo;ll name its device management. Windows? Microsoft Intune — and before it, SCCM, now called MECM, which nobody pronounces with confidence. macOS? Jamf — so taken for granted that Mac admins couldn&amp;rsquo;t act otherwise if they tried. iPhones and iPads? MobileIron, MaaS360, Workspace ONE — a whole zoo of MDM suites, all speaking the same Apple protocol. ChromeOS? The Google Admin console, elegant to the point of dullness. Android? No trouble at all — every Knox fleet, every carrier plan ships with management baked in.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
