Windows Agent

New Features

• ControlUp for Desktops now has improved support for devices that get reimaged. You can use the REGISTERWITHNAME=1 flag to use the device’s name as its ID. When the device is reimaged, ControlUp recognizes it as the same device if the name remains the same. Learn more.

• The following metrics are now recorded in the device_status index:

  • memory_page_reads_sec - Memory page reads per second

  • disk_usage - Disk usage percentage

  • cpu_max_core_usage - Highest single core CPU usage

  • gpu_usage - GPU usage

  • device_temp - CPU temperature

  • network_in_usage_pct - Network In usage percentage

  • network_out_usage_pct - Network Out usage percentage

  • network_in_link_speed_bytes_per_sec - The Network In link speed

  • network_out_link_speed_bytes_per_sec - The Network Out link speed

• The following metrics are now recorded in the _devices index:

  • battery_cycles - Number of battery charge cycles.

• Application crashes in the win_event_log index are now broken down into different categories:

  • Foreground application crashes (event ID 61004) - The foreground application is the one that is actively being used.

  • Windowed application crashes (event ID 61005) - Windowed applications have a visible window but aren’t actively being used.

  • Background application crashes (event ID 61006) - Background applications do not have a visible window.

• The following fields are now in the power_events and win_event_log data indices, making it easier to correlate events such as BSODs:

  • os_name

  • os_patch_string

  • os_version_string

  • hw_manufacturer

  • hw_model

Fixes

• Improved Remote Control reliability by fixing issues causing connection failures.

• Improved capture of BSODs on Windows 11 24H2.

• Windows Firewall status missing for some device.

• Power events missing for some devices.

• Hardware CPU name missing for some devices.

• Latency targets configured to use TCP protocol were using ICMP instead.

Known Issues

• In some cases the agent is not reporting application crashes correctly, leading to inconsistencies between various crash details reports, and employee experience scores being unaffected by crashes.

• Battery health for Windows devices always reports 100%.

• Devices using a Wi-Fi connection are reported as having a wired connection.

New features

• Support for Windows 11 version 24H2.

• The Agent now collects data about all connected displays such as the resolution, orientation, rotation, interface type, serial number, etc. This information is in the new data index Builtin_peripherals. Learn more.

• Updated UPN detection to prevent identifying employees with their personal email addresses. Employees are now identified using their accounts signed into applications on the device (such as Microsoft 365) only if you have created a list of approved domains.

• Updated the Agent to compile using .NET 8. Note that this is self-contained within the Agent and does not require you to update your devices to a specific version of .NET.

Fixes

• Improved detection of Citrix-optimized Microsoft Teams calls. Learn more.

• Customizing device geolocation by IP address range wasn’t working correctly. Learn more.

• Added support for TLS 1.3.

• Improved logging.

New Features

• Remote Control and Remote Shadow sessions can now automatically reconnect in case of a network connection interruption or device reboot. Automatic reconnect after device reboot is currently in beta testing and supported only on Windows, and must be manually enabled. Learn more.

• Added a tooltip in the Sentiment survey response window to inform respondents when they are completing a non-anonymous survey.

• The Agent now collects information about non-responding applications, including whether the app recovers (app freeze with event ID 61003), or is eventually killed (app hang with event ID 61002).

• The Agent now collects additional Blue Screen of Death (BSOD) data to help identify the driver that caused the error.

• More hardware model name information for Lenovo devices.

• Added Remote DX server-side DLLs for future product enhancements.

Fixes

• Improved reliability of recurring surveys.

• Incorrect system CPU calculation.

• Improved detection of User Principal Name from Microsoft Teams and Office.

• Faster WebSocket connection after a network change or outage.

• Improved process friendly name detection.

• The user is not considered Idle during a video conference or other application that prevents system idle state.

• Fixed an issue that caused the Agent to download built-in scripts multiple times.

• Fixed errors during Agent Manager updates.

• Employee Sentiment questions/answers positioning over the background was incorrect.

• Employee Sentiment pop-up notification was missing the 1 hour “Snooze” option.

• Improved agent logging.

• Company name changed and icon updated for all agent components to ControlUp Technologies Ltd.

• Improvements update method for the UCC data capture dll.

• Improved reliability of Power Event capture.

• Added support for new Agent version control settings to control the timing of Agent installation.

• Security improvements

• Fixed an issue when connecting to your tenant through the GUI installer.

• Made it more difficult for end users to stop the Agent Manager service.

• Improved error message when unable to download Agent MSIs.

New Features

• Added support for the improved Employee Sentiment feature for delivering customized surveys on Windows devices. Learn more.

• The Agent now collects user information and activity for the first user physically signed into the device (console user) OR the first user remotely signing in to the device. Previously, data was only collected for the first console user.

• Secured the ControlUp SIP Agent service to make it more difficult for end users to stop the service on their device or change the service start settings.

• Added per process network IO counts to process_stops index.

• Added device platform id into process_stops index to allow filtering by platform.

• Improved BSOD data collection from WER. To see the collected data, go to the power_events data index and filter on event_type = BSOD-WER.

• If you set the ProxyAddress registry key to the string “0”, the Agent will never use a proxy, regardless of environment variables.

• Additional WiFi information is now collected, including:

  • RSSI

  • Auth type

  • 802.11 network type

  • Center frequency

  • Channel number

  • Tx Speed

• Additional data is collected to improve the Employees view. Note that this feature is currently available only for certain customers.

Fixes

• Agent data collection for UC&C monitoring could cause Microsoft Teams to crash. If you previously implemented the workaround solution, then the workaround is no longer necessary if you upgrade to version 2.14.

• Some script output uploads failed due to empty strings. We changed the validation to allow empty strings.

• Improved discovery of foreground app friendly names.

• The Live Callers Dashboard sometimes showed rows with no active call.

• When a device was rebooted from Edge DX, the pop-up window warning the user that their device is about to be rebooted wasn’t showing any text.

• Temporary CustomActions.dll file is now signed during install.

• Improve error handling during service enumeration.

• Improved error handling for AddNetworkInfoToDeviceMetrics exception to prevent crashes,

• The custom setting IgnoreCpuQAfterLogonSeconds was not working correctly.

• Password protected uninstall was not working in some situations.

• ONLYSTARTONBOOT installation option.

Fixes

• UCC monitoring data for Ctirix optimized Microsoft Teams was not available when using the latest ICA client. Learn more.

New Features

• Device performance data is now more accurately collected with high frequency data collection. Seven metrics from Windows Performance Counter are now captured every 3 seconds and averaged for a more accurate data representation in each sample.

• More information about blue screen errors (BSODs) is now collected using Windows Error Reporting (WER) files.

• The Agent can now collect VDI metrics such as active remote sessions if the Remote DX plugin is installed on the device.

• The Agent can identify the user on a device using the accounts signed in to specific applications such as Microsoft 365 or Microsoft Teams.

• Process ID 4 (System) is now included in the list of processes collected on a device. This is reported in the list of Active Processes, and the list of processes with high resource consumption in CPU and Memory charts. You can use the CPU and Memory usage on this process to identify when a kernel process (such as a device driver) is causing high resource usage.

• Disk drive space and disk configuration (partitions, volumes, etc.) is now updated every 60 seconds.

• Additional hardware and performance information is now collected. The following columns are available on the Device details dashboard:

  • Hardware CPU Name

  • Hardware BIOS Name

  • Hardware BIOS Version

  • Hardware CPU Sockets Count

  • Hardware CPU PCORE Count –  records the number of cores in all sockets (physical cores)

  • TCPv4 Connection Failures

  • CPU Kernel Percentage – records the percentage of CPU utilization at the kernel level (privileged)

• The highresourceprocs data index now includes the memperc column to show the percentage of available memory used.

• Additional information from Active Directory is now captured and available in the mswin_logons data index:

  • ds_department records the AD ‘department’ property on a user account.

  • ds_officelocation records the AD ‘physicalDeliveryOfficeName’ property on a user account.

  • azure_ad_registered records whether the user has registered the device with Azure AD (for devices that aren’t Azure AD-joined).

  • azure_ad_joined records whether the admin has joined the device to Azure AD.

  • upn records the User Principal Name (UPN) for the user account if it is available.

• The friendly name of the foreground (active) application is now collected in the column Foreground App Friendly Name.

Fixes

• Missing patches data was not fully cleared after patching was complete.

• Improved calculation for high resource processes.

• ControlUp SIP Agent service restart options restored. This issue was preventing auto-restart in case the Agent crashes.

• Reduced resource consumption for devices being remote controlled/shadowed.

• Improved Remote Control/Shadow support for devices with complex multi-display layouts.

• Changed the screen location of the remote control notification so that it is always visible with multiple displays

• When Remote Controlling/Shadowing a device and switching from a Console session to a user session, the notification icon was not appearing correctly and the file transfer path location was not updating to the new user session.

• Some process names were missing in foreground application detection.

• Improved foreground URL detection for different browser configurations.

• totaldiskqueuelength was sometimes showing as -1.

• Issue detecting multiple monitors during Remote Control sessions on Windows devices immediately after a user logon.

• Issue where incorrect GPU VRAM information was displayed for Windows devices with over 4GB VRAM.

• UCC fixes to get rid of an unneeded end-of-call report in builtin_ucc_agent_data and to stop Agent injection into the WiFi network driver name.

• Updated the capture of Idle and Locked status in app_focus so that Idle and Locked times are not captured in End User Activity (back to how it worked in version 2.12).

• Ignore VMware virtual Network Interfaces for more reliable geolocation on laptops running VMware hypervisors.

• Ignore the foreground app if there are no active sessions.

• Fixed line wrap and cursor location issues during Remote Shell sessions.

• Updated UCC data collection for the new version of Microsoft Teams (Oid and Tid were missing from the data index Builtin_ucc_agent_data).

• Some UCC data was missing for Zoom calls.

• 1074 events are now recorded in the correct time zone.

• Microsoft Teams monitoring at device boot.

• Updates blocked by locked files.

• Added support for a custom setting to allow Microsoft Teams processes to start before the Edge DX Agent monitors Teams data. This issue was causing problems for some hardware.