IBM Security Join our 16,000+ members as we work together to overcome the toughest challenges of cybersecurity. Join the Community
I understand that I can push an update to a device different ways. individually, or through a group. However, since all of our devices are company owned the challenge is getting device holders to connect to WiFi. Everytime there is a download it is required that the device holder be connected to WiFi. The challenge is getting users to connect to WiFi then go to download and install.
What I would like is some suggestions on how others are ensuring that devices are up to date. Since most of the people that are devices work out in the field they rarely have a WiFi connection. Even if they could get to a wifi connection this will take time away from them doing their job. How have other overcome this situation?
First off. I'm sorry you have to deal with this. My company went the same route with before I came on to 'save money on costs' by going Wi-Fi only with our fleet. Frankly they are an absolute nightmare to manage. I have been slowly migrating our fleet to 4G-5G but that is of little help to you.
Honestly, it took a cost-benefit analysis written down on paper to management before they realized while there was cost savings upfront the back end support and updates quickly overrode that.
Sadly many of the answers I'm about to give are not going to be a great solution, just a stop gap measure. Here has what worked for me in the past, and also relies on how much your field ops have started to use the devices for personal usage and what type of devices they are.
I know these are not the best answers, but it is something I've had to deal with at my location. I hope this helps you find a few solutions that will work for you.