Hi Michael,
Thanks..
Our scenario is, that we don't have the option to 'move the image to the datacenter', as we are managing networks, typically without having desktops or servers on the sites. We have network equipment, like Cisco, HP & Ruckus.
And yes, we definitely alway plan upgrades - we would never run a firmware upgrade without a service window and agreement with the local property.
That is why my suggestion is:List available upgrades that are approved from your end, and let the Admin allow the cluster to fetch it to cache, so it's ready for the admin to apply when ready.
The really cool way to do it, would be something like this:
----------------
Current version: 3.4.0.0.976
Upgrades available:
3.4.1.0.208 [Download],
3.4.2.0.152 [Download],
3.4.2.0.169 [Download], Latest possible direct upgrade for current system
3.5.0.0.832 [Download],
3.5.1.0.862 [Download],
3.6.0.0.510 [Download], Latest release
---------------
If the Software Update server can return that list, based on the SZ sending current version, model and a list of AP models managed, it should be so easy to fetch that image and prepare it for the admin to run.
You can even make it check ones a day/week/month and have an event triggered to the admin email when new updates are possible.
The product name says 'smart', let it be so..