Your comments
No it was horrifically bad with under 200 clients.
Sadly the Windows version works well, but I now own a VM that I don't trust...
Ironically I was forced to move my install to Windows because of a client requirement - something I said I would never do.
But Connectwise please note- I also was able to install Powershell, .NET and other frameworks to my Mac the other day, they work just fine...
@Wwarren we can always hope. I don't know what the engineering burden would be to get the versions in sync, but it does appear to be a good strategy if
1. you want to be known as a multi platform company
2. you want to offer alternatives in case, say, SSO stops your main product(s) from working
and so on...
Currently we are at a stalemate- I'm not putting any more money into my 6 licenses until CW make a public commitment to Control Linux.
I can run up open source alternatives that have better long term prospects for each of the platforms I support, but ultimately I'd prefer to pay for something I'm already invested in.
Cool projects get abandoned, I'm just surprised that Control has so much promise and is being left to die by beancounters
I completely disagree that it's time to accept it's over and migrate to Windows. Connectwise always have the option to do that but if they do they lose me as a customer.
The rest of the world is moving towards Linux in a big way- the phone system I use, the servers I use, Docker, Kubernetes etc.
Even Windows is introducing a Linux subsystem. I don't support any Windows servers and will only do so for clients, not suppliers. I have options if I need to move - I don't want to, but I simply don't have time to support another OS
Could someone from Connectwise please give us an official answer on this?
I am currently using HAProxy with Centos to get TLS v1.3 compatibility
I am keen to build a new Ubuntu/ Debian VM to run without HAProxy, but can't do anything until this is conformed. Although v19.6 Stable doesn't appear to be available right now anyway...
I've actually written this up but couldn't find anywhere to submit to the community
https://servicemax.com.au/tips/connectwise-control-pppc-profile-in-mosyle/
voted for this- as the downloaded Mac installers are not signed, you can't extract a developer ID from them. This means that you can't easily add a kext whitelisting profile. And that means you have to walk users through whitelisting it manually...
Customer support service by UserEcho
Hi Andrew,
I appreciate the extra info, but let's be clear. up until macOS Sequoia we had the ability to right-click and open unsigned installers. This has gone away. Using System Preferences/ Privacy & Security 'Open Anyway' requires Admin privileges which none of our users have, so I did not consider this a viable option.
- ScreenConnect is a major part of our stack
- Apple has been saying unsigned installers would be disallowed for a decade
- bypassing the enforcement is incredibly poor
Dear Connectwise,
Having signed installers is a requirement. It is not optional. You've had a decade to re-engineer this.
From my limited experience it doesn't look too hard, you just need to separate the hardened / notarised installer from the preferences which are custom.
I'm super annoyed that I've had to purchase an alternative (and less good) product because one day we may not be able to use yours due to your lack of interest.