In regarding the rejected hello packet...
If the SCCM SP1 client agent is installed, SCCM expects you to provision the vPro client through agent (which is why the hello packet is ignored). Please reference the SCCM SP1 In-band vPro Client provisioning through the SCCM SP1 Client Agent blog on how to provision via the SCCM SP1 Client Agent.
Matt Royer
The WS-MAN Translator is required for proper provisoning, configuration, and management of a vPro Client less than firmware version 3.2.1. It needs to be installed on the same server as your out of band service point listening on port 443. You need to ensure that the ws-man translator working properly and configured correctly in SCCM for any management or configuration or firmware less than 3.2.1.
Matt Royer
Hi Matt,
i finished to install (again) the WS-MAN (bete version) and the error regarding the Registry key seems to be solved BUT
in the same log i'm getting an error : HTTP digest authentication failed with status = 401
any idea?
Kobi
Hi Matt,
another error in the log file just before the error 401
CAMTDiscoveryWSMan::DoDetectAMTVersion: recv failed: 10054
and i can't open the https://SCCM.MYDOMAIN/wstrans i'm getting that "internet explorer cannot display the web page" error
when i'm using telnet to the same server with port 443 it seems to answer.
i followed all the instruction in the PDF file for WS-MAN installation.
I'm assuming that SCCM.MYDOMAIN is the FQDN of your server? if not, you need to use the actual FQDN of the server you installed the Intel WS-MAN Translator on (which should also be the server that your SCCM OOB Service Point is installed on). For example in my test environment, my SCCM server is installed on server sccmsp1.vprodemo.com; so when I connect up to the Intel WS-MAN Translator web site, I use https://sccmsp1.vprodemo.com/wstrans.
The other thing I would recommend trying is turning on logging within the WS-MAN Translator; check out the following post on how to do that. After turning on logging and restarting the WS-MAN Translator service, can you tell me what the C:\Program Files\Intel Corporation\Intel WS-Management Translator\wstrans.log says?
Matt Royer
Hi,
this is the error from wstrans.log after truning the logging on (verbose)
*********************************
Starting Translator.
listening for http://+:443/wstrans/.
Failed to listen on prefix 'http://+:443/wstrans/' because it conflicts with an existing registration on the machine.
Starting Translator.
listening for http://+:5001/wstrans/.
Listener Stopped
Starting Translator.
listening for http://+:443/wstrans/.
Failed to listen on prefix 'http://+:443/wstrans/' because it conflicts with an existing registration on the machine.
*********************************
any ideas ?
kobile,
Do you have any other web based services running on that server that you have the translator installed on? From the log, it appears that something has the 443 port under is exclusive control.
Matt Royer
Hi,
I think there are two things that cause this problem :
1. SCCM support for internet based computer management (IBCM) requires SSL certificate and IIS installed, this is why port 433 is in use.
(this is the installation type i'm using)
2. WINRM (Microsoft WS-MAN) also need port 443 to work with AMT computers.
is there a way to work with Intel WS-MAN using different port (the configurator is allowing this change but with no luck) ?
Dell released a new Bios update today A10. (06-19-2008) This updates your AMT FW to 3.2.1. WOW
Hi,
thanks for the reply, i updated my Dell machine to A10 and fixed my SCCM env. so finaly it works witout the Intel WS-MAN,
BUT
1. Power Control work fine (Turn on, off,restart)
2. I can't access https:
mypc.mydomain:16993 from sccm server , i'm getting the log on page and after entring USER/PASS no luck, i tried local admin pass, MEBx pass etc)
3. when i open the OOBC , i cant connet to the machine.
The symptoms you are describing are transitionally consistent with Kerberos authentication issues. Can you double check that an object for the vPro Client was created in the AD OU you specified in the AMT settings? The object should be there and in a good healthy state. If it is not there or in unhealthy state, verify that the SCCM Primary Site Servers has been granted full control permissions on the out of band management OU. SCCM SP1 Help File Article: "How to Prepare Active Directory Domain Services for Out of Band Management".
--Matt Royer
We have a environment which is simmilar to yours. SCCM SP1 with Dell Clients. Our Desktop Clients are Dell Optiplex 755 with Firmware A10 (AMT 3.2.1). These Clients I can manage without any problems. Our Laptops are Dell D630c Firmware A04 (AMT 2.6.3). For those Clients I need the Intel WS Translator. I have the same problem as kobile described earlyer. Port 443 is already in use by SCCM and WS Trans Service won't start.
Is there any solution?
What is running that is using port 443? Unfortantly, SCCM looks for the WS-MAN Translator on the same server as the Out of Band Service point on Port 443. So we need to determine what has that port exclusively used.
--Matt Royer
Looks like one of the SCCM Components uses 443. I startet wtranscfg.exe again and configured the listening port from 443 to 5100. At the end of the configuration there was a error : An attemp was made to load a program with an incorrect format.(Exception from HRESULT: 0x8007000B). After pressing OK the message Restart Translator Service appears and I was able finish setup (SCCM Server is running W2k8 x64).
Now I've got the following error
Using translator for version *.
session params : https://S-30105.testdom.local/wstrans/dsc/eoi20/w-900047.testdom.local/wsman , 41001
ERROR: Invoke(get) failed: 80020009argNum = 0
Description: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
Error: Failed to get AMT_SetupAndConfigurationService instance
I believe the "ERROR: Invoke(get) failed: 80020009argNum = 0" error is in direct relation to SCCM trying to communicate with the Translator on port 443 (but the Translator is listening on port 5100). There currently is no interface to change where SCCM looks for the translator; it is expecting it on same server as the SCCM OOB Service Point and listening on port 443.
Which sccm component is using port 443?
--Matt Royer