<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Co-Exist - Tag - byteben</title><link>https://byteben.com/tags/co-exist/</link><description>Co-Exist - Tag - byteben</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ben@byteben.com (Ben Whitmore)</managingEditor><webMaster>ben@byteben.com (Ben Whitmore)</webMaster><lastBuildDate>Thu, 29 Aug 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://byteben.com/tags/co-exist/" rel="self" type="application/rss+xml"/><item><title>Co-management Series "Merging the Perimeter" - Part 1: What is Co-management?</title><link>https://byteben.com/bb/co-management-series-merging-the-perimeter-part-1-what-is-co-management/</link><pubDate>Thu, 29 Aug 2019 00:00:00 +0000</pubDate><author>ben@byteben.com (Ben Whitmore)</author><guid>https://byteben.com/bb/co-management-series-merging-the-perimeter-part-1-what-is-co-management/</guid><description><![CDATA[<p>In the following series we will take a deep dive into Co-management. Co-management is a technology that harmonizes workloads between the the Intune and SCCM agent. It is a unique relationship that only Intune and SCCM can be part of. Other MDM vendors can only &ldquo;co-exist&rdquo; with SCCM - infact when the SCCM agent sees another MDM vendor managing a device, all (well nearly all) SCCM workloads are disabled, resulting in the SCCM agent performing basic inventory task - what a wasted investment.</p>]]></description></item></channel></rss>