Was wondering if anybody has got the WS-MAN C# examples working on XP?
I've downloaded the WinRM for XP from the microsoft site, and this seems to work :)
Also the WM-MAN C# sample 'AssertDisplay' now loads and compiles in VS2005.
I'm trying to communicate with an AMT device that has been configured with password security only (using AMT Director). I can access the machine remotely using AMT Director/Commander.
When I run the example asset example passing the following command line:
-host 192.168.1.103 -user username -pass password
I get the following message back:
System.Runtime.InteropServices.COMException (0x80338042): The WS-Management service does not support the specified feature.
Remove the unsupported feature from the request and retry. at WSManAutomation.IWSManSession.Enumerate(Object resourceUri, String filter, String dialect, Int32 flags) at HW_Assets.Class1.EnumFunc(String RESOURCE, IWSManEnumerator& objResultSetEnum) in D:Intel AMTSDK3WindowsIntel AMT WS-Management SDKSamplesAssetDisplayAssetDisplay.cs:line 726 Exception caught.
Anybody got any ideas?
Is it possible you are not using English? In this situation, there are two ways to solve this issue:
- Change OS to an english version OS, and then install english version WinRM.
- Or update the ME firmware to a 3.0.7 version or above.
Please let us know if this helps?
Are you able to run other samples ok and having trouble with just the AssetDisplay sample? Also WinRM requires windows XP with SP2, can you confirm you met these requirements? Do you have access to any other AMT 3.0 machines and can you get the sample working on those machines? Can you also let us know AMT firmware version?
Thanks for responding.. Yes I am using an english version, as I am in England.
I've just checked the version of the firmware on the DELL Optiplex 755, it is 3.0.2. So from the sounds of it, there is no WS-MAN on the machine :(
Also DELL don't seem to have any updates for the MEBX :(
Is there anybody from DELL monitoring this forum ?
I don't have any other machines that have AMT 3 on them, so will have to wait for DELL to issue a MEBX update..
You should be fine with your version of the firmware - my response was only if you were using a non-English version. We are currently thinking your problem my be due to your "security" environment. Can you verify the following?
Are you running with TLS? Kerberos?
You are running with XP SP2, correct?
Note that if you change port numbers to non AMT port numbers (like 443, etc) then you aren't talking to AMT - Windows is what would be responding. We will be posting more instructions later today.
Thanks for all the information..
So by the sounds of it my DELL will support WS-MAN.. :D Now all i have to do is to get it working.
I had already downloaded and installed winrm 1.1 for xp and did manage to configure the winrm as follows:
D:>Winrm get winrm/config/client
NetworkDelayms = 5000
URLPrefix = wsman
AllowUnencrypted = true
Basic = true
Digest = true
Kerberos = true
Negotiate = true
Certificate = true
HTTP = 80
HTTPS = 443
TrustedHosts = 192.168.1.102, 192.168.1.103, 192.168.1.124, 192.168.1.152
The Machine that I'm trying to communicate with has been provisioned without tls.
So I'm a little lost at the moment.
Has anybody else tried this with DELL Optiplex 755?
the only difference is that I have enabled the Basic Authority and the Trusted Hosts.
The reason for this is because the machines don't belong to a domain. So I'm a little stuck at the moment... Any other ideas?
We are looking into the possiblity that this may actually be a bug (specific to your Dell system) - can you send us the information that Sree has asked for? Do you have a different AMT system that you can try it on as well?
First off, if your going to try WSMAN, I suggest you install WinRM on Windows XP, setup WinRM correctly (see Readme.txt in DTK or instructions in SDK). Then go into Intel AMT Commander, connect to the computer and in the "Management Engine" tab, look for "Interaction type". It will show "WSMAN + EOI" if Commander was able to use WinRM, otherwise, it will show "EOI Only". Click the small button next to "WSMAN + EOI" to enter the WSMAN browser built into Commander.
Each time you connect using Commander, it will automaticaly try to use WinRM and WSMAN. If it can't it will automaticaly fall back to SOAP calls only. After Commander starts to work, go back to the SDK samples...
Looking at the samples, I think the Asset sample is the only one that does not use WinRM, it parses XML on it's own. All the other samples use WinRM... well, I should double check this, but I am pretty sure looking at the Asset sample, it was built different than the others. So just watch out, Asset sample any work when others don't.
Also, make sure your system's proxy settings don't interfere with WinRM. Commander is set to ignore any proxy setting you set on your system, but WinRM will use these settings.When using TLS, because WinRM does all the HTTP/WSMAN requests, Commander also can't just connect and ignore the certificate if the AMT's certificate is not correct. Instead of displaying a certificate warning, WinRM will simply fail.
Ok, I hope this helps.
Ylian (Intel AMT Blog)
I am encountering a similar issue to what the author of this message thread experienced. I did use Commander as Ylian suggested and saw "EOI(SOAP) + WS-MAN" in the Management Engine tab indicating that WS-MAN can be used.
Below is what I see when I run the StorageAdministration sample.
Could not load file or assembly 'Interop.WSManAutomation, Version=188.8.131.52, Cultu
re=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot f
ind the file specified.