<?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>Windows-10 on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/windows-10/</link>
    <description>Recent content in Windows-10 on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 29 Mar 2022 07:27:18 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/windows-10/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Updated March 2022: Ultimate Comparison of Defender for Endpoint Features by Operating System</title>
      <link>https://campbell.scot/march-22-defender-for-endpoint-feature-comparison/</link>
      <pubDate>Tue, 29 Mar 2022 07:27:18 +0000</pubDate>
      <guid>https://campbell.scot/march-22-defender-for-endpoint-feature-comparison/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s been about 5 months since I last updated my comparison of Defender for Endpoint features by OS.  This is a &amp;ldquo;matrix&amp;rdquo; of the &lt;em&gt;tons&lt;/em&gt; of features, services, and important components that make up Microsoft Defender for Endpoint.&lt;/p&gt;
&lt;p&gt;Three months later, it&amp;rsquo;s overdue an update.  So here it is :)  I&amp;rsquo;ve also decided to rename it to The Ultimate Comparison of MDE Features by OS&amp;hellip; because renaming&amp;rsquo;s what we do, right?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Updated October 2021: Availability of Defender for Endpoint Features by Operating System</title>
      <link>https://campbell.scot/october-2021-comparison-of-defender-for-endpoint-features/</link>
      <pubDate>Tue, 19 Oct 2021 20:36:54 +0000</pubDate>
      <guid>https://campbell.scot/october-2021-comparison-of-defender-for-endpoint-features/</guid>
      <description>&lt;p&gt;In July, I released v1 of The Big Comparison of Defender for Endpoint Features by Operating System (or, what I think is much catchier, TBCMDEFOS).  This was a &amp;ldquo;matrix&amp;rdquo; of the &lt;em&gt;tons&lt;/em&gt; of features, services, and important components that make up Microsoft Defender for Endpoint.&lt;/p&gt;
&lt;p&gt;Three months later, it&amp;rsquo;s overdue an update.  So here it is :)&lt;/p&gt;
&lt;p&gt;The headline news is that, in preview anyway, there&amp;rsquo;s a bunch of additions to Windows Server 2012 R2 and 2016 thanks to a new agent-based deployment (&amp;ldquo;unified solution&amp;rdquo;) that replaces the need for the Microsoft Monitoring Agent and System Centre Endpoint Protection.  You now get almost feature parity with Windows Server 2019&amp;rsquo;s security features: ASR rules, next-generation protection, block at first sight, etc.  For a guide on how to get up and running with it, &lt;a href=&#34;https://petri.com/how-to-install-defender-for-endpoint-server-2012-r2-2016&#34;&gt;check out my writeup on Petri&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Big Comparison of Defender for Endpoint Features by Operating System</title>
      <link>https://campbell.scot/the-big-comparison-of-defender-for-endpoint-features-by-operating-system/</link>
      <pubDate>Sun, 11 Jul 2021 09:59:10 +0000</pubDate>
      <guid>https://campbell.scot/the-big-comparison-of-defender-for-endpoint-features-by-operating-system/</guid>
      <description>&lt;p&gt;Microsoft Defender for Endpoint (MDE) is a massive platform.  It&amp;rsquo;s not a single product, and it&amp;rsquo;s more than just a service.  It&amp;rsquo;s a platform of &lt;em&gt;tons&lt;/em&gt; of security features, portals, services, and controls.  The more you dig in, the more elements of general Microsoft security have been included in the MDE &amp;ldquo;branding&amp;rdquo;.  It&amp;rsquo;s not only endpoint detection and response (EDR), but also Windows 10 security settings.  It&amp;rsquo;s not just the security software on the device, it&amp;rsquo;s also ongoing threat and vulnerability management.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troubleshooting Hybrid Azure AD Intune Automatic Enrollment</title>
      <link>https://campbell.scot/troubleshooting-hybrid-azure-ad-intune-automatic-enrollment/</link>
      <pubDate>Mon, 19 Apr 2021 20:02:44 +0000</pubDate>
      <guid>https://campbell.scot/troubleshooting-hybrid-azure-ad-intune-automatic-enrollment/</guid>
      <description>&lt;p&gt;As I have blogged about &lt;a href=&#34;https://campbell.scot/hybrid-azure-ad-join-intune-enrollment-prerequisites-checklist-and-process-flow/&#34;&gt;a&lt;/a&gt;&lt;a href=&#34;https://petri.com/how-to-automatically-hybrid-azure-ad-join-and-intune-enroll-pcs&#34;&gt;lot&lt;/a&gt;, there are a bunch of hoops to be jumped through and prerequisites to be met for a successful hybrid Azure AD join and automatic, GPO-invoked Intune enrollment. But sometimes, you have to go back to the basics when you&amp;rsquo;re banging your head off the table, and laugh off the embarrassment of not checking the fundamentals.&lt;/p&gt;
&lt;p&gt;I was recently setting up hybrid Azure AD join and Intune enrollment, as I&amp;rsquo;ve done hundreds of times before, but this time I was hitting a strange problem.  Hybrid Azure AD join went fine, but for the Intune MDM enrollment, I was getting nowhere.  Devices showed in the Azure AD admin centre, but never showed an MDM, and therefore never showed in Endpoint Manager.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Update BitLocker Unique Identifiers with Intune</title>
      <link>https://campbell.scot/update-bitlocker-unique-identifiers-with-intune/</link>
      <pubDate>Mon, 22 Mar 2021 18:01:18 +0000</pubDate>
      <guid>https://campbell.scot/update-bitlocker-unique-identifiers-with-intune/</guid>
      <description>&lt;p&gt;BitLocker unique identifiers are values used to identify the ownership of an encrypted volume.  The device that performs the encryption holds the unique identifier and as encryption begins, it also records this against the metadata of that encrypted volume.&lt;/p&gt;
&lt;p&gt;The identifiers are typically used in tandem with the BitLocker removable data-drive setting &lt;strong&gt;write access to devices configured in another organisation&lt;/strong&gt; which, if set to &lt;strong&gt;block&lt;/strong&gt;, will prevent write operations on devices where the unique identifier of the removable drive doesn&amp;rsquo;t match a list of unique identifiers managed on the device.  The idea here is you want to enforce BitLocker on removable drives to improve data loss (encrypted drives, if found, are unreadable without the means to decrypt them), &lt;em&gt;but&lt;/em&gt; you only want them to be encrypted within your organisation: someone can&amp;rsquo;t encrypt their device elsewhere and then copy data to it.  You may want to do this because it means you, as an administrator, would not be able to decrypt it if required.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender Network Protection - Not Enabling via Intune - Troubleshooting &amp; Fix</title>
      <link>https://campbell.scot/microsoft-defender-network-protection-not-enabling-via-intune-troubleshooting-fix/</link>
      <pubDate>Sun, 07 Mar 2021 13:27:29 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-network-protection-not-enabling-via-intune-troubleshooting-fix/</guid>
      <description>&lt;p&gt;When configuring Defender for Endpoint (MDE) customer recently, I ran into a problem when trying to enable network protection.  Network protection is a feature of MDE and Microsoft Defender Antivirus (MDAV) that takes the filtering capabilities of SmartScreen and applies them to all network traffic.  It is a prerequisite for things such as MDE&amp;rsquo;s web content filtering and URL/domain indicators of compromise.&lt;/p&gt;
&lt;p&gt;This blog details the specific problem I had enabling it with Intune (Microsoft Endpoint Manager), and general troubleshooting steps to follow that will help for that problem and hopefully others you may experience.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender for Endpoint - Offline Onboarding for Windows 10 via a Proxy</title>
      <link>https://campbell.scot/microsoft-defender-for-endpoint-offline-onboarding-for-windows-10-via-proxy/</link>
      <pubDate>Thu, 18 Feb 2021 07:30:40 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-for-endpoint-offline-onboarding-for-windows-10-via-proxy/</guid>
      <description>&lt;p&gt;Getting your devices into Defender for Endpoint is referred to as &lt;strong&gt;onboarding&lt;/strong&gt; and can be done in lots of different ways, depending on the scenario.  The tools you use for Windows Server 2008 R2, for example, are different from the tools you use for Windows Server 2019, which are different from the tools you use for Windows 10, and so on.&lt;/p&gt;
&lt;p&gt;The common denominator behind most onboarding methods is internet connectivity.  Your device connects directly to the cloud service and provides all that telemetry goodness via a direct line of sight.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Turn Existing Azure AD Devices into Windows Autopilot Devices</title>
      <link>https://campbell.scot/turn-existing-azure-ad-devices-into-autopilot-devices/</link>
      <pubDate>Sat, 06 Feb 2021 09:19:13 +0000</pubDate>
      <guid>https://campbell.scot/turn-existing-azure-ad-devices-into-autopilot-devices/</guid>
      <description>&lt;p&gt;To provision Windows 10 PCs using Autopilot and Intune, they must first be registered as &lt;strong&gt;Windows Autopilot devices&lt;/strong&gt; in the &lt;strong&gt;Device Directory Service&lt;/strong&gt;, which is really the cloud Autopilot service.  When a device is registered to the Autopilot service, its &lt;strong&gt;hardware hash&lt;/strong&gt; is used to generate a &lt;strong&gt;Zero Touch Device ID&lt;/strong&gt;(ZTDID) - a globally unique identifier for that device based on hardware information such as (but not only) MAC address, disk serial number, and system serial number.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Protecting Sensitive Information in Windows 10 with Microsoft Endpoint Data Loss Prevention (DLP)</title>
      <link>https://campbell.scot/protecting-sensitive-information-in-windows-with-microsoft-endpoint-data-loss-prevention-dlp/</link>
      <pubDate>Sun, 23 Aug 2020 17:30:21 +0000</pubDate>
      <guid>https://campbell.scot/protecting-sensitive-information-in-windows-with-microsoft-endpoint-data-loss-prevention-dlp/</guid>
      <description>&lt;p&gt;After being released to Public Preview last month (July 2020), I have finally had a chance to test out Microsoft Endpoint DLP.  The management of endpoint DLP - that is, preventing sensitive information from leaving the host computer - comes up frequently in my discussions with companies I help with security and compliance.  Often, they have third-party tools doing it and are looking to centralise under Microsoft&amp;rsquo;s stack.&lt;/p&gt;
&lt;p&gt;In this blog, I&amp;rsquo;ll give an overview of:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
