Benutzerhandbuch

Fixes an issue where upgrades could fail for installation with the minimal 32GB memory requirement.

Fixes an issue where upgrades could fail in case of a misconfigured LDAP provider (manager dn password change, LDAP server unreachable, ...).

Fixes an issue with failing context item searches in TrendHub.

Improves application stability.

Fixes an issue where ConfigHub access recovery was not working in combination with a misconfigured LDAP provider (manager dn password change, LDAP server unreachable, ...).

Fixes an issue with failing full backup restores.

Fixes an issue with failing backup restores.

Fixes a stability issue with crashing services after a backup restore.

Fixes an issue with the ADX provider.

Fixes an issue with failing full backup restores for large installations.

Fixes an issue with failing 2024.R2.1 upgrades.

Fixes an issue with expired internal certificates which can cause MLHub to not load even with a valid license.

Fixes an issue where scheduled full backups show the wrong TrendMiner version if TrendMiner was upgraded since the configuration of the scheduled backups.

Increases timeout for backups and restores from 4h to 48h.

Contains a performance improvement which significantly decreases the time to upgrade to 2024.R2.1 especially for customers with a lot of tag indexes.

Fixes an issue where the upgrade to 2024.R2.1 could fail for customers with large amounts of saved work.

Fixes an issue for PHD connections where local time was used instead of UTC for querying data, causing indexing errors.

Fixes an issue with failing PI EF syncs.

Edge Manager now shows the restore progress and feedback on possible restore failures.

Improves upload speed for upgrade packages.

Fixes an issue with TrendMiner database backup creation which also caused upgrade failures and restore failures.

Fixes an issue where an upgrade to 2024.R2.1 on CentOS could fail for large installations.

Fixes several remote backup restore issues.

Fixes an issue where dnf update fails for single node deployments on RHEL9/Alma9.

Fixes an issue where vertical scaling was not correctly applied.

Fixes an issue where the TrendMiner installation permanently fails after minimal system requirements were not met at the first installation attempt.

Fixes issue with console access on virtual appliances.

Fixes an issue where only the first 100 LDAP groups where accessible in ConfigHub.

Adds VMware tools for VMware virtual appliance deployments.

Fixes failing restores on servers without internet access.

Fixes an issue where an older remote backup restore can go into an invalid state after changing the backup storage location.

Fixes an issue where the upload of the TrendMiner upgrade package can fail when uploading it in Edge Manager via the /edge url.

Fixes an issue where the download of appliance logs can fail when downloading them from Edge Manager via the /edge url.

Fixes an error when configuring the server name on a virtual appliance when TrendMiner is not installed yet.

Fixes several issues caused by configuring an IP on virtual appliances.

Fixes an issue which prevents the configuration of custom K3S IP addresses.Appliance IP requirements

Fixes an issue with MTU size preventing successful connections to external services (e.g. data source connections to cloud providers).

Fixes an issue which prevents updating the system/OS packages on Alma/RHEL9.

Fixes an issue with configuration of the DNS in Edge Manager.

Fixes an issue where in some cases timestamps in the future are shown in current value tiles in DashHub, and implements enhancements to improve the performance and loading speed of these tiles.

Fixes an issue with Shiftconnector context item sync failing because of exception during the retrieval of deleted event priority.

Fixes an issue causing wrong NTP info to be shown in Edge Manager diagnostics.

Fixes an issue where the upgrade to 2024.R2 could fail for customers who have a lot of tag indexes.

Fixes an issue causing no system alerts to be sent via mails.

Adds a button in ConfigHub for data sources with context capabilities which allows to resume a failed or canceled historical context sync. The button is labeled 'resume historical sync' and is shown next to the 'start historical sync' button in the context tab of the data source details in ConfigHub -> Data sources. The 'resume historical sync' button is only shown in case of a failed or canceled sync.