Here's an idea. This is probably too much for a single change but you could develop it into a tool that could save you a lot of time in the long run.
1) Build a "template" configuration for your switches. This would include things like the switches' hostname, management IP address, SNMP community string etc. All the unique characteristics for that switch (e.g. IP address) would be a variable.
2) Make what ever change you need to make to the template (e.g. setting console timeout).
3) Run a script to "fill in" the variables and build a unique config for that switch.
4) TFTP the new config to the switch as startup and reboot the switch.
As I said, this would be something you would need to spend a bit of time setting up and designing but it would be scalable and save you time in the long run.
Another tool you should checkout is Rancid. It is a script that automatically downloads the configs from the switches on your network. It is very useful for disaster recovery if a switch dies and you need to get a replacement up and running ASAP.