OctoSAM 1.10.5 Release

    • Official Post

    Release 1.10.5 is available for download

    Technical Documentation (github.io)

    Supported Environments - minimum Requirements

    Windows Scanner Windows Server 2008 R2

    Windows 7 SP1

    macOS Scanner Mac OS X 10.15 (Catalina)
    Linux Scanner RHEL / CentOS 7
    Rocky Linux 8.4
    Fedora 25
    SUSE 12
    Debian 9

    Ubuntu 16

    other systemd based distributions upon request

    OctoSAM Database SQL Server 2017 (Compatibility Level 140)
    for upgrades from older SQL Server Versions we recommend to update at minimum to SQL Server 2019.
    SQL Server 2019 will be required starting with OctoSAM 1.11.1 (Q2 2024).
    OctoSAM Server Components Windows Server 2016
    .net 7.0 hosting bundle
    OctoSAM GUI Windows 10 Version 20H2 (OS build 19042) / Windows Server 2016
    .net 7.0 desktop runtime 64 bit

    New Features

    • New Microsoft Graph Interface for Microsoft 365 and Azure AD scan replaces the PowerShell based scanner
    • Support for AzureAD only users that are not replicated from on prem AD
    • Azure AD workplace join gets inventoried
    • Package and/or Signature installation approval can be used to track new/unauthorized installations
    • Installation Settings can now be specified on Signature level.
    • New query to find potentially slow WMI and Filesystem scans
    • New Java related queries
    • Optimized database code for SQL Server 2017
    • Extended Octoscan2 for scans in an AzureAD user context
    • Improved performance of Octoscan2 file system scans and java scans
    • Extended configuration options for Octoscan2 scan file upload to web server
    • Improved Service Manager / Service Recory integration for import and monitor services
    • Can now mark users and machines for deletion in the UI. The objects will be removed in the background.
    • Queries: can now specify minlength for query parameters
    • Octopus2 client .MSI now additionally comes in a self contained variant that is not dependent on .net installed on the system
    • Optimized storage requirements for historized WMI classes (Win32_Process)


    • Database Schema Cleanup
    • Updated 3rd Party Components
    • PowerShell based Group scanner is no longer supported
    • PowerShell base MSOL (Microsoft 365) scanner is no longer supported
    • Python based scanner no longer supported for (older) Macs (use shell based scanner)


    • VCenter custom attributes that differ only with - (hyphen) and _ (underscore) can cause problems in queries

    Scan File Compatibility

    • The 1.10.5 import service supports reading 1.10.4, 1.10.3, and 1.10.2 scan files. Import of older .scan files is only partially supported for Windows systems with unsupported operating systems (Windows XP, Windows Vista) that cannot update to the newest scanner. Imported information may be incomplete for these systems.

    Update Instructions
    Update from 1.10.4 to 1.10.5 if updating from an earlier version, see release notes of all versions in between

    • For OctoSAM server installations, make sure you have the newest .net 7.0 hosting bundle installed
    • For the Octopus2 GUI client, make sure you have the newest .net 7.0 desktop runtime installed
    • Stop OctoSAM services on the server
    • Stop IIS if you have deployed an IIS based module
    • Make a backup copy of the database
    • Optionally run the .MSI Installer for the GUI client, but prefer starting the GUI client from the Server/Octopus2 folder without installing the .MSI.
      • If you use the .MSI Installer, note that update installations form 1.10.4 are not supported.
        Uninstall previously installed version before you run the .MSI installer for 1.10.5.
    • Rename the existing Server folder
    • Copy the new Server folder from installation media
    • Migrate the database schema with the supplied migration scripts
    • Create required metadata in the database by running
      OctoUtil dbinit
    • Check your current appsettngs.json settings with the new sample file
      • consider switching to SSL encrypted LDAP connections
    • If you scan license management servers such as FlexLM, make sure the local tools are current. Use the newest tools provided by your servers.
    • Update the repository (formerly Reports and Queries) from provided .zip file.
    • Start OctoSAM services
    • Make sure that a full housekeeping was executed before trying to start the OctoSAM web interface
    • Analyze the Service log files for errors and warnings during initial imports and housekeeping
    • Update Octoscan2 windows scanner
    • After successful update remove the now obsolete renamed Server folder

    Known Limitations

    • DPI scaling is still experimental and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client and DPI settings on involved systems.
    • Modern Theme is experimental
    • FlexLM Diag scan supports only first configured vendor daemon, expiry date and other data scanned from diag is not available for other vendor daemons on the same FlexLM server.
    • Reports with more than 2000 different software packages selected fail due to a limit in SQL Server.