@RJM We may need you to contact Customer Support when you have access to one of the offline machines.
Has anyone been supplied a solution yet? We have had this problem for months. Problems started after we left v4 because I was told it would soon no longer be supported with Rescue Assist on the horizon, then Rescue Assist v1.xxx client version (web-only console) rolled out, then that morphed into version 5, and around then it was downhill from there. I have worked with support three times, sharing my screen from a client with the issue, sending diagnostics, and it has never been solved. I gave up working with support, it's been time intensive and zero productive. We reinstall the client and it works a short time then goes offline again. We have just been sending the support key to the client via Teams Chat and and have the client join the session instead of using Unattended. Not preferred but it works. Until we move to a new platform I am considering rolling all clients back to v4, but with 500+ client computers I'm not thrilled with that decision. Before doing this thought I'd reach out. Thanks for sharing any knowledge you have.
We have had similar issues on and off. After they rolled out a new 188.8.131.525 it seemed to be a bit better. I had to manually uninstall and reinstall several hundred computers. Looks like they are now rolling out 184.108.40.2065 and we will monitor to see how it goes. I have some of the older legacy 4.x agents installed on some computers and can access them from the new V5 console and have never had any issues with them.
We are still having this issue with clients falling off and showing as off line. This happens intermittently. May be time to look for a new solution. This has become too unstable for us.
Thank you for your patience with the Offline Unattended issue.
A fix has been released via Applet version 220.127.116.113 to address this issue. Please be advised that the affected Unattended machines will need to be rebooted to receive the update. Once complete, they should appear online within the Device Inventory.
** During testing there were two issues we identified in some cases that may affect performance:
After completing the upgrade, if you notice any odd behavior please let us know the following:
Agent 18.104.22.1683 is giving me more headaches. After several reboots, the agent is showing up as updated to this version. Then on some machines we have seen up to four GTA icons in the taskbar which disappear when moving the mouse over them and on the same machines and others we have seen no icons and we now have more machines than before not showing up on the device screen.
How can I stop this upgrade and how do I go back to the previous version 22.214.171.1245 as this worked better for us?
In future please allow us to select machines to upgrade so that we can carry out testing firat as this release has caused more problems than it sloved.
We are finding that machines are not showing up on the device list and rebooting means it is just random as to if the machines will. The new client seems very random on if it will start. As GTA support have been unable to answer this and other issues relating to reports in V5 and recording sessions we are looking to seek a full refund and move to another product. We like V5 but do not think it is ready for commercial use. Which I am sorry to say.
Thanks for your patience everyone, we continue to confirm the behavior should be working as expected. Sorry it is taking so long.
For the time being, please continue to use GoToAssist V4 as a backup / alternative until V5 is fully resolved.