Knowing that Intel AMT exists in your environment has been possible for several years now.   Knowing exactly what version of Intel AMT, current configuration, network settings of the management engine (i.e. FQDN, IP address, etc), whether or not certain interfaces or features are enabled, and even more – this is very desirable.


A few years ago, Will Ditto at HP wrote a handy utility – iAMT SCAN.  A gap still existed.  Where was the Intel generated, publicly available utility that works even on the latest generation of Intel AMT systems?    In addition, a utility that worked even if the Intel AMT drivers were not loaded or Intel AMT had been disabled within the BIOS.


This is the summary of what SystemDiscovery allows with the introduction of the SCS_Discovery utility.  SCS_Discovery is a standalone component of the new Intel SCS 7.x application.   SystemDiscovery is the common command used by both utilities – SCS_Discovery and SCS 7.x.   It can be used to locally detect and collect over 60 data points of Intel AMT 2.x or higher systems.


Gathering this information locally on the client via XML file or Microsoft Windows registry enables the information to be collected via a custom inventory solution to a central database.   Having a central inventory of all Intel AMT systems provides a tremendous capability in making decisions to help realize the success of the technology.


To utilize this feature:

  • Obtain from ISN's Manageability and Security community.
  • Copy files to a target client (SCSDiscovery.exe, xerces-c_2_7.dll)
  • Run the command “SCSDiscovery SystemDiscovery”
  • View the data collected in the newly created XML file in the same directory (i.e. <fqdn>.xml)
  • View the data collection in the Microsoft Windows Registry
    • 32-bit Windows - HKLM\SOFTWARE\Intel\SCS7.0\System_Discovery
    • 64-bit Windows - HKLM\SOFTWARE\Wow6432Node\Intel\SCS7.0\System_Discovery


For a best case scenario in collecting all data regardless of the Intel AMT version, stopping the Intel AMT Local Management Service is recommended.


The above steps would be modified as follows:

  • Net stop lms
  • SCS_Discovery systemdiscovery
  • Net start lms


The following image excerpts provide a visual preview:

  • Example of data collected in to XML file

          SystemDiscovery XML.png

  • Example of data collected into registry

SystemDiscovery registry.png


Examples how this data could be used:

  • Determining key data points about the platform: whether AMT is supported, whether KVM remote control is support\enabled, exact versions of firmware and drivers, current configuration state, and so forth.
  • Troubleshooting assistance by knowing certain values within the management engine firmware: current IP address of the management engine (wired and wireless), current hostname and domain of both the operating system and management engine, what mode of configuration, and so forth.
  • Custom inventory collection to a central management database.   Once collected centrally, able to search across multiple systems, define custom collections, and so forth.


More information is available in the PDF file included with SCS_Discovery.