I Execute LocalAgent sample Failed in the local AMT computer, but when I execute the LocalAgent sample successfully with different app name in remote computer.
The error PT_STATUS_AUTHENTICATION_FAILED was returned when calling ISVS_RegisterApplicationEx2.
Is there anyting wrong i did?
Hi, could you please clarify what you are experiencing?
It sounds like you are getting an error with an SDK sample when run locally, but it works when done remotely. Please specify what exacty you are running and how you are initiating it for both situations.
I run the LocalAgent Sample in SDK4.0 on the computer with AMT device failed and the error is PT_STATUS_AUTHENTICATION_FAILED, but it works when registed remotely to the AMT device. The AMT was comfiged for SmallBusiness Module.
Could you provide the following additional info:
- The full command line you are using to run the LocalAgent sample (include the command and all switches/values)
- The version of AMT on your system
- The system's operating system and version
The Local Agent Presence interface can only be accessed locally and not remotely. So, i am confused here. Could you specify the exact name of the SDK sample you are using? In which folder in SDK?
1.The full command line I am using to run the LocalAgent is: (locate)LocalAgent.exe -c blockname http://localhost:16992/StorageService -user admin -pass password.
2. When I run the full command line: (locate)LocalAgent.exe -c blockname http://AMThost IP:16992/StorageService -user admin -pass password remotely, it return successfully.
3. I use different application name and the same vendor name and ent name when run locally and remotely.
4.The version of AMT on my system is 3.0.2
5.The system's operating system is Windows XP and version is SP2
6.The LocalAgent sample is in the folder: SDKWindowsIntel_AMTSamplesSoapStorageVirusignatureFileLocalAgent, and the SDK version is 4.0
7.The AMT was comfiged for SmallBusiness Module.
This looks like a driver issue. You have to have all the latest AMT drivers installed on your system for running this sample locally. Please visit your OEM site and make sure you have all the latest ones installed.
The StartHere Guide I had pointed to earlier will give you a good idea of what are the drivers needed.
Let us know how it goes.
I have had all the latest AMT drivers installed on my system running for LocalAgent.
I run the ApiTest.exe sample in the SDK folder remotely and all the API return successful, but the ISVS_RegisterApplicationEx2 API return failed when I run iton the computer which has the AMT device locally, the erroris SOAP error,NO. is 25. Is there any setting I need on the system which has the AMT device?
When you run the command locally are you typing "localhost" ? You should use the client IP address or the client host name and not use "localhost".
Also please ensure that the password you are typing in the commandis the correct one for the admin.
I was able to successfully run this call locally after running the setup described above. If you are correctly running the command, then there is probably a configuration problem on you local system. You may want to try testing on another AMT client.
I have try "localhost", "127.0.0.1" and "AMTIP" locally and all failed. And I am sure the password is correct for the admin.
I can successfully run the sample on any computer except the AMT computer. That's very strange.
- Intel 82566DM Network Interface Controller
- Intel Management Engine Interface (aka HECI driver)
- Serial-Over-Lan (SOL) Driver
- IDE-Redirect Controller
- IDE-Redirect CD-ROM and Floppy during Redirection Session in Device Manager
- Intel Active Management Technology LMS Service
- Intel AMT System Status Service
For making sure that these are installed, Starte Here guide gives detailed screen shotsfor where and what to look for each of these drivers. If possible, could you capture these screen shots for your system and them to us?
Are you physically typing in the IP address of your AMT system?I'm pretty sure you have to do this.. Is AMTIP the name of they AMT system? Again, you need to enter the actual IP address of they system you are trying to run it on.
Glad it is working now.
You mention that AMT IP is different than the OS IP; Is your AMT setup for DCHP or did you configure as static? If DHCP, it should be the same as the OS.