Posts by Erwin Richard

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.

OctoSAM Release 1.10.1 is available for download

Technical Documentation

Supported Environments - minimum Requirements (no change from 1.10.0)

New Features

• Improved performance for License Manger Server analysis
• Improved performance for License Manager tools and dialogs in the GUI
• User can schedule an immediate Scan of a License Server from GUI
• FlexLM monitor can now distinguish between used, checked-out and borrowed licenses
• FlexLM scan properly parses more vendor specific variants
• OctoSAM Monitor now provides an optional web interface (Beta)

Removed Functionality

• Scanning capabilites for LicenseManagerServers can no longer be limited per server. All capabilities supported by a License Manager Server type are always enabled.
• Group scan via PowerShell script and Import Service is no longer supported. Use the integrated group scan in the OctoSAM import service.

Breaking Changes for OctoSAM Monitor

• In previous releases, FlexLM scan did support scanning of user names that contain spaces. This has been changed to an optional feature now which is disabled by default. If you have FlexLM license servers with usernames that contain spaces, you have to enable the corresponding option in the settings dialog of each affected FlexLM server.
• LicenseManagers section in appsettings.json has been renamed to LicenseManagerServers. Type names have been adjusted for consistency. See the sample configuration file.

Scan File Compatibility

• The 1.10.0 import service supports reading 1.10.1, 1.10.0, 1.9.10 and 1.9.9. scan files. Import of older .scan files 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 the database migration script(s) for additional checks that you may have to run against the database before migration.
• Make sure you are on the required database compatibility level
• 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.0 is not supported
• Check the release notes of earlier versions for migration procedures
• Optionally run the .MSI Installer for the GUI
• 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
  Note that configuration keys in section LicenseManagerServers have been adjusted for consistency
  Note that the configuration section "Rbac" has been extended to support multiple user containers
  Consult the sample file for settings for the new Web interface (Beta)
• Unzip the distribution archive and copy the Server folder to your designated location, usually D:\OctoSAM\Server
• 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
• Note that the LicenseManagerServerObserverService must be started before creating or updating License Manager Server objects in the GUI
• Update Octoscan2 windows scanner
• Update the Mac and Linux Scanner(s)
• Update other scanners and their start scripts. Note that the Powershell Modules are now in the Server folder, usually D:\OctoSAM\Server\Modules

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.

OctoSAM Release 1.10.0 is available for download.

Technical Documentation

Supported Environments - minimum Requirements

New Features

• Adobe User Management assigned licenses can now be scanned and imported into the OctoSAM repository
• OctoSAM can now normalize manufacturer information based on a hardware manufacturer catalog which is maintained and regularly updated via catalog update. This allows for easier grouping and filtering for same manufacturer.
• EPLAN license server monitoring
• OctoSAM now allows to maintain custom fields not only per machine or per software package but also for each individual installation. This can be useful in consolidation and migration projects where you want to enter custom information per software installation.
• Query results can now be exported to JSON from the Octopus2 UI and from Octoutil.
• Query results can now be exported as an SQL Script to load the resulting table into an SQL Server database
• All appsettings configuration files have been migrated to hierarchical system of appsettings.json files
• All settings can now be configured in a single file per installation for all components. Individual configuration per component can still be used to override the global configuration.
• log4net logging was migrated to Serilog.
• Logging configuration has been streamlined. Default installations need exactly 1 setting for logging for all components. The full power of Serilog can be used by configuration but default configuration is now extremely simple to set up.
• The directory structure of the installed software has been simplified and reorganized to support XCOPY deployment
• All Server Components now use XCOPY deployment exclusively
• The OctoSAM GUI can still be installed with an MSI Installer for Installation on Workstations / App-V.
• In the OctoSAM GUI you have a new option to always show 'Junk' Software categories such as drivers.
• ServiceNow integration can now chose to use physical identity attributes such as mac address and SMBIOS UUID to coalesce computers.
• Windows Scanner octoscan2 now scans some BIOS settings directly even if WMI scan is disabled.
• FlexLM Server scan supports newer versions of FlexLM, diag scan is no longer needed for license expiry detection
• New group context query can be started from the group window. This allows to easily export group membership information to Excel or other Tools.
• Windows based upload server OctoCollect is now .net 5.0 based

Changed Architecture of OctoSAM Services

• The OctoSAM services and the OctoUtil command are now .net 5.0 based.

Changed Configuration Architecture for OctoSAM GUI Components

• While the GUI components still depend on Windows Forms and .net Framework 4.8, the configuration mechanism has been ported to the .net 5.0 mechanisms using appsettings.json file. EXE.config files are still there but only for .net specific configuration which normally does not need to be changed.
• Login environments can now be configured directly in appsettings.json, Environments.xml is no longer used.
• The Powershell modules are now in a Subdirectory of the Server folder, you need to change your scripts that reference the Powershell modules

Changed Functionality for OctoUtil

• Anonymizer functionality has been moved to the OctoUtil anonymize command.
• The OctoUtil command parsing logic has been improved. The parser is now more strict, check your OctoUtil scripts
• OctoUtil now sets the exit code more consistently so that calling scripts can test %ERROR_LEVEL%

Removed Functionality

• Configuration options for conditional WMI import have been removed. Former default setting of "ALWAYS" is now the only option.
  Much more functionality also for SAM reporting depends on this information now, so we need to always import this information.
• The anonymizer tool is no longer available as a stand-alone executable. Its now integrated into OctoUtil, Anonymizers Scripts may have to be adapted.

Scan File Compatibility

• The 1.10.0 import service supports reading 1.10.0, 1.9.10 and 1.9.9. scan files. Import of older .scan files 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

• Before upgrading, read the modified installation documentation for release 1.10 since architecture and installation procedures have changed considerably from previous versions.
• 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
• Uninstall the OctoSAM services from the system either using the --uninstall option or the SC utility
• Make a backup copy of the database
• Note that a direct migration from a Version other than 1.9.10 is not supported.
• Check the release notes of earlier versions for migration procedures.
• Make a backup copy of all configuration files
• For Server / Full installations: Uninstall the previous installation from the system, for GUI only (clients) you do not need to remove the previous installation.
• Set the system environment variable OCTOSAM_CONFIGURATION_FOLDER to your designated configuration folder, usually D:\OctoSAM\Config
• Migrate your settings from the diverse configuration files in prior version to the new central configuration file appsettings.json starting from the provided sample file.
• Optionally run the .MSI Installer for the GUI
• Install the Microsoft .net 5.0 Runtime (For OctoSAM Server only)
• Unzip the distribution archive and copy the Server folder to your designated location, usually D:\OctoSAM\Server
• If you scan license management servers such as FlexLM, make sure the local tools are current. Use the newest tools provided by your servers.
• Install the services using the supplied install_service.ps1 scripts. Note that you have to change the Service Accounts manually after installation of the services.
• Import standard queries and Reports from provided .zip file.
• Start OctoSAM services
• Update Octoscan2 windows scanner
• Update the Mac and Linux Scanner(s)
• Update other scanners and their start scripts. Note that the Powershell Modules are now in the Server folder, usually D:\OctoSAM\Server\Modules

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.

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.

Can be downloaded from the Filebase

Supported Environments - minimum Requirements

New Features

• Improved Java detection
• Oracle GA / BPR release detection for Java 1.6, 1.7 and 1.8
• HTTP/S based scan file collection server is now also available on Windows / IIS.
• A summary of detected Java versions and features can be found here
• Improved VMWare ESX Support to directly indicate VCenter to ESX host relations required for Oracle licensing calculations
• Catalog based Oracle Core Factor. Can be manually overridden per machine.
• Software catalog update can now be scripted (OctoUtil) or automated in import service
• Improved performance of the Windows GUI.
• Improved application startup performance by significantly reducing the number of database round trips.
• Improved OctoUtil plan processing logging and .csv parsing.
• Master catalog info now lists package to publisher relations
• Improved High DPI rendering of the Windows GUI
• Additional Fields in Queries
• Data model clean-up

Potentially Breaking Changes

• Windows Server 2008 no longer supported
• Windows 7 without Service Pack 1 no longer supported
• WIndows 7 SP1 and Windows Server 2008 R2 need patches to support SHA-2

Potentially Breaking Changes for Custom Queries

• Attribute sortstyle is no longer supported for multiselect and dropdownlist controls

Potentially Breaking Changes in the Data Model

• Tables and Columns in the database that were not used have been removed in this release
• User.Guid must now be unique. You cannot migrate the database is this requirement is not met

Potentially Breaking Changes in OctoUtil Import Plans

• The .csv parser has been refactored. Comment lines starting with # are now always ignored, The new implementation of skiplines does no longer count comment lines.

Scan File Compatibility

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

Update Instructions

• 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.8 is not supported.
  Update to version 1.9.8 and run a full housekeeping before updating to 1.9.9
• Make a backup copy of all configuration files
• Run the .MSI Installer
• Merge the configuration settings with the new configuration template files.Update the software catalog
• Import Standard Queries and Reports from provided .zip file.
• 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.

OctoSAM releases 1.9.8 to 1.10.9 greatly extended the detection capabilities for various java distributions.

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

Can be downloaded from the Filebase.

Supported Environments - minimum Requirements

New Features

• Detect Windows App Store installed apps
• Improved Java Detection:
  A summary of detected Java versions and features can be found here.
  • Detect if Oracle Java commercial features are enabled.
  • Detect Oracle Java .MSI installation.
  • Improved detection of different OpenJDK publishers. You now get detailed Information about different OpenJDK distributions such as RedHat, Azul, Amazon, AdoptOpenJDK etc.
  • Linux: Improved Java detection based on process and optional filesystem scan.
  • Windows Server: improved Java detection based on optional process scan even if Metering is not enabled.

• Mac: Identification of 32-bit applications to help prepare for macOS 10.15 Catalina migration.
• Software InstallDate now gets scanned, if available.
• The lastWritten date of the installer registry key gets scanned and can be used together with InstallDate.
• Signatures have 2 new fields: FileVersion which gets the file version resource if available, BaseVersion where per product logic can write a common version, such as the Java OpenJDK version that the distribution is based upon.
• LicensingRelevant can now be set on the Signature level for packages that have different licensing requirements for minor patch levels such as Oracle Java.
• More tabs in the GUI are now disabled if there is no data.
• High DPI rendering has been improved in the Windows GUI.
• The import service now has built-in capability to collect scan files from Linux based collection servers using ssh/sftp.
• Streamlined installation and configuration:
  • Additional configuration of the database connection string for log4net in services is no longer required.
  • A separate Installation of SQL Server SMO / Feature Pack is no longer required for interactive database selection. The OctoSAM .msi installs and updates all required components.
  • Environments.xml file in the program directory gets picked up without further configuration.
  • SiteTasks.xml file in the program directory gets picked up without configuration.
  • License constrained queries do now show/hide immediately after a license option gets enabled (import of a new license) no need to re-import queries.
  • Data constrained queries do now show/hide immediately after housekeeping.

Removed Functionality

• Import/Export Signatures and Packages functionality has been removed. Export of custom packages can be achieved through Query: Internal / Table Dumps / Software Package and selecting 'Predefined By Octopus' = false. Later Builds will provide a mechanism to export custom Publishers and Packages to the new file based software catalog format.
  

Potentially Breaking Changes in the Data Model

• SoftwarePackge.SoftwarePublisherID can no longer be NULL. Joins from SoftwarePackge to SoftwarePublisher should be converted to to inner joins.
  Queries that depend on this column being NULL must be refactored.
• SoftwareSignature.AutoAssigned has been removed as it is no longer needed. Custom Queries may have to be adjusted.

Potentially Breaking Changes in config files

• 1.9.8 introduces the OctopusAdoNetAppender for log4net. This appender behaves like the standard ADO.net appender but takes the connection string directly from the appsettings file. You no longer have to set the connection string twice per service. See the provided sample configuration files.
• The 1.9.8 installer now unconditionally overwrites existing .exe.config files. Application specific settings should be in .appsettings.config files and not affected. However, if you changed settings in an .exe.config file, these changes have to be re-applied after installation updates or repairs. This change was introduced to make sure you have valid assembly redirect configurations in your .exe.config files.

Other Breaking Changes

• If you have Windows XP or Windows Vista systems on the network, you need to make sure that GPO starts of the windows scanner do not affect these Systems. Use GPO mechanisms such as WMI filters to exclude these machines from scan. Starting the scanner on a non-supported OS version will produce a Windows error message that cannot be suppressed.

Scan File Compatibility

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

Update Instructions

• Make sure all custom software packages have a software publisher assigned.
  Database Migration will fail if this is not the case. See the database migration script for details.
• Make sure .NET Framework 4.8 is installed
• 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.7 is not supported.
  Update to version 1.9.7 and run a full housekeeping before updating to 1.9.8
• Make a backup copy of all configuration files
• Run the .MSI Installer
• Merge the configuration settings with the new configuration template files.
  For services log4net configuration, change AdoNetAppender Type to the new OctopusAdoNetAppender and change the connectionString according to sample config.
• Update the software catalog
• Import Standard Queries and Reports from provided .zip file.
• 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.
• Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignore

Can be downloaded from the Filebase

Supported Environments

New Features

• OctoSAM License: detailed software item change history
• OctoSAM License: more compact layout of pages
• OctoSAM License: Publisher landing page with list of Items
• OctoSAM License: Context Queries
• Unified Python based macOS and Linux scanner
• New web-based upload server for scan files
• Windows scanner: more robust configuration parsing, canary test for new versions of the scanner
• Windows scanner: improved Java installation detection
• Windows scanner: metadata about custom files can be scanned. This allows to scan for specific files on a windows machine.
• WIndows scanner: improved Oracle database detection
• GUI: improved optional High DPI support
• GUI: cleaner loading of documents with less screen flickering
• GUI: Improved performance for tree controls
• GUI: Updated 3rd party components with many integrated bug fixes
• GUI: Group information and link now available on the Software Package document for published applications
• Improved Active Directory import performance and stability
• Completely refactored LDIF import with much better performance for importing huge files
• Up to 4 site-specific Active Directory extended schema properties can now be imported per User and Machine object
• All standard grids now contain a hidden column "CurrentDateTime" with the time the data was read
• Extensions to the Repository and Catalog structures allow centrally managed client specific queries, reports and catalog items
• Unique Customer and Installation IDs are now encoded in the License file
• Improved performance of software usage queries
• Extended Query engine to support more flexible rendering on web pages
• Cleaned up Data Model including Documentation
• Support for new SQL Server 2017 and 2019 Cumulative Update versioning
• Support for SWID tag files schema version 2015
• Anonymizer now handles computer account user objects consistently using the anonymized machine name

Removed Functionality

• None

Potentially Breaking Changes in the Data Model

• Fields DirectoryExt1 / DirectoryExt2 and Ext1 / Ext2 are now used to optionally load site specific schema extension properties from Active Directory. If these fields were previously used to load site-specific Data from external sources, this needs to be re-designed.

Potentially Breaking Changes in octoscan.config

• if match conditional regex comparison is now case in-sensitive

Potentially Breaking Changes in config files

• default encoding for LDIF import is now 'utf-8', ldif lookup configuration may have to be adjusted
• default Active Directory Lookup.Method changed from "accountmanagement" to "directoryservices"

Scan File Compatibility

• The 1.9.7 import service can read 1.9.7, 1.9.6 and older scan files. 1.9.7 and 1.9.6 .scan Files can only be imported on 1.9.6 or newer.

Update Instructions

• Order an updated License for 1.9.7 from Octosoft
• 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.6 is not supported.
  Update to version 1.9.6 and run a full housekeeping before updating to 1.9.7
• Make a backup copy of all configuration files
• Run the .MSI Installer
• Merge the configuration settings with the new configuration template files.
• Install the updated license
• Update the software catalog
• Import Standard Queries and Reports from provided .zip file.
• Start OctoSAM services
• Update Octoscan2 windows scanner
• Update the Mac 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.
• Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignore