WS-Management Translator for Intel AMT

You must be thinking why would AMT need a translator to talk WS-Man? Starting with AMT 3.0, Intel AMT can communicate WS-Man protocol along with the legacy SOAP based communication. WS-Management protocol is now industry standard and Intel jumped on the bandwagon starting last year with AMT 3.0 release.

Many of the ISVs are now developing their applications based on WS-Management protocol. You may ask, there are so many of Intel AMT enabled machines that are below AMT 3.0 out it the market, how will these new management applications manage them? All of the vPro machines with firmware version below AMT 3.0 can only communicate using the legacy SOAP based protocol.

To address the gap between the management of pre-AMT 3.0 machines using the new ISV management applications based on WS-Management, Intel has come up with the WS-Management translator tool. For instructions on how to use the translator tool, refer to the readme file in the installation package.  Using Intel WS-Management translator tool, management consoles can issue WS-Man commands to the translator, the translator will perform the equivalent operation using the legacy SOAP interface.

Along with the installable package, source code is also made available for the ISVs. The source code will allow for tighter integration of the ISV management application with the translator. What does that do for me? With the management application that was developed based on WS-Management protocol,  and integrating Intel WS-Management Translator, now you have the ability to manage all generation of Intel AMT systems seamlessly. Check out this primer describing Intel AMT and WS-Management.

In summary, if you are an ISV developing the management application using WS-Man, and want to manage all generation of Intel AMT devices, Intel WS-Management translator is a very useful tool for you. For any questions on this tool or other Intel AMT related questions, submit your questions in the manageability community.

For more complete information about compiler optimizations, see our Optimization Notice.