6 Replies Latest reply: Dec 11, 2013 3:10 AM by Kishorek RSS

SCCM - Failed to establish TCP session

jhodges Community Member
Currently Being Moderated

Hi all,

 

I have configured up OOB management as per the instructions on TechNet and the Intel vPro Expert Center using a GoDaddy certificate for provisioning. I have sucessfully discovered and provisioned a number of HP desktop machines that have AMT 5.2.1.

 

When trying to discover OOB controllers on a HP EliteBook 8440p and EliteBook 2540p I get the following:

 

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:38 AM 2308 (0x0904)
AMT Discovery Worker: Reading Discovery Instruction C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{947750BF-3129-44F6-9A40-D3D3774F9592}.RDC... SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:38 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_IPToResourceID '10.10.60.11', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:38 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::IPv4ToResouceID - Found matched machine SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:DD668E32-3DD2-42B9-93B2-154467EDA7BF', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine HP2730TABLET-10 (HP2730TABLET-10.BGGS.QLD.EDU.AU), ID: 1103 - 10.10.60.98 from Resource GUID:DD668E32-3DD2-42B9-93B2-154467EDA7BF. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 1103 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_IPToResourceID '10.10.61.36', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::IPv4ToResouceID - Found matched machine SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:2edc1fbd-1641-4b39-a164-876efcb0d6e3', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine E-HP5102-17 (E-HP5102-17.BGGS.QLD.EDU.AU), ID: 2290 - 10.10.61.82 from Resource GUID:2edc1fbd-1641-4b39-a164-876efcb0d6e3. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 2290 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_IPToResourceID '10.10.61.39', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::IPv4ToResouceID - Found matched machine SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:2B3E0F1E-A6A6-42C2-96AC-686297047F9A', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine C-HP6710-22 (C-HP6710-22.BGGS.QLD.EDU.AU), ID: 950 - 10.10.61.99 from Resource GUID:2B3E0F1E-A6A6-42C2-96AC-686297047F9A. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 950 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_IPToResourceID '10.10.8.85', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::IPv4ToResouceID - Found matched machine SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_IPToResourceID '10.10.9.38', 'GGS' SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::IPv4ToResouceID - Found matched machine SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Finish reading discovery instruction C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{947750BF-3129-44F6-9A40-D3D3774F9592}.RDC SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: There are 5 tasks in pending list SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Send task  to completion port SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
Auto-worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Send task  to completion port SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
Auto-worker Thread Pool: Work thread 7268 started SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 7268 (0x1C64)
Auto-worker Thread Pool: Current size of the thread pool is 2 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Send task  to completion port SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
Auto-worker Thread Pool: Work thread 11436 started SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 11436 (0x2CAC)
Auto-worker Thread Pool: Work thread 12164 started SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 12164 (0x2F84)
Auto-worker Thread Pool: Current size of the thread pool is 3 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Send task  to completion port SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
Auto-worker Thread Pool: Current size of the thread pool is 4 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Send task  to completion port SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
Auto-worker Thread Pool: Current size of the thread pool is 5 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: 5 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=FREYJA SITE=GGS PID=1860 TID=2308 GMTDATE=Sun Mar 20 23:07:39.476 2011 ISTR0="5" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 2308 (0x0904)
Auto-worker Thread Pool: Work thread 10888 started SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 10888 (0x2A88)
Auto-worker Thread Pool: Work thread 8104 started SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:39 AM 8104 (0x1FA8)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.10.61.39:16992. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:40 AM 7268 (0x1C64)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.10.8.85:16992. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:40 AM 8104 (0x1FA8)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.10.61.36:16992. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:40 AM 10888 (0x2A88)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.10.61.39:16993. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 7268 (0x1C64)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.10.8.85:16993. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 8104 (0x1FA8)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 7268 (0x1C64)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 8104 (0x1FA8)
Auto-worker Thread Pool: Succeed to run the task . Remove it from task list. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 7268 (0x1C64)
Auto-worker Thread Pool: Succeed to run the task . Remove it from task list. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 8104 (0x1FA8)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.10.61.36:16993. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 10888 (0x2A88)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 10888 (0x2A88)
Auto-worker Thread Pool: Succeed to run the task . Remove it from task list. SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:41 AM 10888 (0x2A88)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 3/21/2011 9:07:59 AM 2308 (0x0904)

  • 1. Re: SCCM - Failed to establish TCP session
    jjcopela Community Member
    Currently Being Moderated

    Make sure you are connected via a Wired Lan connection for those laptops when trying to provision.

     

    If it still is not behaving correctly, you can try to "Re-Open" the provisoning ports on those systems by using the "Activator" utility:

    http://software.intel.com/en-us/articles/intel-vpro-technology-activator-utility/

     

    you would run the following command (as administrator) on the mobile client:

    activator.exe /s http://localhost/ /c /h

     

    see if that helps!

    Josh

  • 2. Re: SCCM - Failed to establish TCP session
    jhodges Community Member
    Currently Being Moderated

    Thanks for your reply Josh. I've run the activator utility which seems to run correctly but returns Exit code 7. It says that Sending the hello message has failed.

     

    SCCM logs the same error when trying to discover the controller.

     

    C:\Windows\system32>E:\intel_vpro_technology_activator_utility_3.3\Activator.exe
    /s http://localhost/ /c /h
    Step Into: GetHostFQDN
    host Name is <blah>

    Step Into: CheckAMT
    Connected to HECI driver, version: 6.0.0.1179

    BIOS Version:            68CCU Ver. F.11


    Intel AMT code versions:
            Flash:                   6.0.3
            Netstack:                6.0.3
            AMTApps:                 6.0.3
            AMT:                     6.0.3
            Sku:                     24584
            VendorID:                8086
            Build Number:            1195
            Recovery Version:        6.0.3
            Recovery Build Num:      1195
            Legacy Mode:             False


    Setup and Configuration:
    In process

    Provisioning TLS Mode:
    PKI
    Step Into: CSCSER::PerformSCSRemoteConfiguration
    Step Into: CSCSER::SCSSetAMTIdentity
    AMT version: 6.0 Step Into: StartConfiguration

    BIOS Version:            68CCU Ver. F.11


    Intel AMT code versions:
            Flash:                   6.0.3
            Netstack:                6.0.3
            AMTApps:                 6.0.3
            AMT:                     6.0.3
            Sku:                     24584
            VendorID:                8086
            Build Number:            1195
            Recovery Version:        6.0.3
            Recovery Build Num:      1195
            Legacy Mode:             False


    Setup and Configuration:
    In process

    Intel AMT Mode:
    Non Legacy

    Remote Configuration:
    enabled

    Provisioning TLS Mode:
    PKI

    RNG seed status:
    exists

    PT_STATUS_INVALID_PT_MODE: Command is not permitted in current operating mode.
    Activate Intel AMT configuration:
    failure
    PT_STATUS_INVALID_PT_MODE: Command is not permitted in current operating mode.St
    ep Into: StartConfiguration
    Step out: StartConfiguration error 3
    After StartConfiguration 3
    Step Into: CheckPKIPPSPIDStatus
    Connected to HECI driver, version: 6.0.0.1179
    Step out: CheckPKIPPSPIDStatus error 0
    Connect to localhost: at port: 9971:Unable to connect to server! (localhost)
    Sending the hello message has failed!
    Connect to localhost: at port: 9971:Unable to connect to server! (localhost)
    Sending the hello message has failed!
    Connect to localhost: at port: 9971:Unable to connect to server! (localhost)
    Sending the hello message has failed!
    Exit with code 7

  • 3. Re: SCCM - Failed to establish TCP session
    jjcopela Community Member
    Currently Being Moderated

    The exit code looks fine, we were only using the first portion of the command that opens the ports and we just redirected the hello packets to our local machine (which should fail).

     

    Can you try to ping the IP address of the client from the SCCM server?

    Try to ping -a the FQDN of the machine also.

     

    You want to make sure that the IP / Name resolves and the addresses are what we expect.

     

    thanks!

    Josh

  • 4. Re: SCCM - Failed to establish TCP session
    brunodom Community Member
    Currently Being Moderated

    Hi,

     

         No worries with error, the objective with this utility is open TCP ports for provisioning as you see in this piece of log:

     

    Intel AMT code versions:
            Flash:                   6.0.3
            Netstack:                6.0.3
            AMTApps:                 6.0.3
            AMT:                     6.0.3
            Sku:                     24584
            VendorID:                8086
            Build Number:            1195
            Recovery Version:        6.0.3
            Recovery Build Num:      1195
            Legacy Mode:             False


    Setup and Configuration:
    In process

     

         At this point, you can provision this machine from SCCM console.

     

    Best Regards!

    -- Bruno Domingues

  • 5. Re: SCCM - Failed to establish TCP session
    Kishorek Community Member
    Currently Being Moderated

    Could you please suggest where I can find the Activator.exe program?

  • 6. Re: SCCM - Failed to establish TCP session
    Alan Alderson Community Member
    Currently Being Moderated

    Kishorek,

     

    Activator is no longer available, please use either ACUConfig, or ACUWizard to configure your vPro computers.

     

    Both can be found in the SCS 9 download located here.

    SCS 9 Download

  • 7. Re: SCCM - Failed to establish TCP session
    Kishorek Community Member
    Currently Being Moderated

    Could you please suggest what is the equivalent way to reopening the provisioning ports on the system like the suggestion above with "activator.exe /s http://localhost/ /c /h" when using ACUConfig or ACUWizard?

     

    Thanks

    KishoreK

More Like This

  • Retrieving data ...