OctoSAM 1.9.10 Release

OctoSAM 1.9.10 Release can be downloaded from the Filebase.

Supported Environments - minimum Requirements (no change from Release 1.9.9)

New Features

• Improved Hyper-V Server scan and import
  • Settings for virtual processor and memory configuration are now scanned also from the Hyper-V host.
    This allows to fill the corresponding virtual machine fields without a guest scan.
  • Hyper-V Data Exchange Key Value Pairs (KVP) intrinsic settings are now scanned from the Hyper-V host side.
    This allows to scan information about the installed guest operating system from the Hyper-V host without a guest scan.
    The guest VM must be in running state and the Hyper-V Data Exchange / KVP Service must be installed and running.
  • The Hyper-V Host import now logs more information about its progress. Debug logging has also been greatly enhanced.
• Hyper-V and VMware: absolutely all scanned data of a virtual machine is now persisted to the database as XML.
  Previously only the most interesting aspects of VMs were normalized into the database schema.
• VMWare: Configured guest Operating System of a VM is now available in the VirtualMachine object.
• Improved Java detection. A summary of detected Java versions and features can be found here
• Automatic update of the OctoSAM software master catalog can now be configured. The import service updates the master catalog from a central location managed by OctoSAM.
  Firewall and proxy configuration must allow REST calls and download of binary files from https://www.octosoft.ch.
• Machines that are only found in Active Directory can now be flagged if they are not to be scanned. This helps with coverage analysis.
• Users and Machines from Active Directory (DirectoryMissingMachines /Users tables) now Support CustomField1 - CustomField4
• The built-in filetransfer capabilities have been enhanced. Now you can define Get and Put transfers that are run at specific points in the import or housekeeping phase. Aditionally you can initiate onDemand filetransfers from octoutil.
• New OctoUtil commands to update mappings and to trigger housekeeping from scripts and plans
• New OctoUtil commands to delete or patch (custom) repository items in the database
• New OctoUtil commands to initiate a filetransfer
• OctoUtil tables can now be loaded from the database via SQL.
• OctoUtil query can now export to .xlsx files in addition to .csv
• OctoUtil commands that accept a machine or user id now also accept the guid or the name of the object.
• Dialog Group Settings Published Software Package now behaves as expected, persists only on OK button. Cancel discards any changes made.
• Data model clean-up, added Indexes
• Housekeeping delete actions are now executed in smaller chunks to relieve the database transaction log
• Queries now support pragma configuration to selectively turn off some checks for queries that do not adhere to OctoSAM Standards, for example export Queries that need to use non-standard names for columns or that cannot provide tooltips.
• New fields on Query: SQL Server Overview
• New fields on Query: Export/Metrix/01 Machines
• Octoscan2 now supports scanning of metadata and version info from specified custom paths configured in the config file. This can be used to scan installation status and detailed version information (if available) about custom packages that do not use an installer.
• Octoscan2 refactoring, migration to C++17 standard.
• Improved logging in the import service
• Updated Lucene full-text search engine for OctoWeb
• Updated 3rd Party components and libraries throughout

New Authenticode Certificate

• All Windows executables are signed with a renewed code signing certificate. Antivirus whitelists based on the Octosoft AG certificate must be verified and adjusted accordingly.

Breaking Changes for Custom Queries

• The query schema Version changes from 2018 to 2020. Custom Queries need to be adjusted and re-imported after the update.

Potentially Breaking Changes in the Data Model

• Tables and Columns in the database that were not used have been removed in this release
• SoftwarePackage.Guid and SoftwarePublisher.Guid no longer accept NULL values, see readme at the start of migration scripts.

Breaking Changes in OctoUtil Plans

• Octoutil plans must now specify the schema. Processing also now validates the Schema. see documentation
• Octoutil plan tasks can now contain multiple script and foreach elements that are processed in the order in which they are defined.
  Scripts can now be SQL or octoutil commands. This allows to execute octoutil commands driven by import data.

Scan File Compatibility

• The 1.9.10 import service can read 1.9.10, 1.9.9, 1.9.8, and 1.9.7 scan files.

Update Instructions

• Check the database migration script(s) for additional checks that you may have to run against the database before migration.
• Stop OctoSAM services on the server
• Make a backup copy of the database
• Migrate the database schema using the provided migrate_* scripts
• Note that a direct Migration from a Version other than 1.9.9 is not supported.
  Check the release Notes of earlier versions for migration procedures.
• Make a backup copy of all configuration files
• Run the .MSI Installer
• Merge the configuration settings with the new configuration template files.
• Consider configuring automatic software catalog update or update the software catalog manually
• Import standard queries and Reports from provided .zip file.
• Re-import custom queries after adjusting the schema version from 2018 to 2020.
  alternatively you can use the new octoutil export repostiory and octoutil update repository commands to patch custom queries
• Start OctoSAM services
• Update Octoscan2 windows scanner
• Update the Mac and Linux Scanner
• Update other scanners and their start scripts

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