First, a facility that the church has previously installed broadband Internet to support an official Family HIstory Center, Facilities Management Office, Employment Resouce Center, etc. As other's have indicated, this installation was initiated and cordinated by the church through the facilities manager. In all cases, a church managed firewall was installed, and frequently a wireless network was also installed (Cisco AP's).
- Clerk PC's are now authorized to share previously installed CCN connections.
- You can share the wireless network by contact GSD and requesting that they add the "LDS Access" profile to the existing Cisco Access Points. This will allow you to use any wireless client and connect with a WPA pre-shared key (provided by GSD).
- You can of course connect via hard-wire or other options as well.
- There is no need for the Odyssey client after the "LDS Access" profile is added to the existing access points.
Last night I discussed this with my stake president and he authorized me to request the LDS Access profile for our Stake Center, which has an existing CCN, with WAPs installed under the direction of the FM Group. The stake president also set policy for who would have access to the WPA key.
So last night after presidency meeting I called the GSD, thinking this would be a quick call for service under policy. The first-level support person had no clue what LDS Access was, or even that the GSD had the ability to push profiles to WAPs. But at least he figured out quickly that he didn't know, and forwarded me to a second-level support person.
The second-level person certainly knew about the technical side, but he had a different view of the policy. He said that the GSD doesn't usually push the LDS Access profile to existing CCNs because of security concerns. He asked me why we wanted the access. I explained that my stake president had determined that it would be helpful for clerks to have access to LUWS, Missionary Recommendation System, lds.org, and other sites that would help clerks fulfill their callings to support the leadership.
He still seemed reluctant to grant access. I explained that I certainly did not want to request something our stake should not have, but that through my participation in the LDS Tech Forum I had heard from a couple of Church employees that this was an appropriate request. He seemed skeptical of that source (my apologies to tsheffield and rmarchant
). But he did eventually say he would grant access, although it was more along the lines of "Well, I guess I'll make an exception just this once and give you access, since you asked so nicely," rather than "I'm happy to grant your appropriate request under Church policy."
So there seems to be some disconnect between the statements posted on this forum and what at least one person at the GSD thinks is policy. It would be nice to resolve that conflict.
I also was so distracted by the way the conversation went that I neglected to specify whether we wanted LDS Restricted Access or LDS Extended Access. I haven't been back to the stake center to try it out or to see which option we have. I would have thought that he would ask, but he didn't. It will be interesting to see what we got....
tsheffield wrote:When I referred to the asking GSD to push out the new LDS Access profile I was talking about locations that have the church installed wireless Cisco AP’s. Sorry for not making that more clear. The WPA key will be given to the STS when this profile is pushed out (you might need to ask for it…) If it needs to be changed, for the time being, that will require another call to GSD. We hope to change this in the future.
The second-level GSD support person denied this statement. He said that there is absolutely no way to change the WPA key at this point. It would be nice to resolve that disagreement as well....