A user asked about the behavior of ControlUp when running long scripts. It was clarified that if the same script is rerun before the first one finishes, a separate process will be started and the scripts will run one after another. It was also mentioned that this process will soon be automated and trigger only runs daily if needed. This was done to prevent running the scripts manually too aggressively.
Read the entire article here...
ControlUp Scripts & Triggers Training & Support Archives
ControlUp Script and Trigger training and support-related archives from inside the ControlUp Community on Slack.
Automating the Deployment of ControlUp for Compliance
A user asked about automating the deployment of ControlUp for Compliance (formerly known as Secure DX) for new physical machines. Another user shared a script that could run the installation silently. The script can be found at https://cdn.spm.controlup.com/agent. Instructions were provided on checking for the latest version and running the script if necessary.
Read the entire article here...
Read the entire article here...
Deploying ControlUp agent on MacOS with Workspace ONE UEM
A user asked for advice on deploying the ControlUp agent to a MacOS device using Workspace ONE UEM. Another user offered to check with the macOS agent development team for insights and asked for screenshots as well. The first user also clarified that they are looking for a correct plist file and suggested that scripting may not be needed. The conversation ended with the second user requesting to keep the screenshots. No resolution was provided yet.
Read the entire article here...
Read the entire article here...
Setting Up Alerts for SQL Always On Availability Group Failovers
A user asked for help with setting up an alert for a customer's SQL Always On Availability Group. Suggestions were made to use a PowerShell script or a scheduled trigger using the Edge DX agent. It was eventually resolved with the use of a PowerShell script that runs every 5 minutes and checks event logs for specific event IDs. No incidents are generated due to the potential scale of scheduled triggers.
Read the entire article here...
Read the entire article here...
Implementation of ControlUp monitoring for specific failed events
A user is looking to use CU to monitor their CA server for specific failed events, and wants to know if the trigger will work for each event. The trigger will only work for Warning or Error events, and one way to test it is by using a PowerShell script to generate a similar event on a machine with the CU agent installed. The script to create a test event is also provided. The event source must be created first if it does not already exist.
Read the entire article here...
Read the entire article here...
Using ListOfColumns Template Variables in ControlUp Triggers: A Helpful Tip and Exciting New Feature in the Works
Users discussed using ListOfColumns template variables for triggers and the impact of using them. One user shared an example of encapsulating the template with ListOfColumns to use multiple metrics in a trigger. Another mentioned that ListOfColumns can be replaced multiple times and added a warning about this. Another expressed excitement about the potential uses of this feature. The discussion also touched on the possibility of seeing the top 50 biggest files that were written and a suggestion for running a follow-up script to enrich the data. One user mentioned that the developer responsible was not available at the moment, but that more information would be shared soon and a real-time disk monitor was already available. It was suggested that the user hang on until Monday for a cool invite.
Read the entire article here...
Read the entire article here...
Simplifying Script Management in ControlUp
A user asked if there was a way to update or install all scripts at once, as well as if there was a way to filter or search for specific scripts. Other users discussed the drawbacks of having a menu with hundreds of options and suggested using the search function instead.
Read the entire article here...
Read the entire article here...
BSOD Events in ControlUp and How to Investigate Them
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...
Read the entire article here...
Troubleshooting a Trigger in ControlUp for Unregistered Citrix VDA Machines
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...
Read the entire article here...
How to Troubleshoot ControlUp Monitor Script Actions Not Firing
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...
Read the entire article here...