<?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>Gpo on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/gpo/</link>
    <description>Recent content in Gpo on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Tue, 19 May 2020 19:11:46 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/gpo/index.xml" rel="self" type="application/rss+xml" />
    <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>
