Is there a sticky out there with standard solutions for standard issues?
We use it in our company, (126.96.36.1994 expert, 188.8.131.529 customer) but far to often, when we choose upgrade, so we can do administrative tasks on the users pc, it fails, and we have yet to find a way to make it works once its failed once.
our only option is to restart the PC completely (mood point getting all users in taskmanager and stopping the process etc)
So some standard solutions for this issue would be appreciated.
We discovered an issue recently that was causing some Unattended computers to fail when they tried to update to the latest build 1626. This issue was corrected as of July 10th and upgrades should now be successful.
Okay, so in that case, I would recommend you do the following:
The attended software can be left on a customers computer so that they join the next session without having to install, but it does not automatically update itself so if there is a long time between sessions there may be an issue.
Sorry about that @jasvKAB I misunderstood your issue as being one with upgrading the software versions on your clients, not upgrading your session to Run as a Service.
Do your clients have admin rights on their PCs? If so, you can set your GoToAssist Preferences to always Run support sessions as a service on startup. If you do this you will not need to upgrade the session from the Tools menu.
The clients do not have admin rights, hence why i need to run the upgrade service when we need to install something.
I very much doubt our sysadmin would allow the service to run with admin rights, they would consider it a security risk, ie, why we need to run the program, then run the upgrade service option.
and that brings me back to the question of what can i do when the service fails to go into admin mode, since it runs the upgrade just fine, but when i click to do something that requires admin rights afterward, i get the popup that indicate i dont have admin rights through the gotoassist program.
There is not a lot that can be done if you do not see the option to try and upgrade to Run as a Service again, except start a new session and try again. In order to understand why this is happening we will need more details about the client computer configurations and log files from them: C:\Windows\Temp\LogMeInLogs\GoToAssist Remote Support Customer\
If you email them to gotoservice at logmein dot com we will get them and create a case.