Forum

Posts by jburroughs (jburroughs)

jburroughs
jburroughs
Posts: 3

Thank you guys! That was a really fast turnaround, very impressive.

2 yrs ScreenConnect User Display Name Overwrite
jburroughs
jburroughs
Posts: 3

Have you checked recently? WindowTabs is working well and is pretty close to what we need. Drawbacks are that it's limited to three windows per program for the free version, it doesn't consolidate the taskbar icons, and it is still a separate window from RDM. At least it's one separate window instead of three separate windows. Would be great if RDM could do this natively though, with no extra software to worry about, no limit to three instances tabbed, and no external window to manage outside of the main RDM window.

2 yrs Embedded Tab View ScreenConnect Session
jburroughs
jburroughs
Posts: 3

We do not give users access to ScreenConnect directly, so they do not have user accounts on the system. We use a single RDM integrator account on ScreenConnect to sync sessions and log users in to sessions. These credentials are saved in RDM and users are not able to reveal/access this password, RDM logs them in programmatically with these creds without them ever needing to know them. This greatly simplifies deployment and administration (not having to have users remember and enter their creds for the SC server which is in the cloud and cannot sync with AD or LDAP, not having to set/update this password on all the synced session groups for each customer in RDM, etc).

This is identical to the way LabTech integrates with ScreenConnect. However when users access ScreenConnect through LabTech, LabTech overwrites the display name of the ScreenConnect user so that they see the username of the tech's LabTech account instead of LT_Integration. When we connect through RDM, we would like to have this same effect where RDM overwrites the display name of the integration account using the username of the tech's RDM account instead of RDM_Integration.

This display name is used in chat, in the "under control" banner displayed to end users, in the ScreenConnect session connection history logs, etc. It is also used in the list of active hosts connected to the machine - when two techs connect via RDM, we see two RDM_Integration users connected, and if one user is idle/away and needs to be disconnected, we have to guess at which one to kick off and half of them time kick ourselves off. This is a seemingly small change but with a huge benefit for us. If we have to administer/manage/remember creds for each tech for ScreenConnect, we might as well have users log into ScreenConnect directly instead of RDM and save on the license cost.

2 yrs ScreenConnect User Display Name Overwrite