OctoSAM 1.12.2 Release

1st Official Post
    • Official Post

    OctoSAM 1.12.2 is available from Octosoft

    Technical documentation

    Supported environments - minimum requirements - no changes from 1.12.1.

    Windows scanner

    Windows Server 2012 R2

    Windows 10 (Windows 7 / 8 / 8.1 no longer supported)

    macOS scannermacOS 13 (Ventura)
    Linux scanner

    RHEL / CentOS 8
    Oracle Linux 8
    Rocky Linux 8.10
    Alma Linux 9.4
    Fedora 36
    SUSE 12
    Debian 11
    Alpine 3.18 (limited functionality)
    Ubuntu 16.04 LTS

    other systemd-based distributions upon request

    The Linux scanner depends on the installed system Python. Minimal supported Python version is 3.6.

    OctoSAM DatabaseSQL Server 2019 (Compatibility Level 150).
    SQL Server 2022 (Compatibility Level 160) or newer is recommended for new installations.
    OctoSAM Server ComponentsWindows Server 2016
    Windows Server 2022 or newer is recommended for new installations.
    .net 10 hosting bundle
    OctoSAM GUIWindows 10 Version 22H2 (x64) / Windows Server 2016
    .net 10 desktop runtime 64 bit


    New and improved features

    • Software installation history allows you to analyze software-to-machine relations in the past
      • On a machine: what software was installed on this machine in the past
      • On a package: on what machines was the software installed in the past
    • Environment variables get scanned (Windows, Mac, Linux)
    • License module: Software Items can now be manually assigned to Machines or Users.
    • License / Software Items mail alerts
    • Per-object context queries. Define context queries that are only visible on certain users, machines, packages or software items
    • Overall performance improvements
    • Database query performance improvements through optimized indexes
    • Enhanced dark mode for the Windows GUI Octopus2
    • Enhanced persistence of user customization for queries (Web / Windows UI)
    • Query descriptions are now available as tooltips in the query index (Web)
    • Object property pages now contain the symbol of the object (Web)
    • Checkboxes changed to switches for better visibility (Web)
    • 64-bit Versions of Windows scanner Octoscan2 and binary tools Octodump and OctoscanSettings (beta)
    • WTS client address scan now supports IPV6
    • Windows scanner tested on ARM64
    • Enhanced built-in mail facility. Mails are now queued internally if they cannot be sent directly.
    • Licenses/SoftwareItems can now be manually assigned to users and machines
    • VMWare ESX hosts improved scanning of SerialNumber, AssetTag and IPv4 Default Gateway

    Fixes

    • Stability updates

    Breaking Changes

    • Builds after 2026-02-01 will be signed with a new certificate. If you used the certificate to whitelist the Windows scanner or other executables, the configuration needs to be verified with the newly signed executables.
    • Powershell-based VCenter Scanner requires PowerShell 7. The path to the module does not change for PowerShell 7, but the module for older PowerShell versions is no longer supported.
    • The datamodel has changed considerably. You need to test your custom queries and reports, as well as any custom integration that directly accesses the database.
    • UPX compressed binaries for the Windows scanner are no longer provided.
    • Octoscan2 Windows scanner: minimal Windows version requirements are now enforced. The scanner will not start on unsupported Versions such as Windows 7.

    Scan file compatibility

    • The 1.12.2 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.1 to 1.12.2

    The database schema changes considerably. It is highly recommended to run a test migration on a database copy before migrating your production database.

    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.