Home > Intel Communities > Open Port IT Community > Intel® vPro™ Expert Center > Blog > Tags > soap
Up to Blog Posts in Intel® vPro™ Expert Center

Intel vPro Expert Center Blog

2 Posts tagged with the soap tag
Ylian Saint-Hilaire
0

I am glad you inform everyone that the Intel AMT DTK is back online and once again, my apologies for the interruption. Version v0.52x was released, with just a few fixes over the previously posted v0.51x. It's mostly the same as before, not many new features, but if you have experiences problems in the past, try this version.

 

Probably the area where the DTK is improving most is with general stability and WSMAN. When using Intel AMT 3.0, Intel AMT Commander and Intel AMT Outpost will use WSMAN instead of SOAP. Since all the calls are different, many new bugs showed up. As we get the benefit of more testing and feedback, the code keeps improving. Users can force Commander to use SOAP by going to the "View" - "Advanced properties". The second tab has a check box to remove using WSMAN first. WSMAN will of course still be used if Commander determines that WSMAN is the only available option.

 

Next week I am once again heading to Israel to meet with this Intel AMT firmware development team. Last year I had a pretty shaky flight over, something I had blogged about. Hopefully this year will be better. At Intel, this is going to be the ultimate meeting of everyone related to AMT, so I will get to meet some of the other people that post on the forums, and many of the people that I get the most complicated answers from.

 

Ylian (Intel AMT Blog)

0 Comments Permalink Tags: intel, amt, dtk, commander, release, wsman, soap
Ylian Saint-Hilaire
0

 

With release v0.39 of the Intel AMT Developer Tool Kit (DTK), I started work on adding WS-MAN to Intel AMT Commander. My plan is to have the IAmtRemoteStack.dll be dual mode and support both the older and newer interface at the same time. Ideally, if Intel AMT Commander can use WS-MAN to communicate with Intel AMT, it would not have to use SOAP call at all in the future. Right now, I use only the older interface, or a combination of both. Currently, only the inventory asset and event log are read using WS-MAN.

 

 

Probably the most important feature I needed to get started with WS-MAN was a standard WS-MAN browser to help me understand how everything works. I built one into Intel AMT Commander by including all the WSMAN generated classes from the Intel AMT SDK and performing .NET reflection to display all the data on the UI. I must report that so far, WSMAN is slower than SOAP and I have seen some issued with the interface. I am especially annoyed when SOAP and WSMAN report different data.

 

 

If you plan on downloading the Intel AMT DTK source code and compiling it on Windows XP, or simply using Intel AMT Commander with WSMAN on Windows XP, you will notice that you are missing a COM object for WinRM. You need to download it here from Microsoft. If WinRM is not present on your system, Commander will detect that and simply not use WSMAN.

 

 

On Microsoft Vista or with Microsoft Windows XP with WinRM installed, you still need to setup WinRM correctly to get things to work. I put some instructions in the DTK's readme.txt file. It's the same instructions that are provided with the Intel AMT SDK.

 

 

I have to say that dual porting the stack to use both SOAP and WSMAN is going to be a lot of work. I may do some of it and wait for demand to increase before I complete the work. I have many more features on my plate.

 

 

Speaking of new features, there is a contest going on to collect feedback on the Intel AMT SDK and Intel AMT DTK, nice prices to be had!

 

 

Ylian (Intel AMT Blog)

 

 

0 Comments Permalink Tags: amt, dtk, wsman, commander, soap, winrm

Popular Blog Posts