As a 100% cloud based company, we have a long history of helping clients transition to remote work. Over the last month, we’ve supported hundreds of users who were suddenly working from home. For many, it was easy. They had the tools with them, on their own devices. For the ones who are reliant on in-house servers and legacy apps, we’ve worked on seamless remote access to office PCs and networks.
We’ve learned a few things along the way too (the top five list is below). If your company isn’t working with tkc.io, we have capacity. Send us a message and we’ll see if we can help.
We’ve ranked this list, with number one being the biggest issue so far.
We manage battery backups on servers and networks but what about office PCs? You can’t remote into a workstation that’s offline. What happens if the power is out for a long period of time? Who can help onsite? Power issues have been our number one gremlin.
Remote workers use home connections. Some good, some bad. In many cases, they were never setup for a home office scenario. What are their requirements and how to best manage this? We’ve worked with internet providers and home equipment quite a bit this month.
Apps like Zoom have taken off in popularity. These are apps that were implemented on-the-fly and users are coping with new logins, hardware and subscriptions. It’s difficult for a remote worker to diagnose. We’ve been supporting them via remote viewing sessions.
In the office, connections were easy to administer. But what happens when your workforce is rapidly changing and users cannot get to the data they need? Enforcing policies and permissions can require new thinking when your team is on the outside.
When you have to rethink your office, after years of familiarity, there is always a learning curve. We’ve noticed instances where prior user training could have saved downtime. Having your road warriors mentor others helps. We love to train end users.