Wireless distribution behind Church Managed Firewall

[russellhltn]

Wouldn't it be desirable to install system #2 according to the standards used by system #1?

But I think your post does contain the answer that Global Services Desk (GSD) is the source of standards in this situation.

[MarchantRR]

Wouldn't it be desirable to install system #2 according to the standards used by system #1?

Perhaps, but not always. The "LDS Access" configuration that I mentioned in scenario 1 has a consistent SSID and WPA pre-shared key. Stake's that deploy there own wireless network may want to be very restrictive with access ... and thefore may want to use a different SSID and security configuration. The policy does require industry standard security such as WPA or WPA2, but does not define the entire configuration.

A general priciple with the meetinghouse internet rollout is to empower the Stake Technolgoy Speciailist to install and support a local network under the direction of the Stake President, and with approval from the Facilities Manager.

[rickdez]

I would make the observation that MSR support would probably not want to, or be able to for that matter, support wireless installations which is why their first question to the end user would be; "Are you connected via modem, wireless, or direct connection to the internet?" If there is a local wireless, they would be referred to the STS to rule out connectivity as a source of the problem. This input certainly is very consistent with the written instructions I have seen and I truly appreciate the feedback. Thank you so much.

[rickdez]

Is this LDS Access a packaged hardware/software solution that is offered by the church? It has been referred to a couple of times in the discussion thread and I am not too familiar with it or its scope. Is it more of a protocol or an actual tangible combination of hardware and software that can be acquired for use in stakes with the CCN connection?

[Mikerowaved]

Is this LDS Access a packaged hardware/software solution that is offered by the church? It has been referred to a couple of times in the discussion thread and I am not too familiar with it or its scope. Is it more of a protocol or an actual tangible combination of hardware and software that can be acquired for use in stakes with the CCN connection?

I think that's a valid question and one that I have as well. For example, in our situation we could greatly benefit by the extra range of 802.11n devices (certified Draft 2.0, of course), but if the Church's "approved" equipment consists of 802.11g gear, then the hassle (and expense) of range extenders must be deployed.

OK, I realize I'm doing a lot of the planning that a contractor would be hired to do, but if sacred funds are to be utilized, I would just like to see the best bang for the buck installed.

[MarchantRR]

I would make the observation that MSR support would probably not want to, or be able to for that matter, support wireless installations ...

Exactly, it will be the role of the STS to provide workstation connectivity support (wired or wireless) ... MSR support and/or the Global Service Desk (GSD) should not be asked to support workstation connectivity issues. The concept of local support, is what makes this type of solution scalable to the individual meetinghouse level.

[MarchantRR]

Is this LDS Access a packaged hardware/software solution that is offered by the church?

No hardware/software package ... just a configuration update. "LDS Access" is just a few lines of configuration that creates a new SSID and WPA-PSK security settings that can be added to an existing Church Managed wireless network. In years past, church headquarters has cordinated the installation of wireless networks at some church facilities. The initially deployed configuration required the use of a 3rd party wirelss client (Odyssey client). The "LDS Access" configuration updates makes it possible to connect clerk computers to the existing wireless infrastructure without the 3rd party client.

[MarchantRR]

I think that's a valid question and one that I have as well. For example, in our situation we could greatly benefit by the extra range of 802.11n devices (certified Draft 2.0, of course), but if the Church's "approved" equipment consists of 802.11g gear, then the hassle (and expense) of range extenders must be deployed.

OK, I realize I'm doing a lot of the planning that a contractor would be hired to do, but if sacred funds are to be utilized, I would just like to see the best bang for the buck installed.

So you want to deploy a 802.11n network ... if the following is true you may get your wish ...

• You are a Stake Technology Specialist, or asked to help someone who is.
• The meetinghouse you want to deploy wireless in has an existing church deployed Internet connection (often referred to as a CCN connection). Remember, the notice from the Presiding Bishop allows clerk pc's to connect to existing connection ... but does not authorize the Stake to install new Internet connections.
• There is not an already deployed church managed wireless network in that meetinghouse.
• Your Stake President has authorized clerk pc's to connect to the Internet and has requested that the STS decide the best way to connect the pc's.
• You decide that 802.11n wireless is the way to go and the Facility Manager appproves the installation of the wireless equipment.
• Your have a way to locally fund the purchase, and installation of the equipment.
• The policy requires security (WPA or WPA2) but not specific hardware or wireless specifications.

This is basically scenario 2 that I mentioned in my original response to this thread.

[russellhltn]

Exactly, it will be the role of the STS to provide workstation connectivity support (wired or wireless) ... MSR support and/or the Global Service Desk (GSD) should not be asked to support workstation connectivity issues. The concept of local support, is what makes this type of solution scalable to the individual meetinghouse level.

While the flexibility given to the STS is nice, STS come and go. What happens when the system fails and the new STS can't figure out what the old one did? (You don't fool with what works - and if you don't fool with it, you don't learn it.) Documentation is likely to be non-existent.

I'd expect that he'd probably turn to GSD. What is their response going to be?

Or to put it another way, I want to follow Church standards. Simply to be nice to the next guy and whoever supports him.

[RutzJW]

Or to put it another way, I want to follow Church standards. Simply to be nice to the next guy and whoever supports him.

;)Thank you, thank you. As an FM, I am being deluged with STS requests for approval of wireless installations. I feel that should be a last resort option for the following reasons: 1) Cost - design of most meetinghouses require wall/attic access and installation of power injected cables and "approved" wireless access points, in order to acheive adequate signal - regardless of frequency. Stake Presidents (who now pay for the upgrades) will look for the least expensive option. 2) Security - the old adage applies "If its on the air it can be seen or heard". If we are already working in the walls/attics, cable pulls are best.