A Word of Warning for Remote IT Infrastructure Workforces

To continue to support a remote IT workforce, due diligence must be performed to both reduce the number of hardware components that must be managed and the steps to be taken when outages occur.

A Word of Warning for Remote IT Infrastructure Workforces
(Source: Unsplash)

As we approach the two-year anniversary of the COVID-19 pandemic's beginning, I think back to the number of times I’ve been asked by clients and colleagues about whether remote IT workforces will be a temporary or permanent fixture. While I initially thought that a certain level of team cohesiveness would be lost across the board due to the physical separation of IT team members, I’ve since warmed up to the idea that remote IT workforces may be the way forward given these uncertain times.

However, there are some warning signs that have cropped up recently that show that organizations must plan a bit more carefully for those in IT who are responsible for managing physical equipment such as private data center servers, network infrastructure hardware, and autonomous IoT devices.

A perfect example of what I’m referring to can be found in the recent Facebook outage that occurred earlier this month. Apparently, a flawed DNS update caused the outage that lasted over five hours and impacted users across the globe. What’s more interesting is the fact that, as was reported by the New York Times, the outage resolution required a team of Facebook engineers to travel and gain physical access to a specific data center in order to remediate the problem.

Considering that Facebook is allowing nearly all employees to work remotely due to the pandemic, one must wonder if the outage lasted far longer because the right people with the right skills were not able to be where they needed to be.

Unlike other IT roles that revolve around software and/or programming, IT infrastructure does require a physical element to their role. When physical systems malfunction to the point where they need to be manually replaced or physically reset, time is certainly of the essence. These types of outages also occur far more frequently than one might expect. I recall several times throughout my career where an errant remote configuration change to a network router or switch required that I drive into the office or data center to locally access and/or reset the device so that it would revert to the previous configuration settings.

To lessen the chances of these types of incidents for typical enterprise IT organizations, I recommend that IT leadership consider a two-pronged approach.

Read the rest of this article on InformationWeek.

Read more about:

Remote work

About the Author(s)

Andrew Froehlich, President, West Gate Networks

President, West Gate Networks

As a highly experienced network architect and trusted IT consultant with worldwide contacts, particularly in the United States and Southeast Asia, Andrew Froehlich has nearly two decades of experience and possesses multiple industry certifications in the field of enterprise networking. Froehlich has participated in the design and maintenance of networks for State Farm Insurance, United Airlines, Chicago-area schools and the University of Chicago Medical Center. He is the founder and president of Loveland, Colo.-based West Gate Networks, which specializes in enterprise network architectures and data center build outs. The author of two Cisco certification study guides published by Sybex, he is a regular contributor to multiple enterprise IT related websites and trade journals with insights into rapidly changing developments in the IT industry.

Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like

More Insights