TeamViewer DEX 26.10 release notes
The schedule is subject to change. When changes are made to the original schedule, they are indicated in red. Please check the TeamViewer Status Page for regular updates.
DEX Platform
|
Region |
Date |
Time from (UTC) |
Time to (UTC) |
|---|---|---|---|
|
CanadaCentral1 |
Monday, October 5, 2026 |
8 AM |
12 PM |
|
NorthEurope1 |
Tuesday, October 6, 2026 |
3 PM |
6 PM |
|
WestUS1 |
Wednesday, October 7, 2026 |
8 AM |
11 AM |
|
UKSouth1 |
Wednesday, October 7, 2026 |
6 PM |
9 PM |
|
WestUS2 |
Thursday, October 8, 2026 |
7 AM |
10 AM |
|
EastUS1 |
Thursday, October 8, 2026 |
8 AM |
11 AM |
|
WestEurope1 |
Thursday, October 8, 2026 |
5 PM |
8 PM |
Solutions
|
Region |
Date |
Time from (UTC) |
Time to (UTC) |
|---|---|---|---|
|
CA-Central-1 |
Tuesday, October 6, 2026 |
12 PM |
2 PM |
|
US-East-1 |
Thursday, October 8, 2026 |
11 AM |
1 PM |
|
EU-West-1 |
Friday, October 9, 2026 |
3.30 AM |
5.30 AM |
This release includes enhancements and fixes for the Platform and Solutions.
Application Network Monitoring data
Native Application Network Monitoring is now available to customers who have an Exoprise or Enterprise Plus license. This is a replacement to the Exoprise iframe in the DEX console. In addition, capabilities that relied on the Exoprise backend and agent now run in a native 1E Client module (26.9 or higher), removing the need for external Exoprise services, agents, or browser extensions.
For Application Network Monitoring to work correctly, download and deploy new and updated product packs from the Hub.
The following Product Pack needs to be updated:
Product Pack: 1E-Explorer-TachyonAgent
Instruction: 1E-Explorer-TachyonAgent-Set1EClientAgentConfig
These are new product packs that need to be deployed:
Product Pack: 1E-Tachyon-Platform
Instruction: 1E-TachyonPlatform-ANM-AppNetworkTcpData
Product Pack: 1E-Tachyon-Platform
Instruction: 1E-TachyonPlatform-ANM-AppNetworkUdpData
Enhancements and fixes
|
Enhancement or Fix |
Product/Client |
Issue ID |
Summary |
|---|---|---|---|
|
Enhancement |
Inventory Insights |
PLAT-33197 |
We introduced the ability to add a custom label to normalized software titles within Inventory Insights. Users can assign custom metadata (up to 50 alphanumeric characters, spaces, and | pipe symbols) to individual software titles, enabling flexible categorization and internal reference tracking. In addition, the Label field can be added as an optional column in software inventory views to support custom sorting, filtering, and saved views. |
|
Enhancement |
Software Reclaim |
PLAT - 31272 |
We introduced an optional Average Price field (in USD) under the Software Reclaim section within software details. This allows administrators to configure a specific baseline price for normalized software titles to calculate potential cost savings in Software Reclaim. If an average price is not explicitly set, the calculation falls back to version-specific pricing defined under License Attributes. |
|
Enhancement |
Platform |
PLAT - 33236 |
We added the last software inventory scan timestamp (ScannedTime) to software inventory data views (such as inventory_device_software / vw_software_by_device). This enables customers accessing data via Databricks and Delta Sharing to track exactly when a device last uploaded its software inventory, making it easy to determine whether a software title is currently installed on an endpoint or was previously detected and later uninstalled. |
|
Enhancement |
Inventory Insights |
PLAT - 34995 |
We updated table column headers across Inventory Insights, specifically on the Normalized software, Non-normalized software, and Reported software pages, renaming the Installations column to Installed Devices accompanied by the standard devices icon. This improves UI consistency and clarity across the DEX platform when viewing device installation counts, while preserving the detailed Installations side drawer view. |
|
Enhancement |
Platform |
PLAT - 35010 |
We enhanced Device Refresh rule configuration to support multi-event AND conditions and weighting logic for triggering Refresh statuses. Administrators can now configure multiple mandatory events that must all be satisfied together, or assign weights to individual events to evaluate a combined threshold before triggering a Refresh status, providing greater control than single-event triggers. |
