Tech Forum

Hello There-

I am a newly called Stake Tech Specialist. I am primarily a mac user, and would like to connect to the Internet in the stake center for an upcoming conference where they are going to demo new.familysearch.org. I have installed the Odyssey client on my laptop, but the Global Helpdesk doesn't support Macs. I'm hoping some one else out there is also a Mac user and can help me through the process.

Many Thanks

-steve

applestamps wrote:I am a newly called Stake Tech Specialist. I am primarily a mac user, and would like to connect to the Internet in the stake center for an upcoming conference where they are going to demo new.familysearch.org. I have installed the Odyssey client on my laptop, but the Global Helpdesk doesn't support Macs. I'm hoping some one else out there is also a Mac user and can help me through the process.

The Odyssey client is no longer required. You can ask the Global Service Center to rescript your wireless access points to use the LDSAccess profile, which uses standard WPA security. Then you'll be able to connect much easier.

Before my stake switched over to LDSAccess, we used the Odyssey client, but it only worked by having the Global Service Center give me a specific key for each installation. I never tried it on a Mac, but I would think the process would be similar. So I don't see how you can possibly get Odyssey working without their help.

For that reason, and the fact that LDSAccess is simpler and provides better connectivity, I would highly recommend that you use LDSAccess.

As Alan said using LDSAccess would be easier. By trying to install Odyssey Client on a computer not owned by the Church you also create a licensing problem. The license the Church has for Odyssey Client does not permit installation on any other computers than Church owned computers. That in itself would be a good reason to have the LDSAccess installed.

If you do decide to install LDSAccess on the WAPs make sure the moroni profile is removed. In situations where both the moroni profile and the LDSAccess profile are installed on the WAPs there have been problems with client computers connecting to the network.

Thanks for the feedback. I guess the previous clerks must be breaking a rule - two of them have Odyssey installed on their personal Dell laptops.

How does LDSAccess work? is there a password required to join the network? is there any MAC address filtering available? Is it just an open WAP? What kind of controls are in place? I know my stake president isn't going to want every kid with a PSP or laptop goofing around during Seminary or Sunday School...

applestamps wrote:How does LDSAccess work?

LDSAccess is the SSID of the network profile. More information is available on the wiki at the Wireless Internet page

applestamps wrote:s there a password required to join the network?

Yes. It will be given to you by the GSC technician who sets up the WAPs for the LDSAccess profile. You should establish control procedures for the stake so that it is not passed around carelessly. You can have the passkey changed if the current one gets compromised.

applestamps wrote:s there any MAC address filtering available?

A qualified yes. This is available on the WAPs but since you do not have access to the conrol console of the WAPs (assuming you are using Church provided Cisco Aironet 1200 series WAPs) you will not be able to use this feature. This is also true of the Church provide firewall. If you want to use MAC address filtering you can install a stake purchased router between the Church provided firewall and the WAPs.

applestamps wrote:Is it just an open WAP?

If by an open WAP you mean the SSID is broadcast then the answer is yes. But you must have the passkey installed to gain access. By controlling the passkey you can determine who has access.

As an example for our stake, the STS is the only one with the passkey and he installs it on computers approved by the stake president to access the network wirelessly. No other person has the passkey. After a year of operating this way we are expanding the number of people who will have the passkey to install on approved computers or other wireless devices.

jdlessley wrote:LDSAccess would be easier.

Just remember that when you change it, you'll have to change every computer that's currently using it.

Wow - thanks so much for all of the info. I'll definately be presenting to the Stake President to have our system changed. I really appreciate your help.

applestamps wrote:Thanks for the feedback. I guess the previous clerks must be breaking a rule - two of them have Odyssey installed on their personal Dell laptops.

That is a for sure. The church pays per license on the Odyssey client, and this should only be installed on church computers.

applestamps wrote: How does LDSAccess work? is there a password required to join the network? is there any MAC address filtering available? Is it just an open WAP? What kind of controls are in place?

Here at the GSC we can configure the AP's to suit the meetinghouse that you are in. To keep everything running flawlessly and smoothly through the changeover we ask that you already receive approval from the stake president to switch to LDSAccess, and that you are able to let everyone know (those that connect with odyssey) that there has been a change and help them change their current odyssey settings to the LDSAccess SSID and encryption.

If you are able to do that, you are golden.

Enigma1 wrote:That is a for sure. The church pays per license on the Odyssey client, and this should only be installed on church computers.

So, it would save the church money if we changed to LDSAccess? And if we do, does the Odyssey client go away, and we would then just use the normal wireless SSID and encryption process?

(Understanding that the GSD has to reconfigure the Pix at the same time, and asking on behalf of the STC.)

lajackson wrote:So, it would save the church money if we changed to LDSAccess? And if we do, does the Odyssey client go away, and we would then just use the normal wireless SSID and encryption process?

It would save the church money to go to LDSACCESS, and odyssey client would either be disabled or uninstalled and you would use either windows Wireless zero configuration utility or whatever other utility comes with your Wlan card.

lajackson wrote: (Understanding that the GSD has to reconfigure the Pix at the same time, and asking on behalf of the STC.)

*note: the only hardware that will be reconfigured is the Cisco Aironet (AP), the cisco pix will remain untouched.