TechWiki - User contributions [en]

Wireless Best Practices

2026-05-14T21:53:17Z

HooperJM: Hid obsolete files until new ones can be created

> [[Meetinghouse Technology]] > [[Meetinghouse Networking]]

Poor wireless access point (AP or WAP) installation can degrade the speed and performance of the wireless network. Below are some “best practices” to consider when installing a wireless network in a building. It is understood that not all buildings are the same and the recommendations below may not be practical in all buildings.

== '''Mounting Considerations''' ==
Mounting APs to the ceiling where they are visible and the wires run above the ceiling is preferred (see diagram 1). If APs cannot be installed in this manner due to security or other considerations, mount APs above the ceiling in the attic space ''facing down'' (see diagram 2). Do not mount APs on top of a desk, shelf, or similar type of surface.
[[File:Wireless Best Practice img 1.png|none|thumb|375x375px]]
'''Diagram 1:''' Ceiling Mounted Example
[[File:Wireless Best Practice img 2.png|none|thumb|319x319px]]
'''Diagram 2:''' Attic Mounted Example

Three primary factors impact the number of APs required within a meetinghouse:

# '''Building Material—'''Dense building material, such as brick and concrete, will impede the wireless signal more than materials such as drywall. Buildings with thicker internal building materials may require more APs to provide sufficient wireless coverage.
# '''Building Size—'''The larger the area requiring wireless coverage, the more APs will be needed. APs have a limited coverage area that is decreased by environmental conditions such as building materials, as noted above. The farther away a device is from an AP, the slower the connection will be between the device and the AP.
# '''Devices—'''The number of devices connected to a single AP and the type of traffic generated by those devices will greatly impact wireless performance. Members should be encouraged to use the wireless network only for Church purposes and to disconnect from the network when they are not using it. To optimize performance, APs should be installed in or near rooms that will have the most devices connected to the wireless network.

Other mounting recommendations and considerations include mounting APs in the following areas:

* In areas free from physical barriers such as metal structures, pipes, beams, air conditioning ducts, and so forth.
** As noted above, when mounting near ductwork or metal structures, mount the APs so they are facing down, away from the ductwork.
* Inside offices or classrooms where possible, as opposed to hallways.
** The Meraki MR33 will increase power and extend its range when there aren’t other APs nearby. By placing APs so they are not in direct line of sight in hallways, it forces the AP to power up to find the next closest AP. If APs are run only in hallways, they will see each other too easily and will power down their coverage.
* Near principle teaching and administrative areas, such as Relief Society rooms, elders quorum rooms, and bishop's and clerk’s offices.
* At least 10 feet (3 meters) from signal-emitting devices, such as microwaves, fluorescent lights, electric fans, cordless phones, and building automation equipment.
** These devices emit a wireless signal that can degrade AP performance.
* In clean, climate-controlled locations to increase the operational life of the APs.
* Less than 300 feet (91 meters) from a network switch or firewall.
* In locations that are accessible for future troubleshooting and support.
* Away from the exterior walls of the building to increase coverage within the building.
** Note that the MR33 emits a spherical pattern, connecting with devices in all directions. Take this into account when making decisions about placement locations.
* At standard ceiling levels of 10 feet (3 meters).
** Placing APs in vaulted ceilings makes them less effective because of extreme distances to connecting devices and makes them difficult to access for future troubleshooting and support.

'''NOTE:''' If physical security is an issue, mount the AP in a location that is not visible from the outside of the building.

Also, when the ISP modem has APs built in, be sure the modem AP is turned off, as it can create instability in the system.

Wireless is also impacted by the rest of the network infrastructure, such as the firewall, switches, and cabling. For current network infrastructure standards, visit the “Networking Hardware” section of Meetinghouse Tech.

== '''Example AP Placement''' ==
Below are general guidelines for how much area a single AP can support, based on two different wall material types: (Updated Nov 20, 2025 to match current hardware specs)
{| class="wikitable"
|'''Material'''
|'''Square Feet'''
|'''Meters'''
|-
|Cinder Block Wall
|2,092 ft²
|194 m²
|-
|Drywall
|2,187 ft²
|203 m²
|}

Configuring Network and Sensor Alerts

2026-04-22T23:14:53Z

HooperJM: /* Add Sensors to the Network */

== Introduction ==
Church Network Manager (CNM) can be configured to send email messages to a list of recipients based on events configured for a network. Alerts can be sent to any valid email address, and are not dependent on CNM access. They are specific to a single network. If a user is responsible for multiple networks, alerts will need to be configured for each network.

There are two kinds of alerts in Church Network Manager-
#'''Network alerts'''- Triggered based on a predefined set of events available in the Meraki API. Not all supported events were selected, but the CNM team has chosen those most relevant to most users. These events will be enumerated later in this document.

#'''Sensor alerts'''- Triggered by events detected by one of the optional Meraki sensors.

We’ll explain network alerts first. Scroll down if you want to skip to instructions for sensor alerts.
==Configuring Network Alerts-==
===Navigate to your network in CNM===
*Go to: <nowiki>https://cnm.churchofjesuschrist.org</nowiki>

*Click on '''Search'''

*Search for your network using one of the following options:
**Firewall Serial Number
**Device Serial Number
**Property Number
**Unit Name
**Unit Number
**ReceiverUA
**CNM Network ID
**IP Address

*Click on the name of the unit in the search results.

*On the Unit Information page, click on the blue header in the card that represents the property

===Configure Alert Settings===

* From the '''Menu''' dropdown, select '''Alert Settings'''
* On the Network Alert Settings screen:

[[File:Screenshot 2024-07-02 at 2.50.06 PM.png|alt=Configure Alert Settings Dialogue. The email address has a yellow caution sign because the user has not yet accepted the opt-in email.|thumb|Configure Alert Settings Dialog]]
*Enter an email address for the first recipient.

*Select a language in which the emails will be sent.

*Click '''Verify'''.

*If desired, you can enter additional email addresses, with a corresponding language selection for each recipient.

*Click '''Save'''.

*Click '''Enable Network Alerts''', to ensure the setting is turned on.

*A validation and opt-in email will be sent to the email address entered. If the user doesn’t see a message, they might check their spam or junk folder, or try adding cnm-noreply@mail.churchofjesuschrist.org to their address book.

*Alerts will only be sent after the email recipient has opted-in by responding to the validation email.

*You are now ready to receive network alerts.

*To remove an email recipient, click the circle slash icon next to the language identifier.

*When a trigger event occurs, an email message will be sent to all addresses that have been validated and opted-in.

=== The following events will trigger a network alert: ===
*A Rogue Access Point is detected

*A gateway (AP) goes offline for more than 30 minutes

*A gateway becoming a repeater

*A WAN appliance goes offline for more than 30 minutes

*The DHCP lease pool is exhausted

*An IP Conflict is detected

*A rogue DHCP server is detected

*A switch goes offline for more than 30 minutes

*A new DHCP server is detected

*Power supply goes down for a managed switch

*Critical temperature alert for switches (only certain models supported)

For a detailed description of each alert, you can reference the Cisco Meraki documentation: <nowiki>https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications</nowiki>
==Configuring Sensor Alerts==
===Navigate to your network in CNM===
*Go to: <nowiki>https://cnm.churchofjesuschrist.org</nowiki>

*Click on '''Search'''

*Search for your network using one of the following options:
**Firewall Serial Number
**Device Serial Number
**Property Number
**Unit Name
**Unit Number
**ReceiverUA
**CNM Network ID
**IP Address

*Click on the name of the unit in the search results.

*On the Unit Information page, click on the blue header in the card that represents the property
===Add Sensors to the Network===
If you haven’t already, add your sensors to the network.
*From the '''Menu''', select '''Add Devices'''.

*Enter the '''Serial Number'''

*Optionally give your device a '''Label'''

*Click '''Add Device'''

===Configure Alert Profiles===
*On the Network page, select the '''Sensors''' tab.

*Click '''Alert Profiles''' button the right of the screen.

*Enable, disable, or modify the sensor alerts in the default profile as desired. The default profile applies to all sensors on the network.

*Click the '''Add''' button.

*Give your new profile a name (Required field)

*In the next section, sensor alert settings are available in an accordion menu. Select the sensor type to expand the configuration options.

*Configure sensor alerts as desired.

*The bottom section is where you will select the specific sensors you want this profile to apply to.

*Click '''Save''' and notice the new profile name listed in the left pane.

*Close the dialog box.
===Configure Alert Settings===
*Back on the Network Page, select '''Menu''' (normally on the right-hand side of the screen), then select '''Alert Settings.'''

*On the Alert Settings Dialog, select the '''Sensor Alert Settings''' tab.

*Enter an email address for the first recipient.

*Select a language in which the emails will be sent.

*The email address will perform a validation step after you select a language.

*If desired, you can enter additional email addresses, with a corresponding language selection for each recipient.

*Click '''Save'''.

*Click '''Enable Sensor Alerts''', to ensure the setting is turned on.

*A validation and opt-in email will be sent to the email address entered. If the user doesn’t see a message, they might check their spam or junk folder, or try adding cnm-noreply@mail.churchofjesuschrist.org to their address book.

*Alerts will only be sent after the email recipient has opted-in by responding to the validation email.

*You are now ready to receive sensor alerts.

*When a trigger event occurs based on the alert profiles you configured or a default profile, an email message will be sent to all addresses that have been validated and opted-in.

*The following Meraki sensors are supported in CNM:

*Temperature and Humidity (MT10)

*Probe Sensor (MT11)

*Water Detection (MT12)

*Indoor Air Quality (MT14)

*Open/Close Detection (MT20)

*Smart Power Controller (MT40)
*(Note: Meraki also sells the MT15 and MT30, but CNM does not support them at this time.)
==Additional Resources==
*Meraki documentation for the MT series sensors: <nowiki>https://documentation.meraki.com/MT</nowiki>

*For a detailed description of each alert, you can reference the Cisco Meraki documentation: <nowiki>https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications</nowiki>

Meetinghouse Network Upgrade

2026-04-17T15:10:55Z

HooperJM: /* Frequently Asked Questions */

== Summary ==
Sometime during 2025-2027, your unit's building will receive a network and Wi‑Fi upgrade to provide a faster internet (according to need and availability), and a more secure and reliable network experience for everyone. As part of this work, some physical network jacks will be removed or disabled. Devices in leaders’ offices, clerk offices, and other locations—such as resource centers—may need to connect to the Wi‑Fi network after the upgrade.

== Purpose(s) ==

* '''Improved teaching and learning experiences'''- This upgrade is designed to support gospel learning by improving the ability to stream Church videos for lessons, live meeting broadcasts, and provide a backbone for translation technologies. The entire building will receive enhanced Wi‑Fi coverage. And where internet speed increases are needed, they will be increased, based on the availability of faster service plans.
* '''Wireless preferred'''- The benefits of a wireless preferred approach include flexibility for the end-users and long-term cost savings for the Church. Network drops are expensive to install, maintain, and upgrade, far exceeding the cost of the networking hardware itself. By minimizing the number network jacks, we reduce the overall cost of the network. And by increasing the number of access points in meetinghouses, the end-users will find greater flexibility for the placement of equipment and other uses of the network.
* '''Device security and continued operation'''- The access points (MR33) and switches (MS120) in most meetinghouses will no longer be supported by Meraki and need to be replaced. By upgrading the equipment on schedule, we ensure continued operation, as well as security updates.

== Scope ==

* Replace expiring, obsolete, and unsupported hardware.
* Provide comprehensive Wi-Fi coverage throughout each meetinghouse.
* Ensure cabling meets the Cat6A standard.
* Install a network cable to the rear of each chapel to enable streaming now or in the future. (Cameras not provided as part of this project. Just the network connection).
* Ensure internet speeds are at least 500 Mbps- Where internet service providers are available at a reasonable price.
* Provide a standard, clean, and orderly networking rack.
* Ensure rack locations meet local building code requirements, are secure, and have sufficient air flow.
* Re-install and configure network in CNM. Vendor is to ensure the network is functional.
* Provide helpful artifacts in CNM: Network diagrams, cable test results, pictures of the rack and location, and more.
* Fill holes in ceiling tiles, and patch holes in walls from old equipment.
* Vendors are required to remove old equipment and cabling.

== How to prepare ==

* Ensure all of your devices are Wi-Fi ready. This includes:
** Clerk computers
** Printers
** Copy machines in the Materials Resource Center
** Smart TV's and set-top streaming devices
** Any other device your unit depends on for Church purposes
* You may need to purchase an ethernet to Wi-Fi adapter from a local retailer if your device (eg copier) doesn't have built-in wireless.
* In some rare cases, you might need to upgrade or replace older equipment.
* As a contingency, note the IP and Mac addresses of any devices with static IP assignments. This upgrade ''should'' NOT affect IP ranges. But in rare cases, IP assignments might be affected. If you make note ahead of time, you'll be able to re-assign devices post-installation.
* '''*Note*''' If your network still includes a FAC16 zone (Facility zone with 16 addresses), please upgrade at your earliest convenience to a FAC32 zone, through the "upgrade IP range" link in Church Network Manager (CNM). This change can be made irrespective of the network upgrade, but you will definitely need to make a note of all devices, in particular door access systems that have a static IP reservation assigned. Write down their Mac addresses and their IP addresses, and follow the in-app instructions to ensure a successful upgrade.

== What to do after the installation ==

* Please utilize CNM to ensure the network is functioning properly, and all necessary devices are connected to the network
* '''*Note*''': You do not need to fix issues with the physical installation. Contact your Facility Manager, who will require the contractors to address any of the following issues:
** Damaged or dead cables
** Cables installed in walkways or present any kind of a safety hazard
** Cables run or access points that appear to be installed in the wrong place
** Old obsolete cables or hardware (access points) that were not removed after being disconnected
** Unpatched holes in the ceilings or walls.
** Other damage or clutter from the installation that was not repaired or removed by the vendor

== Frequently Asked Questions ==

* '''Which kinds of facilities are included in this network upgrade initiative?'''
** All meetinghouses, FM offices, and standard Family History Centers (FHC)
* '''Will this make my internet faster?'''
** The newer equipment is capable of incrementally faster throughput. Additionally, ICS is also working with Internet Service Providers (ISP's) to increase speeds where available and financially feasible. The target speeds are at least 500Mbps download, and at least 100Mbps upload. This is highly dependent on the availability of ISP's at the site.
* '''What about the network jack in the pulpit?'''
** The network jack at the pulpit may not be reconnected as part of this project. While the pulpit is part of the AV system, if the existing cable does not reach the new or current network rack location, it may remain disconnected until the AV system is replaced or upgraded.
* '''Will my network rack be moved?'''
** Generally, network racks will be left in place. The following reasons might require a network rack to be relocated:
*** To meet building code safety requirements
*** Improve security (behind a locked door)
*** Ensure a clean, safe environment with sufficient airflow for cooling
* '''Are there any exclusions?'''
** Buildings proposed for redeployment within 2 years of the scheduled upgrades will not be upgraded.
* '''How are the network upgrades being funded?'''
** The Meetinghouse Facilities Department is funding all network upgrades included in this project. FM groups will not be invoiced for this project.
* '''How long does an upgrade take?'''
** The average upgrade takes approximately 2-3 days for an individual site. However, because each site is unique, this will vary.
* '''Will we know exactly when the vendors will be at each location to upgrade the networks?'''
** Vendors have been asked to inform FM groups with a 2 week window, but with so many upgrades happening simultaneously, this is difficult to enforce.
*'''What if any current Meraki equipment breaks before the new equipment is installed? Is there a contingency plan?'''
**FMs should use operations funds to do a 1:1 replacement of any Meraki equipment (firewall, switch or access point) that malfunctions before the network upgrade is performed. This helps ensure the church adheres to international accounting regulations (FS6110).
*'''How are network upgrades being funded?'''
**MFD is funding all network upgrades through a HQ-sponsored initiative. FM groups will not be invoiced for this project.
*'''What time of day will the vendors perform the work?'''
**The work typically is performed during business hours, so units shouldn’t see vendor technicians, ladders, wires, etc. during evening or weekend activities.
*'''How many access points will each building get?'''
**ICS has generated heatmaps based on the floorplan of each building, and will install the appropriate number of access points to ensure comprehensive coverage. Most buildings will receive between 7-9, with larger buildings receiving more, and smaller buildings requiring fewer.
*'''Why are my access points placed where they are?'''
**Each meetinghouse has been reviewed for uniform wireless coverage, and a heatmap for each standard plan and custom plan has been developed. The installers have been instructed to follow the heatmaps for AP placement in each building and are allowed to install each AP within 3 feet of the locations identified on each heatmap.
*'''Will any IP addresses change as a result of the upgrade?'''
**Vendors have been provided with instructions that will preserve IP addresses on the network. If you find that your IP addresses have changed, please communicate that through your FM. *NOTE*: If your network still contains a FAC16 zone, we encourage you to select the "Upgrade IP range" link in CNM and upgrade to a FAC32 zone as soon as possible. Please be sure to not any IP reservations as instructed in the onscreen dialogues when doing this upgrade. This process will change your IP addresses, but is not part of the process assigned to vendors.
*'''What equipment will still be connected to the network with cabling?'''
**If these systems listed below are currently connected to the network at the time the network is upgraded, they will continue to be connected to the network with cabling:
***Audio/visual systems, including cameras mounted in approved locations in the chapel
***Door access systems
***HVAC systems and controls
*'''What cables will NOT be reconnected after the network upgrade?'''
**You will need to connect the following devices to the Wi-Fi network:
***Clerk/bishop offices computers and printers
***Materials center copies and printers
***Cables connected to the network jack at the pulpit or at the pulpit controls (see the next FAQ)
***Non-standard equipment, such as unmanaged switches, TVs, older audio/visual systems that aren’t currently connected to the network.
***Additionally, custom or non-standard equipment that may have been installed by a local leader or technology specialist will not be reconnected.
***FMs have been instructed to communicate these changes with stake leaders and technology specialists to ensure they are well-informed of the changes in cabling standards and connectivity practices. Additionally, local leaders and stake technology specialists will need to prioritize what else gets connected in the building. It will be their responsibility to reconnect these other devices.
*'''What if I have equipment installed that's better than what the contractor has been instructed to install?'''
**The Presiding Bishopric has approved this project to establish a global standard that applies to every meetinghouse in the world. The contractors are required to follow the statement of work they signed. We ask that you please support the contractors and the project team as they complete this upgrade project. Past problems with slow internet speeds and insufficient WiFi coverage are being actively addressed with this upgrade project. If problems persist, please report the specific problems to your FM Group, and they will work with the vendor or escalate problems as needed. Thank you for your cooperation.

Meetinghouse Network Upgrade

2026-04-09T15:59:38Z

HooperJM: /* Summary */

Meetinghouse Networking

2026-04-09T15:58:44Z

HooperJM:

> [[Meetinghouse Technology]]

__NOTOC__
<div style="margin: 10px 0px 0px 0px;">
The content of this wiki is under construction and does not always reflect official Church information. This content is provided by product managers, moderators, and technology specialists and is subject to change. For more general content go to the Help Center at: https://www.ChurchofJesusChrist.org/help/support/meetinghouse-technology.

This section has articles to help manage network devices in each meetinghouse.
<div class="mw-category"><div class="multi-column">

<div class="no-column-break">
===Overviews===
*[https://www.churchofjesuschrist.org/tools/help/networking-overview?lang=eng Network Overview]
*[https://www.churchofjesuschrist.org/tools/help/cnm-overview?lang=eng CNM Overview]
*[https://www.churchofjesuschrist.org/tools/help/firewall-overview?lang=eng Firewall Overview]
*[https://www.churchofjesuschrist.org/tools/help/switch-overview?lang=eng Switch Overview]
*[https://www.churchofjesuschrist.org/tools/help/wap-overview?lang=eng WAP Overview]
*[[Approved Equipment List]]
*[[Network Status Report Guide]]
*[[Glossary]]
</div>

<div class="no-column-break">
===Networking/CNM===
*[[Network Training]]
*[[Church Network Manager]]
*[[Assigning a Static IP|Assigning a Static IP Address]]
*[[CNM Group Policies|CNM Group Policies]]
*[[Configuring Network and Sensor Alerts]]
*[[Favorites Feature In CNM]]
*[[Add ISP Info|Adding Internet Service Provider Information]]
*[[What is Church Network Manager]]
*[[Using the “No Networks” Report]]
*[[Adding a Facility or Workforce Zone to a Meraki Firewall]]

</div>
<div class="no-column-break">
===Firewall===
*[[Using Filters]]
*[[Firewall Activation on CNM]]
*[[Meraki Installation Guide 2024|New Firewall and Switch installation - 2024-2025]]
*[https://tech.churchofjesuschrist.org/wiki/images/9/92/Replace_Existing_Firewall.pdf Replace an existing installed firewall]
*[[Moving Firewalls]]
</div>
<div class="no-column-break">

===Switch===
*[[Unmanaged Switches]]
*[https://tech.churchofjesuschrist.org/wiki/images/0/0f/Meraki_MX_and_Switch_Installation_guide_NEW.pdf Managed Switch Installation]
</div>

</div>
</div>

<div class="mw-category">
<div class="multi-column">

<div class="no-column-break">
===Wireless Access Points===
*[[Activating WAP|Activating a WAP]]
*[[Disabling Wireless Access]]
*[[Meraki WAP]]
*[[Wireless Best Practices]]
*[[Lehi and Liahona Wireless Networks|Lehi and Liahona Wireless Networks]]
*[[IOTConnect SSID|IoTConnect Wireless networks]]
*[[Generate A WiFi Heatmap]]
</div>

<div class="no-column-break">
===Reference Articles===
*[[Facilities Zone]]
*[[Power Over Ethernet]]
*[[MAC Addresses]]
*[[Internet Speed Tests]]
*[[Improving Internet Access]]
*[[Network search|Search for a Network]]
*[[Portable Meetinghouse Network]]
*[[Meetinghouse Network Upgrade|2025-2026 Meetinghouse Upgrade Project]]
</div>
===Troubleshooting===
*[[Troubleshooting Firewalls|Firewalls]]
*[[Troubleshooting Meraki switches|Switches]]
*[[Troubleshooting Wireless Access Points|Wireless Access Points (APs)]]
*[[Improving Bandwidth|Improving Bandwidth (8 Steps)]]
*[[Troubleshooting Connections]]
</div>

</div>
</div>

Meetinghouse Networking

2026-04-08T21:44:36Z

HooperJM: Added article for the meetinghouse upgrade project.

> [[Meetinghouse Technology]]

__NOTOC__
<div style="margin: 10px 0px 0px 0px;">
The content of this wiki is under construction and does not always reflect official Church information. This content is provided by product managers, moderators, and technology specialists and is subject to change. For more general content go to the Help Center at: https://www.ChurchofJesusChrist.org/help/support/meetinghouse-technology.

This section has articles to help manage network devices in each meetinghouse.
<div class="mw-category"><div class="multi-column">

<div class="no-column-break">
===Overviews===
*[https://www.churchofjesuschrist.org/tools/help/networking-overview?lang=eng Network Overview]
*[https://www.churchofjesuschrist.org/tools/help/cnm-overview?lang=eng CNM Overview]
*[https://www.churchofjesuschrist.org/tools/help/firewall-overview?lang=eng Firewall Overview]
*[https://www.churchofjesuschrist.org/tools/help/switch-overview?lang=eng Switch Overview]
*[https://www.churchofjesuschrist.org/tools/help/wap-overview?lang=eng WAP Overview]
*[[Approved Equipment List]]
*[[Network Status Report Guide]]
*[[Glossary]]
</div>

<div class="no-column-break">
===Networking/CNM===
*[[Network Training]]
*[[Church Network Manager]]
*[[Assigning a Static IP|Assigning a Static IP Address]]
*[[CNM Group Policies|CNM Group Policies]]
*[[Configuring Network and Sensor Alerts]]
*[[Favorites Feature In CNM]]
*[[Add ISP Info|Adding Internet Service Provider Information]]
*[[What is Church Network Manager]]
*[[Using the “No Networks” Report]]
*[[Adding a Facility or Workforce Zone to a Meraki Firewall]]

</div>
<div class="no-column-break">
===Firewall===
*[[Using Filters]]
*[[Firewall Activation on CNM]]
*[[Meraki Installation Guide 2024|New Firewall and Switch installation - 2024-2025]]
*[https://tech.churchofjesuschrist.org/wiki/images/9/92/Replace_Existing_Firewall.pdf Replace an existing installed firewall]
*[[Moving Firewalls]]
</div>
<div class="no-column-break">

===Switch===
*[[Unmanaged Switches]]
*[https://tech.churchofjesuschrist.org/wiki/images/0/0f/Meraki_MX_and_Switch_Installation_guide_NEW.pdf Managed Switch Installation]
</div>

</div>
</div>

<div class="mw-category">
<div class="multi-column">

<div class="no-column-break">
===Wireless Access Points===
*[[Activating WAP|Activating a WAP]]
*[[Disabling Wireless Access]]
*[[Meraki WAP]]
*[[Wireless Best Practices]]
*[[Lehi and Liahona Wireless Networks|Lehi and Liahona Wireless Networks]]
*[[IOTConnect SSID|IoTConnect Wireless networks]]
*[[Generate A WiFi Heatmap]]
</div>

<div class="no-column-break">
===Reference Articles===
*[[Facilities Zone]]
*[[Power Over Ethernet]]
*[[MAC Addresses]]
*[[Internet Speed Tests]]
*[[Improving Internet Access]]
*[[Network search|Search for a Network]]
*[[Portable Meetinghouse Network]]
*[[Meetinghouse Network Upgrade.|2025-2026 Meetinghouse Upgrade Project]]
</div>
===Troubleshooting===
*[[Troubleshooting Firewalls|Firewalls]]
*[[Troubleshooting Meraki switches|Switches]]
*[[Troubleshooting Wireless Access Points|Wireless Access Points (APs)]]
*[[Improving Bandwidth|Improving Bandwidth (8 Steps)]]
*[[Troubleshooting Connections]]
</div>

</div>
</div>

Meraki Installation Guide 2025-2026

2026-04-03T17:32:22Z

HooperJM:

== Meraki Managed Firewall ==

* The Meraki MX67 firewall is the approved firewall for meetinghouses at this time.
* Port 2 on the MX67 should be connected to an SFP port on the Meraki Switch using an SFP Module. * Ports 3, 4, 5 will be disabled.

<nowiki>**</nowiki> If you don’t have an SFP module then connect to one of the Switch Access Ports and configure that switch port to be “LINK” in Church Network Manager. (CNM)

== Meraki Managed Switches ==

* For a successful install, please read the instructions before beginning the switch install or contacting the GSD for assistance. Reading and understanding this guide before you begin is imperative for success.
* Label cables before disconnecting them from the current unmanaged switches.
* At least one Meraki managed switch must be installed in every meetinghouse worldwide
* Most meetinghouses will use a combination of the Meraki switch and current unmanaged switches. If there are enough Meraki ports for all data cables then remove all unmanaged switches.
* The installer will need access to a mobile computer or an iPad in order to activate and configure the new Meraki switch in Church Network Manager during the Meraki switch installation
* All wireless access points (APs) in the meetinghouse must connect directly to the a Meraki managed switch. Do not connect Cisco APs into the Meraki Switch. Upgrade Cisco APs to Meraki APs.
* Order an SPF module when ordering a Meraki Switch.
* If a second Meraki switch is needed in the same meetinghouse then two additional SFP modules will be needed.
* You will need a screwdriver and wood screws if you are mounting a switch to a wall, cabinet, or rack
* You will need a pen or pencil, tape and paper to create a cable mapping sheet of the meetinghouse data drops
* The Switch installation will be much easier if you have 2 people to identify where each data cable connects. Especially for the Wireless Access Points.
* The Meraki switch(es) installed in a meetinghouse will be logically tied to the Meraki Firewall in the Meraki Cloud Management application.
* Use of the 48-port switch is an exception and should only be used when the number of in-use Ethernet network lines running to a single location exceeds 22.

== SFP Modules ==
[[File:SFP Module.jpg|thumb|SFP Module –Approved Optics 1000BASET SFP transceiver module for Category 5e/6 copper wire]]

* Every switch will need a SFP module installed in port SFP 9 on the "8 Port switch", port SFP 25 on the "24 Port switch" and port SFP 49 on the “48 port switch.

* If a second Meraki switch is needed in the same meetinghouse then two additional SFP modules will be needed. Install the extra SFP module in Port 10 of the first Meraki 8 Port switch (or port SFP 26/SFP 50 on the first 24 or 48 port switch respectively) to connect the two Meraki Switches.
* To install the SFP module- open the lock, insert the module and close the lock. This will lock the SFP module into the switch.
* Connect the data cable to the SFP modules with the lock closed in the locked position.
* To remove an SFP module- open the lock and remove the module from the switch.
<gallery mode="slideshow">
File:Lock Diagram.png|Insert the SFP modules into the switch with the lock open and then close the lock
File:Lock is closed.png|SFP lock is open
File:SFP Lock is Open.jpg|SFP lock is closed
File:Lock with Data cable.png|SFP lock is closed with data cable connected
</gallery>

== Steps before installing Meraki Managed Switch (MS130-8P,-24P,-48P) ==
[[File:UnmanagedSwitch1.png|thumb|Examples of unmanaged switches]]
# Using tags or tape, identify and label the following possible cables connecting to:
## Wireless Access Points (tag as AP)
## Clerk’s and unit Leader’s offices (tag as Clerk or BP or SP)
## The HVAC, Door locks, and other Facility devices (tag as HVAC or Locks or FAC)
## Webcast equipment, Audio/Video distribution systems (tag as AV)
## The Family History Center (if present) (tag as FHC)
## The Seminary and Institute Teacher Offices and student classrooms (if present) (tag as S&I)
## FM office, Mission office, etc... (if present) (tag as FM or Mission)
## All other rooms in the meetinghouse (all of these will be public zone)
# This is a great opportunity to determine if all classroom connections are used or needed. If they are no longer used, then leave the cables disconnected to reduce the number of needed switch ports. If you leave a room disconnected, then add a sticker to the data jack faceplate in that room stating that it is disconnected.
# After labeling, take photos of the current configuration to inform the troubleshooting process if problems occur during the new switch installation.
## It is recommended that you leave a sheet of paper with the cable and port mappings next to the switch. This will facilitate future changes to the network. (example: Port 7 on the switch goes to the Clerk’s office, etc. )

== Figure 1- One Meraki MS130-8P (8 port switch) Configuration ==
[[File:Screenshot 2026-04-03 at 11.15.55 AM.png|left|frameless|4778x4778px]]

== Figure 2- Two Meraki MS130-8P (8 port switch) Configuration ==

== Figure 2.1- Two Meraki MS130-8P (8 port switch) Configuration in multiple network closets==

== Figure 3- Three Meraki MS130-8P (8 port switch) Configuration ==

== Figure 4- One Meraki MS130-24P (24 port switch) Configuration ==

Meraki Installation Guide 2025-2026

2026-04-03T17:31:11Z

HooperJM:

Meraki Installation Guide 2025-2026

2026-04-03T17:24:29Z

HooperJM: /* Figure 1- One Meraki MS130-8P (8 port switch) Configuration */

Meraki Installation Guide 2025-2026

2026-04-03T17:23:51Z

HooperJM:

File:Screenshot 2026-04-03 at 11.15.55 AM.png

2026-04-03T17:21:12Z

HooperJM:

Meraki Switch insallation diagram

Meraki Installation Guide 2025-2026

2026-04-03T17:12:11Z

HooperJM:

== Meraki Managed Firewall ==

* The Meraki MX67 firewall is the approved firewall for meetinghouses at this time.
* Port 2 on the MX67 should be connected to an SFP port on the Meraki Switch using an SFP Module. * Ports 3, 4, 5 will be disabled.

<nowiki>**</nowiki> If you don’t have an SFP module then connect to one of the Switch Access Ports and configure that switch port to be “LINK” in Church Network Manager. (CNM)

== Meraki Managed Switches ==

* For a successful install, please read the instructions before beginning the switch install or contacting the GSD for assistance. Reading and understanding this guide before you begin is imperative for success.
* Label cables before disconnecting them from the current unmanaged switches.
* At least one Meraki managed switch must be installed in every meetinghouse worldwide
* Most meetinghouses will use a combination of the Meraki switch and current unmanaged switches. If there are enough Meraki ports for all data cables then remove all unmanaged switches.
* The installer will need access to a mobile computer or an iPad in order to activate and configure the new Meraki switch in Church Network Manager during the Meraki switch installation
* All wireless access points (APs) in the meetinghouse must connect directly to the a Meraki managed switch. Do not connect Cisco APs into the Meraki Switch. Upgrade Cisco APs to Meraki APs.
* Order an SPF module when ordering a Meraki Switch.
* If a second Meraki switch is needed in the same meetinghouse then two additional SFP modules will be needed.
* You will need a screwdriver and wood screws if you are mounting a switch to a wall, cabinet, or rack
* You will need a pen or pencil, tape and paper to create a cable mapping sheet of the meetinghouse data drops
* The Switch installation will be much easier if you have 2 people to identify where each data cable connects. Especially for the Wireless Access Points.
* The Meraki switch(es) installed in a meetinghouse will be logically tied to the Meraki Firewall in the Meraki Cloud Management application.
* Use of the 48-port switch is an exception and should only be used when the number of in-use Ethernet network lines running to a single location exceeds 22.

== SFP Modules ==
[[File:SFP Module.jpg|thumb|SFP Module –Approved Optics 1000BASET SFP transceiver module for Category 5e/6 copper wire]]

* Every switch will need a SFP module installed in port SFP 9 on the "8 Port switch", port SFP 25 on the "24 Port switch" and port SFP 49 on the “48 port switch.

* If a second Meraki switch is needed in the same meetinghouse then two additional SFP modules will be needed. Install the extra SFP module in Port 10 of the first Meraki 8 Port switch (or port SFP 26/SFP 50 on the first 24 or 48 port switch respectively) to connect the two Meraki Switches.
* To install the SFP module- open the lock, insert the module and close the lock. This will lock the SFP module into the switch.
* Connect the data cable to the SFP modules with the lock closed in the locked position.
* To remove an SFP module- open the lock and remove the module from the switch.
<gallery mode="slideshow">
File:Lock Diagram.png|Insert the SFP modules into the switch with the lock open and then close the lock
File:Lock is closed.png|SFP lock is open
File:SFP Lock is Open.jpg|SFP lock is closed
File:Lock with Data cable.png|SFP lock is closed with data cable connected
</gallery>
[[File:UnmanagedSwitch1.png|thumb|Examples of unmanaged switches]]

== Steps before installing Meraki Managed Switch (MS130-8P,-24P,-48P) ==

# Using tags or tape, identify and label the following possible cables connecting to:
## Wireless Access Points (tag as AP)
## Clerk’s and unit Leader’s offices (tag as Clerk or BP or SP)
## The HVAC, Door locks, and other Facility devices (tag as HVAC or Locks or FAC)
## Webcast equipment, Audio/Video distribution systems (tag as AV)
## The Family History Center (if present) (tag as FHC)
## The Seminary and Institute Teacher Offices and student classrooms (if present) (tag as S&I)
## FM office, Mission office, etc... (if present) (tag as FM or Mission)
## All other rooms in the meetinghouse (all of these will be public zone)
# This is a great opportunity to determine if all classroom connections are used or needed. If they are no longer used, then leave the cables disconnected to reduce the number of needed switch ports. If you leave a room disconnected, then add a sticker to the data jack faceplate in that room stating that it is disconnected.
# After labeling, take photos of the current configuration to inform the troubleshooting process if problems occur during the new switch installation.
## It is recommended that you leave a sheet of paper with the cable and port mappings next to the switch. This will facilitate future changes to the network. (example: Port 7 on the switch goes to the Clerk’s office, etc. )

File:UnmanagedSwitch1.png

2026-04-03T17:11:50Z

HooperJM:

Examples of Unmanaged switches

Meraki Installation Guide 2025-2026

2026-04-03T17:08:45Z

HooperJM:

== Meraki Managed Firewall ==

* The Meraki MX67 firewall is the approved firewall for meetinghouses at this time.
* Port 2 on the MX67 should be connected to an SFP port on the Meraki Switch using an SFP Module. * Ports 3, 4, 5 will be disabled.

<nowiki>**</nowiki> If you don’t have an SFP module then connect to one of the Switch Access Ports and configure that switch port to be “LINK” in Church Network Manager. (CNM)

== Meraki Managed Switches ==

* For a successful install, please read the instructions before beginning the switch install or contacting the GSD for assistance. Reading and understanding this guide before you begin is imperative for success.
* Label cables before disconnecting them from the current unmanaged switches.
* At least one Meraki managed switch must be installed in every meetinghouse worldwide
* Most meetinghouses will use a combination of the Meraki switch and current unmanaged switches. If there are enough Meraki ports for all data cables then remove all unmanaged switches.
* The installer will need access to a mobile computer or an iPad in order to activate and configure the new Meraki switch in Church Network Manager during the Meraki switch installation
* All wireless access points (APs) in the meetinghouse must connect directly to the a Meraki managed switch. Do not connect Cisco APs into the Meraki Switch. Upgrade Cisco APs to Meraki APs.
* Order an SPF module when ordering a Meraki Switch.
* If a second Meraki switch is needed in the same meetinghouse then two additional SFP modules will be needed.
* You will need a screwdriver and wood screws if you are mounting a switch to a wall, cabinet, or rack
* You will need a pen or pencil, tape and paper to create a cable mapping sheet of the meetinghouse data drops
* The Switch installation will be much easier if you have 2 people to identify where each data cable connects. Especially for the Wireless Access Points.
* The Meraki switch(es) installed in a meetinghouse will be logically tied to the Meraki Firewall in the Meraki Cloud Management application.
* Use of the 48-port switch is an exception and should only be used when the number of in-use Ethernet network lines running to a single location exceeds 22.

== SFP Modules ==
[[File:SFP Module.jpg|thumb|SFP Module –Approved Optics 1000BASET SFP transceiver module for Category 5e/6 copper wire]]

* Every switch will need a SFP module installed in port SFP 9 on the "8 Port switch", port SFP 25 on the "24 Port switch" and port SFP 49 on the “48 port switch.

* If a second Meraki switch is needed in the same meetinghouse then two additional SFP modules will be needed. Install the extra SFP module in Port 10 of the first Meraki 8 Port switch (or port SFP 26/SFP 50 on the first 24 or 48 port switch respectively) to connect the two Meraki Switches.
* To install the SFP module- open the lock, insert the module and close the lock. This will lock the SFP module into the switch.
* Connect the data cable to the SFP modules with the lock closed in the locked position.
* To remove an SFP module- open the lock and remove the module from the switch.

[[File:Insert SFP Module.jpg|thumb|Insert the SFP modules into the switch with the lock open and then close the lock]]
[[File:SFP Lock is Open.jpg|thumb|Lock is Open]]
[[File:SFP Lock is Closed.jpg|thumb|SFP lock is closed]]
[[File:SFP is closed with Data Cable connected.jpg|thumb|SFP is closed with Data Cable connected]]<gallery mode="slideshow">
File:Lock Diagram.png|Insert the SFP modules into the switch with the lock open and then close the lock
File:Lock is closed.png|SFP lock is open
File:SFP Lock is Open.jpg|SFP lock is closed
File:Lock with Data cable.png|SFP lock is closed with data cable connected
</gallery>

== Steps before installing Meraki Managed Switch (MS130-8P,-24P,-48P) ==

# Using tags or tape, identify and label the following possible cables connecting to:
## Wireless Access Points (tag as AP)
## Clerk’s and unit Leader’s offices (tag as Clerk or BP or SP)
## The HVAC, Door locks, and other Facility devices (tag as HVAC or Locks or FAC)
## Webcast equipment, Audio/Video distribution systems (tag as AV)
## The Family History Center (if present) (tag as FHC)
## The Seminary and Institute Teacher Offices and student classrooms (if present) (tag as S&I)
## FM office, Mission office, etc... (if present) (tag as FM or Mission)
## All other rooms in the meetinghouse (all of these will be public zone)
# This is a great opportunity to determine if all classroom connections are used or needed. If they are no longer used, then leave the cables disconnected to reduce the number of needed switch ports. If you leave a room disconnected, then add a sticker to the data jack faceplate in that room stating that it is disconnected.
# After labeling, take photos of the current configuration to inform the troubleshooting process if problems occur during the new switch installation.
## It is recommended that you leave a sheet of paper with the cable and port mappings next to the switch. This will facilitate future changes to the network. (example: Port 7 on the switch goes to the Clerk’s office, etc. )

Meraki Installation Guide 2025-2026

2026-04-03T17:01:59Z

HooperJM:

File:SFP Module.jpg

2026-04-03T16:58:47Z

HooperJM:

SFP Module –Approved Optics 1000BASET SFP transceiver module for Category 5e/6 copper wire

File:SFP is closed with Data Cable connected.jpg

2026-04-03T16:57:17Z

HooperJM:

SFP is closed with Data Cable connected

File:SFP Lock is Closed.jpg

2026-04-03T16:56:13Z

HooperJM:

SFP Lock is Closed

File:SFP Lock is Open.jpg

2026-04-03T16:54:32Z

HooperJM:

SFP lock is Open

File:Insert SFP Module.jpg

2026-04-03T16:51:29Z

HooperJM:

Insert the SFP modules into the switch with the lock open and then close the lock

Meraki Installation Guide 2024

2026-04-03T16:47:12Z

HooperJM: Replaced content with " Printable instructions for replacing networking hardware in meetinghouses: [https://tech.churchofjesuschrist.org/wiki/images/6/64/Meraki_MX_and_Switch_Installation_guide_2024.pdf Meraki MX and Switch Installation Guide 2024]"

Printable instructions for replacing networking hardware in meetinghouses:

[https://tech.churchofjesuschrist.org/wiki/images/6/64/Meraki_MX_and_Switch_Installation_guide_2024.pdf Meraki MX and Switch Installation Guide 2024]

Meraki Installation Guide 2025-2026

2026-04-03T16:46:52Z

HooperJM: A new article is born!

Meraki Installation Guide 2024

2026-04-03T16:41:07Z

HooperJM: Incremental saves, so I don't lose my progress.

Meraki Installation Guide 2024

2026-04-03T15:48:44Z

HooperJM:

Meraki Installation Guide 2024

2026-04-03T15:48:28Z

HooperJM:

Meraki Installation Guide 2024

2026-04-03T15:46:40Z

HooperJM:

Printable instructions for replacing networking hardware in meetinghouses:

[[Images/6/64/Meraki MX and Switch Installation guide 2024.pdf|Meraki MX and Switch Installation Guide 2024]]

[[:File:Meraki MX and Switch Installation guide 2024.pdf]]

Meetinghouse Networking

2026-04-03T15:45:24Z

HooperJM:

> [[Meetinghouse Technology]]

__NOTOC__
<div style="margin: 10px 0px 0px 0px;">
The content of this wiki is under construction and does not always reflect official Church information. This content is provided by product managers, moderators, and technology specialists and is subject to change. For more general content go to the Help Center at: https://www.ChurchofJesusChrist.org/help/support/meetinghouse-technology.

This section has articles to help manage network devices in each meetinghouse.
<div class="mw-category"><div class="multi-column">

<div class="no-column-break">
===Overviews===
*[https://www.churchofjesuschrist.org/tools/help/networking-overview?lang=eng Network Overview]
*[https://www.churchofjesuschrist.org/tools/help/cnm-overview?lang=eng CNM Overview]
*[https://www.churchofjesuschrist.org/tools/help/firewall-overview?lang=eng Firewall Overview]
*[https://www.churchofjesuschrist.org/tools/help/switch-overview?lang=eng Switch Overview]
*[https://www.churchofjesuschrist.org/tools/help/wap-overview?lang=eng WAP Overview]
*[[Approved Equipment List]]
*[[Network Status Report Guide]]
*[[Glossary]]
</div>

<div class="no-column-break">
===Networking/CNM===
*[[Network Training]]
*[[Church Network Manager]]
*[[Assigning a Static IP|Assigning a Static IP Address]]
*[[CNM Group Policies|CNM Group Policies]]
*[[Configuring Network and Sensor Alerts]]
*[[Favorites Feature In CNM]]
*[[Add ISP Info|Adding Internet Service Provider Information]]
*[[What is Church Network Manager]]
*[[Using the “No Networks” Report]]
*[[Adding a Facility or Workforce Zone to a Meraki Firewall]]

</div>
<div class="no-column-break">
===Firewall===
*[[Using Filters]]
*[[Firewall Activation on CNM]]
*[[Meraki Installation Guide 2024|New Firewall and Switch installation - 2024-2025]]
*[https://tech.churchofjesuschrist.org/wiki/images/9/92/Replace_Existing_Firewall.pdf Replace an existing installed firewall]
*[[Moving Firewalls]]
</div>
<div class="no-column-break">

===Switch===
*[[Unmanaged Switches]]
*[https://tech.churchofjesuschrist.org/wiki/images/0/0f/Meraki_MX_and_Switch_Installation_guide_NEW.pdf Managed Switch Installation]
</div>

</div>
</div>

<div class="mw-category">
<div class="multi-column">

<div class="no-column-break">
===Wireless Access Points===
*[[Activating WAP|Activating a WAP]]
*[[Disabling Wireless Access]]
*[[Meraki WAP]]
*[[Wireless Best Practices]]
*[[Lehi and Liahona Wireless Networks|Lehi and Liahona Wireless Networks]]
*[[IOTConnect SSID|IoTConnect Wireless networks]]
*[[Generate A WiFi Heatmap]]
</div>

<div class="no-column-break">
===Reference Articles===
*[[Facilities Zone]]
*[[Power Over Ethernet]]
*[[MAC Addresses]]
*[[Internet Speed Tests]]
*[[Improving Internet Access]]
*[[Network search|Search for a Network]]
*[[Portable Meetinghouse Network]]
</div>

*

*<div class="no-column-break">
===Troubleshooting===
*[[Troubleshooting Firewalls|Firewalls]]
*[[Troubleshooting Meraki switches|Switches]]
*[[Troubleshooting Wireless Access Points|Wireless Access Points (APs)]]
*[[Improving Bandwidth|Improving Bandwidth (8 Steps)]]
*[[Troubleshooting Connections]]
</div>

</div>
</div>

Meraki Installation Guide 2024

2026-04-03T15:44:03Z

HooperJM: Created page with "Printable instructions for replacing networking hardware in meetinghouses: :File:Meraki MX and Switch Installation guide 2024.pdf"

Printable instructions for replacing networking hardware in meetinghouses:

[[:File:Meraki MX and Switch Installation guide 2024.pdf]]

File:Meraki MX and Switch Installation guide 2024.pdf

2026-04-03T15:42:30Z

HooperJM:

Meetinghouse Networking

2026-04-03T15:30:15Z

HooperJM: Restored the missing file.

> [[Meetinghouse Technology]]

__NOTOC__
<div style="margin: 10px 0px 0px 0px;">
The content of this wiki is under construction and does not always reflect official Church information. This content is provided by product managers, moderators, and technology specialists and is subject to change. For more general content go to the Help Center at: https://www.ChurchofJesusChrist.org/help/support/meetinghouse-technology.

This section has articles to help manage network devices in each meetinghouse.
<div class="mw-category"><div class="multi-column">

<div class="no-column-break">
===Overviews===
*[https://www.churchofjesuschrist.org/tools/help/networking-overview?lang=eng Network Overview]
*[https://www.churchofjesuschrist.org/tools/help/cnm-overview?lang=eng CNM Overview]
*[https://www.churchofjesuschrist.org/tools/help/firewall-overview?lang=eng Firewall Overview]
*[https://www.churchofjesuschrist.org/tools/help/switch-overview?lang=eng Switch Overview]
*[https://www.churchofjesuschrist.org/tools/help/wap-overview?lang=eng WAP Overview]
*[[Approved Equipment List]]
*[[Network Status Report Guide]]
*[[Glossary]]
</div>

<div class="no-column-break">
===Networking/CNM===
*[[Network Training]]
*[[Church Network Manager]]
*[[Assigning a Static IP|Assigning a Static IP Address]]
*[[CNM Group Policies|CNM Group Policies]]
*[[Configuring Network and Sensor Alerts]]
*[[Favorites Feature In CNM]]
*[[Add ISP Info|Adding Internet Service Provider Information]]
*[[What is Church Network Manager]]
*[[Using the “No Networks” Report]]
*[[Adding a Facility or Workforce Zone to a Meraki Firewall]]

</div>
<div class="no-column-break">
===Firewall===
*[[Using Filters]]
*[[Firewall Activation on CNM]]
*[[Images/a/a7/Meraki MX and Switch Installation guide 2025.pdf|New Firewall and Switch installation - 2025]]
*[https://tech.churchofjesuschrist.org/wiki/images/9/92/Replace_Existing_Firewall.pdf Replace an existing installed firewall]
*[[Moving Firewalls]]
</div>
<div class="no-column-break">

===Switch===
*[[Unmanaged Switches]]
*[https://tech.churchofjesuschrist.org/wiki/images/0/0f/Meraki_MX_and_Switch_Installation_guide_NEW.pdf Managed Switch Installation]
</div>

</div>
</div>

<div class="mw-category">
<div class="multi-column">

<div class="no-column-break">
===Wireless Access Points===
*[[Activating WAP|Activating a WAP]]
*[[Disabling Wireless Access]]
*[[Meraki WAP]]
*[[Wireless Best Practices]]
*[[Lehi and Liahona Wireless Networks|Lehi and Liahona Wireless Networks]]
*[[IOTConnect SSID|IoTConnect Wireless networks]]
*[[Generate A WiFi Heatmap]]
</div>

<div class="no-column-break">
===Reference Articles===
*[[Facilities Zone]]
*[[Power Over Ethernet]]
*[[MAC Addresses]]
*[[Internet Speed Tests]]
*[[Improving Internet Access]]
*[[Network search|Search for a Network]]
*[[Portable Meetinghouse Network]]
</div>

*

*<div class="no-column-break">
===Troubleshooting===
*[[Troubleshooting Firewalls|Firewalls]]
*[[Troubleshooting Meraki switches|Switches]]
*[[Troubleshooting Wireless Access Points|Wireless Access Points (APs)]]
*[[Improving Bandwidth|Improving Bandwidth (8 Steps)]]
*[[Troubleshooting Connections]]
</div>

</div>
</div>

File:Meraki MX and Switch Installation guide 2025.pdf

2026-04-03T15:27:05Z

HooperJM: HooperJM uploaded a new version of File:Meraki MX and Switch Installation guide 2025.pdf

Meetinghouse Network Upgrade

2026-03-04T18:54:12Z

HooperJM: /* Frequently Asked Questions */

== Summary ==
In the coming months, your unit's building will receive a network and Wi‑Fi upgrade to provide a faster internet (according to need and availability), and a more secure and reliable network experience for everyone. As part of this work, some physical network jacks will be removed or disabled. Devices in leaders’ offices, clerk offices, and other locations—such as resource centers—may need to connect to the Wi‑Fi network after the upgrade.

== Purpose(s) ==

* '''Improved teaching and learning experiences'''- This upgrade is designed to support gospel learning by improving the ability to stream Church videos for lessons, live meeting broadcasts, and provide a backbone for translation technologies. The entire building will receive enhanced Wi‑Fi coverage. And where internet speed increases are needed, they will be increased, based on the availability of faster service plans.
* '''Wireless preferred'''- The benefits of a wireless preferred approach include flexibility for the end-users and long-term cost savings for the Church. Network drops are expensive to install, maintain, and upgrade, far exceeding the cost of the networking hardware itself. By minimizing the number network jacks, we reduce the overall cost of the network. And by increasing the number of access points in meetinghouses, the end-users will find greater flexibility for the placement of equipment and other uses of the network.
* '''Device security and continued operation'''- The access points (MR33) and switches (MS120) in most meetinghouses will no longer be supported by Meraki and need to be replaced. By upgrading the equipment on schedule, we ensure continued operation, as well as security updates.

== Scope ==

* Replace expiring, obsolete, and unsupported hardware.
* Provide comprehensive Wi-Fi coverage throughout each meetinghouse.
* Ensure cabling meets the Cat6A standard.
* Install a network cable to the rear of each chapel to enable streaming now or in the future. (Cameras not provided as part of this project. Just the network connection).
* Ensure internet speeds are at least 500 Mbps- Where internet service providers are available at a reasonable price.
* Provide a standard, clean, and orderly networking rack.
* Ensure rack locations meet local building code requirements, are secure, and have sufficient air flow.
* Re-install and configure network in CNM. Vendor is to ensure the network is functional.
* Provide helpful artifacts in CNM: Network diagrams, cable test results, pictures of the rack and location, and more.
* Fill holes in ceiling tiles, and patch holes in walls from old equipment.
* Vendors are required to remove old equipment and cabling.

== How to prepare ==

* Ensure all of your devices are Wi-Fi ready. This includes:
** Clerk computers
** Printers
** Copy machines in the Materials Resource Center
** Smart TV's and set-top streaming devices
** Any other device your unit depends on for Church purposes
* You may need to purchase an ethernet to Wi-Fi adapter from a local retailer if your device (eg copier) doesn't have built-in wireless.
* In some rare cases, you might need to upgrade or replace older equipment.
* As a contingency, note the IP and Mac addresses of any devices with static IP assignments. This upgrade ''should'' NOT affect IP ranges. But in rare cases, IP assignments might be affected. If you make note ahead of time, you'll be able to re-assign devices post-installation.
* '''*Note*''' If your network still includes a FAC16 zone (Facility zone with 16 addresses), please upgrade at your earliest convenience to a FAC32 zone, through the "upgrade IP range" link in Church Network Manager (CNM). This change can be made irrespective of the network upgrade, but you will definitely need to make a note of all devices, in particular door access systems that have a static IP reservation assigned. Write down their Mac addresses and their IP addresses, and follow the in-app instructions to ensure a successful upgrade.

== What to do after the installation ==

* Please utilize CNM to ensure the network is functioning properly, and all necessary devices are connected to the network
* '''*Note*''': You do not need to fix issues with the physical installation. Contact your Facility Manager, who will require the contractors to address any of the following issues:
** Damaged or dead cables
** Cables installed in walkways or present any kind of a safety hazard
** Cables run or access points that appear to be installed in the wrong place
** Old obsolete cables or hardware (access points) that were not removed after being disconnected
** Unpatched holes in the ceilings or walls.
** Other damage or clutter from the installation that was not repaired or removed by the vendor

== Frequently Asked Questions ==

* '''Which kinds of facilities are included in this network upgrade initiative?'''
** All meetinghouses, FM offices, and standard Family History Centers (FHC)
* '''Will this make my internet faster?'''
** The newer equipment is capable of incrementally faster throughput. Additionally, ICS is also working with Internet Service Providers (ISP's) to increase speeds where available and financially feasible. The target speeds are at least 500Mbps download, and at least 100Mbps upload. This is highly dependent on the availability of ISP's at the site.
* '''What about the network jack in the pulpit?'''
** The network jack at the pulpit may not be reconnected as part of this project. While the pulpit is part of the AV system, if the existing cable does not reach the new or current network rack location, it may remain disconnected until the AV system is replaced or upgraded.
* '''Will my network rack be moved?'''
** Generally, network racks will be left in place. The following reasons might require a network rack to be relocated:
*** To meet building code safety requirements
*** Improve security (behind a locked door)
*** Ensure a clean, safe environment with sufficient airflow for cooling
* '''Are there any exclusions?'''
** Buildings proposed for redeployment within 2 years of the scheduled upgrades will not be upgraded.
* '''How are the network upgrades being funded?'''
** The Meetinghouse Facilities Department is funding all network upgrades included in this project. FM groups will not be invoiced for this project.
* '''How long does an upgrade take?'''
** The average upgrade takes approximately 2-3 days for an individual site. However, because each site is unique, this will vary.
* '''Will we know exactly when the vendors will be at each location to upgrade the networks?'''
** Vendors have been asked to inform FM groups with a 2 week window, but with so many upgrades happening simultaneously, this is difficult to enforce.
*'''What if any current Meraki equipment breaks before the new equipment is installed? Is there a contingency plan?'''
**FMs should use operations funds to do a 1:1 replacement of any Meraki equipment (firewall, switch or access point) that malfunctions before the network upgrade is performed. This helps ensure the church adheres to international accounting regulations (FS6110).
*'''How are network upgrades being funded?'''
**MFD is funding all network upgrades through a HQ-sponsored initiative. FM groups will not be invoiced for this project.
*'''What time of day will the vendors perform the work?'''
**The work typically is performed during business hours, so units shouldn’t see vendor technicians, ladders, wires, etc. during evening or weekend activities.
*'''How many access points will each building get?'''
**ICS has generated heatmaps based on the floorplan of each building, and will install the appropriate number of access points to ensure comprehensive coverage. Most buildings will receive between 7-9, with larger buildings receiving more, and smaller buildings requiring fewer.
*'''Why are my access points placed where they are?'''
**Each meetinghouse has been reviewed for uniform wireless coverage, and a heatmap for each standard plan and custom plan has been developed. The installers have been instructed to follow the heatmaps for AP placement in each building and are allowed to install each AP within 3 feet of the locations identified on each heatmap.
*'''Will any IP addresses change as a result of the upgrade?'''
**Vendors have been provided with instructions that will preserve IP addresses on the network. If you find that your IP addresses have changed, please communicate that through your FM. *NOTE*: If your network still contains a FAC16 zone, we encourage you to select the "Upgrade IP range" link in CNM and upgrade to a FAC32 zone as soon as possible. Please be sure to not any IP reservations as instructed in the onscreen dialogues when doing this upgrade. This process will change your IP addresses, but is not part of the process assigned to vendors.
*'''What equipment will still be connected to the network with cabling?'''
**If these systems listed below are currently connected to the network at the time the network is upgraded, they will continue to be connected to the network with cabling:
***Audio/visual systems, including cameras mounted in approved locations in the chapel
***Door access systems
***HVAC systems and controls
*'''What cables will NOT be reconnected after the network upgrade?'''
**You will need to connect the following devices to the Wi-Fi network:
***Clerk/bishop offices computers and printers
***Materials center copies and printers
***Cables connected to the network jack at the pulpit or at the pulpit controls (see the next FAQ)
***Non-standard equipment, such as unmanaged switches, TVs, older audio/visual systems that aren’t currently connected to the network.
***Additionally, custom or non-standard equipment that may have been installed by a local leader or technology specialist will not be reconnected.
***FMs have been instructed to communicate these changes with stake leaders and technology specialists to ensure they are well-informed of the changes in cabling standards and connectivity practices. Additionally, local leaders and stake technology specialists will need to prioritize what else gets connected in the building. It will be their responsibility to reconnect these other devices.

Meetinghouse Network Upgrade

2026-02-26T22:53:26Z

HooperJM: /* Frequently Asked Questions */

== Summary ==
In the coming months, your unit's building will receive a network and Wi‑Fi upgrade to provide a faster internet (according to need and availability), and a more secure and reliable network experience for everyone. As part of this work, some physical network jacks will be removed or disabled. Devices in leaders’ offices, clerk offices, and other locations—such as resource centers—may need to connect to the Wi‑Fi network after the upgrade.

== Purpose(s) ==

* '''Improved teaching and learning experiences'''- This upgrade is designed to support gospel learning by improving the ability to stream Church videos for lessons, live meeting broadcasts, and provide a backbone for translation technologies. The entire building will receive enhanced Wi‑Fi coverage. And where internet speed increases are needed, they will be increased, based on the availability of faster service plans.
* '''Wireless preferred'''- The benefits of a wireless preferred approach include flexibility for the end-users and long-term cost savings for the Church. Network drops are expensive to install, maintain, and upgrade, far exceeding the cost of the networking hardware itself. By minimizing the number network jacks, we reduce the overall cost of the network. And by increasing the number of access points in meetinghouses, the end-users will find greater flexibility for the placement of equipment and other uses of the network.
* '''Device security and continued operation'''- The access points (MR33) and switches (MS120) in most meetinghouses will no longer be supported by Meraki and need to be replaced. By upgrading the equipment on schedule, we ensure continued operation, as well as security updates.

== Scope ==

* Replace expiring, obsolete, and unsupported hardware.
* Provide comprehensive Wi-Fi coverage throughout each meetinghouse.
* Ensure cabling meets the Cat6A standard.
* Install a network cable to the rear of each chapel to enable streaming now or in the future. (Cameras not provided as part of this project. Just the network connection).
* Ensure internet speeds are at least 500 Mbps- Where internet service providers are available at a reasonable price.
* Provide a standard, clean, and orderly networking rack.
* Ensure rack locations meet local building code requirements, are secure, and have sufficient air flow.
* Re-install and configure network in CNM. Vendor is to ensure the network is functional.
* Provide helpful artifacts in CNM: Network diagrams, cable test results, pictures of the rack and location, and more.
* Fill holes in ceiling tiles, and patch holes in walls from old equipment.
* Vendors are required to remove old equipment and cabling.

== How to prepare ==

* Ensure all of your devices are Wi-Fi ready. This includes:
** Clerk computers
** Printers
** Copy machines in the Materials Resource Center
** Smart TV's and set-top streaming devices
** Any other device your unit depends on for Church purposes
* You may need to purchase an ethernet to Wi-Fi adapter from a local retailer if your device (eg copier) doesn't have built-in wireless.
* In some rare cases, you might need to upgrade or replace older equipment.
* As a contingency, note the IP and Mac addresses of any devices with static IP assignments. This upgrade ''should'' NOT affect IP ranges. But in rare cases, IP assignments might be affected. If you make note ahead of time, you'll be able to re-assign devices post-installation.
* '''*Note*''' If your network still includes a FAC16 zone (Facility zone with 16 addresses), please upgrade at your earliest convenience to a FAC32 zone, through the "upgrade IP range" link in Church Network Manager (CNM). This change can be made irrespective of the network upgrade, but you will definitely need to make a note of all devices, in particular door access systems that have a static IP reservation assigned. Write down their Mac addresses and their IP addresses, and follow the in-app instructions to ensure a successful upgrade.

== What to do after the installation ==

* Please utilize CNM to ensure the network is functioning properly, and all necessary devices are connected to the network
* '''*Note*''': You do not need to fix issues with the physical installation. Contact your Facility Manager, who will require the contractors to address any of the following issues:
** Damaged or dead cables
** Cables installed in walkways or present any kind of a safety hazard
** Cables run or access points that appear to be installed in the wrong place
** Old obsolete cables or hardware (access points) that were not removed after being disconnected
** Unpatched holes in the ceilings or walls.
** Other damage or clutter from the installation that was not repaired or removed by the vendor

== Frequently Asked Questions ==

* '''Question''': Which kinds of facilities are included in this network upgrade initiative?
* Answer: All meetinghouses, FM offices, and standard Family History Centers (FHC)
* '''Question''': Will this make my internet faster?
* Answer: The newer equipment is capable of incrementally faster throughput. Additionally, ICS is also working with Internet Service Providers (ISP's) to increase speeds where available and financially feasible. The target speeds are at least 500Mbps download, and at least 100Mbps upload. This is highly dependent on the availability of ISP's at the site.
* '''Question''': What about the network jack in the pulpit?
* Answer: The network jack at the pulpit may not be reconnected as part of this project. While the pulpit is part of the AV system, if the existing cable does not reach the new or current network rack location, it may remain disconnected until the AV system is replaced or upgraded.
* '''Question:''' Will my network rack be moved?
* Answer: Generally, network racks will be left in place. The following reasons might require a network rack to be relocated:
** To meet building code safety requirements
** Improve security (behind a locked door)
** Ensure a clean, safe environment with sufficient airflow for cooling
* '''Question''': Are there any exclusions?
* Answer: Buildings proposed for redeployment within 2 years of the scheduled upgrades will not be upgraded.
* '''Question''': How are the network upgrades being funded?
* Answer: The Meetinghouse Facilities Department is funding all network upgrades included in this project. FM groups will not be invoiced for this project.
* '''Question''': How long does an upgrade take?
* Answer: The average upgrade takes approximately 2-3 days for an individual site. However, because each site is unique, this will vary.
* '''Question:''' Will we know exactly when the vendors will be at each location to upgrade the networks?
* Answer: Vendors have been asked to inform FM groups with a 2 week window, but with so many upgrades happening simultaneously, this is difficult to enforce.
*'''Question:''' What if any current Meraki equipment breaks before the new equipment is installed? Is there a contingency plan?
*Answer: FMs should use operations funds to do a 1:1 replacement of any Meraki equipment (firewall, switch or access point) that malfunctions before the network upgrade is performed. This helps ensure the church adheres to international accounting regulations (FS6110).
*'''Question:''' How are network upgrades being funded?
*Answer: MFD is funding all network upgrades through a HQ-sponsored initiative. FM groups will not be invoiced for this project.
*'''Question:''' What time of day will the vendors perform the work?
*Answer: The work typically is performed during business hours, so units shouldn’t see vendor technicians, ladders, wires, etc. during evening or weekend activities.
*'''Question:''' How many access points will each building get?
*Answer: ICS has generated heatmaps based on the floorplan of each building, and will install the appropriate number of access points to ensure comprehensive coverage. Most buildings will receive between 7-9, with larger buildings receiving more, and smaller buildings requiring fewer.
*'''Question:''' Why are my access points placed where they are?
*Answer: Each meetinghouse has been reviewed for uniform wireless coverage, and a heatmap for each standard plan and custom plan has been developed. The installers have been instructed to follow the heatmaps for AP placement in each building and are allowed to install each AP within 3 feet of the locations identified on each heatmap.
*'''Question:''' Will any IP addresses change as a result of the upgrade?
*Answer: Vendors have been provided with instructions that will preserve IP addresses on the network. If you find that your IP addresses have changed, please communicate that through your FM. *NOTE*: If your network still contains a FAC16 zone, we encourage you to select the "Upgrade IP range" link in CNM and upgrade to a FAC32 zone as soon as possible. Please be sure to not any IP reservations as instructed in the onscreen dialogues when doing this upgrade. This process will change your IP addresses, but is not part of the process assigned to vendors.
*'''Question:''' What equipment will still be connected to the network with cabling?
*Answer: If these systems listed below are currently connected to the network at the time the network is upgraded, they will continue to be connected to the network with cabling:
**Audio/visual systems, including cameras mounted in approved locations in the chapel
**Door access systems
**HVAC systems and controls
*'''Question:''' What cables will NOT be reconnected after the network upgrade?
*Answer: You will need to connect the following devices to the Wi-Fi network:
**Clerk/bishop offices computers and printers
**Materials center copies and printers
**Cables connected to the network jack at the pulpit or at the pulpit controls (see the next FAQ)
**Non-standard equipment, such as unmanaged switches, TVs, older audio/visual systems that aren’t currently connected to the network.
**Additionally, custom or non-standard equipment that may have been installed by a local leader or technology specialist will not be reconnected.
**FMs have been instructed to communicate these changes with stake leaders and technology specialists to ensure they are well-informed of the changes in cabling standards and connectivity practices. Additionally, local leaders and stake technology specialists will need to prioritize what else gets connected in the building. It will be their responsibility to reconnect these other devices.

Meetinghouse Network Upgrade

2026-02-26T22:52:56Z

HooperJM:

== Summary ==
In the coming months, your unit's building will receive a network and Wi‑Fi upgrade to provide a faster internet (according to need and availability), and a more secure and reliable network experience for everyone. As part of this work, some physical network jacks will be removed or disabled. Devices in leaders’ offices, clerk offices, and other locations—such as resource centers—may need to connect to the Wi‑Fi network after the upgrade.

== Purpose(s) ==

* '''Improved teaching and learning experiences'''- This upgrade is designed to support gospel learning by improving the ability to stream Church videos for lessons, live meeting broadcasts, and provide a backbone for translation technologies. The entire building will receive enhanced Wi‑Fi coverage. And where internet speed increases are needed, they will be increased, based on the availability of faster service plans.
* '''Wireless preferred'''- The benefits of a wireless preferred approach include flexibility for the end-users and long-term cost savings for the Church. Network drops are expensive to install, maintain, and upgrade, far exceeding the cost of the networking hardware itself. By minimizing the number network jacks, we reduce the overall cost of the network. And by increasing the number of access points in meetinghouses, the end-users will find greater flexibility for the placement of equipment and other uses of the network.
* '''Device security and continued operation'''- The access points (MR33) and switches (MS120) in most meetinghouses will no longer be supported by Meraki and need to be replaced. By upgrading the equipment on schedule, we ensure continued operation, as well as security updates.

== Scope ==

* Replace expiring, obsolete, and unsupported hardware.
* Provide comprehensive Wi-Fi coverage throughout each meetinghouse.
* Ensure cabling meets the Cat6A standard.
* Install a network cable to the rear of each chapel to enable streaming now or in the future. (Cameras not provided as part of this project. Just the network connection).
* Ensure internet speeds are at least 500 Mbps- Where internet service providers are available at a reasonable price.
* Provide a standard, clean, and orderly networking rack.
* Ensure rack locations meet local building code requirements, are secure, and have sufficient air flow.
* Re-install and configure network in CNM. Vendor is to ensure the network is functional.
* Provide helpful artifacts in CNM: Network diagrams, cable test results, pictures of the rack and location, and more.
* Fill holes in ceiling tiles, and patch holes in walls from old equipment.
* Vendors are required to remove old equipment and cabling.

== How to prepare ==

* Ensure all of your devices are Wi-Fi ready. This includes:
** Clerk computers
** Printers
** Copy machines in the Materials Resource Center
** Smart TV's and set-top streaming devices
** Any other device your unit depends on for Church purposes
* You may need to purchase an ethernet to Wi-Fi adapter from a local retailer if your device (eg copier) doesn't have built-in wireless.
* In some rare cases, you might need to upgrade or replace older equipment.
* As a contingency, note the IP and Mac addresses of any devices with static IP assignments. This upgrade ''should'' NOT affect IP ranges. But in rare cases, IP assignments might be affected. If you make note ahead of time, you'll be able to re-assign devices post-installation.
* '''*Note*''' If your network still includes a FAC16 zone (Facility zone with 16 addresses), please upgrade at your earliest convenience to a FAC32 zone, through the "upgrade IP range" link in Church Network Manager (CNM). This change can be made irrespective of the network upgrade, but you will definitely need to make a note of all devices, in particular door access systems that have a static IP reservation assigned. Write down their Mac addresses and their IP addresses, and follow the in-app instructions to ensure a successful upgrade.

== What to do after the installation ==

* Please utilize CNM to ensure the network is functioning properly, and all necessary devices are connected to the network
* '''*Note*''': You do not need to fix issues with the physical installation. Contact your Facility Manager, who will require the contractors to address any of the following issues:
** Damaged or dead cables
** Cables installed in walkways or present any kind of a safety hazard
** Cables run or access points that appear to be installed in the wrong place
** Old obsolete cables or hardware (access points) that were not removed after being disconnected
** Unpatched holes in the ceilings or walls.
** Other damage or clutter from the installation that was not repaired or removed by the vendor

== Frequently Asked Questions ==

* '''Question''': Which kinds of facilities are included in this network upgrade initiative?
* Answer: All meetinghouses, FM offices, and standard Family History Centers (FHC)
* '''Question''': Will this make my internet faster?
* Answer: The newer equipment is capable of incrementally faster throughput. Additionally, ICS is also working with Internet Service Providers (ISP's) to increase speeds where available and financially feasible. The target speeds are at least 500Mbps download, and at least 100Mbps upload. This is highly dependent on the availability of ISP's at the site.
* '''Question''': What about the network jack in the pulpit?
* Answer: The network jack at the pulpit may not be reconnected as part of this project. While the pulpit is part of the AV system, if the existing cable does not reach the new or current network rack location, it may remain disconnected until the AV system is replaced or upgraded.
* '''Question:''' Will my network rack be moved?
* Answer: Generally, network racks will be left in place. The following reasons might require a network rack to be relocated:
** To meet building code safety requirements
** Improve security (behind a locked door)
** Ensure a clean, safe environment with sufficient airflow for cooling
* '''Question''': Are there any exclusions?
* Answer: Buildings proposed for redeployment within 2 years of the scheduled upgrades will not be upgraded.
* '''Question''': How are the network upgrades being funded?
* Answer: The Meetinghouse Facilities Department is funding all network upgrades included in this project. FM groups will not be invoiced for this project.
* '''Question''': How long does an upgrade take?
* Answer: The average upgrade takes approximately 2-3 days for an individual site. However, because each site is unique, this will vary.
* '''Question:''' Will we know exactly when the vendors will be at each location to upgrade the networks?
* Answer: Vendors have been asked to inform FM groups with a 2 week window, but with so many upgrades happening simultaneously, this is difficult to enforce.
*'''Question:''' What if any current Meraki equipment breaks before the new equipment is installed? Is there a contingency plan?
*Answer: FMs should use operations funds to do a 1:1 replacement of any Meraki equipment (firewall, switch or access point) that malfunctions before the network upgrade is performed. This helps ensure the church adheres to international accounting regulations.
*'''Question:''' How are network upgrades being funded?
*Answer: MFD is funding all network upgrades through a HQ-sponsored initiative. FM groups will not be invoiced for this project.
*'''Question:''' What time of day will the vendors perform the work?
*Answer: The work typically is performed during business hours, so units shouldn’t see vendor technicians, ladders, wires, etc. during evening or weekend activities.
*'''Question:''' How many access points will each building get?
*Answer: ICS has generated heatmaps based on the floorplan of each building, and will install the appropriate number of access points to ensure comprehensive coverage. Most buildings will receive between 7-9, with larger buildings receiving more, and smaller buildings requiring fewer.
*'''Question:''' Why are my access points placed where they are?
*Answer: Each meetinghouse has been reviewed for uniform wireless coverage, and a heatmap for each standard plan and custom plan has been developed. The installers have been instructed to follow the heatmaps for AP placement in each building and are allowed to install each AP within 3 feet of the locations identified on each heatmap.
*'''Question:''' Will any IP addresses change as a result of the upgrade?
*Answer: Vendors have been provided with instructions that will preserve IP addresses on the network. If you find that your IP addresses have changed, please communicate that through your FM. *NOTE*: If your network still contains a FAC16 zone, we encourage you to select the "Upgrade IP range" link in CNM and upgrade to a FAC32 zone as soon as possible. Please be sure to not any IP reservations as instructed in the onscreen dialogues when doing this upgrade. This process will change your IP addresses, but is not part of the process assigned to vendors.
*'''Question:''' What equipment will still be connected to the network with cabling?
*Answer: If these systems listed below are currently connected to the network at the time the network is upgraded, they will continue to be connected to the network with cabling:
**Audio/visual systems, including cameras mounted in approved locations in the chapel
**Door access systems
**HVAC systems and controls
*'''Question:''' What cables will NOT be reconnected after the network upgrade?
*Answer: You will need to connect the following devices to the Wi-Fi network:
**Clerk/bishop offices computers and printers
**Materials center copies and printers
**Cables connected to the network jack at the pulpit or at the pulpit controls (see the next FAQ)
**Non-standard equipment, such as unmanaged switches, TVs, older audio/visual systems that aren’t currently connected to the network.
**Additionally, custom or non-standard equipment that may have been installed by a local leader or technology specialist will not be reconnected.
**FMs have been instructed to communicate these changes with stake leaders and technology specialists to ensure they are well-informed of the changes in cabling standards and connectivity practices. Additionally, local leaders and stake technology specialists will need to prioritize what else gets connected in the building. It will be their responsibility to reconnect these other devices.

Meetinghouse Network Upgrade

2026-02-26T22:48:51Z

HooperJM: /* Frequently Asked Questions */

== Summary ==
In the coming months, your unit's building will receive a network and Wi‑Fi upgrade to provide a faster internet (according to need and availability), and a more secure and reliable network experience for everyone. As part of this work, some physical network jacks will be removed or disabled. Devices in leaders’ offices, clerk offices, and other locations—such as resource centers—may need to connect to the Wi‑Fi network after the upgrade.

== Purpose(s) ==

* '''Improved teaching and learning experiences'''- This upgrade is designed to support gospel learning by improving the ability to stream Church videos for lessons, live meeting broadcasts, and provide a backbone for translation technologies. The entire building will receive enhanced Wi‑Fi coverage. And where internet speed increases are needed, they will be increased, based on the availability of faster service plans.
* '''Wireless preferred'''- The benefits of a wireless preferred approach include flexibility for the end-users and long-term cost savings for the Church. Network drops are expensive to install, maintain, and upgrade, far exceeding the cost of the networking hardware itself. By minimizing the number network jacks, we reduce the overall cost of the network. And by increasing the number of access points in meetinghouses, the end-users will find greater flexibility for the placement of equipment and other uses of the network.
* '''Device security and continued operation'''- The access points (MR33) and switches (MS120) in most meetinghouses will no longer be supported by Meraki and need to be replaced. By upgrading the equipment on schedule, we ensure continued operation, as well as security updates.

== Scope ==

* Replace expiring, obsolete, and unsupported hardware.
* Provide comprehensive Wi-Fi coverage throughout each meetinghouse.
* Ensure cabling meets the Cat6A standard.
* Install a network cable to the rear of each chapel to enable streaming now or in the future. (Cameras not provided as part of this project. Just the network connection).
* Ensure internet speeds are at least 500 Mbps- Where internet service providers are available at a reasonable price.
* Provide a standard, clean, and orderly networking rack.
* Ensure rack locations meet local building code requirements, are secure, and have sufficient air flow.
* Re-install and configure network in CNM. Vendor is to ensure the network is functional.
* Provide helpful artifacts in CNM: Network diagrams, cable test results, pictures of the rack and location, and more.
* Fill holes in ceiling tiles, and patch holes in walls from old equipment.
* Vendors are required to remove old equipment and cabling.

== How to prepare ==

* Ensure all of your devices are Wi-Fi ready. This includes:
** Clerk computers
** Printers
** Copy machines in the Materials Resource Center
** Smart TV's and set-top streaming devices
** Any other device your unit depends on for Church purposes
* You may need to purchase an ethernet to Wi-Fi adapter from a local retailer if your device (eg copier) doesn't have built-in wireless.
* In some rare cases, you might need to upgrade or replace older equipment.
* As a contingency, note the IP and Mac addresses of any devices with static IP assignments. This upgrade ''should'' NOT affect IP ranges. But in rare cases, IP assignments might be affected. If you make note ahead of time, you'll be able to re-assign devices post-installation.
* '''*Note*''' If your network still includes a FAC16 zone (Facility zone with 16 addresses), please upgrade at your earliest convenience to a FAC32 zone, through the "upgrade IP range" link in Church Network Manager (CNM). This change can be made irrespective of the network upgrade, but you will definitely need to make a note of all devices, in particular door access systems that have a static IP reservation assigned. Write down their Mac addresses and their IP addresses, and follow the in-app instructions to ensure a successful upgrade.

== What to do after the installation ==

* Please utilize CNM to ensure the network is functioning properly, and all necessary devices are connected to the network
* '''*Note*''': You do not need to fix issues with the physical installation. Contact your Facility Manager, who will require the contractors to address any of the following issues:
** Damaged or dead cables
** Cables installed in walkways or present any kind of a safety hazard
** Cables run or access points that appear to be installed in the wrong place
** Old obsolete cables or hardware (access points) that were not removed after being disconnected
** Unpatched holes in the ceilings or walls.
** Other damage or clutter from the installation that was not repaired or removed by the vendor

== Frequently Asked Questions ==

* '''Question''': Which kinds of facilities are included in this network upgrade initiative?
* Answer: All meetinghouses, FM offices, and standard Family History Centers (FHC)
* '''Question''': Will this make my internet faster?
* Answer: The newer equipment is capable of incrementally faster throughput. Additionally, ICS is also working with Internet Service Providers (ISP's) to increase speeds where available and financially feasible. The target speeds are at least 500Mbps download, and at least 100Mbps upload. This is highly dependent on the availability of ISP's at the site.
* '''Question''': What about the network jack in the pulpit?
* Answer: The network jack at the pulpit may not be reconnected as part of this project. While the pulpit is part of the AV system, if the existing cable does not reach the new or current network rack location, it may remain disconnected until the AV system is replaced or upgraded.
* '''Question:''' Will my network rack be moved?
* Answer: Generally, network racks will be left in place. The following reasons might require a network rack to be relocated:
** To meet building code safety requirements
** Improve security (behind a locked door)
** Ensure a clean, safe environment with sufficient airflow for cooling
* '''Question''': Are there any exclusions?
* Answer: Buildings proposed for redeployment within 2 years of the scheduled upgrades will not be upgraded.
* '''Question''': How are the network upgrades being funded?
* Answer: The Meetinghouse Facilities Department is funding all network upgrades included in this project. FM groups will not be invoiced for this project.
* '''Question''': How long does an upgrade take?
* Answer: The average upgrade takes approximately 2-3 days for an individual site. However, because each site is unique, this will vary.
* '''Question:''' Will we know exactly when the vendors will be at each location to upgrade the networks?
* Answer: Vendors have been asked to inform FM groups with a 2 week window, but with so many upgrades happening simultaneously, this is difficult to enforce.
*'''Question:''' What if any current Meraki equipment breaks before the new equipment is installed? Is there a contingency plan?
*Answer: FMs should use operations funds to do a 1:1 replacement of any Meraki equipment (firewall, switch or access point) that malfunctions before the network upgrade is performed. This helps ensure the church adheres to FS 6110.
*'''Question:''' How are network upgrades being funded?
*Answer: MFD is funding all network upgrades through a HQ-sponsored initiative. FM groups will not be invoiced for this project.
*'''Question:''' What time of day will the vendors perform the work?
*Answer: The work typically is performed during business hours, so units shouldn’t see vendor technicians, ladders, wires, etc. during evening or weekend activities.
*'''Question:''' How many access points will each building get?
*Answer: ICS has generated heatmaps based on the floorplan of each building, and will install the appropriate number of access points to ensure comprehensive coverage. Most buildings will receive between 7-9, with larger buildings receiving more, and smaller buildings requiring fewer.
*'''Question:''' Why are my access points placed where they are?
*Answer: Each meetinghouse has been reviewed for uniform wireless coverage, and a heatmap for each standard plan and custom plan has been developed. The installers have been instructed to follow the heatmaps for AP placement in each building and are allowed to install each AP within 3 feet of the locations identified on each heatmap.
*'''Question:''' Will any IP addresses change as a result of the upgrade?
*Answer: Vendors have been provided with instructions that will preserve IP addresses on the network. If you find that your IP addresses have changed, please communicate that through your FM. *NOTE*: If your network still contains a FAC16 zone, we encourage you to select the "Upgrade IP range" link in CNM and upgrade to a FAC32 zone as soon as possible. Please be sure to not any IP reservations as instructed in the onscreen dialogues when doing this upgrade. This process will change your IP addresses, but is not part of the process assigned to vendors.
*'''Question:''' What equipment will still be connected to the network with cabling?
*Answer: If these systems listed below are currently connected to the network at the time the network is upgraded, they will continue to be connected to the network with cabling:
**Audio/visual systems, including cameras mounted in approved locations in the chapel
**Door access systems
**HVAC systems and controls
*'''Question:''' What cables will NOT be reconnected after the network upgrade?
*Answer: You will need to connect the following devices to the Wi-Fi network:
**Clerk/bishop offices computers and printers
**Materials center copies and printers
**Cables connected to the network jack at the pulpit or at the pulpit controls (see the next FAQ)
**Non-standard equipment, such as unmanaged switches, TVs, older audio/visual systems that aren’t currently connected to the network.
**Additionally, custom or non-standard equipment that may have been installed by a local leader or technology specialist will not be reconnected.
**FMs have been instructed to communicate these changes with stake leaders and technology specialists to ensure they are well-informed of the changes in cabling standards and connectivity practices. Additionally, local leaders and stake technology specialists will need to prioritize what else gets connected in the building. It will be their responsibility to reconnect these other devices.

Meetinghouse Network Upgrade

2026-02-26T22:31:21Z

HooperJM: /* Frequently Asked Questions */

Meetinghouse Network Upgrade

2026-02-26T22:27:40Z

HooperJM: /* How to prepare */

Meetinghouse Network Upgrade

2026-02-26T22:26:40Z

HooperJM: /* Scope */

Meetinghouse Network Upgrade

2026-02-26T22:21:58Z

HooperJM: /* Scope */

Meetinghouse Network Upgrade

2026-02-26T22:18:10Z

HooperJM: /* Frequently Asked Questions */

Meetinghouse Network Upgrade

2026-02-26T22:16:41Z

HooperJM: /* Frequently Asked Questions */

Meetinghouse Network Upgrade

2026-02-26T18:07:10Z

HooperJM: /* Purpose(s) */

Meetinghouse Network Upgrade

2026-02-19T21:11:25Z

HooperJM: /* How to prepare */

Meetinghouse Network Upgrade

2026-02-19T21:10:20Z

HooperJM: /* How to prepare */

Meetinghouse Network Upgrade

2026-02-19T00:45:55Z

HooperJM:

Meetinghouse Network Upgrade

2026-02-19T00:39:36Z

HooperJM:

CNM Group Policies

2026-02-17T22:37:10Z

HooperJM: /* STEP 1: IDENTIFY DEVICE INFORMATION */ Removed password information.

> [[Meetinghouse Technology]] > [[Meetinghouse Networking]]

=== Group Policies in CNM: ===

#'''NoSplash Group Policy:''' By-Pass the Terms of Use (Splash Screen)
## Access to the Liahona wireless network requires users to accept the terms of use (splash page), which emphasize the purposes of Church-provided internet access.
## Some devices, like printers, do not have a screen to accept the terms of use. In these cases, the device’s MAC address must be manually added to the NoSplash Group Policy in CNM to bypass the terms of use splash page.
# '''IoT Group Group Policy:''' [[IOTConnect SSID|Instructions to create an IoT Group Policy]]<br> <br>

== Steps to create a NoSplash Group Policy: ==

===='''STEP 1: IDENTIFY DEVICE INFORMATION'''====

# Identify the device that must connect wirelessly to the network that does not support click-through navigation to the splash page. (In the device's Wi-Fi Settings, “forget” the LDSAccess network if it is still connected)
# Connect the device to the wireless network by selecting “Liahona” and entering the password.
# Collect the device [[MAC Addresses|MAC address]] from the device's settings.
# Sign-in to Church Network Manager ([https://cnm.churchofjesuschrist.org/ CNM.ChurchofJesusChrist.org]) using your Church Account.
<br>

===='''Step 2: REGISTER DEVICE IN CHURCH NETWORK MANAGER'''====
1. Click the firewall serial number in the building that you want to set up your device in.
[[File:Select FW Serial Number.png|none|thumb|656x656px]]
2. Once the Firewall Details screen is displayed, click the Menu on the far-right side of the screen. Then select '''Group Policy'''.
[[File:Menu Group Policy.png|alt=|none|thumb|777x777px]]
3. In the “Find a Device” section of Group Policy Manager, select '''NoSplash''' from the Policy Group drop-down, use the '''[[MAC Addresses|MAC Address]]''' drop-down menu to select the device you wish to register. Or you can manually enter the device's MAC address.

* ''Note: Devices need to be connected to Liahona for several minutes before they will display in the drop-down. Only devices connected to Liahona will display in the drop-down.''
[[File:Group Policy Screen.png|alt=|none|thumb|571x571px]]
4. Add a descriptive device name under “Name” that will help identify the device in the future.

5. Click '''Save'''

6. '''Complete'''! 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.''

Meetinghouse Network Upgrade

2026-02-17T21:10:28Z

HooperJM: /* Frequently Asked Questions */

Meetinghouse Network Upgrade

2026-02-17T21:08:12Z

HooperJM: Added FAQ's.

Meetinghouse Networking

2026-02-17T16:12:42Z

HooperJM: Added "Portable Meetinghouse Network" under Reference Articles.

> [[Meetinghouse Technology]]

__NOTOC__
<div style="margin: 10px 0px 0px 0px;">
The content of this wiki is under construction and does not always reflect official Church information. This content is provided by product managers, moderators, and technology specialists and is subject to change. For more general content go to the Help Center at: https://www.ChurchofJesusChrist.org/help/support/meetinghouse-technology.

This section has articles to help manage network devices in each meetinghouse.
<div class="mw-category"><div class="multi-column">

<div class="no-column-break">
===Overviews===
*[https://www.churchofjesuschrist.org/tools/help/networking-overview?lang=eng Network Overview]
*[https://www.churchofjesuschrist.org/tools/help/cnm-overview?lang=eng CNM Overview]
*[https://www.churchofjesuschrist.org/tools/help/firewall-overview?lang=eng Firewall Overview]
*[https://www.churchofjesuschrist.org/tools/help/switch-overview?lang=eng Switch Overview]
*[https://www.churchofjesuschrist.org/tools/help/wap-overview?lang=eng WAP Overview]
*[[Approved Equipment List]]
*[[Network Status Report Guide]]
*[[Glossary]]
</div>

<div class="no-column-break">
===Networking/CNM===
*[[Network Training]]
*[[Church Network Manager]]
*[[Assigning a Static IP|Assigning a Static IP Address]]
*[[CNM Group Policies|CNM Group Policies]]
*[[Configuring Network and Sensor Alerts]]
*[[Favorites Feature In CNM]]
*[[Add ISP Info|Adding Internet Service Provider Information]]
*[[What is Church Network Manager]]
*[[Using the “No Networks” Report]]
*[[Adding a Facility or Workforce Zone to a Meraki Firewall]]

</div>
<div class="no-column-break">
===Firewall===
*[[Using Filters]]
*[[Firewall Activation on CNM]]
*[[Images/a/a7/Meraki MX and Switch Installation guide 2025.pdf|New Firewall and Switch installation - 2025]]
*[https://tech.churchofjesuschrist.org/wiki/images/9/92/Replace_Existing_Firewall.pdf Replace an existing installed firewall]
*[[Moving Firewalls]]
</div>
<div class="no-column-break">

===Switch===
*[[Unmanaged Switches]]
*[https://tech.churchofjesuschrist.org/wiki/images/0/0f/Meraki_MX_and_Switch_Installation_guide_NEW.pdf Managed Switch Installation]
</div>

</div>
</div>

<div class="mw-category">
<div class="multi-column">

<div class="no-column-break">
===Wireless Access Points===
*[[Activating WAP|Activating a WAP]]
*[[Disabling Wireless Access]]
*[[Meraki WAP]]
*[[Wireless Best Practices]]
*[[Lehi and Liahona Wireless Networks|Lehi and Liahona Wireless Networks]]
*[[IOTConnect SSID|IoTConnect Wireless networks]]
*[[Generate A WiFi Heatmap]]
</div>

<div class="no-column-break">
===Reference Articles===
*[[Facilities Zone]]
*[[Power Over Ethernet]]
*[[MAC Addresses]]
*[[Internet Speed Tests]]
*[[Improving Internet Access]]
*[[Network search|Search for a Network]]
*[[Portable Meetinghouse Network]]
</div>

*

*<div class="no-column-break">
===Troubleshooting===
*[[Troubleshooting Firewalls|Firewalls]]
*[[Troubleshooting Meraki switches|Switches]]
*[[Troubleshooting Wireless Access Points|Wireless Access Points (APs)]]
*[[Improving Bandwidth|Improving Bandwidth (8 Steps)]]
*[[Troubleshooting Connections]]
</div>

</div>
</div>
</div>