Unable to discover local machine on version 7?

Unable to discover local machine on version 7?

Imagen de johnnysdev

Is it no longer possible to perform discovery on a machine locally (ie 127.0.0.1) for the version 7 AMT machines? This was a feature that was working well in prior versions v4/v6.

publicaciones de 9 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.
Imagen de Judy Hartley (Intel)

Hi johnnysdev,
I don't think I've ever tried to do this locally. Can you giveme more information, such as the version of your HECI driver, and what tools and/or APIs you are using to perform this action on the older AMT versions?

With AMT 7 there are many ways to discover .. through HECI, through WMI, through RMCP and we have many tools such as SCS discovery. Take a look at this blog: http://communities.intel.com/community/openportit/vproexpert/blog/2011/03/09/improved-local-discovery-of-intel-amtwhich discusses this very question and go here:http://software.intel.com/en-us/articles/download-the-latest-version-of-intel-amt-setup-and-configuration-service-scs/to download the System Discovery Utility. It works on all platforms with or without AMT drivers installed.

If you are still having issues, please post again and I will investigate further.

Cheers,
Judy

Imagen de johnnysdev

I am using the Intel Manageability DTK and AmtDiscovery.cs class to try to discover on the local machine.

Imagen de johnnysdev

Is there any update on this situation?

Using the code from the Intel Manageability DTK, I get the following exception when trying to discover AMT presence locally

System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it on 192.168.0.36:16992

I am able to connect to the web ui through 192.168.0.36:16992 from a different machine, but not on the AMT machine.

Network has been activated on the AMT box with a static IP and Legacy redirect mode has been enabled

Imagen de Judy Hartley (Intel)

Hi Johnnysdev,
I'm wondering if you have tried theSystemDiscovery Utilitytool I mentioned in my previous response? If so, were you still unable to get the information you needed?

Please let me know. Meanwhile we will take another look at what you are doing and see if we can pinpoint the problem.

Cheers,
Judy

Imagen de johnnysdev

The SCS tool is able to discover, but that is not a solution to our problem, as we need to distribute AMT capabilities as part of our software. Is there an option that needs to be enabled in the AMT configuration to allow local discovery? There is definitely an underlying issue with the machine, as both the SDK discovery tool and DTK discovery tool are unable to discover AMT presence locally.

Imagen de Judy Hartley (Intel)

Hi Johnnysdev,
Ok, I see that you want a programmical way to obtain the information. I'm a little concerned that neither one of the discovery methods was able to detect the AMT presence locally. Butsince you were able to talk to that machine remotely, itsounds as if the machine is enabled for AMT.

Could you please run the Discovery Utility and then attach the output to your next post? That may help us in determining the solution.

Thanks,
Judy

Imagen de johnnysdev

Using the SDK discovery tool :

C:UsersintelDesktopdiscovery2>discovery -host 192.168.0.36 -mask 255.255.255.255 -verbose

Scan from: 192.168.0.36 to 192.168.0.36

Checking 192.168.0.36

Discovery Finished Successfully:
Found 0 AMT Devices.
Using the SCS discovery tool :
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>2011-11-16 12:35:17falseWORKGROUPINTEL-PCTo be filled by O.E.M.To be filled by O.E.M.To Be Filled By O.E.M.DesktopTo be filled by O.E.M.4.6.4Microsoft Windows 7 Ultimate 00:03:E1:91:03:37192.168.0.36, fe80::9c79:6bf2:7139:a5bd255.255.255.0, 64intel-PCfalse192.168.0.103000200-0400-0500-0006-000700080009truefalseFull AMT Manageability7.0.3.1184falsetruetruetruetruetruetruefalse
SCS discovery tool's verbose log file:
2011-11-16 12:35:16: Thread:1360(INFO) : ACU Configurator , Category: HandleOutPut Source: SrcActivatorUtils.cpp : HandleOutput Line: 213: Starting log 2011-11-16 12:35:16
2011-11-16 12:35:17: Thread:1360(INFO) : SCSDiscovery, Category: -SystemDiscovery- Source: SrcDiscoveryMain.cpp : wmain Line: 188: intel-PC: Discovering the System information...
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: -Start- Source: SrcDiscoveryMain.cpp : SystemDiscovery Line: 58: ***** Start SystemDiscovery ******
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: -Start- Source: SrcHECIDiscovery.cpp : HeciDiscovery Line: 432: ***** Start HeciDiscovery ******
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: -Start- Source: SrcHECIDiscovery.cpp : CheckAMT Line: 97: ***** Start CheckAMT ******
2011-11-16 12:35:17: Thread:1360(ERROR) : ACU Configurator , Category: -HECI- Source: SrcHECIWin.cpp : HECIWin::Init Line: 142: Intel Management Engine Interface error- Cannot find the Intel Management Engine Interface driver. 
2011-11-16 12:35:17: Thread:1360(ERROR) : ACU Configurator , Category: Error message Source: SrcHECIDiscovery.cpp : CheckAMT Line: 148: The Intel Management Engine Interface driver is not installed or cannot be accessed. (0xc000001f)
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: -END- Source: SrcHECIDiscovery.cpp : CheckAMT Line: 198: ***** END CheckAMT ******
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: AMT Status Source: SrcHECIDiscovery.cpp : HeciDiscovery Line: 475: This system does not have Intel AMT (or it is disabled in the MEBx, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers).(0xc0000063)
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: MEIDiscovery Source: SrcSystemDiscovery.cpp : MachineDataOp::FullDiscovery Line: 175: This system does not have Intel AMT (or it is disabled in the MEBx, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers).(0xc0000063) (MEIDiscovery)
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: RegistryData Source: SrcSystemDiscovery.cpp : MachineDataOp::FullDiscovery Line: 197: 2(2) (RegistryData)
2011-11-16 12:35:17: Thread:1360(DETAIL) : ACU Configurator , Category: GetDNSLookupName Source: SrcSystemDiscovery.cpp : MachineDataOp::FullDiscovery Line: 209: Failed to get the FQDN. (0xc0002823) (GetDNSLookupName)
2011-11-16 12:35:20: Thread:1360(WARN) : SCSDiscovery.exe, Category: System Discovery Source: SrcDiscoveryMain.cpp : SystemDiscovery Line: 69: System Discovery finished with warnings: System Discovery failed to get data from some of the interfaces on this system. . ( Failed to get data from the MEI interface (This system does not have Intel AMT (or it is disabled in the MEBx, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers).). Failed to get data from the OS Registry interface (2). Failed to get data from the GetDNSLookupName interface (Failed to get the FQDN. Failed to get the hostname (A socket operation was attempted to an unreachable network. 0x2743. ). ). ) 
2011-11-16 12:35:20: Thread:1360(DETAIL) : ACU Configurator , Category: -END- Source: SrcDiscoveryMain.cpp : SystemDiscovery Line: 81: ***** END SystemDiscovery ******
2011-11-16 12:35:20: Thread:1360(INFO) : SCSDiscovery, Category: Exit Source: SrcDiscoveryMain.cpp : wmain Line: 250: ***********Exit with code 32 - The requested operation completed, but with warnings. Details: System Discovery finished with warnings: System Discovery failed to get data from some of the interfaces on this system. . ( Failed to get data from the MEI interface (This system does not have Intel AMT (or it is disabled in the MEBx, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers).). Failed to get data from the OS Registry interface (2). Failed to get data from the GetDNSLookupName interface (Failed to get the FQDN. Failed to get the hostname (A socket operation was attempted to an unreachable network. 0x2743. ). ). ) 

Imagen de Judy Hartley (Intel)

Hi johnnysdev,
The issue you have is that your MEI driver (sometimes called HECI driver) is not installed, and MEI is not enabled on the system.

You can see this here:

<?xmlversion="1.0"encoding="UTF-8"standalone="no"?>2011-11-1612:35:17>falseWORKGROUP

(ERROR):ACUConfigurator,Category:ErrormessageSource:Src\HECIDiscovery.cpp:CheckAMTLine:148:TheIntelManagementEngineInterfacedriverisnotinstalledorcannotbeaccessed.(0xc000001f)

To fix this problem, you will need to get or install the MEI driver. It is interesting that it wasn't already installed when you got the system as it generally comes that way. It is possible that you have a CD that came with the system that has the correct driver. Alternatively, you will have to get it from the OEM site or you might be able to get it from Windows Update.

Once you have the right driver installed, then please enable MEI. Doing this should solve your problem.

Cheers,
Judy

Inicie sesión para dejar un comentario.