<?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>Fsmo on The IT Hollow</title>
    <link>https://theithollow.com/tags/fsmo/</link>
    <description>Recent content in Fsmo on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Jul 2012 19:15:14 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/fsmo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Infrastructure Master with Global Catalogs Rundown</title>
      <link>https://theithollow.com/2012/07/16/infrastructure-master-with-global-catalogs-rundown/</link>
      <pubDate>Mon, 16 Jul 2012 19:15:14 +0000</pubDate>
      <guid>https://theithollow.com/2012/07/16/infrastructure-master-with-global-catalogs-rundown/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s a pretty common best practice to not install the Infrastructure Master (FSMO) Role on a Global Catalog Server.  This post should help to explain why that is, and the circumstances where you can get away with it.&lt;/p&gt;
&lt;h3 id=&#34;global-catalog-review&#34;&gt;Global Catalog Review&lt;/h3&gt;
&lt;p&gt;A Global Catalog contains a full set of attributes for the domain that it&amp;rsquo;s a member of and a subset of information for all domains in its forest.  So basically, what this means is that all of the little attributes that are stored on objects in Active Directory, in the GC&amp;rsquo;s domain, will be housed on Global Catalog servers.  The global Catalog will also have a replica of the objects from other domains in the forest, but only a smaller set of their attributes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
