New Features and Enhancements
The following security enhancements were added:
- Prevent ControlUp users from logging into ControlUp organizations for which they do not have privileges.
- Users need to enter an OTP code sent to their email address when they start the Console and log into a ControlUp organization.
- The OTP is saved for 14 days, so users won’t need to enter it again for that period.
- Organization owners and users with the Login Access Manager role are now the users that can permit access to the Real-Time Console and Insights.
Support for non-NVIDIA GPU metrics
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.
To gather the new GPU metrics, make sure the machine on which the GPU is running meets the following requirements:
- Windows 10 or higher
- Windows Server 2019 or higher
- 113191: SSH connection is forcibly closed when connection to IGEL 11.07.x.
- 123526: CuMonitor process fails to stop after service is stopped.
- 121823: Description for trigger condition “AWS Attached Snapshot Hourly Cost” is cut off.
- 123887: Remote DX – CUEPUX_VIRTUAL_CHANNEL_ERROR when switching between sessions.
- 124355: The register page appears after logging into the Console, even though it shouldn’t.
- 124600: After restarting cuAgent, Remote DX displays N/A for Citrix sessions.
- 124601: Remote DX displays data for disconnected sessions.
- 124781: When Wi-Fi settings are changed during a Citrix/Horizon session, Remote DX does not update Wi-Fi metrics.
- 124829: After restarting cuAgent, Remote DX displays N/A for Horizon sessions.
- 124987: When switching from Wi-Fi to Ethernet, Remote DX does not refresh data.
We have now fixed the following bugs. Refer to the previous ControlUp release notes to see where the bugs were identified.
- 81183: Executing Monitor PS cmdlets succeeded with wrong error description.
- 85225: It is possible to see stress levels more than 100%.
- 97011: No tooltip display when Linux connection fails.
- 100279: Console – Multiple instances of the console process are running on the same machine after closing.
- 100379: Issue with trigger “Do not record incident” schedule does not work.
- 100544: Console – After deleting AWS connection and adding a new one, opening the connection settings shows the settings of the removed connection.
- 100554: Too much text in the license tooltip.
- 100570: Imprecise tooltip information in the License window.
- 109844: “ CVAD Logon” tooltip indicates value in milliseconds, though the metric shows seconds.
- 101203: Logon Duration stops reporting statistics unless CUAgent is being restarted.
- 108372: Missing .NET FW 4.8 validation upon upgrading monitor.
- 110179: The Central Auditing Log does not correctly indicate From/To State filters.
- 110399: Using Console triggers, REST API FUA with failed test can be saved.
- 110543: Console trigger scope multi-selection: only a parent node can be checked when all its children are not and vice versa.
- 110561: There is no indication that all checkboxes are checked or partially checked when selecting the trigger scope.
- 110679: Not all Azure virtual machines are displayed in rare cases.
- 111397: Console triggers: Empty UserName variable values in the trigger email/event.
- 111032: AZ Forecast Cost shows 0 after several hours.
- 111036: Export-CUQuery cmdlet: Output file is missing entries.
- 111169: .NET script execution passes positional and named parameters that have a space enclosed in double quotes.
- 112455: Citrix Cloud connection failed when using proxy server.
- 112500: Remote DX – Wi-Fi signal is displayed in orange or red color at the beginning of the session.
- 113929: Stress Levels do not apply when using Disk Read/Write KB/s.
- 114530: NullReferenceException with .NET engine script execution.
- 117279: Script Action activity has wrong Credentials, RequestingUser, RequestingUserSID values in Central Auditing.
- 118616: “BrowserURL” and “Active Application” cannot be disabled.
- 118729: Setting a registry key value with types REG_MULTI_SZ (multi-string value) or REG_BINARY shows wrong values
- Binary values (REG_BINARY) were displayed as “System.Byte”
- Multi-string values (REG_MULTI_SZ) were displayed as “System.String”
- 121462: Monitor can’t log in to BE and throws an error message in the Console “Access to ControlUp backend is not permitted”. The error occurs when the CultureInfo of the monitor OS is not set to English.
- 121498: Unable to use Solve Actions when subdomains are configured in the monitor settings.
- 121973: Real-Time Console freezes if you auto-connect a large number of managed machines at the same time.
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.
New Features and Enhancements
You can now run built-in actions in Solve. Refer to the Getting Started with Solve Actions guide to learn more about this feature.
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.
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.
- 125954: The folder tree lacks/incorrectly displays machines and their folder paths