@Dashrender said in ScreenConnect Unable to Start on Fedora 33:

@scottalanmiller said in ScreenConnect Unable to Start on Fedora 33:

You can use an RDP client if you want for Windows users.

I've read that - I need to figure how how that works.

We have some customers using them, but we don't use them internally AFAIK.

@CCWTech said in Connectwise Control / Screenconnect recommends you break the law to run their software:

@JasGot said in Connectwise Control / Screenconnect recommends you break the law to run their software:

@scottalanmiller said in Connectwise Control / Screenconnect recommends you break the law to run their software:

spending so much time waiting for ScreenConnect to finally be able to load its device list. We spend just as much time waiting for SC's list to stop flashing from its load problems as it

How many clients?
What list?
SC is very fast in my experience.

2,000 clients and navigation and opening are fairly slow.

Have you used session filtering and subgroup expressions to keep any given window at a reasonable level?

We have thousands of clients sorted into hundreds of sub folders [for lack of a better word]. Our largest folder is 332 clients and it is loaded before I can get my finger off the mouse button.

@JaredBusch said in Chromebook and ScreenConnect:

@scottalanmiller said in Chromebook and ScreenConnect:

@JaredBusch said in Chromebook and ScreenConnect:

Heard more from the user.

Would prefer 15" screen and a numeric keypad... /sigh..

Found this one. https://www.amazon.com/Acer-CB715-1W-P4Y6-Chromebook-4417U-Chrome/dp/B07W996BQ5

Anyone have a comment on it?

Only 32GB, but it is supposed to be only for browsing and ScreenConnect.

32GB is PLENTY. I don't even need the 16GB that I have. And 8GB of RAM, that's a monster of a Chromebook. Should be way, way fast enough. Just really expensive is all.

Mostly it is the form factor, I think, 15” with the numeric keypad

True, the extra size brings up the price quite quickly.

@JaredBusch said in Chocolatey not available after being installed through ScreenConnect:

I guess you could cycle the screenconnect client service. That should do the same.

This did it; thanks. It's the only working solution short of a reboot. I did not want to connect to the client with SC so I pushed a re-install, it was current, so it just went through the motions and restarted the services. Perfect for my needs.

Holy cow, I just realized that we've been using MC since Dec, 2018. That's 27 months ago!

@JaredBusch said in ScreenConnect agent on Fedora fails rpm install:

rpm -U ConnectWiseControl.ClientSetup.rpm

ConnectWise Control version 19.0.23234.7027 resolved the failure to update. but they neglected to remove the old screenconnect version as the new install is named connectwisecontrol

bc755dec-f586-4439-a406-222af7737ed0-image.png