OctoSAM 1.8.12 is available for download in the filebase.
Active Directory Group Scanner
Allows scanning of security groups from Active Directory. Primary intent is to consolidate Information about access permissions for published applications (for example Citrix).
VMWare vSphere vCenter Scanner
The vCenter scanner gathers Information about virtual machines and ESX hosts.
Master Software Catalog
Software Package Signature Auto Assign can now specify if the pattern matches metering Information
Detailed detection of SQL Server variants also as Software SIgnatures
OctoSAM Inventory GUI
New windows and dialogs to inspect and manage the new objects introduced by the VMWare and group scans. Many usability improvements.
Changes and Enhancements:
- Updates to used 3rd Party components
- Stability Updates
- Updated Documentation
- Deploy the new Version of Octosocan2.exe to your Environment
.scan files are compatible with versions 1.8.6 or newer of the import Service
no changes to octoscan.config in this release
- Stop OctoSAM services on the server
- Make a backup copy of the database
- Run database migration script(s) from support.zip
- Run the .msi Installer
No changes to configuration files are needed if you are upgrading from 1.8.11. From earlier versions take the new configuration files from SampleConfigurationFiles and work from there
- Update the software catalog from latest master file.
- Restart OctoSAM services
- Optionally configure the VMWare vCenter scanner (Support.zip/VMWare)
- Optionally configure the AD Group scanner (Support.zip/GroupScan)
Known Limitations (will be fixed in further releases):
- 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 ignored.
- Adobe SWID tag files my be left on disc even if the software gets uninstalled, OctoSAM currently counts packages as installed if they contain a swid signature that is found on disc. This may lead to wrong installation counts.