Intel vPro Expert Center Blog

5 Posts tagged with the wsman tag
Click to view Ylian Saint-Hilaire's profile
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
Click to view Ylian Saint-Hilaire's profile
0


Hi all. I wanted to announce the release of the Intel AMT DTK v0.51 on the public web site. As usual, lots of improvements have been made since the last version thanks for much testing and feedback from users. There are a few things that are particularly interesting about this new release of the Intel AMT DTK and lets get right to it:

  • Build-in C# WSMAN stack. As Intel AMT is transitioning to WSMAN calls for remote managibility, adding WSMAN support into the DTK has been increasly important. In the past, the DTK made use of WinRM, a Microsoft component that needed to be installed and configured. With version 0.51 of the DTK, I build my own WSMAN stack in C# right into the DTK stack. As a result, no more dependency on WinRM at all and no more compile problems. Additionaly, the DTK is now much faster at making WSMAN calls since all HTTP requests are now pipelined, and the DTK can connect to AMT computers that have invalid TLS certificates (a warning will be displayed of course). This is big news for anyone interested in WSMAN work. If you build your own managibility solution, I suggest you look at grabbing at least that part of the DTK source code.
  • Intel AMT Flash Tool. This version of the DTK adds a new Intel AMT Flash Tool. It will help users correctly setup a USB flash key so that it can be use to provision Intel AMT computers. As many of you many know, Intel AMT will in the right conditions, read a setup.bin file in a USB flash key when booted and use the information to help setup Intel AMT. The setup.bin file must be at the very start of the USB key and this new tool with help with that. The new tool is based on a similar tool that has already been released on the Intel Pro Center.
  • Intel AMT Reflector tool. Another new tool is a TCP connection reflector. It's a small generic tool that accepts connections and forwards the data back to the source IP address on a target port. It's useful for accessing Intel AMT from your own computer using a reflector on a different computer. I use it for recording some of my demonstration videos, but it can also be used by agents running localy that want to re-configure Intel AMT on itself. For example, detecting an OS name change and updating Intel AMT.

Many more changes and fixes have also been done, for example the terminal now correctly detects Serial-over-LAN disconnection, etc. For a full list, the DTK includes a change log.

Intel AMT DTK v0.51x Audio Blog (.mp3)

Ylian (Intel AMT Blog)

http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1317/ScreenShot67.jpg

http://communities.intel.com/openport/servlet/JiveServlet/downloadImage/1316/ScreenShot64.jpg

0 Comments Permalink Tags: intel, amt, dtk, reflector, wsman, flash, usb, update
Click to view Ylian Saint-Hilaire's profile
0

First off, happy new year to everyone. It's this time of year to reflect on 2007 and it certainly was a great year for the Intel AMT Developer Tool Kit (DTK) and all of Intel vPro Technology and Intel AMT. For one, the DTK has new been public on the Intel web site for about a year now and certainly getting better and better with every version.

In the last few weeks, we have received early prototypes of new upcoming Intel platforms and been working on them. I know many Intel partners read my blog and if you have access to early prototypes, make sure to ask your Intel representative for the latest version of the DTK designed to work with them.

I also worked quite a bit on improving the user interface for many aspects of the DTK. I generally think the UI improvements is absolutely impossible to finish, there is always more to do. For example, I am starting to add support for drag & drop where it makes sense, improving the UI at other places, etc.

For 2008, we will continue to improve the quality of the DTK tools, add a pile more features and keep trying to make things easier to use. I also expect to support more WSMAN, and I would like to get more time to work on Intel AMT Monitor since I think that's the next fun Intel AMT vPro tool in the works.

Ok, I will try to get a new public version of the DTK released soon.

Ylian
(Intel AMT Blog)

0 Comments Permalink Tags: intel, amt, dtk, developer, tool, kit, monitor, wsman
Click to view Ylian Saint-Hilaire's profile
2

Hi everyone. I just released the Intel AMT DTK v0.41 with a few new things ahead of my departure to Taiwan for the Intel Developer Forum . In this new version, I have 3 major new things to report:

  • Intel AMT Defender. I added a new tool called Intel AMT Defender. It's like a community supported version of the Intel System Defense Utility (ISDU) but does it's all new source code. It's a nice new UI, the most impressive thing about it is the new System Defense user interface that is live and very cool.
  • Added Endpoint Access Control (EAC) support. I don't know much about this feature and certainly did not test it, but looking at the Intel AMT API, I added support for it in Commander. If you make it work, let me know.
  • Added WSMAN browser in Intel AMT Outpost. This is very useful to see that WSMAN objects are available on the local Intel AMT interface. As a reminder, what is available locally and remotely is very different.

Intel AMT DTK v0.41 Audio Blog (.mp3)


http://softwareblogs.intel.com/wordpress/wp-content/uploads/2007/10/screen52.jpg

Ylian (Intel AMT Blog)

2 Comments Permalink Tags: intel, amt, dtk, commander, defender, outpost, wsman, eac
Click to view Ylian Saint-Hilaire's profile
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