Posts by Erwin Richard

    Octosam 1.9.8 Release extends Java scan to detect optional commercial features.

    The following Table shows the current capabilities per platform:


    Detection Windows Linux Mac
    Detailed version, edition and publisher detection Yes Yes Yes
    Detailed Open JDK publisher detection Yes Yes Yes
    JRockit detection Yes Yes Planned
    Detection of updates within Oracle Java version that require licensing
    (Updates that are not publicly available or change of license policy within a version)
    Yes Yes Yes
    Patchlevel within Update version information Yes Yes No
    Use of .MSI installer vs. free .exe based installer Yes N/A N/A
    Java Usage Tracker Feature system-wide file based configuration Yes Yes Planned
    Java Usage Tracker JAVA_HOME file based configuration Yes Yes No
    Java Usage Tracker command line configuration at scan time Yes Yes Planned
    Java commercial features command line configuration at scan time Yes Yes Planned
    Weblogic / Websphere command line configuration at scan time Yes Yes Planned
    Tomcat command line configuration at scan time Yes Yes Planned
    Tomcat Windows service detection Yes N/A N/A
    Catalog based Oracle processor core factor detection
    Yes Yes Yes


    The different scanners use a collection of platform specific methods to detect Java installations


    Method Windows Linux Mac
    Standard system Java (PATH) Yes Yes Yes
    System default package installer Yes Yes Yes
    Custom package installer N/A N/A Planned (Homebrew)
    Java Registry Yes N/A N/A
    JRockit Registry Yes N/A N/A
    Running processes at system scan Yes Yes Planned
    Running processes during whole user session session (metering) Yes No Planned
    Standard file system locations No Yes Yes
    Configurable custom file system locations Planned Yes No
    Windows Services scan Yes N/A N/A
    Systemd scan N/A Planned N/A

    Can be downloaded from the Filebase.


    Supported Environments - minimum Requirements

    Windows Scanner
    Windows Server 2008 R2 SP1, Windows Server 2008 SP2.

    Windows 7 or newer (32 and 64bit) - Windows Vista no longer supported.

    Use 1.9.7 Version of the scanner for Windows Vista

    Use 1.9.6 Version of the scanner for Windows XP / Windows Server 2003.
    macOS Scanner Mac OS X 10.12 (Sierra)
    Linux Scanner RHEL / CentOs 7
    Fedora 25
    SUSE 12
    Debian 9

    Ubuntu 16

    other distributions upon request

    OctoSAM Database SQL Server 2016 SP1 or newer
    OctoSAM Server Components .net Framework 4.8 64 bit required
    OctoSAM GUI .net Framework 4.8 64 bit required



    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


    Windows Scanner Windows Server 2008,
    Windows Vista or newer (32 and 64bit) - Windows XP And Windows Server 2003 no longer supported.
    Use 1.9.6 Version of the scanner for Windows XP / Windows Server 2003.
    macOS Scanner Mac OS X 10.10 (Yosemite) or newer
    Linux Scanner (beta) RHEL / CentOs 7
    Fedora 25 or newer
    SUSE 12 or newer
    Debian 9 or newer
    Ubuntu 16 or newer **
    ** on minimal Ubuntu installations you may need to install python-minimal
    OctoSAM Database SQL Server 2016 SP1 or newer
    OctoSAM Server Components .net Framework 4.7.2 64 bit required
    OctoSAM GUI .net Framework 4.7.2 64 bit required




    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

    Can be downloaded from the Filebase


    Supported Environments


    Windows Scanner Windows Server 2003, Windows XP or newer (32 and 64bit)
    macOS Scanner Mac OS X 10.6 (Snow Leopard) or newer
    Database SQL Server 2016 SP1 or newer is required
    OctoSAM Server Components .net Framework 4.7.2 64 bit required
    OctoSAM GUI .net Framework 4.7.2 64 bit required



    New Features

    • Integrated Microsoft 365 licensing information
    • All Reports (including Custom Reports) can now be used from the web interface with role-based access control per report. Reports can be printed and exported in various formats.
    • Most Queries (including Custom Queries) can now be used from the web interface with role-base access control per query and for each column within the query. Queries can be exported to Excel.
    • You can now prepare site-specific queries and reports with access to a precisely defined subset of the inventory and OctoSAM License data and allow people to run them without any local software installation or remote access to the OctoSAM desktop UI.
    • VDI VMWare Horizon ViewClient Information gets collected. This allows to query for specific clients or users on a VMWare Horizon server.
    • Volatile environment information gets collected and scanned
    • License Manager fields now support up to 2,147,483,647 issued licenses per feature. Previously they were limited to max 32,787.
    • Database Objects now have a database independent unique id for external links
    • Detailed Windows operating system and SQL Server version detection moved from the scanner to server components
    • Windows scanner now detects lock screen and does not meter applications during screen lock
    • Detailed and accurate Visual Studio installation information using the Visual Studio Setup Configuration API
    • Mac scanner has been updated for more flexible user mapping to Active Directory accounts
    • VMWare ESX scanner now reports more details about ESX host hardware including bios serial number and asset id.
    • VMWare ESX scanner now reports more details about VCenter configuration including the Server Unique ID.
    • OctoSAM Inventory now supports scanning of cloned VCenters as long as they have a unique Server Unique ID.
    • BIOS asset tag is now directly available on the machine object
    • Additional fields in OctoSAM License
      • New flag 'Active' to hide inactive Items from upcoming items list
      • New AdministratorNotes formatted text field
      • New PrintableName field for easier and more consistent listing of items in queries and reports
    • More flexible signature rewriting rules, now support conditions using regular expressions. This reduces the number of needed rewriting rules significantly and catches point updates to required signatures without having to update the catalog.
    • New option to octodump to re-compress .xml files after manual changes or scripted XML transformation.
    • Organization mapping rules can now also be applied to Missing Users and Missing Machines tables
    • Icons for machine and user now reflect Active Directory information for disabled and deleted accounts (if available). Orphaned objects are now directly visible in the GUI.
    • XML Schema support for queries
    • octoutil delete user and machine commands can be called with domain/machine or user principal name instead of id only.
    • Improved Anonymizer to create more congruent anonymized instances of your database.
    • Improved logging. Minimize warn messages in log files. Added new configuration parameters to suppress warn logs for known warnings that can be ignored due to site specific configuration issues.
    • Improved optional High DPI support
    • Improved Active Directory import
    • Improved Performance throughout the application
    • Updated 3rd party components with many integrated bug fixes
    • Migrated to .net 4.7.2

    Removed Functionality

    • Scanning of Product Keys has been removed
    • Fields CostPerSeat and LicenseCount on SoftwarePackage have been removed.
    • Manual Signature to Package management has been removed, define custom packages with auto assign rules

    Potentially Breaking Changes in the Data Model

    • Check your custom Queries/Reports for the following breaking changes in the Data Model:

      Removed Columns:
      SoftwarePackage.CostPerSeat
      SoftwarePackage.LicenseCount
      Machine.HintProductKey

      RenamedColumns:
      SoftwareItem.Notes (from SoftwareItem.Remarks)
      SoftwareItem.OwnerNotes (from SoftwareItem.OwnerRemarks)
      NB: RBAC Privilege names change also. These privileges need to be re-applied after migration and first full housekeeping.

      Removed Tables:
      ProductKey

    Potentially Breaking Changes for Queries and Reports

    • Queries now must declare namespace xmlns="http://www.octosoft.ch/schema/query/2018/query.xsd" on the <query> element.
    • XInclude feature to include sub queries has been removed. For multiselection input use the new stockquery attribute.
    • Processing of sub reports from repository reports has been removed

    Potentially Breaking Changes in octoscan.config

    • The windows scanner octoscan2 uses a new regex engine
      The new engine always uses implicit ^ and $, the pattern must match the whole string and not only a substring.
      Check regular expressions used in octoscan.config file.

    Scan File Compatibility

    • The 1.9.6 import service can read 1.9.5 and older scan files. However, 1.9.6 scan files can only be imported by 1.9.6 and newer versions of the import service. Lookup tables for operating system and server products have been moved from the scanner to the import service, therefore 1.9.6 .scan files cannot be imported with older import services.

    Update Instructions

    • Installation Directory changes from c:\Program Files (x86) to c:\Program Files therefore you cannot update in-place.
    • Make a backup copy of the database
    • Stop OctoSAM services on the server
    • Migrate to schema version 1.9.6 from 1.9.5.
      See release notes of 1.9.5 if you migrate from earlier versions.
      Configure enough maximal log space for migration of the License Manager statistics table. Recommended is min. 5 times the size of the database.
      Plan for enough time for the database Migration. Installations with many license manager servers may take several hours to migrate.
    • Make a backup copy of all configuration files
    • Uninstall the Services from the Service Registry using the --uninstall option on the service executables
    • Uninstall the current software installation and remove all left over files (manually changed configuration files)
    • Run the .msi Installer
      Note that the Install Location changes from c:\Program Files(x86) to c:\Program Files
    • Merge the configuration settings with the new configuration template files.
    • If you have created copies of the start shortcut in the taskbar or on the desktop, these are now invalid, re-create with the new path
    • Update the software catalog (note that the format of the software catalog has changed, use new version of catalog).
    • Import Standard Queries and Reports from provided .zip file.
      Test your custom queries with the new release. Note that you have to declare the namespace on the <query> element (xmlns="http://www.octosoft.ch/schema/query/2018/query.xsd")
    • Register OctoSAM services
    • Start OctoSAM services
    • Update Octoscan2 windows scanner (do not update the windows scanner before the 1.9.6 import service is up and running)
      1.9.6 import can import older .scan files but 1.9.6 scan files require Import Service 1.9.6. Note that the 'ScanProductKeys' configuration setting is no longer supported.
    • Update the Mac Scanner
    • Update the VMWare vCenter scan start script - if in use - according to sample provided.
      Note that the path to the OctoSAM Powershell modules has changed
    • Update the AD Group scan start script - if used - according to sample provided.
      Note that the path to the OctoSAM Powershell modules has changed


    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 ignored

    Die Information über Monitore wird für windows 7 und neuer aus WMI abgefragt.


    Die Info welche man von Windows/WMI erhält ist nicht immer aktuell/akkurat - besonders bei Laptops welche wechselnd an mehrere externe Monitore angeschlossen werden (z.B. in Umgebungen mit Desksharing) gibt es teilweise irreführende Resultate.


    Wir haben daher die Monitor Queries aus den Standardqueries entfernt. Sie können weiter bei uns bezogen und verwendet werden, wenn man sich über die Limiten der Genauigkeit der Resultate im Klaren ist.

    Falls das Gerät über USB angeschlossen - und wenn die USB ID bekannt ist - könnte man über entsprechende SQL Statements die Geräte annähernd ermitteln. Die Funktionalität ist aber nicht ins UI eingebaut, bzw. es gibt keine mitgelieferten Queries. Bei Geräten, welche abwechselnd an verschiedenen Computern angeschlossen werden können ist die Interpretation der Resultate aus der Inventardatenbank nicht trivial. Eine andere Möglichkeit ist die Suche via die verwendete Treibersoftware.

    Can be downloaded from the Filebase.


    Supported Environments


    Octoscan2 Scanner Windows Server 2003, Windows XP or newer (32 and 64bit)
    (no change between 1.9.4 and 1.9.5)
    Database SQL Server 2016 SP1 or newer, Support for SQL Server 2012 SP1 with restricted functionality.
    OctoSAM Server Components .net Framework 4.7.1 64 bit required
    OctoSAM GUI .net Framework 4.7.1 64 bit required


    New Features

    • New web based module for internal list of software resources.
      Publish information about your software to your users and software owners and combine it with a concise subset of inventory information.
      Flexible RBAC model to decentralize information update and limit visibility of inventory information according to target audience.
    • A lot more attributes from Active Directory are now directly available on the User, Machine, DirectoryMissingUser and DirectoryMissingMachine objects.
      Attributes whenCreated and whenChanged are now replicated to all Tables that contain AD objects.
    • HardwareUniqueID and OperatingSystemUniqueID fields on Machine abstract the source of this information for different OS Types.
      Mac Serial Number and Platform UUID Support.
    • Group Scan can now be performed directly from the Import Service in most scenarios.
    • Machine Group Membership now displayed in the OctoSAM Inventory GUI.
    • User Device Affinity can now be imported from other systems such as SCCM
    • Last User and Most Frequent User information can now be viewed in opposite direction. (All machines where a user is Last user).
    • Greatly improved load time for main object windows (Machine, User, SoftwarePackage).
    • Consolidated metering is now available for all packages that support detection of processes. Up until now, each Package had to indicate consolidated metering, this is no longer needed.


    Update Instructions


    Prerequisites

    • Check your custom Queries/Reports for Changes in the Data Model that are not backward compatible:
    • Plan migration of your Database to Sql Server 2016 SP1 or later. Consult with us if you cannot move to SQL Server 2016 yet.
    • .net Framework 4.7.1 is required, For High DPI UI features, WIndows 10 Creators Update is required.

    Database

    • Make a backup copy of the database
    • Migrate to schema version 1.9.5 from 1.9.4. See release notes of 1.9.4 if you migrate from earlier versions.

    Scanner

    • Deploy the new Version of Octosocan2.exe to your environment .scan files are compatible with versions 1.8.16 or newer of the import Service

    GUI Client

    • OctoSAM Inventory client: Update Installation is supported, just install the .msi over the existing installation.

    Server Components

    • Stop OctoSAM services on the server
    • Make a backup copy of all configuration files
    • Uninstall your current version of the software from the system.
    • Remove any files that might be left over after uninstall from the program folder.
    • Run the .msi installer
    • Merge the your old configuration settings from the backed up config files with the new configuration template files.
      Note that appSettings and log4net config are now externalized into their own files.
      You usually do not have to edit the .exe.config files. Best to leave them unchanged as they are now maintained by the installer/update.
    • Note that Active Directory configuration has changed considerably in this release. Refer to the provided sample config files.
    • Update the software catalog from latest master file
    • Import standard queries and reports from provided .zip file.
      Tests your custom queries with the new release.
    • Restart OctoSAM services
    • Update the VMWare vCenter scan start script - if used - according to sample provided in Support.zip
    • Update the AD group scan start script - if used - according to sample provided in Support.zip.
      Consider using the new group scanner integrated in the Import Service.

    Known Limitations

    • DPI scaling works only on Windows 10 creators update or later.
    • 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.
    • Currently, the license manager statistics database does not allow more than 32767 issued licenses per server. Counts greater than that value will get truncated. "Unlimited" will also be converted to 32767
    • Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignored

    Can be downloaded from the file base.


    Supported Environments


    Octoscan2 Scanner Windows Server 2003, Windows XP or newer (32 and 64bit)
    (no change between 1.9.3 and 1.9.4)
    Database SQL Server 2012 R2 or newer.
    OctoSAM Server Components .net Framework 4.6.2 64 bit required
    OctoSAM GUI .net Framework 4.6.2. 64 bit required



    New Features

    • Repackaging information can now be collected per installation. For sites that tag software installations with special entries in the uninstaller registry, this information can now be collected per installation. This allows to locate installations that were not made using the official packages.
    • MAC address is now available directly in the machine object for Windows, Mac and ESX. In previous versions it was complicated to get the 'active at scan time' MAC address in the inventory for systems with multiple network adapters. Now the MAC address is reported by the scanners.
    • License manager server housekeeping has been improved
    • Powershell modules are now installed in the program folder and maintained with the .MSI. Placing the shell modules in the program folder protects them from unintentional modification and allows automatic update of the modules via .MSI installation.
    • VMWare ESX Scanner now supports PowerCLI 6.5 (Modules instead of Snapins)

    Removed Functionality

    • NetInstall Scanning has been removed from Octoscan2

    Update Instructions

    • Check your custom Queries/Reports for Changes in the Data Model that are not backward compatible:

      SoftwareSignature.Repackager
      SoftwareSignature.RepackagerInfo
      SoftwareSignature.RepackagerVersion

      have been removed. Use Columns in MachineSoftwareSignature instead.

      SoftwarePackage.LicensingRelevant

      has been removed. Use SoftwareLicensingType.LicensingRelevant instead.
    • Check the changed prerequisites: SQL Server 2012 R2 is required, .net Framework 4.6.2 is required
    • Make a backup copy of the database
    • Migrate to schema version 1.9.4 from 1.9.3. See release notes of 1.9.3 if you migrate from earlier versions.
    • Deploy the new Version of Octosocan2.exe to your environment .scan files are compatible with versions 1.8.16 or newer of the import Service
    • Stop OctoSAM services on the server
    • Make a backup copy of all configuration files
    • Run the .msi Installer
    • Merge the configuration settings with the new configuration template files.
      Be especially careful with the assembly binding redirect section of the configuration files. This section must exactly match the settings in the provided sample configuration files.
    • Update the software catalog from latest master file
    • Import Standard Queries and Reports from provided .zip file.
      Tests your custom queries with the new release.
    • Restart OctoSAM services
    • Update the VMWare vCenter scan start script - if used - according to sample provided in Support.zip
    • Update the AD Group scan start script - if used - according to sample provided in Support.zip


    Known Limitations

    • DPI scaling 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.
    • Currently, the license manager statistics database does not allow more than 32767 issued licenses per server. Counts greater than that value will get truncated. "Unlimited" will also be converted to 32767
    • Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignored

    Release Version 1.9.3 can be downloaded from the filebase.


    Supported Environments


    (no change between 1.9.2 and 1.9.3)


    Windows Server 2003 SP1, Windows XP SP3 or newer (32 and 64bit)
    SQL Server 2012 R2 or newer
    .net Framework 4.6.1
    .net Framework 4.6.1. 64bit OS and minimum of 8GB RAM recommended



    New Features


    Master Catalog and Custom Packages

    Conflict handling between Master Catalog and custom packages has been modified in 1.9.3. If there are simple conflicts between package definitions in the Master Catalog and custom packages, custom packages always override the Master Catalog.

    If you want the master package back, delete the conflicting custom package. If a new custom package conflicts with an existing Master Catalog package, delete the master catalog package. The catalog update wizard has a new tab 'Custom' that shows all custom package that have potential conflicts with the Master Catalog.



    Octoscan2: Microsoft Visual Studio Detection

    Octoscan2 now uses the Microsoft documented methods to find out the installed edition of Visual Studio versions from 2010 to 2015.

    Visual Studio 2017 RC recognition if installed on standard paths. Special signatures msvs: are emitted by the scanner.


    Octoscan2: Status Window

    Cleaned up drawing of the debug/status window, eliminated excess flicker.

    Under Windows 10, the status window is now per Monitor DPI aware.


    Adobe Acrobat DC Editions

    Can now distinguish Pro / Standard Editions based on SWID Serial Number


    OctoScanSettings

    This utility program to override Octoscan2 configuration per machine is now a native program with no dependencies on .net.

    It supports the same platforms as the scanner Octoscan2.


    Machine

    2 new Fields on Machine

    • PcSystemType
      New hardware type based on Win32_ComputerSystem.PCSystemType / PCSystemTypeEx that's easier to handle than 'ChassisTypes'.
    • ProcessorFamily
      .

    SWIDDocument

    Key elements from SWID Tag files are now available directly in the SwidDocument table. No more complex XML XPath code in Queries needed to access these values.


    Data Model

    Cleanup of data model and database documentation


    High DPI Support for the OctoSAM Inventory GUI

    Fonts are now scaled according to System DPI settings and are more crisp than when using Windows default scaling on high DPI devices.

    Note that when you have multiple Displays with different DPI settings, windows may still scale the GUI with slightly blurred fonts and icons, depending on the configuration.


    Queries

    Overhauled queries for more consistent field names and tooltips on all columns.

    Tooltips are now also shown in the Column Chooser window.

    In developer mode, the query engine makes more checks to help detect coding errors such as typos etc in query definition.


    Custom Queries, Tasks and Reports Paths

    Paths to custom queries, tasks, and reports can now be configured per database in the ConfigurationInformation table in addition to

    configuration in the application configuration file (Octopus2.exe.config).


    WMI Codes

    Most WMI codes are now shown also in clear text


    Code Translation via Master Catalog

    Code translations are now stored in the database and can be updated via Global Catalog update.

    This makes code translations also available for Queries.

    Hard-coded translations in queries have been removed.


    OctoUtil

    Database connection can now be specified on the command line for scripting multiple databases

    New commands 'import repository' and 'import codes'


    Changed Functionality

    • Installation of a new software version of the import service now triggers a full housekeeping cycle with recalculation of all attributes. Previously that was only triggered by database schema update.
    • Logging of time information has been changed from milliseconds to 'rush format' showing the two most significant units.
      For example 1m 2s instead of 62000 ms.

    Removed Functionality

    • Display(Monitor) information via VESA for systems prior to Windows 7 is no longer supported. WmiMonitorID information is fully supported but not available on Windows XP.
    • Display(Monitor) information has been removed from machine reports as it has become largely irrelevant. WmiMonitorID information is still available in some Queries.
    • FlexLM user filtering feature has been removed
    • The AutoAssign view has been removed.
    • Database tables deprecated in earlier versions have ben removed
    • Office 2003 related queries have been removed

    Update Instructions:

    • Make a backup copy of the database
    • Migrate to schema version 1.9.3 from 1.9.2. See release notes of 1.9.2 SP1 if you migrate from earlier versions.
    • Deploy the new Version of Octosocan2.exe to your environment .scan files are compatible with versions 1.8.16 or newer of the import Service
    • Stop OctoSAM services on the server
    • Make a backup copy of all configuration files
    • Run the .msi Installer
    • Merge the configuration settings with the new configuration template files.
      Be especially careful with the assembly binding redirect section of the configuration files. This section must exactly match the settings in the provided sample configuration files.
    • Update the software catalog from latest master file
    • Import Standard Queries and Reports from provided .zip file.
      Tests your custom queries with the new release.
    • Restart OctoSAM services
    • Update the VMWare vCenter scanner if older than 1.9.2 (Support.zip/VMWare)
    • Update the AD Group scanner if older than 1.9.2 (Support.zip/GroupScan)

    Known Limitations :

    • DPI scaling does sometimes not work over RDP sessions, depending on the version of the server, the RDP client and DPI settings on the server.
    • Printing of charts does not work on DPI Settings other than 100%
    • 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.
    • Currently, the database does not allow more than 32767 issued licenses per server. Counts greater than that value will get truncated.
    • Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignore

    Das ist leider nicht so einfach möglich, da eine Maschine mehrere Netzwerkinterfaces und damit Mac Adressen hat. Es gibt extra Logik um auf dem Maschinenobjekt die IP Adresse zu hinterlegen die für die Kommunikation mit dem Firmennetzwerk verwendet wird.

    Um die Mac Adresse dieses interfaces ebenfalls im Maschinenobjekt hinterlegen zu können muss das DB Modell erweitert werden. Ich habe das als Pendenz aufgenommen (#527). Könnte in 1.9.4 realisiert werden.

    Mit einer Custom Query wäre es möglich, die notwendige Logik einzubauen um die Mac Adresse zur aktuellen Netzwerkadresse zu finden.

    Das möchten wir aber nicht in die Standard Query einbauen, da es eine erhebliche Verschlechterung der Performance der Query bedeuten würde.

    Die Query 'Machine Search by MAC Address' gibt eine Liste aller MAC Addressen und Maschinen aus.


    Lieben Gruss

    Erwin

    Verified with Windows 2012 R2 Domain Level and Servers (fully patched as of September 24, 2016).


    To scan servers in the system context, you can set up a scheduled task via GPO.


    Make sure that the GPO affects the desired servers only, and that software metering is not enabled for these scans.


    Metering should only be enabled on scans that run in an ordinary user context.


    If you need software metering or login history on servers, you have to additionally run the scanner in the user context, usually through logon GPO.

    Octoscan2 implements sensible default settings for server scans in system/administrator or regular user context.


    Prepare


    • Make sure that Group "Domain Computers" has read/execute access to the share where you published Octoscan2.exe (\\server\OctoSAM$\bin)
    • Make sure that Group "Domain Computers" has change access to the share where the .scan files are collected (\\server\OctoSAM$\data)


    Test Permissions From a Test Server


    Install PSTools from


    https://technet.microsoft.com/…sysinternals/pstools.aspx


    To start an interactive Console as system User:


    • Login with an Administrator Account
    • start cmd run as Administrator
    • psexec -i -s cmd.exe

    A new command window opens which runs as NT_AUTHORITY\SYSTEM. In this new command window start Octoscan2.exe from your network share with /show /keep Options:



    Verify that the .scan file gets written to the expected location and there are no ERROR messages in the Octoscan2 window.


    Do not continue if these prerequisite tests did not run properly!


    Configure GPO


    In the Group Policy Editor



    Set the desired triggers (once a day is recommended). Set a random delay.





    Save the GPO, allow to replicate or force replication


    On the test server run (as Administrator)


    gpudate /forced


    Verify in local task scheduler that the task has been created



    Interactively test the scheduled task (Context Menu Run ...)

    Hallo Stephan,


    Ein Script welches die Maschinen automatisch löscht gibt es bewusst nicht im Standardumfang des Produkts, da vor dem Löschen manuell kontrolliert werden sollte, ob die Ausgabe der Query Sinn macht. Die Kriterien für die Löschung von Maschinen sind von Kunde zu Kunde zu unterschiedlich.


    Hat man die Query ausgeführt und möchte alle dort ausgelisteten Maschinen nach Prüfung löschen, so kann man dies mittels Kontext Menü (Rechte Maustatse) -> Database -> Delete Visible erreichen. Dazu braucht man natürlich Schreibrechte auf der Datenbank.


    Das Grid kann ad-hoc noch gefiltert werden, wenn man nur nach bestimmten Zusatzkriterien löschen möchte (wie z.B. nur Server oder nur Laptops usw.). Delete Visible selektiert dann nur die noch sichtbaren Maschinen.


    Es gibt auch die Möglichkeit, im Grid eine oder mehrere Zeilen zu markieren und dann mit 'Delete Selected' nur diese Maschinen zu löschen.


    Mit dem Tool OctoUtil können Maschinen gescripted automatisch gelöscht werden.
    Dies kann sinnvoll sein, wenn der Kunde z.B. über einen automatisierten Workflow für das Decomissioning von Systemen verfügt.
    Ist dies der Fall sind wir gerne bei der Integration behilflich.



    Lieben Gruss
    Erwin

    Du meinst 0 (false)? Das Feld OperatingSystemServer kann aufgrund des DB Schema nicht NULL sein. Es kann nur die Werte 1 = WAHR oder 0 = FALSCH einnehmen.


    Im nächsten Build wird für macOS die OperatingSystemFamily auf 'OSX' gesetzt werden.
    In einem späteren Major Release wird die Family wohl mal von OSX nach macOS umbenannt werden müssen.


    Hingegen wird OperatingSystemServer für OSX und macOS immer 0 = FALSCH gesetzt werden. macOS Server / OS X Server wird als installiertes SoftwarePackage abgebildet..


    Lieben Gruss
    Erwin

    Ich habe eine Pendenz für die Zuordnung der macOS 10.* Signaturen zur Family OSX erfasst (#458). Das sollte in einem der nächsten Builds korrigiert sein.


    macOS Server ist, soweit ich das verstanden habe, keine eigene Betriebssystemvariante sondern eine "Applikation" die via App Store auf ein MacOS / OS X Betriebssystem installiert wird.
    Da müssen wir intern noch diskutieren, ob das OperatingSystemServer Flag gesetzt werden soll.


    Paketdefinition für mac:Server habe ich ebenfalls in Auftrag gegeben.


    Danke und Freundliche Grüsse


    Erwin Richard

    OctoSAM 1.9.2 SP1 is available for download in the file base.

    Supported Environments

    (no change from 1.9.2)


    Octoscan2 Scanner Windows Server 2003 SP1, Windows XP SP3 or newer (32 and 64bit)
    OctoSAM Database SQL Server 2012 R2 or newer.
    OctoSAM Server Components .net Framework 4.6.1
    OctoSAM GUI .net Framework 4.6.1. 64bit OS and minimum of 8GB RAM recommended



    New Features


    Database Maintenance / Housekeeping

    • All Database Maintenance and Housekeeping tasks have been moved to the Import Service. The database maintenance dialog has been removed and replaced by the Housekeeping Settings Dialog.
    • Housekeeping now automatically removes old Software Signatures that are no longer used.
    • Housekeeping in the import service supports compression and deletion of log files in a specified folder (see sample configuration file)



    Other Changes

    • SQL Server 2016 SP1 Scan
    • Updates to 3rd Party components
    • Stability Updates



    Update from 1.9.2:

    • No change in the database schema from 1.9.2
    • Stop OctoSAM services on the server
    • Make a backup copy of all configuration files
    • Run the .msi Installer
    • Merge the configuration settings with the new configuration template files. Special attention to the new houskeeping log4net configuration and settings.
    • Set housekeeping preference from the new version of the GUI (Setup -> Databse -> Import Service Housekeeping) before restarting the import service, Otherwise the first housekeeping will use default settings which may not be what you want.
    • Update the software catalog from latest master file
    • Import Queries and Reports from provided .zip file
      If you have custom queries, reports or tasks: Unzip the .zip File from the release and copy your custom files to the appropriate folder. Zip the folder structure again and import the new .zip file into the database.
      Using configuration file Query.Folder setting in Octopus2.exe.config is still supported.
    • Restart OctoSAM services

    Known Limitations :

    • 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.
    • Currently, the database does not allow more than 32767 issued licenses per server. Counts greater than that value will get truncated.
    • Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignored

    OctoSAM 1.9.2 is available for download in the file base.


    Supported Environments
    (no change between 1.9.1 and 1.9.2)


    Octoscan2 Scanner Windows Server 2003 SP1, Windows XP SP3 or newer (32 and 64bit)
    OctoSAM Database SQL Server 2012 R2 or newer.
    OctoSAM Server Components .net Framework 4.6.1
    OctoSAM GUI .net Framework 4.6.1. 64bit OS and minimum of 8GB RAM recommended


    New Features


    Hyper-V Virtualization Scan
    Scan of Hyper-V hosts (Windows Server 2012 and newer) and guests (all supported Windows platforms).


    Virtual Machine Mobility (vCenter and Hyper-V)
    OctoSAM Inventory now keeps track of the virtual machine to host relations. This allows to identify virtual machines that change their hosts frequently and can help to answer license mobility questions.


    Software Publisher
    OctoSAM Inventory now supports and maintains a catalog of software publishers.
    Publishers defined by Octosoft can be assigned to signatures using regular expressions.
    Software package to publisher relations are either set based on the detected signatures or can be specified manually.
    Site specific software publishers can also be defined and assigned to packages.


    Software Publisher Auto Assign
    octosoft.ch/forum/wcf/index.php?attachment/24/


    The software tree can now be grouped by publisher in addition to the default category grouping.


    octosoft.ch/forum/wcf/index.php?attachment/22/


    Normalized software publisher information is available in many queries and reports.


    Junk Signatures
    The master catalog now contains rules to identify junk signatures. These signatures are per default not displayed if unassigned.
    Junk detection rules are per publisher.


    octosoft.ch/forum/wcf/index.php?attachment/23/



    URL Columns in Grids
    Urls in grids do now render as hyperlinks that are directly clickable to open the web page.


    Search Context Menus and Buttons
    Allow direct search via Google with the selected value.


    ImportControl / ImportFolder / ImportStatistics
    ImportControl now keeps track of the import folder where a scan file was imported from. Table ImportStatistics has been removed.


    Service Refactoring
    All services now use a common framework for installation and basic operation. Installation now sets reasonable start type and recovery options automatically.


    Import Service
    The order of import file operations in case of multiple import folders has been optimized. The import service now reads information of all files from all folders before importing the files oldest first.
    New property 'title' (Personal Title) synchronized from Active Directory for User Objects.
    Housekeeping scripts can now be configured to cover many integration and transformation problems where OctoUtil or other external scripts had to be used in the past.
    Service installation now configures reasonable defaults for service recovery


    Anonymizer
    New program name OctopusAnonymizer. Now included in the .msi Server Components, including sample configuration files. This allows for automatic update of the program together with the other OctoSAM server components.
    New option to remove users and machines with non-standard names that may lead to strange results
    Multithreaded scan and update for large tables results in twice the throughput compared with older versions
    The anonymizer can now execute OctoUtil scripts. This allows for example to remove specific objects before or after anonymization.

    XML
    1. <!-- delete machine id 15 before anonymizer -->
    2. <script language="OctoUtil" run="before">
    3. delete machine 15
    4. </script>


    Windows Server 2016 Support
    Windows Server 2016 is supported by the scanner and also as an installation platform for OctoSAM.


    New Windows 10 Variants
    Windows 10 Pro Education and Windows 10 Pro Education N are now detected, Windows 10 LTS Versions are properly detected.


    New SQL Server Variants
    Additional SQL Server variants are detected


    Improved GUI performance
    Improvements from careful tuning of database access code throughout the code.
    Improved drawing performance


    Update Instructions:

    • Make a backup copy of the database
    • Migrate to schema version 1.9.2 from 1.9.1. See release notes of 1.9.1 if you migrate from earlier versions.
    • Deploy the new Version of Octosocan2.exe to your environment
      .scan files are compatible with versions 1.8.11 or newer of the import Service
      Consider new setting ScanProductKeys to disable the product key scan. Default is enabled.
    • Stop OctoSAM services on the server
    • Make a backup copy of all configuration files
    • Run the .msi Installer
    • Merge the configuration settings with the new configuration template files.
      Be especially careful with the assembly binding redirect section of the configuration files. This section must exactly match the settings in the provided sample configuration files.
    • Update the software catalog from latest master file
    • Import Queries and Reports from provided .zip file
      If you have custom queries, reports or tasks: Unzip the .zip File from the release and copy your custom files to the appropriate folder. Zip the folder structure again and import the new .zip file into the database.
      Using configuration file Query.Folder setting in Octopus2.exe.config is still supported.
    • Restart OctoSAM services
    • Update the VMWare vCenter scanner if in use (Support.zip/VMWare). Note the new sample code in scan_vcenter.ps1
    • Update the AD Group scanner if in use (Support.zip/GroupScan). Note the new sample code in scan_groups.ps1

    Known Limitations :

    • 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.
    • Currently, the database does not allow more than 32767 issued licenses per server. Counts greater than that value will get truncated.
    • Group Settings Published Software Packages: Changes to the published Software Packages are immediately written to the database, cancel out of the dialog is ignored

    Das Büro wird üblicherweise im Attribut 'physicalDeliveryOfficeName' abgelegt. Dieses wird bereits synchronisiert.
    (OctoSAM: User.DirectoryPhysicalDeliveryOfficeName bzw. DirectoryMissingUser.PhysicalDeliveryOfficeName.


    Das Attribut physicalDeliveryOfficeName erscheint in manchen MS Produkten als 'Office'. Z.B. Powershell Set-ADUser command.


    Freundliche Grüsse
    Erwin Richard