jltware wrote:It is also their policy here to not allow anybody (stake president included) a key to access any internet equipment. I queried them on this as well, and was told that it was their desire that nobody in any unit should have any need to access this equipment, and to direct any enquiries about the running of this equipent to them (ie, nobody's getting a key, so don't bother asking). While I'm happy enough for them to not trust me personally with a key if they feel so inclined, I would hope the people entrusted with priesthood keys can also be trusted with physical keys, especially as it going to be our stake budget funding this endeavour.
Once authorized and approved, the only device the Church ships to you is one Cisco ASA firewall/router for each building receiving the Internet. There is no charge for these. They initially arrive without password protection and clear instructions on how to finalize the configuration based on your particular internet connection (DSL, Cable, static or dynamic IP, etc.) Once configured, CHQ can access it remotely to "script" it for the level of filtering desired by the Stake President, as described in the WIKI
. Once scripted, it is indeed "locked", to protect it from local tampering. The internal configuration is quite complicated, and once running, there is really nothing in there we as end-users need anyway.
The ASA firewall has 8 Ethernet ports available for the stake to do with as they wish. The stake will have to decide on a topology for each building's LAN, be it wired, wireless, or a combination of both. Once a topology is decided upon, any additional cables, patch panels, routers, switches, wireless access points, etc. will be the stake's financial responsibility. Rest assured, anything the stake purchases will be under complete control of the stake STS. He will set and maintain the passwords for configuring each device. For wireless access, he will set and maintain a wireless key for each building. The only device "locked" is the Cisco ASA box, and if the STS suspects a problem with it, it just takes a quick call to CHQ's 24/7 help desk and they can access it remotely to resolve any problems.
I can't help you with your timetable, as I am obviously not in the loop. I can only echo what mkmurray said. Because of the financial burden on the stake for each installation, ours could not start the project right away, even though they were given the green light. It took a while, but once funds were budgeted, it moved rather quickly.