Automating the addition of Virtual Desktop Infrastructure (VDI) machines to the ControlUp console upon agent installation can streamline management and monitoring processes. While ControlUp for Desktops offers a command-line installation method that automatically registers machines, a similar approach for VDIs requires specific configuration.
To achieve automated registration of VDIs, you can utilize the Install-CUAgent PowerShell cmdlet, which is part of the ControlUp Automation module. This cmdlet allows for the download and installation of the ControlUp Agent on local machines, including VDIs. By providing the necessary authentication key during installation, the agent registers the machine with your ControlUp environment. For non-domain-joined machines, an API authentication token is required. ([support.controlup.com](https://support.controlup.com/docs/install-cuagent-install-an-agent?utm_source=openai))
For non-persistent VDIs, such as those created from a master image, it's essential to configure the agent to handle these scenarios appropriately. By setting the agent as a master image, it ensures that new VDIs created from this image will automatically register with the ControlUp console, preventing duplicate entries and maintaining an accurate device inventory. ([support.controlup.com](https://support.controlup.com/v1/docs/agent-outbound-communication?utm_source=openai))
Additionally, enabling folder synchronization with your VDI infrastructure can further streamline management. This feature ensures that VDIs are correctly registered and prevents stale machines from cluttering the interface. By integrating with your VDI environment, ControlUp can automatically detect and manage VDIs, enhancing the efficiency of your monitoring and management processes. ([support.controlup.com](https://support.controlup.com/docs/connecting-to-your-vdi-infrastructure?utm_source=openai))
By implementing these methods, you can automate the addition of VDIs to the ControlUp console, ensuring accurate device registration and efficient management of your virtual desktop environment.
Read the entire article here...
Automation & Alerting Related Training & Support Archives
Automation & Alerting training and support-related archives from inside the ControlUp Community on Slack.
How to Alert on Added Storage Devices by Drive Letter in ControlUp Using os_disk_configuration Filters
A community member sought assistance with creating a ControlUp trigger or alert to detect when storage devices are added to a physical endpoint and assigned a drive letter or mounted. The data relevant to this event is visible in the ControlUp 4D (CU4D) Performance tab under the Operating System location and stored in the *_devices* index. Specifically, the data is found in the os_disk_configuration field, which contains a JSON array showing details about mounted drives, including drive letters. The user’s challenge was to configure an alert that could detect any newly mounted drive except the system drive C:\ without having to set multiple alerts for every potential drive letter (e.g., D:\, E:\, etc.). They noted the lack of regex support in the filter queries limited their options.
The issue arises because the os_disk_configuration field holds a JSON array with multiple drive entries, and filtering out drive_letter "C:\" naively removes all entries due to the structure of the array. Attempts to use a “does not contain” filter eliminated all Windows devices, only showing macOS devices, complicating detection on Windows endpoints. The user also tried to narrow the focus to removable media but learned that their security team's use case requires alerting on any disk, mounted by drive letter, which remains the best indicator available.
Advice provided during the discussion included adding filters for platform or OS to ensure the alert targets only Windows devices (e.g., platform set to 1 or OS equals Windows). This helped reduce irrelevant results but did not completely solve the filtering problem. Suggestions included playing with additional filters such as combining conditions to exclude drive_letter "C:\" while explicitly including removable devices, though this required trial and error. A recommendation was to test filter configurations in the CU4D index view, including setting the platform to 1 to target Windows devices specifically.
Ultimately, the thread highlights the challenge in using ControlUp’s current filtering capabilities on complex JSON arrays like os_disk_configuration for dynamic drive letters without regex support. The workaround involves narrowing the scope by platform/OS filters and experimenting with composite negation filters, although a straightforward out-of-the-box solution for this specific alert scenario is limited. Users needing comprehensive coverage for any drive letter other than C:\ must create a series of alerts or await enhanced filter features. For now, leveraging the detailed disk configuration data in the *_devices* index with strategic filter layering is the best approach.
For further reading on creating and troubleshooting alerts and filters in ControlUp, users can consult official documentation at https://docs.controlup.com and explore ControlUp Academy resources at https://cuacademy.controlup.com.
Read the entire article here...
Read the entire article here...
How to Diagnose Microsoft Teams SlimCore Optimization in Citrix and Other VDI Environments Using PowerShell Scripts
This discussion highlights two PowerShell scripts developed to aid tracking and diagnosing Microsoft Teams SlimCore Optimization specifically within Citrix environments, with potential applicability to Azure Virtual Desktop (AVD), Windows 365 (W365), and VMware Horizon sessions. SlimCore is an optimized media stack used in virtual desktop infrastructure (VDI) scenarios to enhance Teams call performance by offloading audio and video processing to the client side.
Read the entire article here...
Read the entire article here...
Issues with Failed Scheduled Runs on ControlUp
Multiple users reported issues with scheduled runs showing as failed despite successful manual runs. The ControlUp Engineering team has been notified to investigate. Additionally, there is a separate case regarding scheduled flows not firing. A user expressed their thanks for avoiding the need to open a ticket about the issue.
Read the entire article here...
Read the entire article here...
Managing Local Admin Privileges in ControlUp
A user asked for help with removing users from the local Administrators group when they are not allowed those privileges. Other members suggested using a script through the Action > System Scripts or utilizing the Compliance module. The conversation also touched on using specific triggers and including tags or device groups in the criteria for running the script. Ultimately, the user was able to find a solution through the use of device tags in the Scripts capabilities. The conversation can be found in the #channel channel.
Read the entire article here...
Read the entire article here...
Automation Issue Resolved by YoDeck Support in “Application” Framework
After investigating an issue with automation, it was discovered that the issue was resolved by the YoDeck Support team within the "application" Framework. A script was provided to assist with a button click code in the automation process. A screenshot was requested for comparison after the auto-fill process is completed. A script was also provided for inputting credentials into the fields. The button is clicked after the input. The issue was resolved by YoDeck Support within the "application" Framework.
Read the entire article here...
Read the entire article here...
ControlUp Synthetic Monitoring Workflows and Workarounds
A user named Alexander asked Nathan about a known limitation with ControlUp Synthetic Monitoring - specifically, that the server_name is often empty for NetScaler Gateway scouts. Nathan recommended a few different workarounds for auto-restart and suggested adding more fields to the webhook payload for debugging. The suggested workflow was to use resource and query ControlUp Real-Time DX / CVAD for machines or sessions matching the published resource.
Read the entire article here...
Read the entire article here...
Understanding Pausing Limits in ControlUp Workflows
A user asked about limits for pausing in workflows and how to disable alerts for maintenance windows. The topic was mentioned to two members. It was suggested that workflows have a maximum runtime of 2 hours and pauses may not be exempted from this duration.
Read the entire article here...
Read the entire article here...
Troubleshooting a Workflow Scheduling Issue in ControlUp.
Some users reported a workflow issue where a scheduled workflow still appeared as manual, even after changing it to scheduled. Another user suggested that selecting an interval and offset time may solve this issue. The post includes screenshots showcasing the problem and solution, and a user confirms that the issue has been resolved. The team has been alerted to this issue.
Read the entire article here...
Read the entire article here...
Automating Notifications for Users with Low WiFi Signal in ControlUp
A discussion was held about using workflows to automate notifications for a high volume of users experiencing low WiFi signal on corporate WiFi. Ideas were shared about centralizing events and using AI features in ControlUp to count the number of affected devices and trigger an email or teams message. The suggested solution involved querying the _devices and device_status to gather relevant data.
Read the entire article here...
Read the entire article here...
