Make sure you understand that you have a very, very, very wide range of users. I deal with non-tech graduate students all the time(the same age as the youngest teachers in the field) and they are not tech savvy. They can myspace and youtube, and maybe superpoke someone on facebook, but that's it. Don't expect the youngest teachers to be the most techy. You'll find good, older teachers near retirement that can give you a run for your money.
Be aware that most k-12 schools have almost no budget. They can get money for hardware/software purchases, but a *good* tech to handle some of the idiosyncrasies of F/OSS is out of their budgets. A 50 computer lab on a 4 year rotation(many schools would kill for computers that new) only costs around $15,000 a year. They'll come with an os installed and maybe a cheap educational copy of office. To hire someone, say 40k-50k a year + benefits, to put a different os on the desktops is a huge expense.
My suggestion would be to start small. Make the decision making process open and transparent. Ask schools to have a cost/benefit analysis of the software purchases. You'll see your biggest savings in server apps, not desktops.
See if you can get schools to have a traveling tech, consolidate servers, etc. This can be difficult. A lot depends on what state you are in. A midwestern state, with lots of small schools with low enrollments(30-50 in a graduating class) may be better served by server consolidation. On the other hand, if you are in a big city where the graduating class is bigger than the entire k-12 school I graduated from, you'll have a bigger budget and a better chance of getting an onsite tech.
Show them security. Student records are highly confidential. Show them how spending less on the server software can increase their security.
It really comes down to knowing your audience and what they want and expect.