I don't know they've been working on this.  I brought this up right when it happened.   I followed up over the months and being told it'd be fixed in each release.  Last it was for 24.4, now it's for 25.0.  It's ridiculous to break something so paramount to functionality.  They know when and HOW they broke it but it's still not resolved.

Hi Dave,

We basically tried to update the copy/paste feature so we could copy/paste images within a session. What you are seeing is 100% this bug.

SCP-38718

Attempting to copy table data into Excel pastes an image of the content after updating to 24.1.  Only resolution I have would be reverting back to 23.9 or waiting till the patch is released.

Andrew Robinson

Senior Software Support Specialist I

 
After a follow up a few months later:

Hi Dave,

I apologize on the delay. To be honest, it's been a rough year for ScreenConnect updates. This is something our Product team acknowledges and is committed to getting sorted.

Right now, the Copy/Paste Clipboard update has been planned for v24.4.
We are currently in v24.2. The next release v24.3 is set to be small.
Then we will be rolling out v24.4.

Again, I apologize. I understand the major disruption is causing. We are doing everything we can to fix this as quickly as possible.

Andrew Robinson

Senior Software Support Specialist I

Now this after seeing 24.4 did NOT fix it and following up to check the status.   This clearly is super low priority to them which is unfortunate

Hi Dave,

I do appreciate your continued patience. Right now, the patch for the clipboard copy bug is set to be included in the v25.1 release.
If all goes well, that should be next month.

The known issue will be updated once the patch is released but we will also post this to the output stream located here: ScreenConnect Output Stream / ConnectWise ScreenConnect

Andrew Robinson

Senior Software Support Specialist I

Thanks I did find a video on this later in the evening.  Is there some way to allow this to report back even if the username is not valid?  Anyone trying to get in brute force is more than likely NOT going to know our username.

I tried to use this event but it does not work  Event.EventType = 'PasswordInvalid'

Can this audit FAILED logins only?  I see LOGIN attempt but I need to sift through them all to find if any failed.  If this is possible, is there a way to create a trigger to email us on failed login attempts?

We NEED this too.  I'm shocked 4 years later this STILL Is not an option.

I just had this happen w/ the latest update.  Never did before.  I have a request into support on how to resolve this.  Will report back.

Dave

This would be helpful.  We have a trigger that we need to send a session name after a new session is created but the session name is not created before the trigger is activated thus sending us a null subject basically.

There is a field to configure the text on screen.  I had set it up at one point years ago, looking for the details now.

Found it, field is BlankMonitorMessageFormat

Dave

Great, thanks for the fast reply.

Dave

Mike, is there a way to initiate this backstage functionality prior to connecting to the session as to not disrupt the user at all?    As of now, a tray icon popups up and notifies the user as well as the top bar stating we are controlling their session.  And of course the blanked background. 

Thanks

Dave

Sorry  I somehow missed this.  What do you mean next time you're disconnected?  Yes it only alerts on the initial chat, subsequent messages do not notify as that would get annoying.  You can set it email on all messages and that is how I had it at one point years ago but it became obnoxious when tech and client were chatting back and forth.  This feature may have been deprecated.  

Dave