Posts by Erwin Richard

OctoSAM 1.12.1 is available for download

Technical documentation

Supported environments - minimum requirements - changes from 1.11.7 are marked.

New and improved features

• Anaconda Miniconda filesystem scan for Windows, including scan of channel configuration
• M365 Copilot usage reports
• EntraID user LastSuccessfulSignInDateTime support
• Built-in Adobe UMAPI Interface
• Improved line charts in the Web interface now have the same scale
• Improved normalized hardware manufacturer handling with improved logging
• Significant performance increase for the property engine used internally. Affects the processing of query definitions and many oder internal data structures.
• Windows per-user filesystem scan signatures for Java and Anaconda/Miniconda/Miniforge
• Overall performance improvements
• New user setting for grid sort style in the Web interface
• Enhanced dark mode for the Windows GUI

Fixes

• Stability updates

Breaking Changes

• The Python-based Adobe UMAPI scanner is no longer supported.
• The list of supported systems has changed considerably.
• octoutil test phonehome command no longer available

Scan file compatibility

• The 1.12.1 import service supports reading 1.11. scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.7 to 1.12.1

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 that the local tools are current. Use the latest tools provided by your servers.
• Update the repository from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Ensure full housekeeping is executed before attempting to start the OctoSAM web interface.
  • Or use the octoutil dbinit command
• Assign per-organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 version, RDP client version, and DPI settings on the involved 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.11.7 is available for download

Technical documentation

Supported environments - minimum requirements - no change from OctoSAM 1.11.6

New Features

• Query engine now supports User-Defined Table Types to pass lists of data as parameters.
• The script engine now supports running markdelete jobs directly from housekeeping scripts without creating an octoutil plan.
• Improved Active Directory information scan in the Windows scanner Octoscan2
• The Adobe UMAPI scan is now integrated in the Import Service, much in the same way as the Microsoft Graph scan.
  The Python-based scanner is no longer required. This integration allows for easier installation and standardized logging.
  See the sample appsettings.json for configuration of the UMAPI scan.
• Microsoft 365 Graph Scan has been optimized to reduce the number of warnings and to log more meaningful messages.
• Reworked data model and query descriptions
• Extended the data model to support multiple RBAC providers in the future
• Improved behaviour of background deletes if there is a large number of scheduled deletes
• Improved logging, reduced warning logs in some well-known cases
• Massively improved performance of scan file imports
• Improved performance of Windows AutoStart import
• Improved diagnostics message if a user tries to import an invalid repository.zip file
• Extended automated testing
• 2 new incubating queries for analysis of Windows desktop usage of Visio and Project vs. M365 licensing plans
• Added some new columns to queries

Fixes

• Stability updates

Changes

• Updated all queries that take list parameters to use the new User-Defined Table Type feature
• Updated 3rd-Party Components
• Unified all statistics queries, dashboards, and progress queries to use the StatisticsSummary table, which was introduced in December 2023. This implies that older historical data is no longer available

Scan file compatibility

• The 1.11.7 import service supports reading 1.11.6, 1.11.5, 1.11.4, 1.11.3, and 1.11.2 scan files. Importing older .scan files is only partially supported for Windows systems, with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.6 to 1.11.7

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 hosting bundle.
• For the Octopus2 GUI client, ensure you have installed the newest supported .NET 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 migrate and patch scripts.
• Check your current appsettings.json settings with the new sample file.
• If you scan Adobe UMAPI, migrate settings to appsettings.json, and disable the scheduled task for the legacy Python-based scanner.
• If you scan license management servers, such as FlexLM, ensure that the local tools are current. Use the latest tools provided by your servers.
• Update the repository from the provided .zip file in the Support subdirectory.
• Start OctoSAM services.
• Ensure full housekeeping is executed before attempting to start the OctoSAM web interface.
  • Or use the octoutil dbinit command.
• Assign per-organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 version, RDP client version, and DPI settings on the involved 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.11.6 is available for download

Technical documentation

Supported environments - minimum requirements

New Features

• Further optimized the handling of JavaScript ES6 modules - overall improved performance of the web UI
• Reworked data model and query description
• Improved Machine - Hardware & Configuration Tab

Fixes

• Stability updates

Changes

• Updated 3rd-Party Components
• Clean-up of the data model

Scan file compatibility

• The 1.11.6 import service supports reading 1.11.4, 1.11.3, 1.11.2, and 1.11.1 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.5 to 1.11.6

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 hosting bundle.
• For the Octopus2 GUI client, ensure you have installed the newest supported .NET 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, ensure that the local tools are up to date. Use the latest tools provided by your servers.
• Update the repository from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Ensure that full housekeeping has been executed before attempting to start the OctoSAM web interface.
  • Or use the octoutil dbinit command
• Assign per-organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 version, RDP client version, and DPI settings on the involved 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.11.5 can be downloaded from the filebase

Technical documentation

Supported environments - minimum requirements

New Features

• License: Can now add multiple links and/or PDF documents to a software item
  • PDF documents can be stored in the database and directly displayed in the OctoWeb UI
• OctoWeb: JavaScript changed to use ES6 modules where possible
• Static files are now served using the gzip and/or brotli compression
• Optimized loading of JavaScript Modules - overall improved performance of the web UI

Fixes

• Stability updates

Changes

• Updated 3rd-Party Components
• Clean-up of the data model

Scan file compatibility

• The 1.11.5 import service supports reading 1.11.4, 1.11.3, 1.11.2, and 1.11.1 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.4 to 1.11.5

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 hosting bundle.
• For the Octopus2 GUI client, ensure you have installed the newest supported .NET 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 that the local tools are current. Use the latest tools provided by your servers.
• Update the repository from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Ensure that full housekeeping has been executed before attempting to start the OctoSAM web interface.
  • Or use octoutil dbinit command
• Assign per-organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 version, RDP client version, and DPI settings on the involved 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.11.4 can be downloaded from the filebase.

Technical documentation

Supported environments - minimum requirements

(no change from 1.11.3)

New Features

• Inventory of installed Chromium browser extensions
  • new tabs on the machine and the user UI
  • new queries
• Improved import service performance
• File-based Java signatures now report the installation date based on filesystem timestamps
• Lots of minor extensions to Queries, additional columns, etc.
• Updated Windows, Linux, and Mac scanners with enhanced Java scanning functionality.
  The release file is now collected for each installation.
• New octoutil commands
• Database documentation via MS_Description attribute is now updated via Repository import.
  This allows for documentation updates without requiring a schema version update.

Fixes

• Stability updates

Potentially Breaking Changes

• UTF-8 encoded .csv exports no longer write a UTF-8 BOM (byte order mark), which makes it easier to work on the files on platforms other than Windows.
• The import service now requires network access to the Google Chrome and Microsoft Edge extension stores via the HTTPS protocol.
• The syntax of the query description element has changed. HTML elements are no longer supported inside the description.
  The filenames and structure of the repository filesystem have changed; some folder names have also been updated.
  See documentation.
• The layout of the query and reports repository has changed. If you have custom context queries, you need to change the path.

Changes

• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.11.4 import service supports reading 1.11.3, 1.11.2, 1.11.1, and 1.10.11, scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.3 to 1.11.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 hosting bundle.
• For the Octopus2 GUI client, ensure you have installed the newest supported .NET 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 that the local tools are current. Use the latest tools provided by your servers.
• Update the repository from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Ensure that full housekeeping has been executed before attempting to start the OctoSAM web interface.
  • Or use octoutil dbinit command
• Assign per-organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 version, RDP client version, and DPI settings on the involved 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 different software packages selected fail due to a limit in SQL Server.

The following table shows the current detection capabilities per platform:

The different scanners use a collection of platform specific methods to detect Java installations

* Windows 7 and later
** definition of filesystems to scan by calling script

Release 1.11.3 can be downloaded from the filebase.

Technical documentation

Supported environments - minimum requirements

(no change from 1.11.1)

New Features

• Improved import service performance
• ServiceNow import imports additional fields (install_status, operational_status, support_group)
• File-based Java signatures now report the installation date based on filesystem timestamps (Windows only in this release)
• Scanners now report the directory where they were started from to help troubleshoot complex environments
• Additional information about import service progress and queryable statistics
• Lots of minor extensions to Queries, additional columns etc.

Fixes

• Stability updates

Potentially Breaking Changes

• None

Changes

• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.11.3 import service supports reading 1.11.2, 1.11.1, 1.11.0, 1.10.11, scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.1 to 1.11.3

When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, ensure that you have the latest supported .NET hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest supported .net 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 starting 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 like FlexLM, please ensure the local tools are current. Use the latest tools provided by your servers.
• Update the repository from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and the DPI settings on involved 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 different software packages selected fail due to a limit in SQL Server.

Release 1.11.1 is available for download

Technical documentation

Supported environments - minimum requirements

(no change from 1.11.0)

New Features

• New field EntraIdCreatedDateTime
• New queries to analyze Office 2016 and Office 2024 LTS usage
• Improved query fieldsets for better consistency of queries
• Grace period for reorganization of dynamic signatures can now be configured (used to be fixed to 10 days in earlier versions)
• New Queries for license calculations
• Query layout for web interface can now be saved per user in the database as an alternative to local browser storage

Fixes

• Stability updates

Potentially Breaking Changes

• None

Changes

• The Windows Java scan now also scans the recycle.bin and some other system folders that were previously skipped.
• Multi-language handling for extended attributes has been removed
• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.11.1 import service supports reading 1.11.0, 1.10.11, 1.10.10, and 1.10.9 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.11.0 to 1.11.1

When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest .net 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 starting 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 appsettngs.json settings with the new sample file
• If you scan license management servers like FlexLM, please ensure the local tools are current. Use the latest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
    
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 is in beta and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and the DPI settings on involved 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 different software packages selected fail due to a limit in SQL Server.

Release 1.11.0 is available for download

Technical documentation

Supported environments - minimum requirements

New Features

• Improved JSON export for very large exports
• Logging improvements
• Improved query fieldsets for better consistency of queries
• Improved high dpi and dark theme support (beta)
• Improved support for Windows Asian languages
• Query definitions now allow explicit SQL parameter definitions
• Performance improvements throughout

Fixes

• Microsoft OpenJDK for Mac not properly recognized

Potentially Breaking Changes

• We no longer deliver a self-contained MSI for the Octopous2 client. Microsoft .net Desktop Environment 64bit must be installed on the target machine.
• The capability to configure SFTP- or ssh-based file transfers directly in appsettings.json has been removed.
• CatalogUpdate settings to allow insecure connections have been removed.
• The default delivery of the Windows Scanner Octoscan2 is no longer compressed. A UPX packed version is still available in the ./Compressed subdirectory.

Changes

• The Windows Java scan now also scans the recycle.bin and some other system folders that were previously skipped.
• Multi-language handling for extended attributes has been removed
• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.11.0 import service supports reading 1.10.11, 1.10.10, and 1.10.9 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.10.11 to 1.11.0

When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest .net 8.0 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 starting 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
• Note that with this update, there is no database schema change from 1.10.11. However, due to updates in the query engine, all components must update to 1.11.0.
• Check your current appsettngs.json settings with the new sample file
  • consider switching to SSL-encrypted LDAP connections
• If you scan license management servers like FlexLM, please ensure the local tools are current. Use the latest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
    
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 is in beta and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and the DPI settings on involved 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 different software packages selected fail due to a limit in SQL Server.

Release 1.10.11 is available

Technical documentation

Supported environments - minimum requirements (no change from 1.10.10)

New Features

• Improved handling of extended attributes throughout the Windows UI and the Web UI
• Improved query favorites handling - select and de-select multiple favorite queries at once.
• Entra ID group import
• Logging improvements
• Improved query fieldsets for better consistency of queries

Fixes

• Cleaned up Database Model
• Fixed a bug in the Windows scanner Octoscan2 on Chinese Windows when bogus Oracle Java SE usage tracker files are present in the file system

Changes

• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.10.11 import service supports reading 1.10.10, 1.10.9, and 1.10.8 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.10.10 to 1.10.11
When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest .net 8.0 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 starting 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
• Migrate the database schema with the supplied migration script(s)
• Check your current appsettngs.json settings with the new sample file
  • consider switching to SSL-encrypted LDAP connections
• If you scan license management servers like FlexLM, please ensure the local tools are current. Use the newest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
    
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 is in beta and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and DPI settings on involved 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 different software packages selected fail due to a limit in SQL Server.

Download from filebase

Technical documentation

Supported environments - minimum requirements

New Features

• Microsoft EntraID can now be used as an IDP for the OctoSAM Web interface / RBAC instead of Windows-integrated security
• Performance improvements for large installations with more than 20'000 computers
• A new global search feature in the Web UI allows for quick access to objects (users, machines, software packages)
• Most internal queries are now also available in the Web UI if the user has the corresponding privileges
• New Queries and new fields in some queries
• New Custom1-Custom4 fields on the Organization object can be manually edited and are now available in most queries.
• Improved high DPI support in Octopus 2 GUI (beta)
• Detailed scan of Office Add-ins under Windows
• Support for tag options on all scanners and availability of tag for organization mapping
• Logging improvements
• The WIndows scanner configuration file octoscan.config can now be fully or partly obfuscated
• Improved query fieldsets for better consistency of queries

Fixes

• Some parts of the Octopus2 GUI were enabled even if the user did not have the required write permissions to the database
• EntraID and on-prem AD users could not be mapped in some multi-domain scenarios

Changes

• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.10.10 import service supports reading 1.10.9, 1.10.8, and 1.10.7 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.

Update instructions

Update from 1.10.9 to 1.10.10
When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest .net 8.0 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 starting 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
• Migrate the database schema with the supplied migration script(s)
• Check your current appsettngs.json settings with the new sample file
  • consider switching to SSL-encrypted LDAP connections
• If you scan license management servers like FlexLM, please ensure the local tools are current. Use the newest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
    
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 is in beta and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and DPI settings on involved 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.10.9 Release can be downloaded from the Filebase.

Technical documentation

Supported environments - minimum requirements

New Features

• Dark theme for the Web UI, respects browser appearance settings for newest Chrome and Edge browsers.
• New themes 'Dark' and 'Light' for the Octopus2 GUI (beta)
• Improved high DPI support in Octopus 2 GUI (beta)
• Can now define a default set of selected organizations in OctoWeb
• RBAC per organization Read and Update privileges
• Upload server OctoCollect now supports both Windows IIS and Linux nginx environments
• Upload server authentication via API Key
• New download API to download files from Upload server. Filetransfer is still supported but no longer required.
• RBAC rights per Organization
• Java project progress is now historized per organization
• Microsoft 365 assigned / used licenses are now historized
• Microsoft 365 app usage
• Support for Alpine Linux 3 for container scans.
  Due to missing functionality of the BusyBox environment in Alpine 3, only server scans under root are supported.
• Cloud licensing plan history.
  See the usage pattern of your cloud licenses over time.
• Performance improvements throughout the application
• Logging improvements
• Improvements for query development:
  Most queries in OctoWeb can now also be called by the Octopus2 GUI in query development mode.
  RBAC within queries can be simulated in Octopus2
• Query fieldsets provide macros for improved consistency of queries
• Improved Import Service for installations that require very low latency between scan and availability in the OctoSAM database.

Fixes

• Computer import from Active Directory did not filter out group-managed service accounts.

Changes

• Updated 3rd-Party Components
• Updated technical documentation
• Sample configuration files reorganized. All are now in Server/SampleConfigurationFiles and subdirectories thereof.

Scan file compatibility

• The 1.10.9 import service supports reading 1.10.9, 1.10.8, 1.10.7, and 1.10.6 scan files. Importing older .scan files is only partially supported for Windows systems with unsupported operating systems that cannot update to the newest scanner. Imported information may be incomplete for these systems.
• Linux systems under Microsoft Hyper-V need to update to the newest release scanner. Import of older scan files is not supported for this configuration.

Update instructions

Update from 1.10.8 to 1.10.9
When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed.
• For the Octopus2 GUI client, ensure you have installed the newest .net 8.0 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 starting 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
• Migrate the database schema with the supplied migration script(s)
• Check your current appsettngs.json settings with the new sample file
  • consider switching to SSL-encrypted LDAP connections
• If you scan license management servers like FlexLM, please ensure the local tools are current. Use the newest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface.
  • Or use octoutil dbinit command
    
• Assign per organization privileges to your RBAC roles. Assign Organization.ALL.Read / Organization.ALL.Update to your existing roles.
• 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 is in beta and does sometimes not work over RDP sessions, depending on the version of the server, the RDP client, and DPI settings on involved 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.10.8 Release Builds can be downloaded from the Octosoft Filebase.

Technical documentation

Supported environments - minimum requirements

New Features

• Improved integration with Entra ID / Microsoft 365 via Graph interface
• Last Entra ID sign-in activity can now be imported (depending on the level of your Entra ID license)
• Microsoft 365 app usage can be imported
• More device information is now imported from Entra ID, and machines not scanned from Entra ID can now be identified
• User information is now imported from Entra ID, and users not scanned from Entra ID can be queried
• Statistics graphs now read new data structures and are more performant
• Performance improvements throughout the application
• Logging improvements

Changes

• Database Schema Cleanup
• Updated 3rd-Party Components
• Updated technical documentation

Scan file compatibility

• The 1.10.8 import service supports reading 1.10.8, 1.10.7, 1.10.6, and 1.10.5 files. Importing 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.7 to 1.10.8
When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed
• For the Octopus2 GUI client, make sure you have the newest .net 8.0 desktop runtime installed
• Make sure your Browsers (Microsoft Edge or Google Chrome) are up to date
• 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.
• Rename the existing Server folder
• Copy the new Server folder from the installation media
• Migrate the database schema with the supplied migration scripts(s)
• 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, ensure the local tools are current. Use the newest tools provided by your servers.
• Update the repository (formerly Reports and Queries) from the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface
  • Or use octoutil dbinit command
• 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 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.
• 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 different software packages selected fail due to a limit in SQL Server.

OctoSAM 1.10.7 Release builds are available for download.

Technical documentation

Supported environments - minimum requirements

New Features

• Improved integration with Entra ID / Microsoft 365 via Graph interface
• Device information is now imported from Entra ID, and machines not scanned from Entra ID can be queried
• A couple of new operating system family types to reflect information from Entra ID from mobile devices etc.
• A new license monitor type 'Script' allows customized scripts to provide license monitor statistics. This allows integrations with a wide range of application servers that report license usage via an API.
• New Oracle Java SE related dashboard
• New and Improved Oracle Java SE related queries
• The list of queries in the web interface can now be searched
• Statistics are now stored independently from the catalog update mechanism
• Performance improvements throughout the application
• New and Improved Mac scanner version with even better Java detection capabilities
• New Linux scanner version with additional detection capabilities
• New Windows scanner version with improved stability and additional detection capabilities
• New Adobe UMAPI scanner with new authentication. Please update your Adobe scanner version and Python runtime
• Logging improvements

Changes

• Migrated to Microsoft .net 8.0
• The Linux scanner no longer depends on the Python distro module
• Database Schema Cleanup
• Updated 3rd-Party Components
• Updated technical documentation

Possibly breaking changes

• AzureAD fields in the database have been renamed to EntraID. Custom queries that access these fields need to be adjusted.

Scan file compatibility

• The 1.10.7 import service supports reading 1.10.6, 1.10.5, and 1.10.4, 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.6 to 1.10.7
When updating from an earlier version, see release notes of all versions in between

• For OctoSAM server installations, make sure you have the newest .net 8.0 hosting bundle installed
• For the Octopus2 GUI client, make sure you have the newest .net 8.0 desktop runtime installed
• Make sure your Browsers (Microsoft Edge or Google Chrome) are up to date
• 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.
• Rename the existing Server folder
• Copy the new Server folder from the installation media
• Migrate the database schema with the supplied migration scripts(s)
• 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 the provided .zip file in the Support subdirectory.
• Start OctoSAM services
• Make sure that full housekeeping was executed before trying to start the OctoSAM web interface
  • Or use octoutil dbinit command
• 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 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.
• FlexLM Diag scan supports only the first configured vendor daemon; the expiry date and other data scanned from diag are 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.

OctoSAM 1.10.6 Release builds are available for download.

Technical Documentation (github.io)

Supported Environments - minimum Requirements

New Features

• Software Signature handling in the web Interface
• Improved Usability of the web interface when a function such as a complex query or one that returns a lot of results requires some more time
• Windows Autostart scanning per system and user specific
• • UI to view Windows AutoStart configuration from user and machine in the Octpus2 GUI and the web UI
  • New query to find WIndows AutoStart configurations on multiple systems/users
• New query to analyze Anaconda/Miniconda usage
• Oracle VirtualBox Extension Pack detection
• Improved reorganization of signatures that are no longer installed
• Java Linux detection has been updated to support newer java distributions
• The public address of the web interface can now be configured via Admin Settings page
• License: Currency part of Money fields is now editable, including custom Money fields
  • Default currency can be set per user in the user preferences
  • For extension Attributes, default visibility of the currency column can be configured
• ServiceNow integration: OctoSAM now exports the URL to a computer object in the new field u_octosam_url, a transform script is no longer needed.
• Octopus2: can now search for the database id of an object by entering #<id> in the filter text box
• Database storage usage for history of Hardware & Configuration data has been optimized which leads to a reduction of database size of around 20%.
• Improved recovery of OctoSAM services in case of database problems
• Improved logging throughout

Changes

• Import of MSOL cloud scan files is no longer supported, Migrate to the Graph Interface
• Logging/telemetry to Stackify has been removed from the product, Logging to site-specific logging infrastructure is of course still possible via SeriLog
• The python based Linux scanner has been restructured, macOS support has been removed. Python 2.6 is no longer supported
• Hyper-V KVP parsing for Linux scans has been moved to the Import Service.
• Linux RPM now imports the Vendor/Publisher and Packager information if available
• Script "export" execution gets performed only during a full housekeeping, partial houskeeping after service restart does no longer call the "export" script handler.
• Experimental "modern" theme has been removed for Octopus2, Theming will be reconsidered with migration to .net 8.0
• Database Schema Cleanup
• Updated 3rd Party Components

Scan File Compatibility

• The 1.10.6 import service supports reading 1.10.5, 1.10.4, and 1.10.3 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.5 to 1.10.6 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
• Make sure your Browsers (Microsoft Edge or Google Chrome) are up to date
• 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 from 1.10.5 are not supported.
    Please uninstall the previously installed version before you run the .MSI installer for 1.10.6.
• Rename the existing Server folder
• Copy the new Server folder from installation media
• Migrate the database schema with the supplied migration scripts
• 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
  • Or use octoutil dbinit command
• Configure the public URL of the OctoSAM web interface in the Admin -> Settings tab`
• Note that the Column SoftwareSignature.Publisher has been renamed to SoftwareSignature.RawPublisher and Machine.Manufacturer to Machine.RawManufacturer. These fields contain the scanned information. Normalized Publisher and Manufacturer names are available via join to the corresponding tables. Custom queries that access these columns need to be adjusted.
• 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.
• 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.

Anmerkung: Ab octoscan2 1.10.5.70 werden für die Konfiguration in octoscan.config die standard c++ Regular Expressions verwendet.

Release 1.10.5 is available for download

Technical Documentation (github.io)

Supported Environments - minimum Requirements

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)

Changes

• 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)

Fixes

• 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.

Release 1.10.4 is available for download

Technical Documentation (github.io)

Technical Documentation (mirror octosoft.ch)

Supported Environments - minimum Requirements

New Features

• Software lifecycle can be configured per software package
• VMware ESXi is now treated the same as other operating system software.
  OS signatures are generated and related to the ESX host machines.
  This allows all features of the catalog and software queries to be applied to ESXi too.
  ESXi packages contain lifecycle information.
• Raw operating system information from scanners is now stored per machine.
  This allows export of very detailed information for other inventory systems, security impact analysis etc
• New field Machine.OperatingSystemUpdateBuildRelease for Windows UBR
• Web: LicensenseManager favorite features can now be configured per user
• Web: cleaned up layout, tabs with icons
• Web: added information to the Software Package page
• Web: added more fine-grained access privileges, existing roles may need to be adjusted
• Web: improved error messages and navigation from error to home
• License: Software Item can now be linked with a License Manager Server
• Improved software lifecycle queries
• Performance improvements throughout
• Improved Active Directory Import diagnostics logging and error handling
• Active Directory no-find warnings can now be suppressed on the scanned operating system for machines and users.
  This allows to suppress no-find warnings for users scanned on Mac if user accounts not integrated into AD.
• Improved error handling and messages in the web interface
• Improved logging, more well-known warnings can be suppressed through configurations

Changes

• "Queries and Reports" has been renamed to Repository for consistency in all parts of OctoSAM.
• Database Schema Cleanup
• Updated 3rd Party Components

Scan File Compatibility

• The 1.10.4 import service supports reading 1.10.3, 1.10.2, 1.10.1, and 1.10.0, 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.3 to 1.10.4 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 6.0 hosting bundle installed
• For the Octopus2 GUI client, make sure you have the newest .net 6.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.
• Rename the existing Server folder
• Copy the new Server folder from installation media
• Migrate the database schema with the supplied migration scripts
• Check your current appsettings.json settings with the new sample file
  • consider switching to SSL encrypted LDAP connections
  • database connections are using SSL now by default, see sample config for workaround if your SQL Server uses a self-signed certificate
• 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.
• Update RBAC definitions by running
  octoutil rbac sync
  alternatively wait until the housekeeping from restarted import service is complete.
  The web UI may not behave as expected without updating RBAC definitions first.
• Start OctoSAM services
• Analyze the Service log files for errors and warnings during initial imports and housekeeping
• See new settings to suppress well known warnings for AD Lookup
• 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.

Release 1.10.3 is available for download

Technical Documentation

Supported Environments - minimum Requirements

New Features

• Lifecycle information for Microsoft operating systems and Microsoft SQL Server (beta)
  • Detailed information about Microsoft product lifecycle for the mentioned software categories.
  • Other publishers and other Microsoft products will be implemented in later versions depending on customer requirements
• First release that is net 6.0 only with no dependencies to .net Framework
• Performance improvements throughout
• Optional filesystem scan for windows provides detailed information to export to other inventory systems that relay on file scan
• Raw signature information from scanners is now stored per signature / per machine. This allows export of very detailed information for other inventory systems, security impact analysis etc.
• More fine-grained permissions for RBAC in the web interface
• RBAC Import now allows multiple group containers
• RBAC Import and AD lookup now support LDAPS via SecureSocketLayer configuration option
• Improved RBAC Import diagnostics logging and error handling
• Improved error messages with more detailed version information in the web interface

Changes

• Migrated code for Wolfram Mathematica LicenseManagerServer
• Database Schema Cleanup
• Updated 3rd Party Components

Scan File Compatibility

• The 1.10.3 import service supports reading 1.10.2 1.10.1, and 1.10.0, 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

• If the monitor feature is used, make sure the license contains the MONITOR license option. Monitor components now check for this option.
• See the database migration script(s) for additional checks that you may have to run against the database before migration.
• For OctoSAM server installations, make sure you have the newest .net 6.0 hosting bundle installed
• For the Octopus2 GUI client, make sure you have the newest .net 6.0 desktop runtime installed
• Stop OctoSAM services on the server
• Stop IIS if you have deployed an IIS based module of OctoSAM
• Make a backup copy of the database
• Note that a direct migration from a Version other than 1.10.2 is not supported.
  Check the release notes of earlier versions for migration procedures from earlier releases
• Optionally run the .MSI Installer for the GUI client, but prefer starting the GUI client from the Server/Octopus2 folder without installing the .MSI.
• Rename the existing Server folder
• Copy the new Server folder from installation media
• Optionally enable service broker on the database
• Migrate the database schema with the supplied migration scripts
• Check your current appsettngs.json settings with the new sample file
  • If you use RBAC, make sure to change the groups setting to the new syntax (list of group containers)
  • consider switching to SSL encrypted LDAP connections
  • database connections are using SSL now by default, see sample config for workaround if your SQL Server uses a self-signed certificate
• 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 standard queries and Reports from provided .zip file.
• Start OctoSAM services
• Analyze the service log files for errors and warnings during initial imports and housekeeping
  • If you use RBAC, see the import service log for newly available privileges. Adjust custom defined roles accordingly. Roles predefined by OctoSAM are managed automatically.
• 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.
• 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.

Release 1.10.2 is available for Download

Technical Documentation

Supported Environments - minimum Requirements

New Features

• OctoSAM Web UI (beta) replaces the former License Web UI and can be used instead of the GUI client in many scenarios
• All components of OctoSAM migrated to .net 6.0
• Octopus2 Windows UI High-DPI scaling can now be controlled via options dialog, editing of a config file is no longer required.
• Overall performance improvements
• Windows Scanner detects more variants of SQL Server TCPPort configuration
• Improved Windows 11 Version handling, DisplayVersion is now separate from Buiild information
• Improved coustomization of query output using the octoutil query command.

Scan File Compatibility

• The 1.10.2 import service supports reading 1.10.2 1.10.1, 1.10.0, and 1.9.10 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

• Check database housekeeping settings, especially the VirtualMachineScanHistoryDays setting.
• If the monitor feature is used, make sure the license contains the MONITOR license option. Monitor components now check for this option.
• Check the database migration script(s) for additional checks that you may have to run against the database before migration.
• For OctoSAM server installations, make sure you have the newest .net 6.0 hosting bundle installed
• For the Octopus2 GUI client, make sure you have the newest .net 6.0 desktop runtime installed
• Stop OctoSAM services on the server
• Stop IIS if you have deployed an IIS based module of OctoSAM
• Make a backup copy of the database
• Note that a direct migration from a Version other than 1.10.1 is not supported.
  Check the release notes of earlier versions for migration procedures from earlier releases
• Optionally run the .MSI Installer for the GUI client, but prefer starting the GUI client from the Server/Octopus2 folder without installing the .MSI.
• Rename the existing Server folder
• Copy the new Server folder from installation media
• Optionally enable service broker on the database
• Migrate the database schema with the supplied migration scripts
• Check your current appsettngs.json settings with the new sample file
• 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 standard queries and Reports from provided .zip file.
• Start OctoSAM services
• 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.
• 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.