Supported Environments - minimum Requirements
||Windows Server 2008 R2
Windows 7 SP1
|macOS Scanner||Mac OS X 10.15 (Catalina)
|Linux Scanner||RHEL / CentOS 7
Rocky Linux 8.4
other systemd based distributions upon request
|OctoSAM Database||SQL Server 2016 SP3 (Compatibility Level 130)
|OctoSAM Server Components||Windows Server 2016
.net 6.0 hosting bundle
|OctoSAM GUI||Windows 10 2004 (20H1) / Windows Server 2016
.net 6.0 desktop runtime 64 bit
- 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
- 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.
- 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
- 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.