OctoSAM 1.12.4 Release

OctoSAM 1.12.4 can be downloaded from the Filebase

Technical documentation

Supported environments - minimum requirements - no changes from 1.12.3.

New and improved features

• Improved throughput in the web interface to support more concurrent users with fewer server resources
• Performance improvements throughout the application, with special focus on the import service
• New features around continuous compliance checking
  • Compliance queries can now update the linked software Item with consumed units
  • Compliance history is now recorded for software items with connected compliance queries
  • Can now define a compliance warning threshold per software item
  • Alerts for compliance problems can be configured
• Export to CSV from web grids
• Copy windows ui grid ranges to markdown
• Can now filter the column selection menu in web grids
• Improved Grafana integration
• Improved error handling and logging for octoutil plans

Fixes

• Fixed some stability issues

Potentially Breaking Changes

• Database schema cleanup removes a number of tables and columns that were not used
• OctoUtil plans have slightly changed how invalid column names in import files (Excel, CSV, etc.) are converted into properties. Please test the existing plans after updating to 1.12.4. If your column headers adhere to valid JavaScript names or if you are using the generic names column1 - columnN, you are not affected.

Scan file compatibility

• The 1.12.4 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.3 to 1.12.4

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