Setting up ScreenConnect to prompt for Password
Good afternoon,
So I am trying to set up a Screenconnect Session within RDM. Each one of my technicians have their own ScreenConnect Login. Ideally, I would like them to connect using their own. i added the credentials into the credential repository, and tried using that under the credentials section of that session. when i use that, it says unable to start session, verify settings. It only seems to work if i put a username and password under the host section. That, of course, is not ideal. if i choose ask for password, it prompts me for a username and password, but i get the same error message. How can I get this to just prompt for a username and password?
All Comments (6)
ok.. so i got it working with the prompt. it was my error.. needed the domain. I didn't need it when I log into the web portal. anyway.. when i disconnect the session, it asks if i want to end the session. if i do, it kills the session on the guest so i cant get back to it later. i have to reinstall on the guest in order to get it to work. These are unattended sessions and should remain open. thoughts?
Hello Brian,
Just to clarify, does the credential repository as well as the "ask for password" prompt work for your ScreenConnect sessions? They work on our end but it's not uncommon to have a different configuration that causes problems.
As for the prompt to end the session, we have a small workaround for this issue. The message itself is asked by ScreenConnect, and we can't do much about that. What we added in the options (File > Options > Types > ScreenConnect) is the option to kill the process on close rather than sending a close message to it.
I hope this helps you, if you have any more issues, feel free to update us on the matter.
Regards,
Hubert Mireault
Hey Hubert,
I apologize for the delay. i resolved the first issue, so i am all set there. it was just a domain issue. however, i did as you suggested but am still being prompted to end the session. Its not a huge deal, but im just afraid that someone is going to press that button without thinking and then we will have to reinstall the client again. any thoughts??
I will try to reproduce the problem and get back to you for a fix.
Regards,
Hubert Mireault
I'm unable to reproduce the issue as I think unattended access doesn't work for trial licenses (it says we have reached the maximum number of concurrent sessions). We have contacted ScreenConnect to check how to do this in our environment.
Meanwhile, could you take a screenshot or a video of your issue? Maybe we're missing something to reproduce the issue.
Thank you,
Hubert Mireault
After changing a few things, we have found our issue with our installation and can now reproduce the issue partly.
We do get the message when we try closing the ScreenConnect client. This problem is why we introduced the option I talked about in RDM to kill the client instead of sending a close message. This option works for me. Are you closing the ScreenConnect client through RDM's "Close session" button? It won't work if you don't close it this way.
Regards,
Hubert Mireault