ControlUp Community

Connect, Learn, and Grow

ControlUp Agent Related Training & Support Archives

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

Deploying ControlUp agent on MacOS with Workspace ONE UEM

Posted on

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...

Setting Up Alerts for SQL Always On Availability Group Failovers

Posted on

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...

Implementation of ControlUp monitoring for specific failed events

Posted on

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...

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 W365 CPC Integration and Visibility Issues

Posted on

A group of ControlUp members discuss issues with the integration between W365 CPC and HDX. They note that EdgeDX does not detect brokering of a Cloud PC session, but the current configuration does show access to TURN and use of UDP. The group mentions that this may be due to the VDA configured on the device. There is also mention of potential confusion around which agent to use for the CPC Desktop, and a suggestion to pull a query to track the number of CPCs with a VDA installed and see what is reported. It is noted that there is interest from established enterprises to go this route.

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...

Troubleshooting WMI Memory Leaks with ControlUp cuAgent

Posted on

A user reported that at a customer, WMI memory leaks were happening due to the use of cuAgent on machines using ControlUp 8.8 or higher. Removing cuAgent resolved the issue and a ticket with support was created. They suggest using a ControlUp script (https://www.controlup.com/script-library-posts/show-local-wmi-activity/) to obtain WMI logs and identify the problematic cuAgent WMI queries.

Read the entire article here...