New GoToAssist logo OK
Allow technician to update stored password GREAT!
New message for sessions disconnected by customer security software Good
New preference to run sessions as a service at startup Very good
Restrict remote control permission for technicians NA for most of us
New Terms of Service agreement Doesn’t blow my skirts up
2. I cancelled and restarted GoToAssist
3. Got “Downloading required version” message
4. Clicked on an unattended client
5. Got “Application needs to adjust its version to match the supported computer”
Your version: 857 Remote application version: 818
6. Clicked Continue
7. Got “you have been upgraded to newest version (2.2 build 818)
8. Logged in normally
9. Checked version on client – 2.3 build 818
10. Checked version on technician – 188.8.131.528
I am noteing problems other folks are encountering with the client/technician version synchronization.
As I understand it, the current update approach relies on the crawler to distribute the client updates. If a session is initiated by a current version technician and detects an older version client, the procedure backs out the technician changes from the current version to the clients old version.
I just wonder, why not make the newer technician connection install the compatible current version client update if needed, rather than decrement strictly rely on the crawler to distribute the client, and back out the technician changes leaving both systems on the older version.
Now an additional hassle - you cant access computers with different versions at the same time. We need to log out - Upgrade/Downgrade whatever 😞 and log into a different machine..
Have checked and only about 20% of our machines have upgraded after 3 days, despite being on all day every day.
Is that what's called "frequent updates"?