Posts by Erwin Richard

    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

    Guten Tag Herr Roth


    Generell ist eine solche Erweiterung durch den Kunden nicht vorgesehen. Wir haben bewusst darauf verzichtet, die Standardobjekte kundenspezifisch erweiterbar zu machen.
    Zusätzliche Standardattribute aus dem AD können jedoch durch uns zügig (in der Regel innert Wochen) integriert werden.


    In der Regel wird zuerst ein ReserveFeld (DirectoryExt1....) verwendet und bei der nächsten Release mit DB Schemaänderung ein neues Feld z.B. DirectoryJobTitle eingeführt.


    Alternativ können die Felder Custom1-Custom4 mit kundenspezifischen Inhalten belegt werden. Welche Attribute möchten Sie ausser JobTitle zusätzlich noch ins User Objekt abgleichen?


    Freundliche Grüsse
    Erwin Richard


    PS: Job Title (bzw. title) Attribut wird in Release 1.9.2 realisiert.

    OctoSAM 1.9.1 is available for download in the file base.


    Supported Environments:


    Octoscan2 Scanner Windows Server 2003 SP1, Windows XP SP3 or newer (32 and 64bit). Windows 2000 no longer suppoorted
    OctoSAM Database SQL Server 2012 R2 or newer. SQL Server 2016 is supported. SQL Server 2008 no longer supported
    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:


    Microsoft User Access Logging (UAL) Support
    For server software that supports UAL, detailed client access data is collected in the database and accessible via the GUI and queries.


    GUI Performance Improvements
    Various performance improvements
    Junk Software is now filtered out in software trees, can optionally be displayed by selecting from the filter menu
    Computer Accounts are now filtered out in user trees, can optionally be displayed by selecting from the filter menu


    Machine Hardware & Configuration ad hoc Search
    The machine Hardware & Configuration tab now features an ad hoc search input similar to the tree controls for Machines, Users, Software.


    Chart Image Copy and Printing
    All charts now support copying of the image and printing via context menu and keyboard shortcuts


    Queries
    Many new columns in queries (often hidden, use Column Chooser)


    Reports
    New file format for packaged Telerik Reports (.trdp) is now supported


    Logging/Logfiles
    Improved diagnostics logging messages and Stackify integration


    Group Scan
    2 new group types ADCLIENTSPECIFIC and ADGENERIC support import of groups that are of interest but do not have associated logic in OctoSAM.
    These groups and Members appear in the OctoSAM UI but have no impact on standard queries or licensing logic.Also you cannot configure published software packages for these groups.


    New Scanner Features
    Microsoft Cluster detection
    SQL Server 2016 detection
    Improvements for App-V scanning


    Changes and Enhancements:

    • Updated documentation
    • Updates to used 3rd party components
    • Stability updates

    Default Value Change in Octoscan2:


    Some of the newly scanned information for servers can only be read if the scanner runs with Administrator permissions. The default value for configuration parameter ScanHardwareInfo has been changed to false if on a server OS and the scan is not performed in Administrator security context. Make sure that servers are periodically scanned with Administrator permissions (possibly in addition to scans made in user context which may still make sense for metering or login scans). This makes sure that the information under "Hardware & Configuration" stays consistent over time. If you start the scanner interactively from the Desktop, use "Run as Administrator".


    Update Instructions:

    • Make a backup copy of the database
    • Migrate to schema version 1.9.1 from 1.8.16. See release notes of 1.8.16 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
    • If you had internal builds of 1.8.16 installed or if you are not updating from the latest 1.8.16 release build, it's recommended to:

      • Uninstall the existing OctoSAM Software
      • Check if the uninstall left any .dll files behind and if yes, manually delete these files
    • Run the .msi Installer
    • Merge the configuration settings with the new configuration template files. Note that client (GUI) installations usually do not need any configuration settings
    • 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 is still supported, but discouraged.
    • 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 (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.
    • 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

    If you suspect a problem with your log4net configuration for OctoSAM programs, here's how to debug:


    In the .exe.config XML file, enter the following under <appSettings>

    XML
    1. <appSettings>
    2. <add key="log4net.Internal.Debug" value="true"/>

    To redirect the diagnostic messages, add the follwing under <configuration> (right after </log4net>) while changing the path to a valid folder for the initializeData attribute


    Es werden überall die standard .net Regular Expressions verwendet, ausser in der Scanner Konfiguration (octoscan.config) wo aus Gründen der Performanz nur ein Subset der Möglichkeiten unterstützt wird.


    Eine Möglichkeit Teilstrings auszuschliessen sind sog. negative lookaheads.


    https://msdn.microsoft.com/en-…y/az24scfc(v=vs.110).aspx
    https://msdn.microsoft.com/de-…y/az24scfc(v=vs.110).aspx


    Ansonsten verweise ich auf die umfangreiche Fachliteratur.z.B.


    http://www.amazon.de/Mastering…frey-Friedl/dp/0596528124



    und diverse Webseiten zum Thema. Für intensives Arbeiten mit Regexen in OctoSAM empfiehlt sich das Tool Regex Buddy (www.regexbuddy.com). Dieses kann über eine Schnitttstelle direkt in das OctoSAM GUI eingebunden werden.



    Lieben Gruss
    Erwin

    One of the lesser known features of OctoSAM Inventory ist the full text search within most grids. To access full text search, use the context menu or press Ctrl+F while a grid has the input focus.
    You can also configure the text search control to be always visible by checking Tools -> Options -> GridTextSearch.


    Out of the Box Client Install
    With OctoSAM 1.8.16 we streamlined the installation process, particularly for the client installation. This should make it easier to distribute the OctoSAM GUI client using the original .msi.
    For simple configurations where users connect to one database only, the .msi can now be used right out of the box with no additional configuration. When the user starts the client he is asked to provide the database server and database names. The entered values are then used as defaults for all subsequent connections.


    Database Repository for Queries, Reports and Tasks
    OctoSAM 1.8.16 now provides a repository for configuration, queries and reports in the database itself. This means that you rollout updates to these definitions without having to configure paths to a central fileserver location first. Updates of queries, reports and other configuration items can now be performed without having to roll out a new client version and without having to provide the infrastructure for centralized configuration files.


    Database Configuration for additional Settings
    Most settings that you could traditionally configure in the Octopus2.exe.config application configuration file are now also configurabe in the database ConfigurationInformation table. This allows not only easy central definition of these values but also different values per database which was not possible in earlier versions.


    Quiet Client Installation
    Per default, the .MSI installs only the client. This is a change form prior versions of the software.

    Code
    1. msiexec /i OctoSAM.msi /qn


    Quiet Server Installation
    Install of the server features and the configuration samples can be requested by using the ADDLOCAL variable

    Code
    1. msiexec /i OctoSAM.msi /qn ADDLOCAL=OctoSAM_UI,OctoSAM_Server,OctoSAM_SampleConfig


    Manual configuration of the server configuration files and manual installation of the server services is still reqired, see the Installation manuals.


    Quiet Uninstall

    Code
    1. msiexec /uninstall OctoSAM.msi /qn

    OctoSAM 1.8.16 is available for download in the file base.


    New Features:


    Database Repository for Queries, Reports and Site Tasks
    Queries, Reports and Site Task definitions can now be stored in the OctoSAM database. The Installer does no longer install any of these files on the client. This allows for more flexible configurations, database specific queries and easy updates of these definitions without having to roll out a new client.


    ESX Scanner
    The ESX Scanner has been updated to include site-specific annotations.
    Sample code for logging is provided in scan_vcenter.ps1. Please integrate with your site-specific code.


    Group Scanner
    The Group scanner now supports scanning of groups from other domains
    Sample code for logging is provided in scan_groups.ps1. Please integrate with your site-specific code.


    Mac Scanner
    Octoscan for Mac now reports domain information for Macs joined into an Active Directory domain


    Site Detection on Import
    Earlier versions use site information as reported by the client scanner exclusively. With 1.8.16, machine objects can be matched with the "Sites and Subnets" configuration of Active Directory on import. This allows systems such as ESX hosts or Macs to be matched with their site.


    Virtualization
    Oracle Virtualbox and Parallels virtualization is now detected on Windows scans.


    Annotations and Extension Attributes
    A generic mechanism has been implemented to extend objects with site-specific fields. This is used for ESX scanner objects (Machine, Virtual Machine, Cluster, Datacenter) first.
    Extension Attributes is a mechanism to add site-specifc information via the GUI. Extension Attributes now also use the Annotation infrastructure.
    Annotations are visible in the Fields tab of any object. The query engine can reference Annotations in a generic way.


    VirtualMachine in OctoSAM Inventory GUI
    Virtual Machine Tab now shows all fields of the VirtualMachine object. VM specific annotations are also shown here.


    GUI Performance Improvements
    Various performance improvements - particularly in tree controls with many elements.


    Anonymizer Performance Improvements


    Installer
    See extra post. Customization of client configuration files is no longer needed for simple installations.


    Changes and Enhancements:

    • Updated documentation
    • Updates to used 3rd party components
    • Stability updates

    Update Instructions:

    • Make a backup copy of the database
    • Migrate to schema version 1.8.16 from 1.8.15. See release notes of 1.8.15 if you migrate from earlier versions.
    • 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
      Consider new setting ScanProductKeys to disable the product key scan. Default is enabled.
    • Stop OctoSAM services on the server
    • Run the .msi Installer
    • 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 is still supported, but discouraged.
    • 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 (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.
    • 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.8.15 is available for download in the filebase.


    New Features:


    Master Software Catalog
    The full master software catalog is now stored in the database. Packages are created as needed, if an incoming signature matches a package in the catalog.
    Redesigned signature auto assign engine with optimized usage of available CPU resources.
    A new flag can be set for packages that leave their SWID tag files on the system on uninstall (typical for Adobe products).


    Octoscan2
    Windows 10 detection, added detection of Windows Embedded 7 and 8.1 variants
    Improved Terminal Server information scanning on Citrix servers
    Product key scan for Microsoft operating systems and applications
    Windows OEM BIOS key scanning


    OctoSAM Inventory GUI
    Added tooltips to many grid column headers
    Added Keys tab to machine window to display scanned product keys
    LM Tree now allows filtering for customers with may License Servers
    Performance improvements


    Licensing Server Statistics
    Support for Sentinel RMS


    Central Logging to Stackify and Incomplete .scan File Analysis
    Log4Net appenders for logging to stackify have been added. See sample configuration files.
    Severity levels of some log entries were changed to no longer report an error on expected error conditions.
    The import service now reads incomplete .scan files and tries to analyze the problem. Expected XML problems due to partially written files no longer trigger an error.
    All remaining ERROR level messages in the log files must be analyzed, you can safely trigger an alert on them.
    See sample configuration files on how to enable .scan file analysis logging.


    Changes and Enhancements:

    • Updated documentation
    • Data model cleanup
    • Updates to used 3rd party components
    • Stability updates

    Update Instructions:

    • If not on OctoSAM 1.8.12, migrate to 1.8.12 first and perform a full housekeeping cycle. The data model cleanup in 1.8.14 requires that all housekeeping tasks from 1.8.12 have at least run once on the database before updating. Migrate to schema version 1.8.15 via 1.8.14 (note that 1.8.13 was not released).
    • 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
      Consider new setting ScanProductKeys to disable the product key scan. Default is enabled.
    • Stop OctoSAM services on the server
    • Make a backup copy of the database
    • Run script 'check_and_clean_before_migrate_1814.sql
    • Run database migration script(s) from support.zip. If coming from 1.8.12, run migrate_1812_1814.sql and migrate_1814_1815.sql
    • Run the .msi Installer
      No changes to configuration files are needed if you are upgrading from 1.8.12.
    • Update the software catalog from latest master file.
    • Restart OctoSAM services
    • Update the VMWare vCenter scanner if in use (Support.zip/VMWare)
    • Update the AD Group scanner if in use (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.
    • 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.8.12 is available for download in the filebase.


    New Features:


    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


    Octoscan2
    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


    Update Instructions:

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

    Release Candidate 1 of OctoSAM 1.8.11 is available for download in the filebase.


    Release Notes:


    Machine

    • 2 additional SMBIOS fields in machine Object get populated from WMI, for direct query and selection of machines based on SMBIOS information
    • Machine report now includes first detected monitor manufacturer and serial number information for Windows 8 / 8.1 and later systems


    Master Software Catalog

    • Software Package Signature Auto Assign can now specify if the pattern matches metering Information


    Octoscan2

    • Significant performance improvement of process scanning (Metering) especially on (Citrix/Terminal) servers
    • New command-line option /restore to show the status window of an already running scanner
    • New command-line option /keep to keep the window visible even if the scanner would exit under normal configuration
    • New menu command 'Hide Window'
    • Improved status window messages
    • New local registry settings utility to override global scanner settings on individual machines for debugging
    • Removed deprecated SkipUser and SkipMachine configuration settings
    • Detect Windows 10 pre-release
    • Detect Windows 8.0/8.1 with Media Center


    License Manager Server Observer

    • Support Wolfram Mathematica license server (usage only, detailed user statistics planned for next release)
      Contact us for instructions on how to integrate Wolfram license server


    Updates to used 3rd Party components


    Stability Updates


    Updated Documentation


    Update Instructions

    • Deploy the new Version of Octosocan2.exe to your Environment
      .scan files are compatible with versions 1.8.6-1.8.10 of the import service
    • 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
      Check OctopusImportService.exe.config for spelling error on parameter ArchiveRetentionDays.
      No changes to other configuration files are needed if you are upgrading from 1.8.10. From earlier Versions take the new configuration files from SampleConfigurationFiles and work from there
    • Update the software catalog from latest master file. This is needed in all situations as the 1.8.11 catalog synchronization is different from earlier versions.
    • Restart OctoSAM services

    About octoscan.config File
    On start Octoscan2 reads a configuration file named octoscan.config in the program directory.


    General Syntax
    Configuration parameters can be set by using the follwing syntax:
    ParameterName = value
    Boolean values can be specified as 'true/false' 'yes/no' or '1/0'


    Parameters can be set on conditions:
    if condition
    ParameterName1 = value1
    ParameterName2 = value2
    end


    Comments start with a #


    For a full list of supported parameters and conditions, see the OctoSAM Windows Scan online Documentation.


    Sample Configurations

    Code
    1. #
    2. # basic configuration file example
    3. # write generated .scan file to central shared folder
    4. #
    5. OutputFolder=\\myserver\OctoSAM$\Data
    6. #
    7. # enable metering (Default = false)
    8. #
    9. Metering = true


    Depending on your GPO structure, you may want to turn off metering for server systems:

    Code
    1. #
    2. # meter all systems
    3. #
    4. Metering = true
    5. if server
    6. #except servers
    7. Metering = false
    8. end


    You may choose not to report hardware and configuration when Octoscan2.exe is started in a remote session:

    Code
    1. #
    2. # meter all systems
    3. #
    4. Metering = true
    5. if remotesession
    6. # do not deliver hardware (wmi) scan if the scanner is called from a remote terminal session
    7. ScanHardwareInfo = false
    8. end


    Use regular expressions for pattern matching:

    Code
    1. #
    2. # do not scan users that start with adm- (our administrators)
    3. # pattern matching uses regular expressions
    4. #
    5. if match user adm-.*
    6. Scan = false
    7. end


    Conditions can be nested:

    Code
    1. # do not scan if a user called adm-* logs in on a server via terminal services
    2. if server
    3. if remotesession
    4. if match user adm-.*
    5. Scan = false
    6. end
    7. end
    8. end


    Test Configuration File Syntax
    To test a configuration file you can start octoscan2 with command-line parameters /show /keep.
    You will get notifications about configuration statements that octoscan did not understand.

    Code
    1. Octoscan2 /show /keep


    Test Configuration Logic
    Octoscan2 reports the setting of all configuration parameters in the generated .scan file.
    To test your configuration, run Octodump on the generated .scan file. In section octoscan_config you will see all configuration parameters with their values after the configuration file has been processed. Note that the 2 Parameters DoHardwareScan and DoSoftwareScan cannot be set explicitely, they are evalutated by the configuration parser on various conditions for the current scan.


    OK, you have successfully installed Octoscan2 to a central network share and are running it via GPO in your environment.
    But what if you want to update the scanner software to take advantage of the newest features? Windows does not let you overwrite an .exe file as long as a copy is running somewhere. Also, starting with Windows Server 2003, you can no longer rename an .EXE file while the program is running.


    A clean way is of course to change the GPO to point to new location, but that is sometimes not desirable because you may have many GPO and/or you may not have the permissions to change the GPO.


    Alternative 1: Close open file handles


    A straightforward method is to close open files on the share, and then just replace the .exe. For this, you need to have Administrator rights on the server.
    To my experience, scanners already started will continue to run. If some fail, there is not much damage, since the .scan file gets written right at the start of the scan. Worst case you lose some metering data. Anyway, it's a good idea to do this during off-peak hours.


    Since OctoSAM 1.9.3, there is a script to close open handles to Octoscan2.exe only. The script must be run as Administrator.


    Code
    1. close_octoscan2_handles.cmd


    Alternative 2: Use emacs style update


    The second method is a bit more elaborate. It is inspired by the way the legendary Unix editor emacs does it. This method relies on support built-in to the Octoscan2.exe program. Here's how it works:


    • Copy the new Octoscan2.exe to the central share but name it Octoscan2-1.exe.
    • The GPO will still start Octoscan2.exe but at the start, Octoscan2.exe will detect that there is a newer Octoscan2-1.exe and will replace itself with the newer executable.
    • After a couple of days, there will be no long-running processes started from Octoscan2.exe, which allows you to replace the original Octoscan2.exe.
    • Now, on start Octoscan2.exe will detect, that Octoscan2-1.exe is older or the same date and will just keep on running. After another few days, you will have no running instances of Octoscan2-1.exe on your network and you can safely delete the file.


    Octoscan2 allows up to 3 updates (Octoscan2-1.exe, Octoscan2-2.exe and Octoscan2-3.exe) to be placed in the same share, but it's a good Idea to clean up after update-1 or update-2.


    NB: This method does not work when you start the scanner with psexec on a remote machine. In this case, configure a separate folder with Octoscan2.exe and octoscan.config for psexec invocation.

    These are the recommended and tested settings for simple Installations. Complex sites may have different requirements or standards.
    When you want to start the OctoSAM Inventory scanner from a central share, you have to make sure that:


    The 'Downloaded from the Internet' Flag on Octoscan2.exe is not set



    Depending on how you downloaded OctoSAM software, octoscan2.exe might be marked as 'downloaded from the Internet'. Make sure to clear that flag when you copy Octoscan2.exe to the central network share.


    The Central Share is in the Intranet Zone



    If the central share is not already in the "Local intranet" zone, add the server to the Intranet Zone through Group Policy. In the example, all servers within the lab.octosoft.net domain are in the local intranet zone.

    Note that these GPO settings are NOT applied on servers where Internet Explorer is in 'Enhanced Security Mode'.

    See: https://msdn.microsoft.com/en-…s537181%28v=vs.85%29.aspx


    Also make sure that all parts of the path to Octoscan2.exe are readable. Bypass Traverse Checking is not supported for the start of Octoscan2 due to a bug in the Windows 7 TCP stack.


    Start the Scanner Through GPO



    There are several ways where to configure the scanner start. Recommended is through User Policy -> Administrative Templates -> System -> Logon ->Run these programs at Logon

    Release 1.8.10 centers around usage metering on Terminalserver / Citrix. A new immediate metering mode has been added to the inventory scanner to accurately report software usage in terminal server farms.


    The machine object has been extended with new fields for easier querying of hardware related information.


    All 3rd party components have been updated to current versions


    Release 1.8.9 adds many new features to the active directory interface. Integration in complex AD architectures is easier with many new configuration options for connecting to AD via LDAP or LDIF files. New queries make it easier to find discrepancies between Active Directory and the OctoSAM Repository.


    1.8.9 also rebrands visible product names from Octopus to OctoSAM.


    Both releases add a lot of significant improvements to queries, the user interface and diagnostic messages.

    Features:

    • Hardware and Configuration:

      • Installed Services
      • SQL Server Instance Information
      • WMIMonitorID replaces X_VesaDisplay for Windows 7 and later
      • History of IP Addresses


    • Performance:

      • Loading of filtered Software tree re-engineered


    • Stability Updates / Bugfixes


    Notes:


    Octoscan2.EXE and OctoDump.EXE are no longer delivered with the .msi because of virus false positive alerts. The two executables are available in the Support Files download.


    OctoscanLicenseManagerServerObserverService needs to be uninstalled before update and re-installed afterwards. There was a typo in the executable name.