Solved

Single domain or multiple domain for a school or university???

Posted on 2011-02-14
7
1,172 Views
Last Modified: 2015-06-14
We are a small southern college.  We are in the midst of an Active Directory design.  The question that has been posed to the design team is whether or not we should maintain a single Active Directory domain for all students, faculty and Staff, or should we maintain separate domains...namely, one for students (several thousand) and one for faculty and staff (about a thousand).

Our contention is that a single domain should be fine.  We'd really prefer this as an Exchange system is also being implemented and we'd prefer a single Exchange organization, rather than multiple.  Additionally, we believe students can easily be maintained in a separate OU, and adequate security measures and GPO's can be employed to maintain security.

Personally, it appears to me, that the practice of deploying a separate AD domain in such circumstances is less prevalent than it once was, mainly b/c the feeling is that both security and manageability can be satisfied by deploying a single directory.

I was hoping for feedback.  Especially anyone who is currently or has worked for a college who at one time or another had to do the same thing.  Are there any big minuses from our thoughts on this matter?  Any thing we should keep in mind?

Thank you.
0
Comment
Question by:patriots
7 Comments
 
LVL 17

Expert Comment

by:James Haywood
ID: 34891800
I would go with the single domain. The only possible reason you might want separate domains is for DR as if there is an issue with your AD and you have a single domain then the problem will affect pretty much everyone and every machine. Saying that, if you have plenty of redundancy and a decent IT team then you should be able to deal with these problems without much issue.

A good AD layout using thought-out OUs and GPOs will give you huge amounts of control and delegation options. If you have more than one site (like most colleges/Unis) then you can use the AD sites and services rather than child domains.

0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 34891810
You can go either way but if you are managing these three groups from one Admin or Tech suppory group  then I would recommend going with Single domain with multiple OUs this will allow for easier administration.

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22803733.html
0
 
LVL 5

Expert Comment

by:mickinoz2005
ID: 34891937
as the others say with the level of control you can have with OU's and GPO's it would not make sense to split them.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 7

Expert Comment

by:Chris Patterson
ID: 34892003
Having just finished an AD/Exchange migration and redesign for a large college (over 20,000 students plus faculty), we consolidated 3 AD domain and 2 Exchange organizations down to a single AD domain and single Exchange organization.  It just took good planning and organization before hand to lay out the project and complete it.  The administrative overhead from supporting multiple AD domains and Exchange organizations was killing the support staff.  After all was said and done, the simplicity of the "new" centralized infrastructure allowed technicians to start working normal hours and saved dollars spent on overtime and supporting too many disparate systems.
0
 
LVL 58

Accepted Solution

by:
tigermatt earned 250 total points
ID: 34892010

Multiple domains within a forest do not provide any security advantage, because the security boundary is the edge of the forest, not the edge of the domain.

Implementing multiple domains is something which is only recommended if you have a very large subset of users with specific requirements, or if you have thousands of users who work for lots of different companies which need a degree of separability, maybe in DNS namespaces or management boundaries for the various IT teams. In your deployment, a single domain is the best configuration you'll opt for. Everything is secured using GPO and separate OUs for each category of user. It's also less costly, because you could potentially have twice the redundancy on a single domain as you could on two domains (since the redundant hardware/software needed for two could all participate in one).

FWIW, my work is at a school environment with a 2500 user network, and we run a single domain. I wouldn't go for anything else, because the TCO in adding hardware, software, training and the interoperability of the two just cannot be justified. As I mentioned above, unless you have a real reason to split the domains off (which you are struggling to identify -- which is good) then sticking with a single domain is the best option you can go for.

-Matt
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 34894526
I agree a single domain has its benifits.

So, maybe we should be providing alternatives and a different form of security. Have you considered a single domain split via VLANS?

ADMIN VLAN, User VLAN, Wireless VLAN, STAFF VLAN, etc...

VLANS allow you to control what ports are accessible by other VLANS if configured right.

You can always count on students hacking into the system.
0
 

Expert Comment

by:garryshape
ID: 40829078
Can I ask what is more difficult about managing two different domains? Say 1 forest and multiple child-domains?
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question