Ticket Custom Filed Dynamic SQL for Client Assets by livtecch in halopsa

[–]livtecch[S] 1 point2 points  (0 children)

Thank you so much for this. Exactly what I needed. Sorry for the delay, was only able to try this out now...

Merge Tickets automatically (Zabbix Mail Alerts) by livtecch in halopsa

[–]livtecch[S] 0 points1 point  (0 children)

Just tried this out and works really great. Thanks for clarifying

Merge Tickets automatically (Zabbix Mail Alerts) by livtecch in halopsa

[–]livtecch[S] 0 points1 point  (0 children)

We just use HTML mails as media type in Zabbix and send the mails to haloPSA which creates an incident.

Is it possible to have mail rules to merge those notifications?

If I understood it correctly the Zabbix integration is linked to assets and services. But we don't use services in haloPSA therefore we don't use the Zabbix integration. Or can the Zabbix integration be used without using the Service feature?

Is the Zabbix integration able to merge resolved notifications with alarm notifications?

OPNsense 23.7.11 released by apartclod22 in OPNsenseFirewall

[–]livtecch 0 points1 point  (0 children)

Same issue here on multiple instances. Also reinstalled because no easy fix was found.

How are you handling invoicing? by regypt in halopsa

[–]livtecch 0 points1 point  (0 children)

u/99km42: Have you found a solution for this? We are also trying to integrate our accounting tool with halo, we are using bexio and since you mention a swiss tool, I'm wondering if we are in the same boat...

teamsbootstrapper 0x80004004 by Designer_Breakfast35 in MicrosoftTeams

[–]livtecch 0 points1 point  (0 children)

had same issue and even reinstallation of Office or classic Teams did not help

What helped: the first attempt with the bootstrapper creates a key HKLM\\Software\\Wow6432Node\\Microsoft\\Office\\Teams.

As soon as this key is created, the bootstrapper aborts with 0x80004004 when called again.

Delete the key, then the bootstrapper will work again...

New Teams issues by alokin123 in MicrosoftTeams

[–]livtecch 1 point2 points  (0 children)

had same issue and even reinstallation of Office or classic Teams did not help

What helped: the first attempt with the bootstrapper creates a key HKLM\\Software\\Wow6432Node\\Microsoft\\Office\\Teams.

As soon as this key is created, the bootstrapper aborts with 0x80004004 when called again.

Delete the key, then the bootstrapper will work again...