Elsinore

User Forum

www.screenconnect.com
Welcome Guest Search | Active Topics | Log In | Register

Tag as favorite
How to remove unattended session so it doesn't appear on server? Don't have access to client.
sysadmin
#1 Posted : Thursday, July 21, 2011 6:59:24 PM
Rank: Advanced Member
Joined: 6/1/2011
Posts: 45
Location: NYC
I need to remove an unattended session from the server, but don't have access to the client to uninstall it.

I'm thinking there must be a way to force expiration on whatever token or key is being used, but I have no idea how to go about that. A simple "delete" such as LogMeIn has would be a HUGE HELP right now.
feri
#2 Posted : Friday, July 22, 2011 1:57:49 PM
Rank: Advanced Member
Joined: 5/12/2011
Posts: 36
Location: Romania
I would like to see this option too.
IT Services
www.icore.ro
sysadmin
#3 Posted : Friday, July 22, 2011 4:44:12 PM
Rank: Advanced Member
Joined: 6/1/2011
Posts: 45
Location: NYC
I really need an answer to know if this is possible. If it's not, I will have to reinstall the server and redeploy all clients, which I'd like to avoid if at all possible.

Should I be emailing support to get an answer from the devs on this?
Jake Morgan
#4 Posted : Friday, July 22, 2011 5:13:33 PM
Rank: Administration
Joined: 4/9/2010
Posts: 858
I'm not sure I understand you. Can you just connect to the client and uninstall it? Don't you have access to the client by it being connected to the server? I just join the session and go to add/remove programs and uninstall.

Also, reinstalling and redeploying clients may not fix. Clients will continue to connect back to the server after a reinstall!
sysadmin
#5 Posted : Friday, July 22, 2011 5:55:34 PM
Rank: Advanced Member
Joined: 6/1/2011
Posts: 45
Location: NYC
Jake Morgan wrote:
I'm not sure I understand you. Can you just connect to the client and uninstall it? Don't you have access to the client by it being connected to the server? I just join the session and go to add/remove programs and uninstall.

Also, reinstalling and redeploying clients may not fix. Clients will continue to connect back to the server after a reinstall!


Not in a typical situation here. The remote machine is offline at the moment, and I absolutely cannot connect to it when it comes back online (and I pretty much need to have this resolved before that happens or we will be taking the server offline). We basically need to kill the connection on our end by whatever means necessary.
Jake Morgan
#6 Posted : Friday, July 22, 2011 7:48:09 PM
Rank: Administration
Joined: 4/9/2010
Posts: 858
I'd block the machine from connecting through your firewall. If you view the session, you can see the last IP it came from. Block the IP, subnet, or whatever it takes. Sorry, but that's the only way to make sure it can't connect back to you. Even reinstalling may not have the behavior you expect. If you have a ScreenConnect relay service listening on the IP/port it's trying to connect with, it will connect, though hosts won't be able to connect to it after a reinstall because the encryption keys won't match.
sysadmin
#7 Posted : Friday, July 22, 2011 9:28:56 PM
Rank: Advanced Member
Joined: 6/1/2011
Posts: 45
Location: NYC
Thanks for the update. I have no idea what the IP will be. Looks like we'll have to reinstall the server using a different domain (subdomain).

It would save us a bit of time if there is a way to change the domain name without re-installation - at least we wouldn't lose all of the users and other settings. This possible?
Jake Morgan
#8 Posted : Friday, July 22, 2011 9:33:24 PM
Rank: Administration
Joined: 4/9/2010
Posts: 858
I'm not sure what you're asking. Any DNS is configured outside of ScreenConnect. You can certainly change how all of that is configured.
sysadmin
#9 Posted : Saturday, July 23, 2011 12:06:37 AM
Rank: Advanced Member
Joined: 6/1/2011
Posts: 45
Location: NYC
OK. I thought I remembered there being some point during setup where I was asked for the external URL. Most apps utilizing a web server these days ask for that info for host header purposes.

Thanks again.
feri
#10 Posted : Tuesday, July 26, 2011 7:49:43 PM
Rank: Advanced Member
Joined: 5/12/2011
Posts: 36
Location: Romania
Wouldn't be possible to implement the following (just my ideea):
1. each unattended host would have a checkbox beside the connection icon for "Accept client connection"
2. each client already has a unique ID, so you could assign the checkbox status to the client's ID and store it in a file (or db in the future).
3. when the client connects to the sever, test if the client is accepted (checkbox on) or not. If in the file the chekbox status is set to on for the connecting client's ID, the client is able to connect to the relay server OR if the checkbox status is set to off then the script/program rejects the client's connection to the relay server. This way the client SC will not be able to connect to the sever.

This is just my ideea. Maybe it's not so good but I wanted to share with you.
Regards,
IT Services
www.icore.ro
x16wda
#11 Posted : Friday, August 05, 2011 10:08:51 PM
Rank: Member
Joined: 8/3/2011
Posts: 13
Location: North Carolina
Throwing in my two cents, there should actually be TWO new options:

1. add a "Blacklist" button or checkbox to prevent the server from accepting the connection (just like you suggested) - the problem here is that the remote host will continue to try connecting back to the server. But that might be fine if you just want to temporarily disable a session for some reason.

2. add a "Kill" button which would (a) tell the client to overwrite the server name with nulls or something and also disable the service, and (b) delete the appropriate file from the Sessions folder. Once triggered, the client can't connect without rerunning the installer. THAT's what would really do the trick. Requires a new client installer though.

As a matter of fact, there needs to be a way to delete an unattended session from the gui, for example if a person leaves the company. You can uninstall the service from the pc, but the session still shows up in the list until you delete the file from Sessions.

(Or, of course, I could be missing something, I've just been playing with the software for a week...)
bigdessert
#12 Posted : Saturday, August 06, 2011 1:45:46 AM
Rank: Advanced Member
Joined: 9/14/2010
Posts: 458
Location: Minnesota
x16wda wrote:


As a matter of fact, there needs to be a way to delete an unattended session from the gui, for example if a person leaves the company. You can uninstall the service from the pc, but the session still shows up in the list until you delete the file from Sessions.

(Or, of course, I could be missing something, I've just been playing with the software for a week...)


I agree with your first two points, but what you quoted already works. By default disconnected sessions are removed from the console after 24 hours.
x16wda
#13 Posted : Saturday, August 06, 2011 4:53:16 PM
Rank: Member
Joined: 8/3/2011
Posts: 13
Location: North Carolina
Ah, didn't know that! I haven't ramped up testing enough to see that happen yet :-)
Users browsing this topic
Guest
Tag as favorite
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.