Log into the Real-Time DX Console through a browser with your ControlUp account. You no longer need an Active Directory or a domain user. You can use SAML SSO or Azure/Google OAuth to access the Console, and you can SSO groups to manage Console permissions. User management is also simplified because you now access the Real-Time Console and app.controlup.com with the same account.
You can now create, read, update and delete triggers, and trigger actions, schedules and templates with PowerShell cmdlets, without having to access Trigger Settings in the Real-Time DX Console. You can efficiently perform bulk actions on triggers with increased flexibility, especially if you frequently update your organization’s triggers.
Improve visibility into the performance of Google Chrome and Microsoft Edge by collecting browser URL and browser tab title information on a per process basis. You can identify performance issues caused by specific web pages that might affect the overall performance of the user session or even other users sharing the same infrastructure.
You can now monitor Citrix EDT (Enlightened Data Transport) user sessions to gain better insight into users that access their virtualized Citrix environments using this method. You can benefit from enhanced real-time visibility into session reliability and performance.
You can now add non-domain joined machines to your organization with the Real-Time DX Console. You no longer need to use the Add-CUComputer PowerShell cmdlet to add a non-domain joined machine to the organization tree.
Released: June 16th, 2024
Current build: 1680
For 9.0, you need to whitelist new URLs on your console and monitor machines to access our new backend services. You can find a full list of required DNS and ports here (for US and rest of the world) and here (EU)
Note that there are additional URLs to whitelist on your agents, if you want to use the the agent outbound communication feature.
Reverse agent communication where agents initiate the communication (“outbound”) with the ControlUp Monitors. By default, monitor machines will expose a gRPC server for agent outbound connections (over TCP 443). However, to mark an agent as ready for outbound communication, you need to explicitly set agents to be able to communicate outbound.
Inbound port 40705 is still required for:
To learn more about this feature, click here.
This feature enhances visibility into the performance of your monitor clusters. These metrics are available in the VDI & DaaS view.
Note
Some of the new actions allow you to:
To learn more about this feature, click here.
To learn more about this feature, click here.
In 9.0, you no longer need to use the Real-Time Console to install, upgrade or remove a ControlUp Monitor. Simply import the new ControlUp Automation module from the PowerShell gallery. Once you import the module into a PowerShell session, you can use the built-in PowerShell cmdlets to manage monitors programmatically. This new approach allows you to deploy the monitor on any workgroup PC (non domain-joined).
To learn more about this feature, click here.
Synchronizing your AVD, CVAD, Horizon, and Citrix Cloud is now built-into RTDX. This allows you to add your virtual machines to the ControlUp organization tree without the need of manually adding them one by one. You can synchronize your machines manually from the console or by configuring the synchronization to be run automatically from your monitors. Synchronization options such as DNS mapping or Sites mappings are included, as well as the option to define specific host pools (AVD), desktop pools (Horizon) or delivery groups (Citrix).
To learn more about this feature, click here.
Install-CUMonitor Invoke-CUMonitorUpdate Uninstall-CUMonitor
Add-CUPolicyRoles Get-CUPolicyRoles Get-CUPermissionEntries New-CUPolicyRoleDescription New-CUPolicyRoleMember New-CUPolicyRoleAcl
Get-CUAPIProfile Set-CUAPIProfile Set-CUAPIToken
Add-AddHorizonEUCConnection Get-EUCConnections Remove-EUCConnection Update-HorizonEUCConnection
To learn more, click here.
You can now use Remote Control for VDI & DaaS which is available as an action in Solve and DEX. To learn more, click here.
Released: November 26, 2023
Current build: 1067
Important Notes
The Process Data Collection feature introduced in this version is enabled by default. Once you upgrade to 8.8 MR, system-level processes will automatically be filtered in the Real-Time DX Console and Solve.
Read this knowledge base article to learn how to add these processes to the Process Inclusion List.
Released May 1, 2023
Important Notes
The following metrics have been added:
Note
1. The new metrics are only available for the Windows Remote DX plugin which you can download from here.
2. Make sure that the client device has access to https://fabric.controlup.com
Released January 9, 2023
IMPORTANT: Version 8.7 includes many security enhancements described below. If you are upgrading from a previous version of ControlUp, you must follow this upgrade flow for all ControlUp users:
If you do not know who the organization owner is for your ControlUp environment, contact support@controlup.com.
In addition to NVIDIA GPU metrics, other GPU metrics are supported. GPU data is now retrieved from the Windows Operating System (WDDM), providing GPU metrics for a wide range of other graphic card manufacturers.
Prerequisites:
To gather the new GPU metrics, make sure the machine on which the GPU is running meets the following requirements:
The details of this Solve release are enabled by the Real-Time Console 8.7 release. The features and fixes described are available in Solve only when the Real-Time Console is updated to version 8.7.
Run built-in and script-based actions to remediate and optimize your environment directly from the Solve interface. Refer to the Getting Started with Solve Actions guide to learn more about this feature.
Prerequisites:
To use Solve Actions, you need to upgrade your monitors to version 8.7. Additionally, you need to have .NET Framework 4.8 installed on each monitor machine. Make sure that your ControlUp Monitors have access to http://solve.controlup.com over TCP port 443
Note:
If the user that runs a Solve action belongs ONLY to the Local Admin role, running a Solve action will fail even when the permission for the script is set to “Allow”. Learn more here.
By enabling the IP Restriction feature, you can now restrict who can access your Solve environment and perform actions in Solve based on IP address. You can add an IP whitelist to enable access only to those users from an IP address listed in your IP whitelist. Learn more.
We have now fixed the following bugs. Refer to the previous ControlUp release notes to see where the bugs were identified.
655 Build:
Released May 24, 2022
Note – starting version 8.6.5 the ControlUp Monitor requires to have .NET Framework 4.8
ControlUp Integration – PowerShell API
Triggers
Script-based Actions
Azure Integration
NOTE: Before upgrading your environment to v8.6.5.XXX, ControlUp recommends backing up your %appdata%/ControlUp directory by creating a copy of it and renaming it “ControlUp_old”.
This may prove useful if you need to revert to the previous version of ControlUp. Some new features require a change to the format or content of ControlUp configuration files. Therefore, if you need to downgrade ControlUp to a previous version, delete or rename the new “ControlUp” directory in %appdata% and rename the “ControlUp_old” directory to “ControlUp”.
The following is a list of known issues in the ControlUp v8.6.5.X general release. As these issues are resolved, this document will be updated:
Released February 17, 2022
ControlUp can now integrate with Microsoft Azure to enable real-time monitoring and management of Azure compute resources in just a few steps. See the relevant metrics displayed in the Real-Time Console and Solve.
The integration automatically discovers and collects comprehensive information such as Cost, Health, Configuration and other metadata on each of the following new objects:
In addition to offering a wide range of new metrics, predefined actions, and drill-down relationships for easier troubleshooting and navigation, this integration supports seamless association between Azure VMs and entities from different CU extensions, virtual machine management, and more!
For all the details on the monitoring Azure, see Getting Started with Azure Integration.
For version 8.5 we introduced the ability to create triggers based first on a schedule you set, rather than an incident.
Now for version 8.6, we’ve expanded the feature to include more options for the schedule which are now:
Read here about how to set scheduled triggers (article details the version 8.5 options).
Designed for remote users working outside the office, Remote DX collects performance metrics from off-the-network client devices running Windows, macOS or IGEL OS, without the need for line of sight to the ControlUp Real-Time DX infrastructure in your datacenter.
Previously available for Citrix and VMware Horizon environments, this release will add support for Microsoft RDS and Azure Virtual Desktop (AVD) environments running on Windows.
See these instructions for deploying Remote DX on your client devices.
ControlUp Solve allows you to see, in real time, the overall health of your EUC environment, end to end. Delivered as a SaaS application, Solve’s features are released independently. Here are features, some with a dependency on Real-Time DX v8.6, that are now being added to Solve:
NOTE: Before upgrading your environment to v8.6.XXX, ControlUp recommends backing up your %appdata%/ControlUp directory by creating a copy of it and renaming it “ControlUp_old”.
This may prove useful if you need to revert to the previous version of ControlUp. Some new features require a change to the format or content of ControlUp configuration files. Therefore, if you need to downgrade ControlUp to a previous version, delete or rename the new “ControlUp” directory in %appdata% and rename the “ControlUp_old” directory to “ControlUp”.
The following is a list of known issues in the ControlUp v8.6.X general release. As these issues are resolved, this document will be updated:
Centralized Auditing
ControlUp Solve
Released October 17, 2021
Version 8.5.1 introduces a security enhancement that we strongly urge our customers to adopt. This version includes using trust certificates to log into ControlUp Consoles and communication to the ControlUp Monitors. You set advanced authentication in the organization settings and they are applied to the monitors. For details, see Certificate-Based Console and Monitor Authentication.
88559 – The Real-Time Console no longer freezes when users log in with Active Directory credentials that have been hardened for security.
NOTE: Before upgrading your environment to v8.5.XXX, ControlUp recommends backing up your %appdata%/ControlUp directory by creating a copy of it and renaming it “ControlUp_old”.
This may prove useful if you need to revert to the previous version of ControlUp. Some new features require a change to the format or content of ControlUp configuration files. Therefore, if you need to downgrade ControlUp to a previous version, delete or rename the new “ControlUp” directory in %appdata% and rename the “ControlUp_old” directory to “ControlUp”.
The following is a list of known issues in the ControlUp v8.5.X general release. As these issues are resolved, this documentis updated:
Released June 29, 2021
ControlUp extends our digital experience capabilities by enabling you to now monitor remote client devices when they are logged into your virtual network. You can see metrics on how well the device’s connections are performing when your end users are remotely logging into your VPN or VDI from anywhere.
These metrics are collected per device for those devices that have the Remote DX .DLL installed. Once collected, these metrics appear in the Real-Time Console and in the Solve interface.
Scheduled Triggers are time-based triggers that fire at specified times. A trigger’s condition can be based on time only, or a combination of time and other parameters. This version includes a one time schedule or hourly recurrence with an interval of 1-24 hours.
Here are just some applicable use cases:
NOTE: Before upgrading your environment to v8.5.XXX, ControlUp recommends backing up your %appdata%/ControlUp directory by creating a copy of it and renaming it “ControlUp_old”.
This may prove useful if you need to revert to the previous version of ControlUp. Some new features require a change to the format or content of ControlUp configuration files. Therefore, if you need to downgrade ControlUp to a previous version, delete or rename the new “ControlUp” directory in %appdata% and rename the “ControlUp_old” directory to “ControlUp”.
The following is a list of known issues in the ControlUp v8.5.X general release. As these issues are resolved, this document will be updated:
Centralized Auditing
ControlUp Solve
Released April 22, 2021
ControlUp Agents authentication methods enhancements
ControlUp Agents communication channel security improvements
High resolution support improvements for the Real-Time Console
Top ribbon fills the whole Console width on high resolution displays.
Citrix Cloud – cloud connector status improvement
No new known issues for version 8.2.5. For a list of existing known issues, read version 8.2 known issues.
Released March 8, 2021
Improved Support for RDP-SxS (WVD) Session Monitoring
Improved support for monitoring performance metrics of Microsoft RDP-SxS remote sessions. These sessions are the side-by-side RDPs used in Windows Virtual Desktop (WVD). The monitored performance metrics include existing metrics that ControlUp already monitors plus these four new columns (also supported for “standard” RDP) :
vSphere hosts connection status
The Hosts view now includes a new metric that indicates the vSphere hosts connection status with their vCenter. The following column was added:
No new known issues for version 8.2.1. For a list of existing known issues, read here.
Released January 19, 2021
Citrix Cloud
Full integration with Citrix Cloud is available for ControlUp 8.2 and up, making it possible for customers that use Citrix Virtual Apps & Desktop service to monitor their EUC environment with ControlUp.
Horizon RDSH
ControlUp can now discover Horizon RDSH components and offer real-time visibility of RDS sessions and applications.
The new RDSH objects in the Horizon integration are displayed on the tree and data grids, with drill-down relations for easy troubleshooting and navigation.
The new views include real-time metrics that display the current configuration, availability, aggregation counters, health status, and other metadata on the following new objects:
Centralized Auditing (CA)
This feature is currently in Preview and we’re working hard to improve it. It’s ready for you to use but please report any issues you may encounter.
Other enhancements
ControlUp SOLVE
ControlUp SOLVE gives you comprehensive, real-time monitoring and analysis in a hosted web application.
Accessing ControlUp via a web interface means there is less resource consumption on the endpoints that are logging in and viewing the data, giving you and your users a leaner, more performance-driven experience.
ControlUp SOLVE provides a wide range of new functionality, including:
NOTE: Before upgrading your environment to v8.2.0.732, ControlUp recommends backing up your %appdata%\ControlUp directory by creating a copy of it and renaming it “ControlUp_old”.
This may prove useful if you need to revert to the previous version of ControlUp. Some new features require a change to the format or content of ControlUp configuration files. Therefore, if you need to downgrade ControlUp to a previous version, delete or rename the new “ControlUp” directory in %appdata% and rename the “ControlUp_old” directory to “ControlUp”.
Centralized Auditing
ControlUp SOLVE
Released October 27, 2020
1) | Resolved an issue with the “Machine Down” Trigger setting, which prevented the settings from being saved properly (#70643). |
2) | Resolved an issue that caused the Trigger to fire every time a machine is brought down/offline/disconnected (#70577). |
3) | Resolved an issue with the “Failover List” tab, which, in some cases, did not display all Horizon Connection servers in a cloud pod environment (#68757). |
4) | Resolved an issue with the AppLoadTimeTracer.exe that was causing IE to crash (#71951). |
5) | Resolved an issue where some Citrix Networking (formerly NetScaler) columns appeared empty (#69183). |
6) | Resolved an issue when editing the Data Source Site Distribution in the Monitors Settings screen, configuration changes were saved automatically without clicking OK (#70896). |
7) | Resolved an issue in Horizon where integration Desktop Pools were not being displayed on the organization tree in case pool provisioning was disabled due to an error (#75162). |
8) | Resolved an issue in Horizon integration, when using the agent as a data collector Pool built-in actions would fail with the error “Object reference not set to an instance of an object.” (#71428) |
9) | Resolved an issue with Active App/Active URL features that caused the cuagent.exe to consume a high amount of CPU on machines with thousands of running processes (#76231). |
10) | Resolved an issue with the internal session id assignment mechanism that caused duplicate session ids (#74115). |
11) | Resolved the “no legible target” error; added cache for selected records (#76006). |
12) | Resolved an issue on Horizon Machines data collection – “an item with the same key has already been added” (#76446). |
13) | Resolved an issue on Powershell module that caused the add/move machine operations to fail (#74868). |
14) | Resolved an issue on the upgrade procedure that caused Machine to “disappear” from the org tree after the upgrade from 7.4 to 8.1.x (Cloud) (#72502). |
15) | Resolved an issue that caused the Console to crash when adding a monitor that was reinstalled on a machine with a changed domain (#74399). |
NOTE: Before upgrading your environment to v8.1.5.649, we recommend backing up your %appdata%\ControlUp directory by creating a copy of it and renaming it “ControlUp_old”.
This may prove useful if you need to revert to the previous version of ControlUp. Some new features require a change to the format or content of ControlUp configuration files. Therefore, if you need to downgrade ControlUp to a previous version, delete or rename the new “ControlUp” directory in %appdata% and rename the “ControlUp_old” directory to “ControlUp”.
1) | While ControlUp can monitor large environments with dozens of endpoints, if the Console is connected to more than 5000 data sources at one time, the performance of the ControlUp Console could be impacted. Under these conditions, please avoid connecting to the entire organization at once. For sizing recommendations, refer to the ControlUp Sizing Guidelines. |
2) | For the v8.x Monitor Cluster architecture to work properly, all of your Consoles must be upgraded to v8.0 or higher. Your Data Collectors must be upgraded as well. Other agent upgrades are recommended, but are not mandatory. |
3) | Triggers on the Accounts and Applications views are supported for Citrix Virtual Apps & Desktops data only. Aggregated process triggers are not supported. As a workaround, process triggers can be defined on the single process level (Process View). |
4) | When the focus is on a folder and you browse to another folder in the tree, you must remove the focus from the first folder before you can focus on another folder. |
5) | When data source fails to connect to the ControlUp Console because it has failed to retrieve shared credentials from the monitor, the Credentials field will show an ‘Obtain password’ message (#67132). |
6) | Logoff Session Forcibly Fails: action fails to complete when the VMware Horizon session is locked (#66380). |
7) | ‘Client IP’ column may display 127.0.0.1 instead of the actual Client IP on VMware Horizon sessions (#65091). |
8) | ‘HZ Pod’ column shows as empty for some Desktop Pool records. |
9) | Horizon and vSphere machines will appear as two distinct entities if the machine is powered off and has no guest name entry on vSphere (#72426). |
10) | In Horizon integrations, configuring desktop pools with the same name will cause the folder aggregation metrics to fail on one of the duplicate pools. As a workaround, ensure all desktop pool names are unique (#76944). |