<div>
Resource domains haven't been recommended since NT4, more than a decade ago.
</div>


Resource domains haven't been recommended since NT4, more than a decade ago.

<div>
So isolating servers from user domains are no longer a concern?
</div>


So isolating servers from user domains are no longer a concern?

<div>
What are the concerns? &nbsp;I cannot think of any that aren't mitigated by security and defining management of OUs.
</div>


What are the concerns?  I cannot think of any that aren't mitigated by security and defining management of OUs.

<div>
Havent designed AD since 2000 - just wondering what the best practices are these days
</div>


Havent designed AD since 2000 - just wondering what the best practices are these days

<div>
<div class="content wysiwyg-content">
Are resource domains still a common practice and what are the benefits of keeping servers in a resource domain? I need some good documentation
</div>
</div>


Are resource domains still a common practice and what are the benefits of keeping servers in a resource domain? I need some good documentation

resource domains

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.