Troubleshooting vPro with SCSDiscovery.exe

Version 4

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.x

    When we install our agent on a Vpro capable machine we install with it a Vpro utility called SCSDiscovery.exe.  We use this tool to prod the Vpro chipset and registry to gather the current state your Vpro machine.  This information is then injected into our inventory information that is sent back to the core.

     

    Sometimes if we are not able to provision a Vpro device we are also not able to get the full output from SCSDiscovery.exe to send back to your core with the current Vpro state.  Here are some tips on how to make sure your systems *is* Intel AMT capable and is also capable of running the samples in the SDK.

     

    1.  Run this command from the LDClient directory on the affected machine:

    SCSDiscovery.exe /Output file test.xml SystemDiscovery /NoRegistry

    Two XML files with be generated in the LDClient directory.  One reads Text.xml and the other is named (computer FQDN name).xml

      • test.xml will be a debug file and the (computer FQDN name).xml is your Vpro status file


    2. Open the xml file from running the Discovery tool and look for the following lines:

    • <LastTimeUpdated>2014-06-06 13:55:40</LastTimeUpdated>

    • <IsAMTSupported>true</IsAMTSupported>

    • <BIOSVersion>G5ET94WW (2.54 )</BIOSVersion>

    • <MEIVersion>8.1.0.1263</MEIVersion>

    • <IsMEIEnabled>true</IsMEIEnabled>

    • <MEPlatformSKUs>Corporate; Mobile; </MEPlatformSKUs>

    • <AMTSKU>Full AMT Managebility</AMTSKU>

    • <IsCILASupported>true</IsCILASupported>

    • <IsAMTKVMSupported>true</IsAMTKVMSupported> (True if the KVM redirection interface is supported in the Intel AMT Firmware.)

    • <IsTLSSupported>true</IsTLSSupported>

    • <AMTversion>8.1.20</AMTversion>

    • <AMTConfigurationMode>Enterprise Mode</AMTConfigurationMode> (AMT Versions 6.2 and above automatically provision to Enterprise Mode or Admin Control Mode if using Zero Touch certificates.)

    • <AMTState>Post Provisioning</AMTState> (Current provisioning state)

    • <IsAMTConfigured>true</IsAMTConfigured>

    • <AMTConfigurationState>PKI</AMTConfigurationState>
    • <IsTLSEnabled>true</IsTLSEnabled> (9.5 SP1 and above only support Non-TLS configurations)
    • <IsAMTIDEREnabled> (IDE-Redirection must be enabled in the bios in order to use the KVM feature using the Redirection ports.)
    • <IsAMTKVMEnabled> (True if the Keyboard Video Mouse (KVM) redirection interface is enabled in Intel AMT) (This refers to the listener and if you have enabled Intel AMT but have not yet configured your KVM connections, this will show up as false.)
    • <IsKVMEnabledInBIOS> (True if KVM redirection is enabled in the MEBx of the Intel  AMT device)
    • <IsKVMSupportedInBIOS> (True if the BIOS of the platform supports KVM redirection.  This entry is not always reported correctly - as you can see on my system it indicates false.  But my system is KVM capable.)


    For root-causing issues, it is good to know what AMT version/ FW Version we are working with and if AMT has been configured. (And that the correct FW version is installed.)  It is important to note that the Discovery tool may indicate that your system can do KVM even if you do not have the right graphics card - that's why you check for that first. See this blog for more KVM troubleshooting.