For just doing WSMAN, you can use Microsoft's WinRM or OpenWSMAN (That I never used). The WSMAN samples in the SDK all use Microsoft's WinRM and I also use WinRM in the DTK.
If you are going to code in C#, I recommand you use IAmtRemoteStack.dll, the Intel AMT stack from the DTK. I am making it so it will transparently work with both EOI and WSMAN and switch automaticaly, using WSMAN first if available.
If you have not tried it already, you should start your WSMAN work by trying out the WSMAN browser in Commander and Outpost. Once WinRM is setup and working, just go in Outpost, login and in the file menu you can access the WSMAN browser. If it is grayed out, WinRM is probably not setup right. In Commander, connect to a computer and in the "Management engine" tab, look for "Interaction Type". If it says "WSMAN + EOI" then you can click the button to the right to enter the browser, it's super useful.
Hope this helps,
Ylian (Intel AMT Blog)
I have never actually tried WinRM on XP... I thought it did not work... but like I said... I have never tried it. ;)
whereas it states...
Windows Server2003, WindowsXP/2000, and WindowsNT:WinRM is not available. You can use WMI to obtain data from remote computers, but remote access requires DCOM configuration. For more information, see Connecting to WMI on a Remote Computer.
Thanks for the detailed post. Unfortunately, when you change the port number to 80 or 443, you are communicating with host OS. AMT will communicate on port 16992 (no TLS) or 16993 (TLS). The samples are using the correct ports. We need to understand if Gibbo has configured WinRM correctly, whether using Kerberos or TLS?
For all of the forum users, the samples in the SDK for WS-Man does not support kerberos authentication or TLS encryption. When runnig the samples, you would need to use digest authentication only. We will provide more details on how to configure WinRM later today.