6 Replies Latest reply: Jul 6, 2009 11:39 AM by Georgi RSS

VPro log file on the Client machine

Currently Being Moderated

HI,

 

I am working on trying to provision a laptop to the SCCM Server and it's just not working. We've gone thorugh a full unprovision, redid the has and all of that, and imported the laptop into the out of band management on the SCCM server. When I look at the amtopmgr.log file on the SCCM I don't see any communication what-so-ever happening between the laptop and the SCCM Server. I do believe that there is a log file on the Client machine that I can view to see what's happening on it's end with the provisioning process. Does anyone know if that's true and if so where can I find the log file.

 

Thanks,

Georgi

  • 1. Re: VPro log file on the Client machine
    dbrunton Community Member
    Currently Being Moderated

    First, make sure you are using a wired connection and not wireless.  Second, you may need to restart the hello packets from the laptop to your SCCM server.  You can use the Intel® vPro Technology Activator Utility to restart the hello packets.  You would run activator with a command line similar to this:

     

    activator.exe /s https://yoursccmserver.company.com /h

     

    Once the activator utility starts sending hello packets to your SCCM server you should see entries in the amtopmgr.log and bare-metal activation should begin.

  • 2. Re: VPro log file on the Client machine
    Currently Being Moderated

    Hi,

     

    Do I run this command from the client machine? So after I do the provisioning of the laptop I run the command to connect back to sccm?

     

    Thanks,

     

    Georgi

  • 3. Re: VPro log file on the Client machine
    dbrunton Community Member
    Currently Being Moderated

    Yes, you run this command from your client machine after you complete the out-of-band import wizard in SCCM.

  • 4. Re: VPro log file on the Client machine
    Currently Being Moderated

    Hi,

     

    I ran the command on the laptop after redoing the out-of-band import on the SCCM server.

     

    Here's the log file. It looks like it's failing in the communication somewhere.

     

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

    BIOS Version:   7UET45WW (1.15 )


    Intel AMT code versions:
    Flash:                   4.0.3
    Netstack:                4.0.3
    AMTApps:                 4.0.3
    AMT:                     4.0.3
    Sku:                     44
    VendorID:                8086
    Build Number:            1124
    Recovery Version:        4.0.3
    Recovery Build Num:      1124
    Legacy Mode:             False


    Setup and Configuration:     
    In process

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

    BIOS Version:   7UET45WW (1.15 )


    Intel AMT code versions:
    Flash:                   4.0.3
    Netstack:                4.0.3
    AMTApps:                 4.0.3
    AMT:                     4.0.3
    Sku:                     44
    VendorID:                8086
    Build Number:            1124
    Recovery Version:        4.0.3
    Recovery Build Num:      1124
    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.Step Into: StartConfiguration
    Step out: StartConfiguration error 3
    After StartConfiguration 3
    Step Into: CheckPKIPPSPIDStatus
    Connected to HECI driver, version: 4.0.1.1074
    Step out: CheckPKIPPSPIDStatus error 0
    Connect to : at port: 9971:Unable to connect to server! ()
    Sending the hello message has failed!
    Connect to : at port: 9971:Unable to connect to server! ()
    Sending the hello message has failed!
    Connect to : at port: 9971:Unable to connect to server! ()
    Sending the hello message has failed!
    Exit with code 7

    Georgi

  • 5. Re: VPro log file on the Client machine
    dbrunton Community Member
    Currently Being Moderated

    Try running the tool as administrator.  You can do this by right-clicking the command prompt icon, and select "Run as Administrator."

  • 6. Re: VPro log file on the Client machine
    Currently Being Moderated

    This is how I ran the tool. I also turned off the firewall on the client to make sure that it wasn't being blocked. maybe there's something blocking communication on the network.

More Like This

  • Retrieving data ...