SSID Changing?

On the Orem YSA 2nd Stake Facebook Page news, they state:

In keeping with Church guidelines regarding the correct use of the name of the Church, the "LDSAccess" wifi name is being discontinued. The new wifi credentials are:

New church wifi name: Liahona
New wifi password: REDACTED

Please share this information with those you minister to so everyone gets the word.

Is this something only their Stake is doing or should we expect to see this change worldwide?

Interesting. It's possible. It's also a bit early for April Fools.

Perhaps they're on a beta for the change.

Someone told me our meetinghouse WiFi had changed this past week, but if it did, it was back to normal Sunday.

lajackson wrote:Someone told me our meetinghouse WiFi had changed this past week, but if it did, it was back to normal Sunday.

Edit: I realize it is the worst kept secret in the world, but who in their right mind would post a church password in the clear on the Internet? There are a few things I will never understand.

More than once, a stake visitor has asked me for the wireless password. Before I tell him the password, I suggest he ask any teenager in the ward. Then I ask him why he needs to connect to the Wi-Fi. The answer is usually that he wants to stream a video. Sigh.

drepouille wrote:More than once, a stake visitor has asked me for the wireless password.

My phone just connects automatically if the local unit has not had the password changed.

My problem is that if this information is correct and the change is going to happen, I think I will have to change the name of my home WiFi network, which is the same as the new one mentioned. I have a much better password, however, than the one proposed. Easier to remember. Harder to type.

This cartoon from a year ago seems fitting...
http://beckstrombuzz.blogspot.com/2019/ ... er-47.html

sbradshaw wrote:This cartoon from a year ago seems fitting...
http://beckstrombuzz.blogspot.com/2019/ ... er-47.html

lajackson wrote:My problem is that if this information is correct and the change is going to happen, I think I will have to change the name of my home WiFi network, which is the same as the new one mentioned. I have a much better password, however, than the one proposed. Easier to remember. Harder to type.

Or, you could change the password to fit the one the Church is using. Then, all your church friends that come over will automatically be able to connect to your WiFi.
/s

EarloftheWest wrote:

lajackson wrote:I have a much better password, however, than the one proposed. Easier to remember. Harder to type.

Or, you could change the password to fit the one the Church is using. Then, all your church friends that come over will automatically be able to connect to your WiFi.

They already do that. This will really confuse all of them.

At least when I choose a new network name they will not have to figure out how to spell it. It will just show up in their WiFi list and I will tell them to use the old password. But it will not make as much sense. And my neighbors will drive by the church and wonder if I have moved.

lajackson wrote:

EarloftheWest wrote:

lajackson wrote:I have a much better password, however, than the one proposed. Easier to remember. Harder to type.

Or, you could change the password to fit the one the Church is using. Then, all your church friends that come over will automatically be able to connect to your WiFi.

They already do that. This will really confuse all of them.

At least when I choose a new network name they will not have to figure out how to spell it. It will just show up in their WiFi list and I will tell them to use the old password. But it will not make as much sense. And my neighbors will drive by the church and wonder if I have moved.

We are currently testing, as well as doing some early deployment for our Church wireless network. There will be more information and instruction to follow.

ccanlas3 wrote:There will be more information and instruction to follow.

Just hit my inbox. It sounds like "Liahona" is available now, "LDSAccess" will continue until April 15 to provide transition.

There's a new password for "Liahona". Also, a "Terms of Use" which must be agreed to each day.

The Notice says there is additional information for the STS, but I did not find anything new at the location specified.

lajackson wrote:The Notice says there is additional information for the STS, but I did not find anything new at the location specified.

That link it just to a section of the Help Center. I didn't see anything new.

But re-reading the letter, I noticed this:

Users need to enter the password only once in their device settings, but the Terms of Use must be accepted once each day a user accesses the network. This agreement helps manage available bandwidth by reminding users of the network’s intended purpose and by preventing unintentional use by devices performing automatic functions (such as updates) when connected to wi-fi upon entry to a Church building.

That should help buildings with limited bandwidth. Fortunately for me, I no longer have buildings that fit that description.

I am a little surprised at the lengthy overlap. A few months ago my daughter's meetinghouse saw Liahona one Sunday along with LDSAccess, and the next Sunday LDSAccess was gone.

The Terms of Use acceptance must not be too onerous, because she has said nothing about it. As STS, I expect I will hear comments. One more thing to do upon arrival at Church each time. But I am good with the explanation.

lajackson wrote:I am a little surprised at the lengthy overlap. A few months ago my daughter's meetinghouse saw Liahona one Sunday along with LDSAccess, and the next Sunday LDSAccess was gone.

I'm guessing they got an earful on that and decided to increase the overlap. I notice that it takes place just after the April General Conference "freeze".

lajackson wrote:The Terms of Use acceptance must not be too onerous, because she has said nothing about it.

I'm sure if you use public WiFi, you're used to it. I know about it when staying in hotel rooms.

lajackson wrote:The Terms of Use acceptance must not be too onerous, because she has said nothing about it.

I'd be shocked if more than 1% even reads it.

Mikerowaved wrote:I'd be shocked if more than 1% even reads it.

I drove by the meetinghouse while I was out and about last evening. It is a two pager. You have to scroll down to get to the accept button. But the font size is quite large.

I expect that after a few weeks the members will all have an idea what it says.

I was moving the Chromecasts in my meetinghouses over to Liahona this morning and thought I'd share the steps I took to get it to work. In order for a device like this to work on Liahona, it does need to be registered in TM. I had access to the TM registration steps, which will be the information in the link that you indicated wasn't updated, so I included those in the instructions. There are other ways to set up the Chromecast on Liahona, I just found these steps to provide the most consistent experience.

[Moderator note: The attachment has been deleted because it contained sensitive information that should not be posted at the forum.]

[Additional moderator note: Those who are authorized access may obtain the information contained in the attachment here at the Help Center, thanks to the excellent work of bartj.]

bartj wrote:TM registration steps

Ohhhh, interesting! Thanks for letting us know.

For those who skimmed over bartj's post - in there is steps to set up selected wireless devices to skip the Terms of Use login screen that is required for Liahona.

Mikerowaved wrote:

lajackson wrote:The Terms of Use acceptance must not be too onerous, because she has said nothing about it.

I'd be shocked if more than 1% even reads it.

I think what lajackson was saying is that the act of accepting it isn't to bad.

As for those who actually read it, I expect a few would at least start to skim it for the novelty of it, but it would still be somewhere around the rate of people who actually read ELUAs.

But I do think it would help with all the devices who suddenly see "free" WiFi and start updating.

Does anybody know how reliable the storage of the NoSplash group will be? I have had all my Assigned IP addresses get completely reset on more than one occasion before. Losing Assigned IPs isn't entirely critical, but if nobody can use any wireless video equipment on Sunday morning because NoSplash settings got lost, then it will be an issue.

Thanks,
Brad

beegman wrote:Does anybody know how reliable the storage of the NoSplash group will be? I have had all my Assigned IP addresses get completely reset on more than one occasion before.

This post indicates that the problems with the IP addresses should be fixed. We'll have to wait and see if there's more bugs.

beegman wrote:Does anybody know how reliable the storage of the NoSplash group will be?

I'm more curious if there's a limit to the number of devices I can register in this group. (Starting with mine. )

Came into the stake center this morning and found that LDSAccess is gone. I haven’t heard from the other buildings in my stake, but I wouldn’t be shocked if they are also having the same issue.

I know that the letter went out to leadership down to the ward council level, but I don’t know if it has been pushed out to general membership yet. Hopefully this was just an oversight that LDSAccess was turned off in our location.

morganreyn wrote:Came into the stake center this morning and found that LDSAccess is gone..

Please send me your stake name so I can have someone look into this. LDSAccess should still be available worldwide.

Mikerowaved wrote:I'm more curious if there's a limit to the number of devices I can register in this group. (Starting with mine. )

Currently there is a limit of 15 devices per building that can be registered.

beegman wrote:Does anybody know how reliable the storage of the NoSplash group will be? I have had all my Assigned IP addresses get completely reset on more than one occasion before.

The issues with the IP address reliability should be resolved with an update made last Friday to TM. This update also included code that would provide the reliability needed for the device registrations. If you run into problems with either of these tools, please escalate to the global service center so we can troubleshoot and resolve them.

bartj wrote:

Mikerowaved wrote:I'm more curious if there's a limit to the number of devices I can register in this group.

Currently there is a limit of 15 devices per building that can be registered.

Thanks for keeping the forum updated with your knowledge of the change. Currently TM is setup to only register active MAC addresses from a drop-down list. (You can't enter a known MAC address.) I assume it's getting the information from the DHCP pool of active leases. It would be helpful in some cases to be able to register a device in all the buildings without waiting for it to show up. For example, we will likely have several MiBox S receivers in the near future and they may not go to the same building each time they're used. Registering each of them for all the buildings in one shot would save a lot of running around.

Mikerowaved wrote:For example, we will likely have several MiBox S receivers in the near future and they may not go to the same building each time they're used.

Hopefully, you're connecting them via wire, not wireless. From what I can tell, the sign in requirement doesn't apply to wired devices.

russellhltn wrote:

Mikerowaved wrote:For example, we will likely have several MiBox S receivers in the near future and they may not go to the same building each time they're used.

Hopefully, you're connecting them via wire, not wireless. From what I can tell, the sign in requirement doesn't apply to wired devices.

A better example would be my SP would like his phone to auto-connect when at any of the stake buildings.

FYI - Here detailed information on MHTech - https://www.churchofjesuschrist.org/hel ... m?lang=eng

Wanting to connect Chromecast to Liahona. The note in step 7 "Find a device" says "Devices need to be connected to Liahona for several minutes before they will display in the Dropdown" If I never get the prompt to key in the password for Liahona because of the splash screen, how do I get it connected to Liahona so it can find the mac address to add it to Nosplash?

ramonc wrote:The note in step 7 "Find a device" says "Devices need to be connected to Liahona for several minutes before they will display in the Dropdown" If I never get the prompt to key in the password for Liahona because of the splash screen, how do I get it connected to Liahona so it can find the mac address to add it to Nosplash?

The device is already connected at the IP level. It's just blocked from communicating to the outside world. In fact, the splash screen is sent via the connection.

The new password has already been published by a news site on the Internet. https://www.thechurchnews.com/members/2 ... ies-174943

If the Church is going to use captive portals for click agreements they could have stuck with just an open (passwordless) network to make it easier.

I personally do not like captive portals due to the headache they add for getting devices setup. It is a shame that openwireless.org never became popular.

rbeede wrote:The new password has already been published by a news site on the Internet. https://www.thechurchnews.com/members/2 ... ies-174943

By a Church-sponsored news site, no less... Interesting.

https://www.churchofjesuschrist.org/hel ... m?lang=eng

Registering Devices in Technology Manager - Step by Step Checklist

Access to the Liahona wireless network requires users to accept the Terms of Use (i.e. splash page) that emphasizes the purposes of Church-provided internet access. Users are required to accept this splash page once per day at every building they visit.

The splash page will only be presented to users that are connected to the Meraki wireless access points. Some facilities have old Church approved Cisco or other non-approved access points installed in their buildings. These devices will not display the splash page and should be replaced with the Meraki access points. The old Church approved Cisco access points (models 1041 and 702) will no longer be supported after March 1, 2020.

Please note that many wireless devices (such as network printers) don’t support a ‘click-through’ experience to accept the Terms of Use. For these devices to function in the new environment, they must be registered in Technology Manager (TM).

Registering A Device in Technology Manager

Step 1: Identify the device that must connect wirelessly to the internet through to the network and does not support a “click-through” to the splash page. In the device Wi-Fi Settings, “forget” the LDSAccess network.

Step 2: Connect the device to the Liahona wireless network (Password: alma3738).

Step 3: Collect the device MAC address. If you have questions, please consult the device’s user manual or search the internet for information related to locating the MAC address for a specific device. The Global Service Department (GSD) will be unable to assist in finding device MAC addresses.

Step 4: Sign into Technology Manager (tm.ChurchofJesusChrist.org) using your Church account.

Step 5: Select the building/property the device needs to be registered at by clicking the firewall serial number associated to the property.


Step 6: Once the Firewall Details screen is displayed, Click the vertical-ellipses icon on the far right side of the screen. Then select “Group Policy Manager.”

Step 7: In the “Find A Device” section of Group Policy Manger, use the “MAC Address” drop-down menu to select the device you wish to register.

Note: Devices need to be connected to Liahona for several minutes before they will display in the dropdown. Only devices connected to Liahona will display in the dropdown.

Step 8: Add a descriptive device name under “Name” that will help identify the device in the future.

Step 9: Select “NoSplash” from Group Policy dropdown.

Step 10: Click “Save.” Devices successfully added to the group policy will immediately appear on the page with the information entered. Test the device to ensure it is working properly on the Liahona network. Note: It will take several minutes after applying the group policy before the device will begin bypassing the splash page.

rbeede wrote:I personally do not like captive portals due to the headache they add for getting devices setup. It is a shame that openwireless.org never became popular.

According to the letter sent: "This agreement helps manage available bandwidth by reminding users of the network’s intended purpose and
by preventing unintentional use by devices performing automatic functions (such as updates) when connected to wi-fi upon entry to a Church building."

Given the amount of traffic I see going to Apple.com, those updates may be pretty significant.

I don't remember where I read it, but in some cases, nearby businesses where handing out the password to their customers. This should put a damper on that. It won't stop willful abuse, but it will expose the act to others.

ccanlas3 wrote:Please note that many wireless devices (such as network printers) don’t support a ‘click-through’ experience to accept the Terms of Use.

According to the email I just got, devices such as printers, that only access the local network will work. Only devices that need to go to the internet have to go though the splash screen or have it disabled.

tm.churchofjesuschrist.org/ is redirecting to https://oos.churchofjesuschrist.org/ Been this way since noonish today now 7pm. Anyone one here have any clues? Trying to move printer(s) to liahona. Thanks,

ramonc wrote:tm.churchofjesuschrist.org/ is redirecting to https://oos.churchofjesuschrist.org/ Been this way since noonish today now 7pm. Anyone one here have any clues? Trying to move printer(s) to liahona. Thanks,

Another post mentioned TM going down for the weekend. I don't remember if got anything about that or not.

An email I did get indicated that as long as the printer is only "local" and doesn't need the Internet, it will function just fine without adding it to the NoSplash policy.

I connected to Liahona, agreed to the terms of use, and disconnected from LDSAccess. Then I rebooted my laptop, opened my browser, and was not asked to agree to the terms of service again. This may be like many public access points in that once you agree to the terms of use, you have a lease period for further access.

I believe the lease period, mentioned in the documentation somewhere, lasts for a day in the same building.

drepouille wrote:I connected to Liahona, agreed to the terms of use, and disconnected from LDSAccess. Then I rebooted my laptop, opened my browser, and was not asked to agree to the terms of service again.

Your acceptance is good for the day. Probably 24 hours, actually, based on my experience.

lajackson wrote:

drepouille wrote:I connected to Liahona, agreed to the terms of use, and disconnected from LDSAccess. Then I rebooted my laptop, opened my browser, and was not asked to agree to the terms of service again.

Your acceptance is good for the day. Probably 24 hours, actually, based on my experience.

Seams it's good forever.
I connected and accepted last week.
This week I see the captive TOS message in the WIFI notifications. I ignored that and was able to sync tools and browse random web sites without accepting again.
(I made sure my data plan was turned off).
I then accepted the TOS and get Liahona is now connected message.......
I could have easily not noticed the TOS message.

Update: The plan to discontinue LDSAccess will go ahead on April 15 as planned. Here's a snippet from the Product Manager - Meetinghouse Networks' email:

Brother Norman wrote:To clear some confusion about the LDSAccess and Liahona SSIDs:

Current state:
Meetinghouses that are 100% Meraki APs - Broadcasting LDSAccess and Liahona
Meetinghouses that don’t have Meraki APs - Broadcasting LDSAccess only
Meetinghouses that have a mix of Cisco and Meraki APs - Broadcasting both LDSAccess(from the Cisco and Meraki APs) and Liahona (from the Meraki APs)

April 15th - shut off LDSAccess worldwide on the Meraki APs ( will be done in the Meraki Dashboard by ICS engineering)
Meetinghouses that are 100% Meraki APs. - Will Broadcast Liahona only
Meetinghouses that don’t have Meraki APs - Will Broadcast LDSAccess only
Meetinghouses that have a mix of Cisco and Meraki APs - Will Broadcast LDSAccess from the old Cisco AP and Liahona from the Meraki AP

After April 15th:
Meetinghouses that still have old Cisco APs broadcasting LDSAccess will eventually be replaced by Meraki APs that will only broadcast Liahona. This will cause an immediate change from LDSAccess to Liahona once the APs are replaced in a meetinghouse.

Is there guidance for going into buildings before April 15th to change devices over? I only got one building converted before our COVID lockdowns. I have 4 buildings I need to convert devices over, but was afraid of contaminating buildings, even if I don't have anything symptomatic, so I avoided going to the other buildings. What I worry is when buildings open again, I can't hit 4 buildings in a short period of time to get them working if we suddenly start having meetings again (regardless of how many weeks or months out that is).

jmalyn wrote:Is there guidance for going into buildings before April 15th to change devices over?

The network itself should not need our help. The question is any "client" devices such as printers, etc.

The letter from the First Presidency canceled all meetings. I do not see anything about making buildings off-limits.

I would check the verbiage of any orders from your governor/mayor/etc. It's likely it includes something to allow for minimum basic operation or continuity of service even for non-essential businesses. I would suggest trying to read the actual signed order and not just the news summery of it.

Of course, follow all local laws and take reasonable precautions against contamination.

Do observe the church policy of not being alone in an unlocked church building.

"Liahona" should be available now, you don't have to wait until the 15th.

I am a little surprised they didn't delay the transition. With the shutdown, the transition isn't likely be be as orderly as planned. A number of leaders/teachers/members are going to arrive at church and discover they can't connect.

Don’t overlook the fact that this only affects devices connected via the WiFi network. Devices that are hard wired to the network aren’t affected.

We're planning on putting an announcement in each ward bulletin on the first Sunday we're allowed back that will have the new SSID and key with brief instructions to sign on. Worst case, members can have an Aaronic Priesthood holder do it for them.

Years ago, the stake young men president asked me for the Wi-Fi password. Seriously, dude? Know any youth?