I have 100+ remote probes, 85 of them are connected over a WAN and 15 are connected locally to the same LAN as the core ( master\secondary) or with high speed links.
When I do an auto upgrade, bi-monthly ( so 6 times a year or more) The update process takes a very long time to complete due to the number of remote probes and the WAN connections.
The problem is my environment that the 15 remote probes I have that are local could be upgraded and back online in a fraction of the time it takes the other 85 to complete the process. But of course they sit there some of them as long as the probes which are 3000km away. The 15 high priority probes have 45% of the total sensors; so monitoring data is lost unnecessarily and the blackout window is much larger than is need be.
I would like a way to could set the order or priority of a remote probes auto update. I don't need to set the specific order but I do need to set a way to identify what priority group of the remote probes should belong too and higher priority be auto updated first. Normal / High / Low perhaps.