- Official Post
OctoSAM 1.12.3 can be downloaded from the filebase.
Supported environments - minimum requirements - no changes from 1.12.2.
| Windows scanner | Windows Server 2012 R2 Windows 10 |
| macOS scanner | macOS 13 (Ventura) |
| Linux scanner | RHEL / CentOS 8 other systemd-based distributions upon request The Linux scanner depends on the installed system Python. Minimal supported Python version is 3.6. |
| OctoSAM Database | SQL Server 2019 (Compatibility Level 150). SQL Server 2022 (Compatibility Level 160) or newer is recommended for new installations. |
| OctoSAM Server Components | Windows Server 2016 Windows Server 2022 or newer is recommended for new installations. .net 10 hosting bundle |
| OctoSAM GUI | Windows 10 Version 22H2 (x64) / Windows Server 2016 .net 10 desktop runtime 64 bit |
New and improved features
- You can now configure queries to specific software items
- Improved auditing of manual software approvals
- Web interface improved layout
- Web interface performance improvements
- EntraID device group membership
- Improved Logging in the import service
- More options to control import service batches and improve overall throughput
- License: charts for license consumption
- License dashboard: show items with the highest license consumption
- Grafana dashboarding integration preview
Fixes
- Fixed some stability issues for very large or very busy databases
Breaking Changes
- Builds after 2026-02-01 are signed with a new certificate. If you used the certificate to safelist the Windows scanner or other executables, the configuration needs to be verified with the newly signed executables.
Scan file compatibility
- The 1.12.3 import service supports reading scan files from 1.11.1 and newer. Importing older .scan files is only partially supported for Windows systems, with unsupported operating systems that cannot update to the latest scanner. Imported information may be incomplete for these systems.
Update instructions
Update from 1.12.2 to 1.12.3
The update fixes the data type for one column in a large table. The database migration may take a few minutes.
When updating from an earlier version, see the release notes of all versions in between
- For OctoSAM server installations, ensure you have installed the latest supported .NET 10 hosting bundle.
- For the Octopus2 GUI client, ensure you have installed the newest supported .NET 10 desktop runtime.
- Make sure your Browsers (Microsoft Edge or Google Chrome) are up to date.
- Stop OctoSAM services on the server
- Stop OctoWeb in IIS
- Make a backup copy of the database
- You can optionally run the .MSI Installer for the GUI client, but the preferred method is to start the GUI client from the Server/Octopus2 folder without installing the .MSI.
- Rename the existing Server folder.
- Copy the new Server folder from the installation media
- Update the database schema using the supplied scripts
- Check your current appsettings.json settings with the new sample file
- If you scan license management servers, such as FlexLM, please ensure the local tools are up to date. Use the latest tools provided by your servers.
- Update the repository using the .zip file provided in the Support subdirectory.
- Run octoutil dbinit
- Start OctoSAM services
- Analyze the Service log files for errors and warnings during initial imports and housekeeping.
- Update Octoscan2 Windows scanner
- After a successful update, remove the now obsolete, renamed Server folder
Known limitations
- DPI scaling for the Windows UI is in beta and may not work correctly over RDP sessions, depending on the server and RDP client versions, as well as the DPI settings on the client and server systems.
- FlexLM Diag scan supports only the first configured vendor daemon; the expiry date and other data scanned from Diag are unavailable for other vendor daemons on the same FlexLM server.
- Reports with more than 2000 distinct software packages selected fail due to an SQL Server limit.OctoSAM 1.12.2 is available from Octosoft