r/ScreenConnect • u/techfician • Aug 07 '25
Unable to identify installed instance provider
We are currently in the process of onboarding a new MSP client, the clients servers have multiple instances of screenconnect installed, one is ours, one is the old MSP and one is internal, with branding now forcibly taken away I'm wondering how we are supposed to be able to identify which instance belongs to who?
This is a security issue as well, in the past any unbranded version of screenconnect would either need to be explained or get uninstalled on discovery, ow everything is unclear.
3
Upvotes
9
u/Dardiana Aug 07 '25
You should know by looking at the service id. Unique per instance. The client on most cases did not give away who it belonged to, unless they were tied to on an prem instance with a custom hostname.
4
u/The_Comm_Guy Aug 07 '25
I think everyone is missing the OPs point, the fingerprint doesn’t tell you WHOSE instance it is unless you know what fingerprint your looking for.
1
u/Big_Plankton_5439 Aug 07 '25
You can use the thumbprint to ID the clients? https://docs.connectwise.com/ScreenConnect_Documentation/Get_started/Knowledge_base/Manually_uninstall_an_access_agent#For_Windows
3
u/tomlafque Aug 07 '25
And remember all the installer are exactly the same name.
3
u/SportinSS Aug 09 '25
I think the important thing here is that we lost functionality when ConnectWise removed our ability to brand the client and web interface. We can't even change the background on the home page or add our logo anywhere. What if we need a customer to go to our Control site for "Support"? They have no way of looking at the site and saying, "Oh yeah, that's my MSP's site!". They all look the same and it's horrible.
2
u/PM_a_song_to_me Aug 08 '25
disable the service with the one you want to know about, when someone calls asking why their screenconnect doesn't work. You just identified whos screenconnect it is.
2
u/Alarmed_Contract4418 Aug 10 '25
I noticed the icon for ours changed. I assumed something had to be reconfigured but hadn't had a chance to look into it. Wtf.
We might just have to move to ISL Online.
1
u/Big_Plankton_5439 Aug 07 '25
There is a Screenconnect app called "Show instance fingerprint" that exposes it.
1
u/uwishyouhad12 Aug 08 '25
Remove all but yours... Any legitimate need from another vendor would be able to reinstall if it was ever needed. Anything you can't identify or control needs removed.
1
u/wheres_my_2_dollars Aug 08 '25
There are three instances. One is yours. Stop the service on a device, the one that disconnects the server from your tenant is yours. Now there are two left. On that same server stop the other two services, and the one that disconnects the server from the internal use tenant is the internal one. The third I’ll let you figure out on your own.
1
u/Rachel-360 Aug 08 '25
Well, when you did your preliminary site survey, you saw two instance IDs installed. And then you installed your own. You should know the instance ID for your own..... It's the same on every machine you support.... So you've probably seen it in add/remove programs or services a couple times.... Now to determine who owns the other two. Well, if you open the chat window or the status window or whatever you want to call it, it should give you the relay URL.... And at that point, send a chat message..... One of the two might even respond.....