<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Dedicated root domain in active directory in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/dedicated-root-domain-in-active-directory/m-p/3197131#M435</link>
    <description>There are both pros and cons.&lt;BR /&gt;&lt;BR /&gt;Securitywise it will not make a big difference, except if you require different password policies etc which can only be set per domain.&lt;BR /&gt;&lt;BR /&gt;Central administration and "political" issues can find easier acceptance with a dedicated root domain.  Also it can be an advantage when companies expect to see strong growth or already are large.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://networking.earthweb.com/netsysm/article.php/10954_3084961_3" target="_blank"&gt;http://networking.earthweb.com/netsysm/article.php/10954_3084961_3&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Also it is beneficial in upgrade scenarios&lt;BR /&gt;&lt;A href="http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbf_upwn_xzjs.asp" target="_blank"&gt;http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbf_upwn_xzjs.asp&lt;/A&gt;&lt;BR /&gt;(and presumably even more beneficial if there comes tools for pruning and grafting AD domains/forests - but that is strictly a guess on my part)&lt;BR /&gt;&lt;BR /&gt;Weighted against this is the extra servers needed and the extra maintenance/administration that needs to be taken into account.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.winnetmag.com/Article/ArticleID/41271/41271.html" target="_blank"&gt;http://www.winnetmag.com/Article/ArticleID/41271/41271.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The main reason to go for the dedicated root domain in my opinion is related to the size of the company/organization.  Large size implies complexity and it is then good to have a relatively unchanging and simple root domain which all the subdomains can rely on.  The size will then also justify implementing highly fault tolerant installations in the dedicated root domain.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Rune</description>
    <pubDate>Wed, 24 Mar 2004 03:45:30 GMT</pubDate>
    <dc:creator>Rune J. Winje</dc:creator>
    <dc:date>2004-03-24T03:45:30Z</dc:date>
    <item>
      <title>Dedicated root domain in active directory</title>
      <link>https://community.hpe.com/t5/windows-server-2003/dedicated-root-domain-in-active-directory/m-p/3197130#M434</link>
      <description>Hi, Need some advice about active directory infrastructures. Is there anyone who has experience of Dedicated root domain in active directory. &lt;BR /&gt;</description>
      <pubDate>Thu, 19 Feb 2004 14:37:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/dedicated-root-domain-in-active-directory/m-p/3197130#M434</guid>
      <dc:creator>Frantic</dc:creator>
      <dc:date>2004-02-19T14:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: Dedicated root domain in active directory</title>
      <link>https://community.hpe.com/t5/windows-server-2003/dedicated-root-domain-in-active-directory/m-p/3197131#M435</link>
      <description>There are both pros and cons.&lt;BR /&gt;&lt;BR /&gt;Securitywise it will not make a big difference, except if you require different password policies etc which can only be set per domain.&lt;BR /&gt;&lt;BR /&gt;Central administration and "political" issues can find easier acceptance with a dedicated root domain.  Also it can be an advantage when companies expect to see strong growth or already are large.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://networking.earthweb.com/netsysm/article.php/10954_3084961_3" target="_blank"&gt;http://networking.earthweb.com/netsysm/article.php/10954_3084961_3&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Also it is beneficial in upgrade scenarios&lt;BR /&gt;&lt;A href="http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbf_upwn_xzjs.asp" target="_blank"&gt;http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dssbf_upwn_xzjs.asp&lt;/A&gt;&lt;BR /&gt;(and presumably even more beneficial if there comes tools for pruning and grafting AD domains/forests - but that is strictly a guess on my part)&lt;BR /&gt;&lt;BR /&gt;Weighted against this is the extra servers needed and the extra maintenance/administration that needs to be taken into account.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.winnetmag.com/Article/ArticleID/41271/41271.html" target="_blank"&gt;http://www.winnetmag.com/Article/ArticleID/41271/41271.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;The main reason to go for the dedicated root domain in my opinion is related to the size of the company/organization.  Large size implies complexity and it is then good to have a relatively unchanging and simple root domain which all the subdomains can rely on.  The size will then also justify implementing highly fault tolerant installations in the dedicated root domain.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Rune</description>
      <pubDate>Wed, 24 Mar 2004 03:45:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/dedicated-root-domain-in-active-directory/m-p/3197131#M435</guid>
      <dc:creator>Rune J. Winje</dc:creator>
      <dc:date>2004-03-24T03:45:30Z</dc:date>
    </item>
  </channel>
</rss>

