Optimize the network *before* you fully map and document it?
A more sure plan to failure I have yet to witness.
First, document the *entire* network. It's a pain in the ass, but it'll pay for itself in less heartburn medication.
Second, learn the word proxy. It'll save you a lot of bandwidth.
So, it'd go:
User – WiFi router – Satellite modem – Satellite – ground station – proxy - Internet
Of course, you can content filter with a proxy, either by crude blacklisting or via something like Websense.
I've been at places where I had 2000 users hanging off of a one meg pipe. I've been at places where 6000 users hung off of a 6 meg pipe. In both instances, our proxy was aged and failed (HD failure dropped it), I stuck a squid proxy on a spare server running Linux. Watched a struggling network become operational, if slow on internet things.
I set squid for relatively primitive filtering and set to work rebuilding the array on the *real* proxy.
I won't even go into the bastardized mess I set up when higher command fucked up and didn't renew our Websense license, which left us in an unlawful position of unfiltered internet.
I'll just suggest that those senior officers did not enjoy my, erm, candor.
The license was swiftly renewed.
But, the *only* path to improvement is complete documentation, down to every endpoint.
I don't envy you the task, as having done so a few times, but if I were in the same nation, I'd give a hand. Heh, those roads aren't so challenging to someone who spent nearly three decades in military service. We'd have to go to Antarctica or the northern ice cap to find conditions I've not operated under.