Had a problem with clients running Windows 10, but mainly Windows Server 2016. After a reboot or update the unattended client is no longer available and I can't connect. Each time I have to manually reinstall the client on the device. This is becoming a pain for multiple clients. Is there a fix or known problem?
Solved! Go to Solution.
Hi Tony,
I'm sorry to hear about this behavior.
Since the problem began, have you tried setting GoToAssist to delayed startup on the problem PCs?
I changed the LogMeIn service to be Automatic (delayed). Hopefully, this fixes the problem.
Is this solution documented anywhere and/or what causes?
I don't have anything specific documented, but will see if there's anything that matches similar criteria on the back log.
Let us know if the delayed start works in your case?
Just performed an update on Windows 2016 Server and lost unattended access once again after making the requested change.
What can be done to prevent this? This, unfortunately, is a huge hassle and renders unattended access useless.
This workaround is not acceptable long-term. When will this be fixed?
With regards to Unattended suppor on Mac High Sierra (build 1599), this issue is hight priority, and is scheduled to be fixed in the coming weeks. For the time being, the only workaround is to reinstall GoToAssist on the affected Mac client, or to simply have the client end reboot manually. As more information becomes available, we will update the Community here.
For Windows users affected by this issue, please make sure the affected Unattended User account is running as a Service, and that the internet connection remains uninterrupted throught the reboot.