ControlUp Community

Connect, Learn, and Grow

ControlUp Scripts & Triggers Training & Support Archives

ControlUp Script and Trigger training and support-related archives from inside the ControlUp Community on Slack.

BSOD Events in ControlUp and How to Investigate Them

Posted on

A user asked about BSOD events in ControlUp and shared that they have around 700 devices and 3-5 BSOD events per day. Another user suggested using the BSOD analysis script from the library to get more detailed information. After looking into the reported BSOD event, it was unclear if it was an actual BSOD or just a minidump. The user wanted this issue resolved and was willing to provide any necessary information. The power events tab in ControlUp can be checked to see if a machine rebooted during a reported BSOD event. The user was unsure if the machine had automatically rebooted when the user was not at their device.

Read the entire article here...

Troubleshooting a Trigger in ControlUp for Unregistered Citrix VDA Machines

Posted on

A user needed help with a trigger that should detect an unregistered Citrix VDA and trigger an OS reboot. They were wondering if the trigger needed to be tagged against the folder with the delivery controllers. Another user suggested trying switch from "uptime" to "triggerable uptime". This solved the issue, and the second user also explained the difference between "uptime" and "triggerable uptime" metrics. The user who originally asked the question also wanted to know how ControlUp checks for CVAD registration, as they were experiencing some false positives. The conversation ended with the user stating their issue with automatically resolving alerts when ControlUp detects that the machine is back to normal.

Read the entire article here...

How to Troubleshoot ControlUp Monitor Script Actions Not Firing

Posted on

A user encountered an issue with script actions not firing as expected on a ControlUp Moniter. This led to a discussion on potential solutions and troubleshooting steps, including checking the script location and examining monitor logs. The user ultimately decided to look into the issue further when they have access to the customer environment. Troubleshooting steps and suggestions were provided by other members in the Slack discussion.

Read the entire article here...

Troubleshooting Trigger for D:\ Drive Alert

Posted on

A user asked for help with a trigger - they were trying to set an alert for when their D:\ drive goes below 500 GB, but the specified trigger was not working. Another user provided a solution and promised to post screenshots. The solution involved changing the File System Path to D:\*

Read the entire article here...

Real-time Monitoring for Registry Changes on ControlUp VDAs

Posted on

A user asked for a way to monitor a registry key or value on a VDA and trigger an action (script) to run if the value changes or is null. Another member suggested using ETW to track registry changes or creating a scheduled task that runs every X seconds to check the key with PowerShell. Real-time monitoring is desired in order to prevent necessary audit trails from being lost.

Read the entire article here...

The Best Trigger for Removing a File After Boot Up in ControlUp

Posted on

Multiple ControlUp users discuss the best trigger to use for deleting a specific file shortly after a machine is booted. Suggestions include using a scheduled task or event ID based trigger. The file causing the issue is a OneDriveStandAloneUpdater.exe, which consumes a large amount of cache space when running. The preferred trigger is determined to be a scheduled task set to run a few minutes after machine startup.

Read the entire article here...

Using ControlUp Scripts to Power On Virtual Machines

Posted on

A question was asked about a specific script from the ControlUp Script Library that powers on a virtual machine. The user asked if the script could also run a custom script on the local VM, explaining that their base image requires a specific patch agent service to be enabled and started at power on and disabled at shutdown. Another member replied that the script only performs a poweron action through CUmonitor and uses the hypervisor connection already set up. No reference is included in this summary.

Read the entire article here...