OctoSAM 1.10.10 Release

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.