Active Directoy Design Advice Needed for a School
Posted on 2014-04-25
I am the IT Manager at a school and need some advice on how to re-design/optimize the network and active directory structure.
In the past before VLANs were common, it was a requirement to seperate the Staff and Student domains for security purposes. This resulted in 2 physically seperated lans as well as Active Directory Domains. While this setup gives additional security, it is an outdated concept and generates a lot of administrative overhead.
I would like to merge the Staff and Student Active Directories into a single AD forest. However, I need to prevent that the students will be able to access specific servers as well as any staff workstations. We have Layer 3 VLAN capable switching equipment, so I suppose the best solution is to create seperate VLANs and restrict access between the VLANS. For example:
VLAN 100 = Servers used by Staff and Students
VLAN 200 = Servers only for Staff
VLAN 300 = Staff Workstations
VLAN 400 = Student Workstations
I would then prohibit VLAN 400 to access any resources in VLAN 200 and 300. Would this be the best practice?
For the students we're also using Google Apps and sync the passwords from our Student Domain controller. However, internal security regulations prohibit us from installing Google Apps Password Syncs on any Domain Controller which is used for staff activities.
My question: is there a common way to prevent a certain user group (e.g students in our case) to contact a certain Domain Controller?
Thank you for your appreciated advice & opinions!