+5
Under Review

monitor for reinstall progress

MikeD 3 years ago updated by PODcom 2 years ago 1

Having updated multiple versions over the years I have often thought it would be good to know what is going on


If I select all connected guests it will typically reinstall to 5,6 or 7 guests in one push request but there is no obvious way of knowing when it has encountered an error or just given up and needs to be restarted. As it is I have to open another browser window to monitor network throughput so that I know it has stopped trying


Whenever a PC disconnects and reconnects with the new version then the host window updates so a simple status message showing how many PCs it was still attempting to reinstall would be good


thanks Mike

Available in Version:

I've up voted this!


In our situation, we have 100's of Access clients, which are Session Grouped representing our different Clients and Locations.  We generally have to up date 5 or so individual Access Clients at a time, as we have no idea of progress if we attempt to update an entire Group (which might contain anything up to 100 clients).


We generally resort to reviewing the Timeline to see if the Reinstall Message has been sent to a particular Client.  This means checking individually.


We then resort to checking whether the Access Client has disconnected and reconnected.  If the version hasn't updated and its had a disconnect and reconnect after the Reinstall Message, then we conclude the Reinstall has failed.


We have a follow up process, using a Session Group with subGroup Connected, then Client Version - so we can see how many Clients remain on the old version(s) - and generally periodically (re)attempt a Reinstall as needed.


It would certainly be nice to know (at a glance), the current state/stage of a Reinstall for each Access Client:


- Reinstall Queued

- Reinstall Downloading Update % (we have a few slow connections that will timeout from time to time - so having some restart logic here might be nice)

- Reinstall Download Complete (once its downloaded and the MD5 continue to match - why send the Client another update)

- Reinstall Updating

- Reinstall Update Failed (with Reason)


Anyway - just my thoughts - and obviously up voting this Feature Request.