RN200898: Release Notes: Raynet One Data Hub 14.0.5886.125 [RTM]

Data Hub has been rebranded to align more closely with the Raynet One platform, reinforcing its role as the centralized solution for data management.

The raw Intune data collected is now also automatically processed by the default transformation and rendered in all relevant places, such as IT Visibility.

Data Hub can now be served via Kubernetes, thanks to improved configuration and feature enhancements.

Hardware data is now automatically processed by the standard transformation layer, which is created when the user imports the updated dashboards and reports. This function has the same semantic structure and purpose as its similar "software" counterpart.

A valid API key is now required when installing the Data Hub Agent. This ensures that only authorized uses are allowed and provides the agent installer with the necessary information for proper instance-agent setup.

In this version, there are four new connectors: GoodData, JetBrains Account, Microsoft Defender and OCI Database. [KOT-666] [KOT-671] [KOT-690] [KOT-596]

Additionally, several improvements and new features were implemented:

• (Microsoft 365) Added Direct Routing Calls. [KOT-698]
• (SAP Concur) Added new endpoint Expense Entries. [KOT-683]
• (Microsoft Graph Generic Query) Added missing features. [KOT-689]
• (Google Cloud Storage) - Added explicit error handling when downloading files. [KOT-636]
• (Microsoft 365) - Added AccountEnabled field to User table. [KOT-699]
• (Microsoft 365) - Improved error messages. [KOT-645] [KOT-694]
• (Microsoft Azure) - Improved error handling. [KOT-659]
• (ServiceNow) - Adjusted default page size to 2000. [KOT-677]
• (VMware vSphere) Added validation for Server URL. [KOT-643]
• (VMware vSphere) Improved log messages. [KOT-642]

Other features and improvements:

• Added new dashboards and reports to the library: Oracle Java powered by Unified Data Platform. [RR-4301]
• The Query Builder window is now larger to accommodate longer scripts and content. [RR-4108]
• Added a checkbox to hide/show empty tables in the Raw Data Viewer. [RR-3182]
• Stricter behavior for handling generated API keys. In this release, the API key is presented to the user after the token is created, preventing insecure behavior or unintentional leaking of API keys. [RR-3815]
• Increased the default single request timeout in the Catalog connector. [RR-2619]
• It is now possible to prevent PowerShell scripts from being executed by the Data Hub Agent. This can be achieved by adding a new configuration property PowerShellScriptsExecutionEnabled set to false (applies to both Windows and Docker builds). [RR-2824]
• The Active Directory (LDAP) connector has been improved for more robust data type handling, resulting in the elimination of mismatches and conversion issues. [RR-4228]
• Many internal and third-party components, controls, and interaction elements have been upgraded to the newer versions, ensuring improvements in performance, security, and robustness.

Resolved issues:

• Resolved an issue where the order of tables was ignored in the conflict resolution of a deduplication step. [RR-4204]
• Resolved an issue where writing the result to a Microsoft SQL Server database could fail for tables with compound primary keys. [RR-4182]
• Resolved minor issues with the IT Visibility Dashboard. [RR-4214]
• Resolved an issue where it was possible to inject a JavaScript code into the e-mail template. [RR-4094]
• Resolved an issue with Active Directory connector where all users were reported even if filter group was enabled. [RR-3496]
• Resolved issues with custom installation path and database setup on Windows. [RR-4230] [RR-4257]

• The application now targets .NET 8.0, which is a new requirement for Windows (official Docker images already include the framework).
• After migration, the old agents will not be able to communicate with the server. The reason for this is the missing API key, a change introduced to enforce the security of the product. To continue using the migrated agents, make sure that the API key is provided.

• Content-Security-Policy is not working anymore.
• Intune connector can not be run (It shows not licensed when trying to start from Tasks view) (In Task details view it still works.) The workaround is to re-create the task.
• Migration in MariaDB needs manual adjustments of the version table
• Custom Tenant Image is not showing on the initial tenant selection page.
• Dashboards with Sankey diagrams may not be properly exported.
• Raynet One Connector does not collect the OS information.
• Oracle DB Server Overview and Oracle DB Details Overview don't work - the workaround is to adjust filter computer_id parameter to import_id.
• For Azure and Office 365 tasks, the timeout is required for the task to be started.

Migration from Data Hub 12.x

The migration steps may vary depending on your setup (Windows/Docker) and the database engine in use (SQL Server/MariaDB).

Windows (MSI) + SQL Server

1. Install or upgrade the MSI server by following the MSI installation dialogs.
2. Access the web UI and create a new API key.
3. Download the latest version of the agent.
4. Install or upgrade the MSI agent.
5. Enter the newly created API key into the appropriate MSI dialog.

Windows (MSI) + MariaDB

1. Back up the appsettings.json file.
2. Install the MSI and select the "do not configure SQL Server" option in the MSI dialog.
3. Restore the appsettings.json file from your backup.
4. Update the connection strings in the file. Add AllowUserVariables=True;UseAffectedRows=False to both connection strings if you're using MariaDB
   Example:
   

   Server=mariadb,3307;User ID=root;Password=raynetRootPassword;Database=DataHub_Default;AllowUserVariables=True;UseAffectedRows=False

5. Restart IIS.

• The database migration will occur on the first start.
• If the web application reports a database version error or other errors (such as when creating a table), restart IIS again to resolve the issue.

Docker

1. Ensure that AllowUserVariables=True;UseAffectedRows=False is set for MariaDB and Encrypt=False if you're using MSSQL, in the connection string within the compose file, under the web section.

   2. Start Docker Compose:

docker compose up

• The database migration will occur on the first start.
• If the web application reports a database version error, restart the web container.

DataHubApiKey=465N31G-1QHMYQD-JDGHPWC-BY3J4MX

docker compose down

docker compose up

   8. If Windows agents are connected, restart their agent services

Detailed instructions for the installation can be found in the Raynet One Data Hub 14.0 User Guide.

FTP Server:

file.raynet.de

User:

raynetone-kd

Password: