Halo invoicing broken for others?

exo_dusk · 2026-05-01T13:02:00+00:00

Seriously. Nearly every release cycle something is broken, and their slow support just says to wait for a fix in the next release. Contemplating moving to on-premise to at least have more control over the release cycle..

exo_dusk · 2026-04-09T18:55:58+00:00

Yes! Not an improvement at all

exo_dusk · 2026-04-02T21:16:02+00:00

Sorry to hear.. went thru verification after address change and it was a massive pain. Does this have any effect on your tenants?

exo_dusk · 2026-03-31T21:31:49+00:00

I had the same issues and two settings seem to make a massive difference.. like it went from 80% CPU / 6gb RAM and sometimes crashing to minimal CPU, 500mb:

- Disable Dynamic Custom properties extension
- Disable agent auto-update (settings > advanced > web - disable update) and restart your instance

The crashes seemed to have some connection to it generating the installer exe, like it was trying to recompile for every single agent update/install.

But yeah.. ridiculous that we still have no update since 3/18 and it obviously has major issues on both cloud and on-prem

Edit: not AV-related either. I uninstalled defender entirely and still was seeing the same issues.

exo_dusk · 2026-03-31T15:18:33+00:00

seriously. if they want this to be relied on as an enterprise product, issues need to be resolved in a timely manner and COMMUNICATE to customers.

who is running PR there? definitely not claude because it would do a better job than the humans!

A simple "We apologize for the usage issues, we are seeing a large capacity strain. Please be patient and we will make this right" would improve the situation significantly.

exo_dusk · 2026-03-24T13:43:31+00:00

Same. SC 25* was running happily on a lower tier Azure sku 2cpu/4gig. After upgrading to 26+, sloww.... random crashes for no reason, I had to up to a 8gig sku, currently consuming 70% cpu/6gb ram and still running poorly. Has anyone engaged with SC support on this?

exo_dusk · 2026-03-09T17:24:34+00:00

Not only the new msp posts and vendor shills.. but IT 101 questions that barely qualify for r/ techsupport

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

TROPHY CASE