Your comments

Can we get the status unmarked as completed? I've clarified on a different request, thanks.

Could I updated this request? I would like for the key icon itself to appear different, say filled if credential is stored and outlined if not. Here is why:

We'd like our techs to start preemptively collecting the end-user passwords in control so we could potentially use un-attended access to resolve issues while they are away from their machine. The techs could gather this during any remote support session where the user is available, however, in most of these cases the user is currently signed in, so the only way the tech would know if credentials are stored would be to sign the user off to view the popup. If the tech saw a non-filled key icon they would know that we still need to gather the password for that PC without needing to sign the user out to check. 

Let me know if this is feasible or not or if you have any questions about this, thanks.

Is this feature still roadmapped? It looks like there haven't been any updates in over 2 years or so.

Thanks for responding Caitlin.

I'm using the plugin "Update property from variables" for a number of uses. One thing it does is it pulls the folder creation date of the ScreenConnect folder found in "Program Files" to get a rough time of when screen connect was installed and adds it as a customproperty "Install Date" for each session. Then I have a subgroup that sorts sessions based on this customproperty in the format MM/DD/YYYY, and by doing this I can get a quick overview of which computers had screenconnect installed on particular dates. This can be useful for hunting down particular unsorted/uncategorized machines when I already have a rough idea of when they were onboarded, but right now it sorts them kind of catywampus so it's hard to look at.

Is that detailed enough? let me know if you have any further questions, thanks.


Thanks! I had no idea about this feature, this is EXACTLY what I was looking for. Thanks again!!

I prefer the Connectwise Implementation of CMD  for a number of reasons, including:

1. The ability to run multi-lind commands, ie:

cd c:\users


2. Much much faster feedback of the command output compared to automate.

And as others have said in this thread, those using Control integrated with Manage and/or Automate don't really have access the CMD feature without independently opening Chrome and signing in to Control Server, as usually in Manage (or Automate) you just launch a Control session directly into the PC you want via it's Configuration / Computer info window.