Checking version compatibility
Who is this article for?
Users and IT Administrators planning for version upgrades.
This article outlines version support policy, compatibility testing scope, and current system requirements for Ideagen Internal Audit (Aura).
Supported Versions
We support the current patch releases for the latest two versions of Ideagen Internal Audit.
What this means in practice:
- We will provide fixes for these two versions where possible, but may require customers to upgrade to the latest release in order to supply a patch.
- We will provide functional support for older versions on a best-effort basis, but may require a customer to upgrade in order to resolve their issue.
Compatibility Testing Policy
Once a version is superseded, we stop compatibility testing it against third-party prerequisites such as Windows and SQL Server.
For an unsupported version, the best we can confirm is what it supported at the time it was superseded. For example, compatibility testing of v4.2 ceased when v5.0 was released in 2017. Therefore, we can only confirm that v4.2 supported Windows versions that were current at that date — Windows 10 and Windows 2016. We cannot comment on compatibility with any updates released after that date.
Scope of Compatibility Comments
We can only comment on compatibility for software that is a direct prerequisite of our application. This means:
- Microsoft Windows
- Microsoft SQL Server
- Microsoft .NET Framework
We are not able to comment on compatibility with third-party software that is not a direct requirement for our application — for example, specific antivirus products or virtualisation platforms such as VMware.
Current System Requirements
The current system requirements documentation is available at: Ideagen Internal Audit | Ideagen Luminate Help.
Please note that the documentation is currently being updated. The published documentation states compatibility with Windows Server 2019 and SQL Server 2019 for v6.0.1.8. However, in practice we have numerous customers successfully running on Windows Server 2022/2025 and SQL Server 2022, and we have not encountered any compatibility issues to date.
Our approach is to resolve compatibility issues that arise between the current, supported releases of Windows and SQL Server and the current version of our software. Formal sign-off on the 2025 versions of these platforms is expected from the development team shortly, at which point the documentation will be updated to reflect this.