Ticket details
- Priority
- Priority 3 - Medium
- Type
- Consulting
- Owner
- Unassigned
- Last updated
- —
Initial description
No description
Read-only review and response drafting
Ticket #15686
Acumen Technology · Eric Albertson · Pending Close
No description
Tim,
I'm working on creating a monitor for ScreenConnect either not installed or not running and would appreciate it if you could
double check what I've done and what needs to be corrected. The monitor is set as an Internal Monitor; AT - ScreenConnect missing/not running \(974541\). If it detects a failure \(service is either missing or not running\), it runs ScreenConnect Repair \(ScritpID:6733\). I did not specify an OS in the initial creation, but I believe the script as configured would be only effective on Windows OS, and I plan to address Macs after I get this initial configuration set up correctly. The goal is that if the circumstances are detected, it runs the repair script and if that is not successful, open a ticket. The Service Ticket #1268751 - ScreenConnect Missing or Not Installed is a result of the monitor, but it combined alerts for 2 separate endpoints automatically, as far as I can tell. Any advice/suggestions appreciated!
Thanks,
Eric Albertson | NOC Administrator
Support: 615.744.2001
[__A__](https://acumentechnology.com/)[__cumen Technology__](https://acumentechnology.com/) | 2699 Fessey Court, Suite 200 | Nashville, TN 37204
Tim,
Sorry, it’s been a little bit since I’ve gotten back to this. As this alert is monitoring for a missing piece of our support software, my hope is that the scripted process to create a ticket would be open the ticket Acumen \(ATECH\) ticket instead of the tenant owner of the endpoint. Is that possible to be configured?
Thanks
Eric Albertson | NOC Administrator
Support: 615.744.2001
__[A](https://acumentechnology.com/)[cumen Technology](https://acumentechnology.com/)__ | 2699 Fessey Court, Suite 200 | Nashville, TN 37204