What is your Active Directory structure? – Help us improve

[Lesley Ford]

To help us improve our classroom management software, Netop is researching how schools use Microsoft’s Active Directory and how they organise their users within the Active Directory tree structure.

Any information and insight into the following would be very useful:-

• If the school, or district, uses unique student login names, what format do these names take?
• Are student login names grouped within the Active Directory in a hierarchical structure?
• Are students grouped by school year, class, from, classroom or in some other way?
• Are teachers grouped in the same hierarchical structure, or grouped separately?
• How does this structure change year after year, if at all?
• Is there any link between teachers and student groups within the Active Directory?
• Do students have a specific attribute which is used to denote the user as a student within the Active Directory?
• Do teachers have a specific attribute which is used to denote the user as a teacher within the Active Directory?
• Would the school be prepared to provide a screen shot of the Active Directory tree structure for research by Netop?

Please post a reply or email me directly.
Thank you in anticipation,

Lesley Ford | Global Product Manager for Education| Netop
lefo@netop.com Skype: Lesley.Ford.Netop

[CCTI]

Here is how it is in our college:

Root
- Computer OU
- - Classrooms
- - - AAAA (classroom door number, like for us we got A1214, which is A block, 1rst floor)
- - - BBBB
- - - ....
- - Departments
- - - Math
- - - Physique
- - - ...
- - Services
- - - Humain Ressources
- - - IT
- - - ...
- Users
- - Student (Each following OU are program number)
- - - 0.A
- - - ...
- - Teachers
- - - Disciplines A
- - - ...
- - Staff
- - - HR
- - - IT
- - - ...


All student have expiration date, are in group student. All teachers are in group teacher and in a group specific to there discipline. All staff are in group staff with a group specific to there title (HR, IT...).

This is the basis, it goes way more then that but it's a start.

You can also use a field in the user properties to defined title and role (student, employee, etc...)

[Dorte Jacobsen]

Hi CCTI,

Thank you for taking the time to explain, we apprecite it :-)

[zelifcam]

Here is how it is in our college:

Root
- Computer OU
- - Classrooms
- - - AAAA (classroom door number, like for us we got A1214, which is A block, 1rst floor)
- - - BBBB
- - - ....
- - Departments
- - - Math
- - - Physique
- - - ...
- - Services
- - - Humain Ressources
- - - IT
- - - ...
- Users
- - Student (Each following OU are program number)
- - - 0.A
- - - ...
- - Teachers
- - - Disciplines A
- - - ...
- - Staff
- - - HR
- - - IT
- - - ...


All student have expiration date, are in group student. All teachers are in group teacher and in a group specific to there discipline. All staff are in group staff with a group specific to there title (HR, IT...).

This is the basis, it goes way more then that but it's a start.

You can also use a field in the user properties to defined title and role (student, employee, etc...)

How do you protect the users from each other, as far as seeing AD attributes, like mobile numbers, etc.?
Or do you not store any of that information in AD as a best practice?