http://product.screenconnect.com/topics/149-extended-auditing-archival-searching-with-additional-data-fields/

http://product.screenconnect.com/topics/211-add-option-to-automatically-archive-video-files-to-another-location/

Refer to these, Modifications could be made to the request to accomodate better archival but it's somewhere to start

I'm not sure that I would suggest this, Attaching the screen recordings to your tickets in CW isn't a bad idea but over time the size of CW is going to grow immensely.

I'm not sure what alternative I would suggest either.

Note that doing this would increase the amount of resources needed by the ScreenConnect server as it does use more resources to convert these videos into a usable format.

If anything I would have a NAS with folder structure per client with dates or ticket numbers to correlate and maybe store on that. It's a lot more work but it would keep the size of CW down. May not seem like much but 20mb 40mb here and there for session recordings adds up fast. Especially if you don't have room on your host for expansion, Makes more sense to upgrade a NAS than an entire server just to be able to support session recordings attached to tickets. But thats just me.

Until ScreenConnect can implement something I would suggest using QoS on your firewall to prioritize certain types of traffic or put file transfers at the bottom of the list and give everything else priority over it.

I would second this. Looking for a way that we could audit potentially machines that are no longer in use and the entry in ScreenConnect was never used. We use LabTech integration and while we can uninstall the LT agent it does not remove the ScreenConnect agent.

Probably the easiest way to do this would be if LabTech ran uninstall command it removed SC from PC ( best way to do this would have it set somewhere in labtech what your ScreenIonnect instance ID is so it doesn't potentially remove other vendors SC installs. and then it would run the commands to remove it from the endpoint/server & end the session in ScreenConnect itself so its no longer present.

And for the stuff that slips by having a way to audit this such as a field in the database tab that says find idle sessions that the guest hasn't connected in longer than X would allow us to say if they haven't connected in X or exceeds X period of time we can select all of those and end the sessions (For the machines that probably are no longer active or in use such as they were replaced or died)

I was just trying to find a solution for this myself.

Ours isn't necessarily for compliance however this would be a incredibly helpful feature.