usually means not a lot of money which usually means the network will be in terrible shape.
If you don't have them already, push for managed switches capable of handling VLANs and ACLs. I've seen situations where the computer labs were on the same network as the faculty/staff computers and it got ugly fast. You'll need VLANs and ACLs so you can separate those networks and control the traffic between them.
I'd also develop a system by which you can re-image computer labs fairly quickly. You'll probably want to get a fresh image on them quite regularly.
There's more useful tips in my brain somewhere but those come to the forefront.
EDIT:
What sort of environment is it? I generally assume Windows based as they have most of the market share, but I know Mac shops can be common in the educational environment.
Other thoughts:
If you don't take a proactive approach to make sure that everything is working the way it should you'll be spending everyday running around putting out fires. It will likely look like a helpdesk position than a net admin position. The more you can make sure that the workstations are functioning the way they should, the happier people will be with your service and the more time you'll have to have to spend on learning and engaging in more interesting projects.
Also, you might want to keep tabs on some Technology in education journals from an educators standpoint. It will probably give you some insight in working with people... especially when it comes to convincing them to buy something.
You'll probably encounters lots of old hardware that the support contract has long expired. Many smaller schools receive old computers as donations from corporations so expect to be dealing with a lot of old hardware that could break down on you any minute.
Second Edit:
What would be a good skill to practice is to be able to translate a "business need" to network requirements. For example, you may hear in some meeting some non-technical person going on about an idea they had for something they could do... probably based on of some article they read or some product they saw.
A good skill to practice to to hear what they are saying and be able to silently translate that into technical requirements. This is helpful because often what they want to do requires certain infrastructure to be in place and this may not be in place. If you don't bring this to their attention (and the cost associated with getting the infrastructure where it needs to be) they will go ahead with it and expect you to make it work... and when you can't or it doesn't work as advertised. They will be upset with you.