The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Unattended access connecting into RDP sessions on Windows Server instead of to the console
We started having a problem yesterday where we were unable to connect to several unattended devices (all Windows Servers). I was only able to connect to 1 out of the 5 or 6 I tried. I had several of ...
Thanks, everyone, for the feedback and cooperation!
In a day or two, we will launch changes to support the VM and Terminal server cases and support the previous behavior:
- In case of a non-multi session environment, the GoTo Resolve session joins the running RDP session.
- If multiple sessions are allowed, then we open the console session's screen (instead of today, where you join the latest running RDP session), so this will go back to the original logic.
Later this year we will enhance the functionality and you will be able to select among the running RDP sessions or open the console.
I have been going back and forth with support for about 7 weeks now and am being told just this week, this is the "intended behavior" which now makes me wish we never would have switched from GoToAssist to GoToResolve. Course now I worry if going back to GoToAssist, it might also have this same problem. I do think GoToResolve works better in some regards than GoToAssist especially with transferring files, but this new RDP problem is a deal breaker for us. If there is not a way around this, we are going to have to search for another solution and move away from GoTo altogether. It took some effort to move all our unattended devices from GoToAssist to GoToResolve last December, and then for it to only work for 6 months usable on some of these servers, it has me thinking we may have to look at other options.
If it is the 'intended behaviour' does that mean it hasn't been working properly for the last two years by connecting to the Admin session?? Logically you would want to connect to the Admin session and then use the Windows system to shadow the relevant RDP session.
