Today, we're going to focus on what comes after implementation. While B.Y.O.D. rollouts usually bring minimal disruption, even if there's a network upgrade involved, there are virtually always hiccups following implementation.
We've got a few common scenarios we see, as well as ideas on solving them.
The most common network problem stemming from implementing BYOD is simple overuse. You may be surprised at just how quickly network usage goes up in the days and weeks following a personal device upgrade.
Aside from large scale deployments, the virtualized networks that are best for B.Y.O.D. are already self-optimizing. While moving access points around (such as away from sources of interference) or adjusting/replacing antennas may help a bit, there's a good chance that a Bring Your Own Device rollout will simply necessitate a bandwidth upgrade to support it.
Restricting usage is another option here, especially in the short term. If you block access to non-work related, bandwidth-heavy sites like YouTube or SoundCloud, that'll alleviate the burden.
However, it is a stopgap measure. As your business comes to use more virtualized services, you'll need more bandwidth sooner or later.
The success of a Bring Your Own Device rollout in part depends on the temperament of your workforce. It's sometimes hard to predict which workers will react well to the relative freedom of BYOD, and which groups will end up abusing it.
However, the network OS provides address management lists for the purpose of managing these issues. For example, the ADTRAN AOS system creates three default lists: A Priority queue for mission-critical resources, an “Everybody” list of globally-allowed websites, and a “Blacklist” of sites which are globally banned.
Since the network OS is universal, this makes it simple to manage which websites are allowed, and changes are implemented across the entire system within moments.
BYOD ready networks include “smart” scanning software that automatically oversees the network traffic and watches for suspicious activities. They can be further customized by sysadmins to look for virtually any activities you might find worrisome.
If you see an uptick in virus threats or other malware following a new implementation, the problem is likely to be on your user's devices.
There are several possible solutions that you can mix-and-match, depending on your situation:
Ban all jailbroken devices with crippled security until they're restored to factory settings. This is a good idea in any case.
Require users maintain the latest device OS updates, especially on Android, which is more prone to malware.
In some cases, Mobile Device Management software can remotely upgrade a connected mobile device to ensure security clearance. eg, Google's Business Chromebooks work in this fashion.
Require passwords of a certain complexity, and ban devices with insufficient security.
Implement exclusionary lists that block everything except sites you specify.
Device-specific bans are probably a last resort due to undercutting the purpose, but some businesses have ended up with “It's OK to use your personal device, except...” policies.
Many businesses that are enthusiastic about allowing personal devices and its possibilities for expanding their workforce's potential will run off to talk about custom app development... only to get sticker shock when they discover most custom apps start in the five-figure range.
However, there has been an explosion of cloud-based Software-as-a-Service offerings that, in many cases, will already provide the functionality you need for a fraction of the price. A telecommunications or networking vendor can usually put you in touch with top SaaS providers, if they don't provide the services themselves.
Do you have more questions? The experts at Hummingbird Networks have been installing and servicing wireless networks since the technology's inception. We are here to help you make it happen!