In our series of (Mis)Adventures in Small Business IT, we will share stories from clients who took on portions of their Small Business IT without seeking expert advice, and the ultimate resolution to their challenges.
For our first episode, we’ll relive a relatively simple change which was planned for a services company. The scope of the change was fairly straightforward, replace the current internet connection with a new connection from the same provider – a swap from cable internet to fiber internet.
As with many small companies, everyone in the business wore many hats, and there was no dedicated network engineer or fulltime IT person. Instead, this change was planned by members of the company who were technical but had specialties in other areas of technology. They were off to a good start, procuring the circuit and getting appropriate static IP addresses provisioned. The circuit physical installation was uneventful, and they planned to bring the service online during a communicated maintenance period. To their credit, they also considered and outlined a rollback plan which included overlapping their current service with the new service for a couple of weeks, to allow for resolution of any issues that might arise.
In a quick review of things this far, they’re putting points on the board for:
- Planning the implementation
- Communicating to staff
- Having a rollback strategy
The day of implementation arrived, and they began to follow their plan by updating the configuration of their network equipment. Unfortunately, right out of the gate, there was a discrepancy related to the static IP information provided by the internet provider. Uncertain of the best way to validate the conflicting information, they were left to “guess and check” their implementation. While there are circumstances when this isn’t a terrible approach, it never instills confidence when this is the only route you have left to take. To make matters worse, none of the combinations seemed to work. Leaning on their rollback plan, they removed the new connection from the mix and maintained connectivity on their old connection.
At this point, they hadn’t experienced any unplanned outages but they had invested a decent amount of time from one of their full-time staff which might have been more appropriately applied to his core responsibilities rather than orchestrating and conducting changes to their internet and network configuration. TexasPGB was aware of the change though not formally involved, but once we heard about what was starting to sound like a prime example of a (Mis)Adventure we offered to assist in making sure this went the right way.
Once brought up to speed, implementing the configuration changes for the new connection proved to be a quick task for our team – with everything up and running in less than 10 minutes.
Before taking a victory lap around the office, we reviewed common impacts that might result from changing their static IP address, including updates to their VPN configuration on laptops used by several of their key employees. Finally, we recommended and conducted a quick review of their other network configurations to ensure there weren’t other impacts specific to their situation that would require updates. Surprisingly, we uncovered one of these less common scenarios – a Site-to-Site VPN connection between their office and Microsoft Azure with their old IP address configured as part of it. This required updates to both the configuration in their local network equipment and Azure settings, a circumstance that both the client and TexasPGB had not initially planned for. Fortunately, with the right skillsets in the room, these additional updates were easily implemented without significant disruption.
As we highlighted, our client did many things “right” when preparing for this change. They were able to determine what they needed, get it physically put in place, identify the need to plan the implementation/rollback, and most importantly they communicated the potential for interruptions to connectivity during the change. With their staff of technically capable individuals, it’s easy to see why they would take on this project unassisted. However, this is also a project which demonstrates how easily things can depart from the “plan” and take you into uncharted territory. This can start if you’re not accustomed to working with network engineers (the technicians activating business internet circuits are often NOT in customer service) to missing nuances in your configuration which will have big impacts later.
Finally, a point to consider – even if it all worked out, how much of your employees’ time should be spent stumbling through technology challenges rather than focusing on the job you hired them for?
We estimate that having the wrong resources on these projects can contribute to a 3x to 5x increase in effort, frustration, and disruption – often resulting in failed projects that never deliver the benefits you anticipated.
Have you been caught up in the DIY craze with your Small Business IT? Want to avoid situations like this one within your business? Contact us here
and let’s talk!