<?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>Group-Policy on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/group-policy/</link>
    <description>Recent content in Group-Policy on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 18 Feb 2021 07:30:40 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/group-policy/index.xml" rel="self" type="application/rss+xml" />
    <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>Block LSASS.exe using Attack Surface Reduction</title>
      <link>https://campbell.scot/block-lsass-exe-using-attack-surface-reduction/</link>
      <pubDate>Sat, 13 Feb 2021 21:10:23 +0000</pubDate>
      <guid>https://campbell.scot/block-lsass-exe-using-attack-surface-reduction/</guid>
      <description></description>
    </item>
    <item>
      <title>Register Domain-Joined Computers as Devices - The Redundant and Broken Hybrid Azure AD Join GPO</title>
      <link>https://campbell.scot/register-domain-joined-computers-as-devices-the-redundant-and-broken-hybrid-azure-ad-join-gpo/</link>
      <pubDate>Tue, 19 May 2020 19:11:46 +0000</pubDate>
      <guid>https://campbell.scot/register-domain-joined-computers-as-devices-the-redundant-and-broken-hybrid-azure-ad-join-gpo/</guid>
      <description>&lt;p&gt;The group policy object &lt;strong&gt;Register domain-joined computers as devices&lt;/strong&gt;, or &lt;strong&gt;Automatically workplace join client computers&lt;/strong&gt; in older templates, was previously a requirement for enabling Hybrid Azure AD Join.  After configuring Azure AD Connect and your Seamless SSO GPOs, this had to be enabled.&lt;/p&gt;
&lt;p&gt;Since Windows 10 1607 (&amp;ldquo;Anniversary Update&amp;rdquo;), in Azure AD Connect environments, on-premises Active Directory joined computers become Azure Active Directory registered when a synchronised user signs in to a synchronised computer; regardless of the GPO existing.  Prior to this, on Windows 10 1511 (&amp;ldquo;November Update&amp;rdquo;) and before, only if this GPO, or other configuration to create this registry value, was used.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
