Reset not working 1712
I have a couple of client machines that can often get stuck. Usually if a local user RDP connected and then rather than logoff they just close the session. On connection I am taken to the desktop ...
Forum Discussion
I encountered the exact same thing this week. Could not connect to Computer 123. There is one user at this site that will RDP to computer 123. What I ended up doing was connect unattended to another computer at the same site. (Computer ABC) Then use RDP myself to the computer 123 with the hung unattended session. Reboot computer 123. Wait a couple minutes and then check gotoassist - issue resolved. This is the only site where I encounter this issue - gut tells me the user who is RDP'ing to this computer never disconnects from the session.
That is the mirror of my situation I have 2 PC's at this customer with unattended, sadly both are stuck right now (since Friday). One of the 2 is always a little trickier as it has to run a process requiring auto login so it is always logged in as the same user i will connect with, this is the only site I have the "restarting screen sharing" happen with.
https://i.imgur.com/WdBOxDL.png
Previously if it happened the reset function always did the trick and i could get back on right now they are still showing "In Session" but they are not.
I am going to try get an attended session and see if reinstalling helps. Right now I wish I could downgrade to 1708 as that had been working great but I could find no archive of installers
are you able to get someone at the site to reboot each of them. That might save you the hassle of doing an attended - won't help with the reinstall of course but would get the connection back.
Friday I was able to get somebody to reboot and after that I got to the login screen, logged in and got the restart screen sharing which I know is doom, I was surprised as it is a fresh reboot and then I was locked out again. I tried to reach them to do a session but nobody was available so despite a desperate need to complete the server work it was impossible.
I am still waiting to get back online and see if this can be salvaged, I am getting more customers blocking or having networks that cause issue.. even our own HQ where I have a VM installed for testing stopped the service connecting so I had to have sysadmin exclude from proxy SSL inspection
