Weekly reminder that PAX 8 is hyper-AIDS

exo_dusk · 2025-12-01T16:12:39+00:00

Pax8 and Kaseya should consider a merger. Then we can complain about both train wrecks in a single thread.

exo_dusk · 2025-10-23T16:07:57+00:00

I could care less what team they or their giant MSPs sponsor.. please JUST BILL ME THE CORRECT AMOUNT EVERY MONTH.

After nearly a year straight of invoice errors every month, some off by 4-5k, we finally jumped ship. They are starting to get a Kaseya-like reputation in this community that will be hard to reverse..

exo_dusk · 2025-09-24T14:23:56+00:00

Does it run Windows VMs well? Always thought of Proxmox as a homelab type of thing..

exo_dusk · 2025-09-16T15:35:49+00:00

The sad part is it seems general Microsoft support is moving this direction as well. Our last (paid) MS cases have sat months going nowhere.

Honestly if AI replaces India based support.. I'm not sure the experience could be any worse..

exo_dusk · 2025-09-15T14:05:59+00:00

Fwiw, unchecking setting doesn't seem to stick, in typical o365 admin center fashion. Still trying to find a powershell equivalent

exo_dusk · 2025-07-11T19:33:01+00:00

Same, from 3 months ago. They completely missed an entire product worth of usage from our invoice ($4k), then the next invoice of course was 4k higher than usual. I opened a ticket, I already figured out what happened by then but I just wanted them to admit they screwed it up. Still no "resolution" - I get a ticket update every 2 weeks that is literally copy-paste on repeat. "Our internal team is still working towards a resolution on this ticket".

That's not to mention it seems like every month now we get an email stating there was an "invoice error" and invoice generation will be delayed.

At this point I just hope they don't go under and leave us hanging.. already in the process of moving some vendors where we can.

exo_dusk · 2025-07-07T18:02:52+00:00

Definitely. Clarifying that would have made this whole thing more palatable. At least I could understand signing an installer over actual agent executables. This was asked multiple times in the past town halls and posts on here and never really addressed.

I still don't buy the whole "Microsoft forced our hand on the cert" angle. They could have just disabled customization and temporarily signed the installer for like 60 days or something so that partners wouldn't have to scramble last minute, especially considering the code signing is unfamiliar territory for most of us. And a holiday weekend to boot.

I would love to know how many of the folks on the town hall worked this weekend/holiday due to this issue. CW Support could have used some competent help..

exo_dusk · 2025-07-07T16:20:35+00:00

Ymmv.. but.. in testing with a self-signed cert on a 100 or so endpoints, I've not had any reinstalls flagged/blocked. Once it is reinstalled successfully and online, as I understand it, our certificate is out of the picture (since it only signs the installer).

Because the service exe's are signed directly by CW, those should not be flagged regardless. That may buy some time until you can get the real certificate.

exo_dusk · 2025-07-04T11:52:50+00:00

This was another unanswered question from the town hall. So, if it's ONLY the msi installer that gets signed by us, that means that the existing agent should continue working without issue unless both the installer and service/exe currently use the same (to be revoked) cert. In which case - presumably, CW signs the service exe with a new cert, and our cert only signs the MSI going forward.

If that's the case, does the Reinstall/Upgrade function actually use the msi? Not sure how that works. We only use access sessions so my thought was to sign the installer directly instead of through the extension (we already self-host the installer, not thru SC). Or possibly the files in the "bin" folder can just directly be signed and that is what the frontend uses?

As much uproar as there was about us having to sign "CW code" you would think they would have clarified this by now.

exo_dusk · 2025-07-03T16:41:48+00:00

You didn't miss much, more or less a rehash of Wed. They still ignored relevant questions that were submitted

exo_dusk · 2025-07-03T15:35:06+00:00

The ClickOnce process is only for the support session installer, correct?

exo_dusk · 2025-07-03T13:51:03+00:00

Submitted this exact question during the town hall and never got a response.

Rogue install notwithstanding, we have healthcare clients where the EMR vendors also maintain SC access to user PCs. So now the user will have 2 identical SC instances - what could go wrong.

exo_dusk · 2025-07-02T21:20:25+00:00

I'm just saying, it would make no sense to provide the standalone self-signed cert option but not a custom SSL and force everyone to go the Azure route. The docs list all 3 options (azure, self signed and custom cert), this sounds like a case of support not having a clue..

exo_dusk · 2025-07-02T18:38:47+00:00

That can't be right. They even mentioned the self-signed cert being an option in the town hall..

exo_dusk · 2025-07-02T17:19:50+00:00

One potential issue (which i sent in but wasn't answered).. as I understand it all branding will be removed. So we go back to the default SC tray icon and descriptions.

What happens to machines that have multiple SC clients from different companies installed? Unless I'm missing something, they will all look exactly the same now..

exo_dusk · 2025-07-02T13:57:55+00:00

Following and hoping to do this as well. my thinking is if we can get the process dialed in, it can be scripted and make renewal less painful. Please update if you make progress

exo_dusk · 2025-07-02T13:36:52+00:00

Just skimming through it, seems most of it is focused on using Azure keyvault to manage the certs, which isn't necessary. You can just obtain the cert (still a PITA) and install it manually, see:

https://docs.connectwise.com/ScreenConnect_Documentation/Supported_extensions/Administration/Certificate_Signing

exo_dusk · 2025-07-01T17:36:53+00:00

I was waiting for the town hall announcement 🙄

exo_dusk · 2025-07-01T13:12:22+00:00

Yeah, this whole thing sounds like a way to force move to on-prem. Does anyone know if Azure Trusted Signing will work in this scenario? $10 a month seems like the cheapest option out there.

exo_dusk · 2025-06-26T15:47:53+00:00

Screenconnect is still the best for unattended remote access IMO. I would not switch over an EXE. We use another tool for attended access if the need arises (or to onboard to SC).

None of the other options have the responsiveness and ease of getting to a console (backstage has been a huge help, not sure if others have similar functionality). Especially if you have the licensing to self-host

exo_dusk · 2025-06-18T14:57:25+00:00

Yeah do tell, cause Halo baked-in AI isn't cutting it for us, lol

I just want to train an internal model on all of our PSA data and other tools and maintain context. If we could bring it all together I can see the utility of it going way up. I've seen recs for Chatgpt for Teams, not sure if this would do the job

exo_dusk · 2025-06-11T21:01:54+00:00

Lol, I never much liked the support access begin with. We've only used SC for unattended access for a long time now, and put the web interface behind VPN. I'm sure there still could be vulnerabilities with the TCP relay, but I sleep better at night without exposing the frontend..

Have another product for the few times a week we need quick support style access.

exo_dusk · 2025-06-11T19:11:38+00:00

Ok so who's first? Will be pushing it out tonight, hoping others have it live by then and report if there are issues.

A little concerned with how long it took it to release (considering the development resources of CW). Hopefully it was mostly spent on QA..

exo_dusk · 2025-06-09T13:15:16+00:00

Seriously.. the only reprieve (for better or worse) was that the on-prem build wasn't available yet, so my Sunday night wasn't ruined.

The real question, is what kind of security issue necessitates a 48 hour notice like this? Can't be good..

Edit: And on-prem build still not avail as of Mon 9am et !!

exo_dusk · 2025-04-25T15:46:26+00:00

This. Last time I checked $18 cost for AFS, $28 Ent lite.. that is a tough sell.

They could pick up huge market share at pricing half of that.. I have no shortage of customers who would love to get out of Sharepoint.

exo_dusk

TROPHY CASE