5 takeaways

1. New business-grade access points can improve capacity, security options and manageability, but only when they are designed and configured correctly.
2. Strong signal bars can hide deeper issues such as high retry rates, poor signal quality, channel congestion or weak roaming.
3. Post-upgrade WiFi problems should be diagnosed with validation data, not guesswork or another hardware purchase.
4. Ekahau validation surveys help confirm whether the installed network matches the building, users and applications it is meant to support.
5. Long-term reliability comes from design, configuration, monitoring and lifecycle planning, not from chasing the newest WiFi standard alone.

Summary

If your WiFi still performs poorly after an upgrade, the issue is usually not that the new hardware is “bad”. In many post-upgrade reviews we see at UK Netcom, the upgrade has exposed a design problem that was already there: access points placed where cabling was convenient, too much transmit power, poor channel planning, weak roaming, old client devices, or a wired network that cannot support the new wireless layer.

We see this regularly across UK offices, warehouses, schools, healthcare sites and mixed-use buildings. The right response is to measure what is happening in the real environment, confirm the root cause, and then rework the coverage, configuration or infrastructure properly. From our work with enterprise WiFi, Ekahau validation and Cambium deployments, the lesson is consistent: reliable WiFi comes from design discipline, not hardware alone.

Introduction

A WiFi upgrade should feel like progress. Staff expect faster logins, smoother video calls and fewer complaints. Operations teams expect handheld scanners, tablets and printers to stay connected. Visitors expect guest WiFi to work without a fuss.

So when the new access points go in and the complaints continue, it is frustrating. The natural reaction is to question the equipment, the supplier or the internet connection. Sometimes one of those is the problem. But in our experience at UK Netcom, the deeper issue is often simpler and more uncomfortable: the wireless network was upgraded, but it was not properly redesigned.

WiFi is not just a box on the ceiling. It is a radio system operating inside a changing building, serving a mix of laptops, phones, scanners, IoT devices, collaboration tools and business-critical applications. If the design does not match that reality, newer hardware can still perform badly.

Why can WiFi still feel poor after new access points have been installed?

Newer access points can improve capacity, security options and manageability when they are designed and configured correctly, but they cannot rewrite the physics of the building. A high-spec AP installed in the wrong place will still produce weak coverage in the wrong areas. 

A powerful radio set too high can create more interference, not less. A wide channel in a congested environment can reduce stability rather than improve speed.

This is why some users report “full signal” but still experience slow applications. Signal strength is only one part of the picture. Good WiFi depends on signal quality, airtime availability, client behaviour, roaming, wired backhaul, authentication and internet performance all working together.

When UK Netcom reviews a poor post-upgrade installation, we usually start by separating user symptoms from network evidence. That helps stop the conversation becoming “the WiFi is bad” and turns it into something measurable.

Typical post-upgrade symptoms include:

• Teams or Zoom calls dropping when users move between rooms
• Warehouse scanners disconnecting at the end of aisles
• Guest WiFi working in reception but failing in meeting rooms
• Laptops showing strong signal but loading cloud apps slowly
• Staff blaming WiFi when the issue is actually DNS, DHCP, firewall throughput or WAN latency

We have covered this distinction in more depth in our guide to why WiFi can be slow even when the signal looks strong, because it is one of the most common misunderstandings we see during support reviews.

What is actually causing the problem: poor hardware or poor design?

The honest answer is that poor hardware is not usually the first place to look. Business-grade access points from reputable vendors are generally capable when they are selected, configured and installed properly. In many post-upgrade cases we investigate, the issue is that the upgrade has been treated as a like-for-like replacement rather than a full design and validation exercise.

A common example is replacing old APs with newer models in exactly the same ceiling positions. That can work, but only if those positions were right in the first place. Often they were chosen years ago based on cable runs, ceiling access or assumptions about how the building was used at the time.

Since then, the business may have changed. Meeting rooms may now host video calls all day. Warehouses may have new racking. Schools may use more tablets. Offices may have more softphone and collaboration traffic. A design that worked for email and web browsing may not work for real-time voice, video and operational devices.

Poor design can include:

• Too few APs in high-use areas
• Too many APs competing on the same channels
• Transmit power set too high
• Poor 2.4 GHz, 5 GHz and 6 GHz planning
• Unnecessary SSIDs creating management overhead
• Weak roaming between access points
• No allowance for building materials, racking or machinery
• No validation survey after installation

The building itself matters enormously. Thick walls, glass partitions, lift shafts, metal shelving, roller shutters and mezzanine floors all affect radio propagation. In UK Netcom projects involving warehouses, schools and large spaces, this becomes even more obvious, which is why our article on designing and troubleshooting WiFi for warehouses, schools and large spaces focuses heavily on environment-specific design.

How do you accurately diagnose post-upgrade WiFi issues?

The first rule is simple: stop guessing. Adding another AP, changing the internet circuit or swapping hardware without evidence can make things worse.

A proper diagnosis starts by separating user symptoms from technical causes. “The WiFi is slow” is not specific enough. We need to know where it happens, when it happens, which devices are affected and what the user was trying to do.

When UK Netcom carries out a post-upgrade review, we are not just checking whether the APs are online. We are looking at whether the wireless environment is actually fit for the way the business operates.

A professional post-upgrade review should typically look at:

1. Coverage, Whether the right areas have suitable signal strength.
2. Signal quality, Whether the device can clearly hear the AP above background noise.
3. Channel utilisation, Whether the wireless medium is too busy.
4. Interference, Whether non-WiFi or neighbouring WiFi sources are affecting performance.
5. Roaming, Whether devices move cleanly between APs.
6. Throughput and latency, Whether real applications can perform reliably.
7. Wired infrastructure, Whether switches, uplinks, VLANs, DHCP, DNS and firewalls are supporting the wireless estate.

This is where Ekahau validation surveys are valuable. A validation survey compares the intended design with what is actually happening on site. It gives heatmaps, measurements and evidence, rather than relying on screenshots of speed tests.

Our Ekahau-led approach is useful because it gives both technical teams and business decision-makers something concrete to work from. A poor call may be caused by high retries. A scanner issue may be caused by racking shadow. A dead spot may be caused by an AP being mounted above an obstruction. A slow login may have nothing to do with RF at all.

For organisations that need this properly documented, our WiFi site surveys and consultancy support can help confirm whether the issue is coverage, configuration, infrastructure or a combination of all three.

What should you do once the problem is confirmed?

Once the evidence is clear, the fix should be controlled and targeted. The aim is not to change everything at once. The aim is to remove the real cause with the least disruption and the best long-term result.

Some problems are mainly configuration issues. These may be resolved by tuning channel widths, adjusting transmit power, simplifying SSIDs, improving roaming settings, updating firmware or standardising controller templates.

Other problems need physical design changes. That could mean moving APs, adding structured cabling, using directional antennas, changing mounting positions or redesigning coverage around warehouse aisles, outdoor loading areas or high-density meeting spaces.

From a UK Netcom engineering point of view, this is where careful prioritisation matters. Not every fault means a full replacement. Sometimes the best outcome is a configuration rework. Sometimes the APs are fine, but the mounting positions are wrong. Sometimes the wireless layer is being blamed for a switching, firewall or DHCP issue.

The wired network should also be checked. A WiFi upgrade can expose old switching problems. If APs need more PoE than switches can provide, performance suffers. If uplinks are congested, users blame WiFi even though the bottleneck is upstream. If DHCP scopes are too small or DNS is slow, users experience delay before they even reach the application.

A practical remediation plan might look like this:

Validation finding	Likely cause	Practical fix	Priority
Strong signal but poor calls	High retries or roaming issue	Tune power, minimum data rates and roaming behaviour	High
Warehouse aisle dropouts	Racking shadow or poor AP placement	Reposition APs or use directional coverage	High
Slow speeds at busy times	Airtime congestion	Redesign channels and reduce unnecessary SSIDs	Medium to high
Users drop when moving rooms	Sticky clients or poor overlap	Adjust cell sizing and roaming thresholds	High
New APs underperform everywhere	Switching, firewall or WAN bottleneck	Test wired path, uplinks and security appliances	High

The key is to prioritise based on business impact. A boardroom with occasional slow browsing is annoying. A warehouse pick path losing scanner connectivity every hour is operationally expensive. A care setting, school or manufacturing site may have even lower tolerance for instability.

Which infrastructure solves these issues long-term?

There is no single access point that solves every WiFi problem. Long-term performance comes from using the right platform in the right design, supported by consistent configuration and monitoring.

Cambium can be a strong fit for many multi-site or remote-operation environments when it is designed and deployed properly. In our view, its value is not just in the access points themselves, but in the ability to manage, optimise and standardise wireless across sites. That matters for schools, logistics firms, care groups, offices, retail locations and mixed estates where IT teams need visibility without unnecessary complexity.

For UK Netcom, a well-managed Cambium deployment is not just a hardware rollout. It should include:

• Selecting the right AP models for the site type
• Designing coverage for real users and devices
• Validating performance after installation
• Applying consistent configuration templates
• Separating corporate, guest, IoT and operational traffic
• Monitoring performance trends over time
• Documenting the design so future changes do not undo the work

Segmentation is especially important. Corporate laptops, guest devices, CCTV, printers, handheld scanners and building systems should not all be treated the same. Good VLAN and SSID design can improve security, simplify troubleshooting and reduce unnecessary background traffic.

We also find that standardisation matters more as organisations grow. A single office can sometimes survive with ad-hoc fixes. A group of schools, warehouses, clinics or regional branches cannot. Once there are multiple sites, repeated complaints or no clear baseline, reactive support becomes expensive and frustrating. Our usual advice is to measure first, then decide whether the fix is configuration, coverage, infrastructure or replacement.

How do you stop the same WiFi problems returning?

WiFi needs periodic review because buildings, devices and applications change. It changes as the building changes, as users move, as applications become more demanding and as client devices are replaced.

This is why UK Netcom treats wireless performance as an operational issue, not only an installation issue. A network that was validated two years ago may not still be right after an office refit, new racking layout, warehouse expansion or shift to more video collaboration. The same applies when moving from WiFi 5 to WiFi 6, WiFi 6E or WiFi 7. New standards can provide real benefits, but only when client devices, spectrum, switching and design are aligned.

In the UK, 6 GHz planning also needs regulatory awareness. Ofcom has opened the lower 6 GHz band, 5925–6425 MHz, for WiFi/RLAN use, and has also consulted on standard-power WiFi in that band using an automated frequency coordination database, including outdoor use. A reliable primary source for UK spectrum policy is Ofcom’s guidance on UK 6 GHz spectrum use.

Standards matter too. WiFi 7 is based on IEEE 802.11be, which extends the 802.11 wireless LAN family with capabilities designed for higher efficiency, improved capacity and more demanding wireless environments. That does not mean every business will see headline laboratory performance, but it does show why design, device compatibility and validation remain essential. For technical reference, see IEEE’s 802.11be-2024 standard information.

For most organisations, future-proofing is less about buying the newest AP every year and more about having a clear lifecycle plan:

• Review WiFi after major layout changes
• Validate performance before and after large deployments
• Document AP locations, channels, VLANs and SSIDs
• Monitor client experience, not just uptime
• Budget for switching, cabling and firewall capacity, not only wireless hardware

A well-designed installation should be planned as a multi-year platform, with review points after major business, building or device changes. That is a more realistic approach than assuming any wireless network can be installed once and left untouched indefinitely.

Conclusion

If your WiFi still performs poorly after an upgrade, it does not automatically mean the new hardware was the wrong choice. More often, the upgrade has highlighted a design, configuration or infrastructure issue that was never properly measured.

The fix starts with evidence. Confirm the symptoms. Validate the RF environment. Check the wired network. Understand the devices and applications that matter most to the business. Then tune, reposition, redesign or optimise based on what the data shows.

For UK Netcom, the most useful question is not “which AP should we buy next?” It is “what does the evidence show about how the network behaves in the areas that matter?” That might be the warehouse pick path, the Teams-heavy meeting rooms, the guest reception area, the classroom block, the clinic floor or the shared office space.

If your business has upgraded but still has complaints, you can speak to us about a WiFi review and we’ll help identify whether the answer is validation, configuration tuning, Cambium optimisation or a wider network redesign.

FAQs

Can poor WiFi affect Microsoft Teams even if broadband speed is good?

Yes. Teams and other real-time tools are sensitive to latency, jitter, packet loss and roaming behaviour. A fast internet circuit will not fix poor wireless airtime, weak roaming or high retry rates inside the building.

Should we remove the 2.4 GHz band from our business WiFi?

Not always. Some IoT devices, handheld scanners and older equipment still depend on 2.4 GHz. From our experience, the better approach is to manage it carefully, reduce unnecessary reliance on it and avoid letting it carry traffic it is not suited for.

Is a speed test enough to prove WiFi performance?

No. Speed tests can be useful as a quick check, but they do not show roaming quality, channel congestion, interference, retries, packet loss or application behaviour. When UK Netcom validates WiFi, speed is only one part of the evidence.

How long should a business WiFi installation last?

A well-designed installation should be planned as a multi-year platform, but it should still be reviewed when the building layout, device estate, application use or security requirements change. The physical APs are only one part of the lifecycle.

Can guest WiFi slow down staff WiFi?

Yes, if it is not designed properly. Guest traffic should be separated, controlled and rate-limited where appropriate. Poorly designed guest access can consume airtime, create security risk and make troubleshooting harder.