Proto School Setup

This page will outline a proto-school which will emulate the features of a larger school district.


This is a hypothetical discussion. I take no responsibility if you do something stupid after reading this.

This school district will be centrally based, with an active board office who provide IT services for the district in general. Schools will be geographically spread and will not be supporting themselves with internet connections but will instead be provided with links back to the board office which will have a high speed connection.

Overview (networking)

Overview (email)

BoardOffice will host email for the school district on redundant disks.

We'd like to use Zimbra for the board office staff but will probably end up going with a postfix solution. We're going to run seperate email servers for the staff vs the students so there's some segregation. Staff are going to use Thunderbird in IMAP mode by default. Students will use Squirrelmail webmail by default. Staff email, excluding spam/junk mail folders, will be backed up.

Overview (web)

Overview (inventory)

Board office will have a central copy of all school data up to a week out for redundancy purposes.

Network topology

First 10 class C's will be for Board Office / internal use. will be for the Board Office LAN space. will be for OpenVPN IP's. Each subnet 10.57.x.0/24 will have a 10.57.10.x associated with it as a convention. The remaining 8 class C's are reserved for further use.

Elementary schools will run from 20-50

High schools will run from 120-150

Centralized management

We're going to use LDAP as a centralized directory of users and machines. We're going to run a single master system from the board office with replication out to each of the sites. We're going to run the Samba3 schema. Computer accounts will also have objectClass=ieee802Device added to their attributes and a macAddress tracked. Computer accounts will also have objectClass=ipHost added to their attributes and an ipHostNumber assigned.