Hi Anon116815 nice to see you!
In some cases, Unattended Access gets stuck on a computer and the issue can usually be resolved following these steps:
Thank you for your response. Can this solution that can be completed remotely? Can I start a new LMI session or will that prevent me from deleting the correct service?
I support over 100 clients in this manner. Many are hours away. LMI unattended is installed on the desktops before deployment. I now have 3 desktops at remote locations that have had this issue. 2 are fairly new rollouts and one has been up for over 2 years and been accessed dozens of times. This all started in the past month, but never in the 10 years previously. Seems like something may be creating this issue. We really need a solution or fix that prevents it from recurring.
Steve
Steve
Hi Anon116815 appreciate your response.
If you have RDP access to the unattended computers you should be able to remotely restart the rescue service on that computer, like turning the rescue software off and on again at which point it should reconnect to our servers.
This experience has been shared with the team. I see that you have a case open with support, you may need to provide logs to the computers that have this issue.
I do have another desktop on our domain that has the issue. I have tried restarting the LMI service on that computer. It did not resolve the problem. When it reconnects it is still reporting the client as In Session.
I do need a solution that I can complete remotely for the other desktops.
Steve
