Rolling out a phased M-Files Desktop Client upgrade to 24.8 when using a shared cache

I have an upgrade to complete to M-Files Client Desktop 24.8 which is packaged up and tested and ready to be deployed, however with shared cache being enabled because users log into different workstations I need to establish the best method to roll this out in a phased approach, ideally we would like to avoid pushing an upgrade out in a big bang to all machines.  Does anyone have a confirmed method of rolling out in a phased approach with shared cache which doesn't risk data loss for users?