r/ScreenConnect

Im 7 days in on my 14 day trial and have been locked out for suspicious activity from day 2.

I've done nothing but test on three workstations for unattended and tried to see what connecting to android was like and was feature gated.

I've asked support to trial a single Standard license to demo the session switching and iPhone/Android support. I was told they would submit an email request. This was on day 2 and when I went to check on day 3. My account was suspended.

I've called support and they submitted a ticket. They closed this without a call and within 10 minutes of responding. I submitted on Friday, response came in on Monday. They say talk to accountsecurity@screenconnect.com. Ive emailed them on Friday and again today with no response and still locked out.

I've checked audit logs and all looks like my activity on day 1 of the trial. We are replacing Dameware and need a good product and locking me out for DAYS is not the answer. Hoping this is a fluke and I can get someone's attention here to get our account reinstated. If this is the norm and to be expected, please someone from the community speak up and feel free to suggest an alternative.

I notice that 26.5.3.9704 is available to update my self hosted instance.

I downloaded it and instantly smart screen has kicked off saying its full of viruses. Weirdly I notice that the release date for this was 27th July and the version I am on (26.4) was released 5th August.

Has anyone updated to 26.5 and had the same smartscreen issues?

I'm using the hosted version of ScreenConnect and lately I'm having a really weird issue with the portal.

When I log in, it opens on the All Machines tab by default, which I believe is normal. I have around 800 devices in there, but I'm not sure if the number of devices actually has anything to do with the problem.

After the page opens, something seems to happen in the background and the browser starts getting slower and slower. Eventually it gets so bad that the whole computer slows down, not just the browser. Sometimes I can barely do anything until the ScreenConnect session times out and logs me out, then everything goes back to normal.

PC is i7 with 64GB RAM, so I don't think this is just a hardware issue.

It's also hard to tell what exactly ScreenConnect is doing because nothing obvious is loading on the page when it happens.

Anyone else seeing something similar with the hosted portal? Any workaround or anything I should check?

Haven't reached out to support yet. My experience with their support in the past wasn't great so figured I'd ask here first.

Even if I wrote in a previous post, I will not upgrade to 26.5.3.9691 before december, I did it yesterday out of curiousity.

But I was immediately punished for this after trying to upgrade a MacOSX Client running 10.12 and SC 26.03. Not only, that 26.5 this version will not run on this machine, it will install but result in an endless loop of on screene messages about the crash a normal user ist not able to fix. I had to get in the car and drive to the client. The old version is deleted. No way to go back.

"dyld: lazy symbol binding failed: Symbol not found: _objc_alloc_init, Expected in: /usr/lib/libobjc.A.dylib"

This is not a difficult problem, it is thrown at start of the executable and tells that the software trying to run is not built for this system. I anyone had tried this release on 10.12 he would have noticed immediately of the problem.

Why does Connectwise does care so less for the Mac Admins and Users? Do they hate us?

I do not love macs, but out of 1200 clients 100 are using a Mac and 50 of these use older MacOSX versions. I still need to support these.

I know connectwise "older macosx version are supported on a best effort basis" - or similar, but for me the way it is done is not best effort. It is dangerous. If a program is not built compatible for a version X it should simply refuse to run - instead here the old version is deleted and the newer crashes. Think about what would have been happend if I had the auto-updates switch to on!

We pay for this software and support. Why cant we expect to get a release tested better? connectwise might need some hardware: an older macmini and a newer version, then install all major MacOSX version on these two, a IMO small investment and a few hours one-time effort. Then test every release with all versions. That might take three hours for every release. I dont think this is asked too much.

And then, why not build two versions of the Mac Client? Or at least try to use a compiler directive like "---mmacosx-version-min=10.9" and if this does not work, then document this in the release notes and disable automatic updating if the OS Version is >X.Y.

Finally, the very minimum is to pre-check if the software is able to run before the old version is deleted as a safeguard against unknown bugs!