Announcing a brand new Intel® AMT SDK!

By Gael Holmes (Intel) (55 posts) on July 17, 2007 at 9:46 am

I'm sure it is what we all have been waiting for on the Manageability Community Developer's web site: an updated Intel® AMT SDK supporting the new AMT releases 2.2, 2.6 and 3.0 (What happened to AMT 2.5? It is now AMT 2.6!) I will use this post to describe what has changed from AMT 2.1. 

AMT 2.2: (Desktops - Intel® Core™ 2 Processor with vPro™ Technology) This AMT release is a refresh of the Current AMT 2.1 platform - developers will need to keep an eye out for updated firmware from their OEMs who are supporting this new AMT release.

AMT 2.5/2.6: (Mobile - Intel® Centrino® with vPro™ Technology) This AMT release requires new hardware - developers will need to keep an eye out for this new product becoming available from their OEMs.

AMT 3.0 (Desktops - Intel® Core™ 2 Processor with vPro™ Technology) This AMT release requires new hardware - developers will need to keep an eye out for this new product becoming available from their OEMs.

Here are the features that the new AMT Releases support:

The new Intel® AMT 3.0 SDK includes the following new features and changes from the Intel® AMT release 2.1 SDK

  1. The Emulator has been removed from the SDK.
  2. Except for the Configuration samples, all the Windows software components were updated to Microsoft Visual Studio* 2005. The Storage library is also provided in Microsoft Visual Studio .NET 2003 project format.
  3. The pre-compiled debug versions of the Storage and the StatusStrings libraries were removed (only "release" builds are included). In case debug versions of these libraries are required, then they can be compiled from the libraries' sources.
  4. A new WSDL file format, using schema files (.XSD files) for common definitions.
  5. New WSDL files were added for Wireless Configuration and Endpoint Access Control.
  6. For the C++ samples, this SDK contains gSOAP generated code files for all WSDLs (and the script to create them). These gSOAP files are now created to use a dedicated namespace for each WSDL.
  7. Several SOAP commands in existing WSDL files are deprecated (though still supported.) The samples in this SDK release do not use deprecated SOAP functions, but the newer API that replaces them.
  8. All samples were updated to support new Intel® AMT 2.6 and 3.0 features. Refer to the versions.txt file for a list of features available in various Intel® AMT release versions. WS-Management MOF files and sample C# classes deriving from them.
  9. The Windows redirection samples can use PuTTY* instead of the Windows Telnet client as a terminal emulator for SOL sessions.
  10. New samples were added for the following features:
    1. Wireless Configuration
    2. Discovery
    3. NAC posture verifier
    4. WS-Management
    5. Remote Configuration local agent
    6. EventLogReader realm

For a complete description of all versions of Intel® AMT along with their evolutionary progressions to the current AMT release, see the Versions.txt file. To view a list of all known issues with this SDK, see the Readme.txt file. 

Categories: Manageability

Comments (16) Comments RSS Feed

By Intel® Software Network Blogs » Blog Archive » July Status Report - Manageability Community on July 18th, 2007 at 2:02 pm
[...] and 3.0). Almost all of the content on the community got refreshed because of this release. Read Gael's Blog post on AMT-SDK to learn about the capabilities supported in each [...]

By Intel® Software Network Blogs on July 18th, 2007 at 8:55 pm
links from Technoratiwith all the additional features for Centrino Pro and Weybridge. This release includes the AMT releases (2.2, 2.5, 2.6 and 3.0). Almost all of the content on the community got refreshed because of this release. ReadGael's Blog post on AMT-SDKto learn about the capabilities supported in each release. Intel AMT DTK Version 33 with the updated documentation was made available for download on the manageability community. Read Ylian's blog post

By Brad Hards on July 20th, 2007 at 6:46 pm
I'm interested in the rationale for not supporting the emulator any more.

I do a bit of open-source development, and I'd like to extend remote management clients (in my case, KDE's Remote Desktop Connection) to be able to talk to the "network serial port" connection.

I've looked at getting new hardware to do this, but it is a reasonable size commitment for a volunteer to buy a machine using technology that isn't mature (e.g. a Dell 745c, which looks to be AMT 2.1) or where it is hard to tell what version of AMT I'll be getting, if any (e.g. a HP dc7700).

An emulator (especially a virtual machine I could use under VMware or Xen) would make my life a lot easier.

Clearly the emulator was out-of-date, but I think there is a place for it in an SDK.

By Gael Holmes on July 23rd, 2007 at 10:37 am
Hi Brad and Thanks for your comment.

While you bring up very good points regarding the emulator, it's purpose in life began mostly to provide a means to get started on writing manageability consoles before actual hardware existed. Maintaining it and keeping it current and then also providing support for it is not something that would really be cost effective. And given that it was so out of date, I'm not sure I would want to base my software on the emulator due to it's being out of date and not-so-perfect itself. Also many folks felt that it was more important at this point to concentrate efforts on the real thing. I do agree that it would be great to have a Virtual AMT machine.

By Santhosh on August 3rd, 2007 at 1:09 am
Hi,
Can somebody help me understand these features a little bit in more detail?? (Basically the benefits of these features in AMT 3.0)
WS-Management interface, System Defense Heuristics, VLAN settings for Intel AMT network interfaces

By Louis Duran on August 29th, 2007 at 10:37 am
A link to where I can download the AMT SDK would have been really helpful in this posting.

By Ajay Mungara on August 30th, 2007 at 7:42 am
@Louis

You can download AMT SDK from http://www.intel.com/software/amt-sdk

By Intel® Software Network Blogs » Blog Archive » Update for Intel AMT SDK 3.0 on September 13th, 2007 at 8:20 am
[...] you are currently using Intel AMT SDK 3.0 to develop applications for Intel CentrinoPro Processor Technology or Intel vPro Processor [...]

By Intel® Software Network Blogs » Blog Archive » Are you ready for SCS 3.2? on September 17th, 2007 at 9:05 am
[...] and the next generation Intel vPro Processor Technology. Lot of features have been added to these platforms and we have recently updated the SDK to develop applications around these [...]

By Aaron Tersteeg (Intel) on October 1st, 2007 at 11:38 am
Automatically translated text:
انا باسم ممكن رجل كبير انا بحب لززب كبير
Anna possible behalf of a large man, I loved the large Zzb...

I wonder what that mean?

By garfield on October 17th, 2007 at 8:58 pm
We need study AMT solution

By Ajay Mungara (Intel) on October 18th, 2007 at 7:55 am
Garfield,
Can you be more specific when you say a study solution? are you saying that you would like us not to release the product so often or what. We are always open to feedback .. thanks.

By Rajat Banerjee on November 27th, 2007 at 7:52 am
Since the emulator has been deprecated, is there any way to generate the WS-MAN packets which the AMT v3 chips will send to management consoles?

In the SDK I see plenty of examples of the MC's sending WS-Man packets to the AMT hosts, but need the reversed functionality. Any help would be much appreciated!

By Akshay Dua on December 3rd, 2007 at 12:33 am
Is there a way I can still get the emulator? I can't seem to find older versions of the SDK anymore.

By Alexander Wuerstlein on April 2nd, 2008 at 1:05 am
The documentation for the SDK is incorrect, the "GNU C compiler" is frequently mentioned, yet all the examples and the supplied libraries are only usable with C++. Also the header files use 'extern "C"', while the libraries which they are provided for (libimrsdk.a) clearly require a C++ compiler since they use e.g. C++-Strings.

It would be nice if this was clarified, or even better if a pure C library was supplied. The latter would also help integrating with other languages like Perl or Python and since the libraries interface does not use any specific C++ features this shouldn't be too hard to accomplish. Since C compilers tend to be more compatible than C++-compilers one should also need less different versions of the library for different distributions/compilers.

By Gael Holmes (Intel) on April 2nd, 2008 at 7:24 am
Great feeback, Alexander. These are issues that we need to hear about!


What do you think?

Name (required)

Email (required; will not be displayed on this page)

Your URL (optional)

Comments (required)