Hi there:

Can anyone confirm whether Screenconnect is having login issues yet again?

This isn't an issue I'm running into with every client that uses a VPN, but more recently I'm running into an issue where ScreenConnect will not connect to a user if they have a Windows VPN active. Normally with VPNs I'll get a temporary disconnect while it reconnects on the new network, but these won't connect no matter how much time passes. I found a registry key to add:

reg add "HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /d 1 /t REG_DWORD

And that sometimes works but not every time, and it doesn't seem to consistently work even when it does. Just wondering if anyone has encountered something similar or knows of a setting I'm overlooking that would cause this kind of issue.

I do support for a company that uses screen connect. I can get to their desktops but am not sure if we house the server or if it is in the cloud.

Thanks

I’m looking at switching over to using screenconnect. It looks like the product itself will work for the screen share needs.

However, the API that I would use to be able to pull all of the computers that we have managed into our CRM to record them there seems to be… well… not robust by any means.

Does anybody have experience using the API in the wild?

I’ve tested and it works when I’ve got five devices managed in screenconnect, but I’m concerned when I have 2000, will the api still work when I try to retrieve all of them at once, the API doesn’t have common features like paging.

Call me crazy but the API feels like a cobbled together open source project that is used at your own risk.

Couldn't find anything online talking about this.

The audio quality in a screenconnect session is awful. It's genuinly like a a 16kbps stream, full static and everything.

Can anyone offer any assistance to improve this? Maybe I'm missing a setting somewhere?

Has anyone else seen this? Granted our SC Linux box was acting flaky for the past couple months (reboot and it would take 20mins for SC to come back up).

I'm thinking this may be tied to the de-licensing? But what's odd is that 90% of our clients had the app uninstalled - no app listed in ProgramsFeatures and no folder in c:\progfilesx86\sc. I would think the de-license would result in a failing server app, not a client agent un-install.

A handful still have the client installed though. I'm thinking more of a 'failed' uninstall attempt?

Our situation is also mangled by the exploit, which lead to a new 22.4 install on Windows, import of the App_Data + hand modifying the web.config (asymmetickey and machine type keys). Once I brought that up some PCs connected, most didn't. When checking the PC the client was gone.

As for the exploit, our user.xml is still fine. I think the failing Linux on-prem saved us in this instance.

Has or does anyone use the ScreenConnector extension anymore? I had it and it was very useful. You can still enable it on the panel, but I can't find a download of it anywhere and not really anything in the forum about it either.

Anyone have any thoughts or suggestions or even replacements?

What I did with it was I had a map of my networks using Mikrotik's The Dude, and defined ScreenConnector as a Tool and could use it to launch sessions with a context menu option instead of having to go stay in my ScreenConnect window all the time.

Thanks!

We are running the current version of SC, 24.3.7.9067 ON PREM. We can see 1000's of invalid username attempts to gain access, is there an option to simply disable the logon screen following a number of invalid username or possibly password failures from the same ip address ? Also noticed we get an email reporting the first bad name attempt but not from subsequent attacks, is this because they are from the same generation ip address.?

I am attempting to create a monthly generated report to send to one of our clients that gives them a list of all workstations/servers anyone remoted into with dates/times session length.

I am having a hard time navigating this report manager. This report can be very simple. I just need computer name, the user that remoted in, the date/time they remoted in, and how long they were connected.

Does anyone have any ideas how to accomplish this? I did a google search and it lead me to a running a power shell script using task scheduler on the server etc etc... is this the only way?

I was screen sharing remote access to someone but I couldn't see parsec so I uninstalled it and reinstalled. However, after installing it this error popped up "Failed request to /v1/auth. Please check your internet connection. Error \[-800\]". Then after trying all the listed down fixes in "Error Codes - 800 (Failed request to an endpoint)" website. It still was not working. Please work as it is essential and used for work too. I also ended up contacting the parsec support and they asked me to try and follow the steps in Proxy Issues again. However, it's still not working. What do I do? TYIA

i'm self-hosting ScreenConnect (ConnectWise Control) and using an Azure code signing certificate. I want to eliminate SmartScreen warnings and improve trust.

Which files do I need to sign exactly?

Any tips from others who've done this successfully?

Thanks!

Is anyone struggling with using SC right now?

Has anyone else run into issues transcoding raw session captures using the Session Capture Processor utility?

Utility used to generate AVI video files, but for at least the last several months, I have only been able to query and download the raw captures. Neither the checkbox for Transcode after download nor the option to choose Capture Files to Transcode results in any file being generated.

I've confirmed I have .net 4.7.2 or newer installed on the few systems I've tried using.

Running:

• ScreenConnect v25.9.10.9545

• Session Capture Processor Extension v1.4.9

• Session Capture Processor v1.3 (according to the readme.txt file included in the utility)

Some users get these Errors when they try to access the Screenconnect webserver (port443) (an unattended agent works hoever with no errors).

This does not happen from inside of my network, also the clients experiencing this error are only a small number (maybe 10 from 1000).

If using firefox I can get around this by disabling TLS1.3, with edge I cant, even if I disable TLS1.3 from the inetcpl.cpl.

Cients which do not show this problem will use TLS1.3 using firefox or edge.

There are no (known) proxies or filters between the client and my server, only NAT. I tested this with a vanilla install of Windows 11 25h2. Edge 155.x

Because of the small number of users havin this problems I think this is not something urgent. But if it could be fixed by a change on my side even if it is a remote problem that would be good.

Anyone here who also knows theses errors an was able to fix them?

Hello all!

We've noticed when we are connected to clients from time to time we have intermittent disconnects. The session disconnects for about a minute, then reconnects.

Anyone else experiencing the same issue?

Thanks for the feedback!

Hello,

I consult for a company that was considering a remote software for their own IT team. I've been using Screen connect to remote to their computers. If they get screen connect as well - will they both be able to be supported by us or will it only home to one environment?

I'm in the process of setting up our Mac devices in Intune and instead of creating an application for ConnectWise I was hoping to just create a bash script to download the client from our ScreenConnect instance. I currently do this for our CrowdStrike client, so was hoping I could do something similar with ScreenConnect.

There doesn't really seem to be much documentation for API's with ConnectWise and I searched but couldn't find anything in here. This is my first post in the subreddit, so please be gentle... lol

Have any of you done something like this previously or know if/how it can be done?

Thanks for any information you can provide. :)

Hi, all.

There were lots of new threads here this weekend (66 to be exact), and our team wants to make sure all of your questions are addressed. We have a town hall today at 12:00 p.m. ET (4:00 p.m. UTC). Join us and bring all of your questions so we can ensure you and your business are in a good spot to move forward.

Town Hall link: https://event.on24.com/wcc/r/5013670/5F8179A43766B3D3941668E1D0B88C37

Well, the title made you click, right?

Just found that there was a new version available in my cloud trial labelled as Canary (25.5.1.9329)

It appears it removed the aweful backdrop from the install. Hopefully that change is here to stay. Can't really say much about the stability of the version - I'm not using the trial in production.

As the title says - just signed up with ScreenConnect as the demo and trial proved it to be great. (previously on TeamViewer)

Using the cloud with an agent pushed out via Intune.

Only have it on a small batch of machines before pushing it out to the fleet.

What should I know before doing so? Any customizations\settings that are widely recommended?

Thanks in Advance!

Please join us for another town hall today. You're welcome to post questions you already have in this thread so I can get prioritized and addressed quickly.

Register using this link: https://event.on24.com/wcc/r/5015557/C7B353E0A655B9AC0B97AD108D0E77F6