<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Configuration-Manager on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/configuration-manager/</link>
    <description>Recent content in Configuration-Manager on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 28 Jun 2020 16:37:29 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/configuration-manager/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microsoft Defender for Endpoint Web Content Filtering - Administration, Limitations, and User Experience</title>
      <link>https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/</link>
      <pubDate>Sun, 28 Jun 2020 16:37:29 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/</guid>
      <description>&lt;p&gt;Historically, one of the big features missing &amp;ldquo;out of the box&amp;rdquo; with MDATP was web content filtering.  Customers typically look at MDATP as an option when their existing endpoint security is due for license renewal, and compare their existing solution against it.  They would be moving from one of the big security vendors such as Sophos, Norton, and McAfee, which all supported web content filtering.  Higher lever stakeholders often listed the ability to block websites as essential, and as Microsoft did not maintain such a categorisation database, if you wanted it with Defender ATP, you&amp;rsquo;d be looking at other solutions too.  This took away from Defender ATP&amp;rsquo;s &amp;ldquo;single pane of glass&amp;rdquo; selling point.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploy Microsoft Store Apps using Intune with Configuration Manager (SCCM) Co-Management (Fix &#39;Not Applicable&#39; Status)</title>
      <link>https://campbell.scot/deploy-microsoft-store-apps-using-intune-with-sccm-co-management-fix-not-applicable-status/</link>
      <pubDate>Fri, 10 Jan 2020 21:00:30 +0000</pubDate>
      <guid>https://campbell.scot/deploy-microsoft-store-apps-using-intune-with-sccm-co-management-fix-not-applicable-status/</guid>
      <description>&lt;p&gt;Intune provides an interface to easily deploy apps from the Microsoft Store to your registered users and devices, but even if you have SCCM (Config Manager) Co-Mangement enabled with the default workloads shifted to Intune in Co-Management properties, there is more to be done.  If you don&amp;rsquo;t follow these steps, you will receive the status of &lt;strong&gt;Not applicable&lt;/strong&gt; in the Intune client apps user and device install status pages.&lt;/p&gt;
&lt;p&gt;&lt;img alt=&#34;00.-Not-Applicable-in-Intune&#34; loading=&#34;lazy&#34; src=&#34;//wp-content/uploads/2020/05/00.-not-applicable-in-intune.png&#34;&gt;&lt;strong&gt;Prerequisite:&lt;/strong&gt; This only works with SCCM 1806+.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
