Yoga 2 Pro PXE boot?

Looking to PXE boot a Yoga 2 Pro so I can create/restore images with Microsoft WDS.  Since Yoga 2 Pro does not have a built-in Ethernet jack, does anyone know if it's possible to do this with a USB Ethernet adapter?
Would it have to be a Lenovo-branded apdater, or can any brand Belkin, TP-Link, etc) work?

How did you get this to work sir?? I have been trying for a solid week and it never see the Lenovo ethernet dongle as a boot option no matter what I choose in the BIOS. I have the X1 Carbon and it works as you would expect it to. But it NEVER works on the YOGA 2 PRO. CAn anyone help me?? The BIOS clearly has an option to boot the dongle thats made by LENOVO but the dongle never ever shows any lights no matter what port its in or regardless of the settings vchanged in the very small bios. I have wasted atleast 60 hrs + trying to figure out how to boot with it and it doesnt work at all. I had to end up making a bootable discover USB to help it find my wds server. Altough now when ever I attempt to drop an image to it it fails right at FINISHING up and finishes with a "corrupt installation file" error message. To make things more confusing is I can drop this same "Corrupt" image to our X1 carbons without a problem. Can anyone guess why??

Similar Messages

  • Can't PXE boot a Surface Pro 3 after already successfully imaging it

    hey guys. To try to eliminate a lot of the initial question that come up with this issue, I figure I will start with established info.  Our SCCM environment is healthy, and all images, drivers and apps are distributed to all of our DP's. We can image
    PC's and laptops with no issue at all. We use network PXE booting.  Using a 64 bit boot image. Needed drivers are injected into the boot image. Firmware on the Surface was updated.  Using the Surface NIC dongle. THis dongle was only used to image
    this Surface Pro 3 tablet one time. There is no record of the MAC of the dongle in SCCM since I deleted the Surface out, to make it an unknown again.
    So, with a lot of trial and error, I was finally able to get this tab to PXE boot, and then successfully image. Was testing out the new windows 8.1 image I had built.
    Since it ewas successful I wanted to add all of our apps to the TS and test them out in imaging. Well, I can no longer get this thing to PXE boot. It shows trying to Start PXE over IPv4, then just skips to IPv6, then boots up into windows.
    I have delted the secure keys form ther BIOS, then reloaded them.  I have tried hte full shut down method (Holding Volume Up and Power for 15 seconds, then waiting for 10 seconds or longer, then trying to PXE boot. I am getting a valid connection fro
    mthe dongle.
    Nothinhg I try works. Its tries to PXE boot over IPv4, but never gets there.  But I can PXE boot any of our PC's or Laptops,m so its just an issue with this damn Surface Pro 3.
    ANy advice?

    So I finally got our server guy to enable the logging and get that smspxe.log file to be accessible. So here is the info from the log, when I attempt to PXE boot the Surface. I see the last 2 lines where it ignores the request, I just don't know why its
    ignoring it.
    PXE::CNotifyTimer::TimerSignalFunc SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::ProcessTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    Potentially missed device 50:1A:C5:FE:D6:E9 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    Cleared Old Devices: 1 / 1 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CBootImageManager::PurgeOldImages SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    Purging old images: 0 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::Init SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::CancelTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    PXE::CNotifyTimer::RegisterTimeout SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
    [172.028.000.223:67] Recv From:[172.028.011.002:67] Len:347 1ad0230 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.002
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 1=DHCPDiscover
        Type = 57 Max DHCP Message Size: 05b8
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    <============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ProcessMessage: Context:0241DF40  dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    [172.028.000.223:67] Recv From:[172.028.011.003:67] Len:347 159d1f0 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.003
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 1=DHCPDiscover
        Type = 57 Max DHCP Message Size: 05b8
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    <============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
    ProcessMessage: Context:0241DE50  dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443  CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath BootImageID="10000087" Mandatory="0"/></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
    3:04:37 PM 7484 (0x1D3C)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    ============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    DHCP message:
     Operation: BootReply (2)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 0
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 172.028.000.223
     Relay Agent IP Address: 172.028.011.002
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 2=DHCPOffer
        Type = 54 Server idenitifier: 172.028.000.223
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    <============ SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
    Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    ::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath="xx
    BootImageID="10000087" Mandatory="0"/></ClientIDReply>
     SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
    3:04:37 PM 7480 (0x1D38)
    50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    ============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    DHCP message:
     Operation: BootReply (2)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 0
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 172.028.000.223
     Relay Agent IP Address: 172.028.011.003
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 2=DHCPOffer
        Type = 54 Server idenitifier: 172.028.000.223
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    <============ SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
    [172.028.000.223:67] Recv From:[172.028.011.003:67] Len:359 1acbeb0 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    [172.028.000.223:67] Recv From:[172.028.011.002:67] Len:359 15a41f0 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    ============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    ============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.003
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 3=DHCPRequest
        Type = 54 Server idenitifier: 172.028.000.015
        Type = 50 Requested IP: 172.028.011.052
        Type = 57 Max DHCP Message Size: ff00
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    DHCP message:
     Operation: BootRequest (1)
     Hardware Address type: 1
     Hardware Address Length: 6
     Hop Count: 1
     Transaction ID: 24038353
     Seconds Since Boot: 0
     Client IP Address: 000.000.000.000
     Your IP Address: 000.000.000.000
     Server IP Address: 000.000.000.000
     Relay Agent IP Address: 172.028.011.002
     Hardware Address: 50:1a:c5:fe:d6:e9:
     Magic Cookie: 63538263
     Options:
        Type = 53 DHCP Message Type: 3=DHCPRequest
        Type = 54 Server idenitifier: 172.028.000.015
        Type = 50 Requested IP: 172.028.011.052
        Type = 57 Max DHCP Message Size: ff00
        Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
        Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
        Type = 94 UNDI: 010310
        Type = 93 Client system Arch: 0007
        Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    <============ SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    <============ SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
    Ignoring req from [172.028.011.003:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
    Ignoring req from [172.028.011.002:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)

  • Yoga 13 - Compatible USB to ethernet devices for PXE booting

    Hi there, 
    I've recently been looking for a means to pxe boot the lenovo yoga 13 to enable me to then image it. After reading that pxe booting is possible I went out and bought a StarTech usb to ethernet adaptor (USB21000S2) but have had no luck so far.. In other postsI've read that pxe booting is only supported if using the official lenovo usb to ethernet adaptor. We're using FOG as our imaging solution (if thats of any use)
    Please can someone confirm if only the official adaptor is supported.
    Regards
    Simon

    Were you able to find any?  I am also very interested in finding one.  I just ordered one of these the lenovo 0A36322 to see if it will work, but it is only 100mb and not sure if it will work or not.

  • Surface Pro 3 PXE Boot Error

    Hi there,
    I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
    Wizard Error:
    A connection to the deployment (my deployment share) could not be made.
    The following network device did not have a driver installed.
    PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
    Retry: Try again to connect to the deployment share.
    Cancel: Give up, cancelling any in-progress task sequence.
    PLEASE HELP!

    I bought a Belkin USB2.0 adapter and connected to my Pro 3 while the Pro 3 ethernet adapter is connected as well. So 2 network cables are needed. I pxed boot using the Pro 3 ethernet adapter and deploy the image using the Belkin2.0 adapter. Error didnt
    come back and deployment was successful. I mean this is a workaround but it works in my environment. The Belkin2.0 drivers are in WinPE and MDT.

  • Lenovo X1 Carbon PXe boot errors with SCCM 2007

    I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1.  I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
    Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
    Now, I have the the following drivers in the boot.wim file:
    x86 -
    1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
    2. PCI bus
    3. Intel ICHR/DO/DH SATA AHCI Controller
    4. Intel USB 3.0 Root Hub
    5. Intel USB 3.0 eXtensible Host Controller
    x64 -
    1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
    2. PCI Bus
    3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
    4. Intel USB 3.0 Root Hub
    5. Intel USB 3.0 eXtensible Host Controller
    I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
    All other hardware works fine. Any suggestions greatly welcomed.
    Cheers - Mark.

    Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
    Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
    W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
    Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac.

  • Ready to install fresh win 8.1 on new Yoga Pro 2

    So, I just got my yoga pro 2 Friday. Can't stand the extra stuff and 7 particians. 
    I've got a usb stick with a copy of win 8.1 on it. I can boot to it and get the windows installer started ( I stopped at the partiican table)
    I got the drivers folder from the D: on the yoga backed up.
    Got my win 8.1 pro product key written down.
    Don't think I will need any of the lenovo apps.
    Nothing else I need, right?  I did actually make a system image of the fresh install on another external drive when I got it, so if i did need to go back, I can.
    The windows installer will take care of all partiicans, correct? I'm new to EUFI boot.  I can see that legacy mode is disabled in the bios now.
    Thanks for any help. Looking forward to a clean install.  Wish I could have gotten this from a MIcrosoft store instead so I don't have to deal with it.
    Solved!
    Go to Solution.

    seems you're already ready.

  • Yoga Pro 2 - Display not recognized in windows (Driver or Hardware issue?)

    Out of warranty by a month!
    Yoga Pro 2 - 256gb, installed new wireless card a month ago. Windows 8.1
    The touchscreen still works while the screen is black.
    System restarted after sleep mode I think.
    The Lenovo logo is displayed, seems to load windows, but when windows loads (I don't see it load so this is an assumption) the screen blanks and the black light is on.
    I can connect an external monintor which will connect after a return from sleep mode(odd). Which then turns the backlight off.
    When on the external monitor the internal display is not even recognized by windows.
    When I boot in safe mode, the internal screen works fine with of course limited capability.
    I have reloaded display drivers from the support site.
    Right now my internal monitor is not recognized by windows and is dark, and I can use an external monitor.
    Anyone have any clues as to what my be going on? Hardware, driver etc???
    What information can I provide?
    Solved!
    Go to Solution.

    This is a pretty weird issue with conflicting observations.
    1) Screen works in Safe Mode but not in regular boot. (So, not hardware issue)
    2) Display works on external monitor in regular mode. (So, not drivers issue)
    Did you install the wireless card yourself? Did you unplug the display cable while installing the card?
    Could you re-open and check that all connections are good?
    Is the Wi-Fi card working well?
    I would also recommend a complete reset of the laptop to eliminate the possibility that this is a corrupt driver. You can use the NOVO button to reset your laptop. Make sure to make a backup on external drive for your personal files.
    Current System - Lenovo Y510P, GT755M SLI, 8GB RAM, 1TB HDD + 24GB SSD
    When your plans fail, your Real Story begins!!

  • OSD to Surface fails to PXE Boot and returns PXEGetPXEData Failed with 0x80004005

    Scenario: When trying to Image Windows 8.1 to a Surface Pro, Surface Pro 2 and Surface Pro 3 I have downloaded the latest Surface Firmware and Drivers (August 18th 2014 I believe), the NIC's are in the x64 PXE Boot Image. I have verified that no DHCP Option
    67 is set, and that SpanningTree PortFast is enabled. All other Images function correctly, Windows 7 Sp1 works. We use the Microsoft USB NIC, and we PXE boot and download the PXE Image fine, then it comes into windows and goes to detect the NIC, at which point
    it fails and reboots.
    The Surface has had Firmware update on it to the latest.
    It appears the NIC just stops working, which makes me think that the latest Driver pack for Surface does not contain the PXE boot versions for their NIC.
    Trying the Docking Station (which utilizes NIC ASIX AX888772) exhibits the same problem.
    The NIC stays active until the OSD Screen comes up, it fails trying to load the Surface NIC though (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which
    make me think this is the case even more so.
    Doing a USB PXE Boot also fails to load the NIC.
    Going to F8 and doing IPCONFIG /RENEW verifies the NIC is not active.
    I see tons of postings on the Surface being a nightmare to image.
    Errors:
    Failed to Download pxe variable file. Code (0x0000001)
    PXEGetPXEData Failed with 0x80004005
    Anybody having any other experiences out there, or have anything else they could think to try?
    David Baur

    (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which make me think this is the case even more so.
    There are no "PXE boot versions" of drivers at all. What you described just indicates that there is no driver in winpe that matches the hardware. WinPe is based on the respective version of the full os so you have to add Win8.x drivers to the boot image.
    The architecture also has to match. Have you added NIC drivers to the boot image at all?
    NIC drivers are never boot critical if I am not mistaken.
    Torsten Meringer | http://www.mssccmfaq.de

  • Driver Added to Boot.wim but won't recognise on PXE boot

    Hi, this is a bit of an odd one. 
    I have taken the boot.wim file from Windows 7 Pro DVD > Sources folder. I have injected the correct network driver (tested within online image using drvload, I get an IP address), committed this to wim and then added into WDS environment:
    Windows Server 2003, WDS not sure what version (how can I find this out)?
    I have DOUBLE checked that the .INF file for this driver I have injected is in fact showing in the C:\windows\system32\driverstore etc by mounting wim again and checking the mount folder.
    When I PXE boot and select this boot image however, I still receive the 'WDSclient, unable to match network driver' error. 
    If I hit shift + F10 and manually load the exact same driver from USB, I can again get an IP address afterwards! So I know for a fact I am injecting the correct driver. It's almost as if the setup.exe process isnt loading the driver even though the file
    is there.
    Any ideas?
    Thanks

    Solved! Well, using a workaround. 
    Installed WDS on one of our Windows 2008 servers so I had the additional options within WDS to add driver packages etc. Added driver this way then exported the image and imported into the original WDS server. Works fine. 
    Can't just switch to using the 2008 server full time currently as I'm on a tight deadline to roll an image out and the network has many vlans, I'd have to change config to allow traffic from our build network VLAN environment to new WDS server etc.

  • Troubleshooting PXE boot issue

    SCCM R2 not able to PXE boot from Surface pro. I am new to environment. How can I tell if PXE broadcasts are making it to device and to sccm ? I recieve the following output in CMTRACE in SMSPXE.log   ..  Am I doing something completely wrong ? 
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16781189" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
    LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
    Mj

    smspxe.log will display the MAC address if the broadcast reached the server. 
    You have to use Wireshark or Netmon if you want to find out if the response reaches the client. 
    Torsten Meringer | http://www.mssccmfaq.de

  • PXE Boot with UEFI. WDS not sending WinPE wim

    I am trying to test PXE booting on devices that only have UEFI and no CSM support.
    We are running Windows Server 2008 R2 in our environment.
    On the DHCP server, we have option 66 and 67 set. If I change option 67 to SMSBoot\x86\wdsnbp.com and boot a traditional BIOS system (non UEFI) the SCCM server responds and gives me the option to hit F12 and PXE boot. This works without issue and can deploy
    images.
    I then change option 67 to SMSBoot\x64\wdsmgfw.efi and use a machine that is pure UEFI (meaning UEFI without any legacy support / CSM). The system appears to successfully download the wdsmgfw.efi and font file via TFTP as shown in the WDS logs. However, it
    then goes to the next sreen where it is trying to contact the WDS server. AFter retrying for a while it will error out with error 0x102 which I believe translates to ERROR_TIMEOUT
    The SMSPXE.log repeats the following:
    Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>8908f9c4-c345-49ba-b137-af7b0b983584</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
    LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="GAS20043" OfferIDTime="7/24/2013 3:12:00 PM" PkgID="GAS00037" PackageVersion="" PackagePath="<a href="http:///SMS_DP_SMSPKG$/GAS00038">http://<IVE
    REMOVED  THIS>/SMS_DP_SMSPKG$/GAS00038" BootImageID="GAS00038" Mandatory="0"/></ClientIDReply>
     SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
    00:50:56:01:00:82, DF6A0C42-F909-B518-7B44-3150B662200B: found optional advertisement GAS20043 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
    Looking for bootImage GAS00038 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
    Any idea what may be going on?

    Hey,
    I am having the following situation:
    DP1 = Windows Server 2008 R2 SP1 (Standalone Primary Site Server SCCM 2012 SP1 CU2)
    DP2 = Windows Server 2012
    UEFI Client: Microsoft Surface Pro (with Microsoft Surface Network Adapter)
    BIOS Client: HyperV Virtual machine with Legacy network adapert
    DP1; DP2 and DHCPServer all in Subnet1.
    (IP Helper is set for DHCPServer for DHCP and for DP1 & DP2 for DHCP and BootP - I checked serveral times if everything is right here)
    UEFI Client and BIOS Client in Subnet2.
    Situation1 -- Using no DHCP Options and both DPs(DP1 and DP2) WDS running:
    UEFI Client - Boots perfectly (contacting Server DP2)
    BIOS Client - Boots perfectly (contacting Server DP2)
    Situaion2 -- Using no DHCP Options and WDS just running on DP1:
    UEFI Client - Does not boot (no error information is provided)
    BIOS Client - Does not boot (no Bootfilename recieved)
    Situation3 -- Using DHCP Options(Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
    UEFI Client - Does not boot (no error information is provided)
    BIOS Client - Boots perfectly (contacting Server DP1)
    Situation4 -- Using DHCP Options(Option 60="PXEClient" Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
    UEFI Client - Boots perfectly (contacting Server DP1)
    BIOS Client - Does not boot (taking hours to recieve dhcp options..)
    My problem is i am having a lot of location with 2008 R2 SP1 server only (this is why situation 1 is not enough for me :-( ).
    Based on this article:
    http://ccmexec.com/2013/05/configmgr-2012-uefi-and-pxe-boot-support/
    x64 UEFI Devices should work with Server 2008 R2 SP1 (not only Server 2012).
    Interesting is I am having ALL files on Server 2008 R2 SP1 like they are on Server 2012 (in SMSBoot\x86 folder, too!)??
    Some more ideas?
    Thank you for help

  • Does Boot Camp Support PXE Booting?

    I have a Mac pro Quad Xeon, 8gb ram, 3 Drives (multiple sizes)
    I want to PXE boot one of the drives to image it with Vista, is this a possible to do this w/ boot camp? If so I cannot figure it out.

    Hi and welcome to Discussions,
    maybe this thread can help you: http://discussions.apple.com/thread.jspa?messageID=7104286
    Regards
    Stefan

  • Trouble with Adobe Reader Touch on Lenovo Yoga Pro 2 in tablet mode. Pdf shows up as blank pages.

    I have a Lenovo Yoga Pro 2 and when I change it to tablet mode and use the Adobe Reader Touch app, my pdf shows up as a blank page. I have installed other pdfs in the past and those show up fine. However, as of three days ago, whatever pdf I install shows up as blank on my screen. Is there a solution to fix this?

    Could you please share your test file?
    You can send the file at [email protected]

  • My macbook pro keeps booting up, then after a few seconds, goes back to the sign in page. This happened after I was doing software updates and my computer restarted in the middle of an update. Help! Thanks.

    My macbook pro keeps booting up, then after a few seconds, goes back to the sign in page. This happened after I was doing software updates and my computer restarted in the middle of an update. Help! Thanks.

    Start up in Safe Mode.
    http://support.apple.com/kb/ph14204
    Repair Disk    Section: "Try Disk Utility"
    http://support.apple.com/en-us/HT203176

  • What type of ssd does yoga pro 3 have?

    Is it MLC or TLC? I heard people say yoga pro 3 uses sumsung SSD, and sumsung like using TLC which i dont prefer.

    Samsung or LITE-ON, per the Hardware Maintenance Manual:
    http://download.lenovo.com/consumer/mobiles_pub/lenovo_yoga_3_pro_1370_hmm.pdf
    I don't work for Lenovo. I'm a crazy volunteer!

Maybe you are looking for

  • Xcode won't allow me to download again...

    I have multiple Mac systems for which I want to install the Xcode software.   I came in to my office and tried to install it from the App Store, only to find it says it's "installed" and won't allow me to reinstall it.    Seems like that's an oversig

  • Isight not getting detected

    I have a standalone isight and I use an IMAC G5.Its funny that my isight is not getting detected by my imac at all!! I have tried changing the firewire ports, but I just dont understand!! I hadnt been using for about a couple of months, I come back a

  • How to configure DTR,CBS and CMS?

    hi all,        I am working with SneakPreview (EP7.0).Is it possbile to configure DTR,CBS and CMS on sneskpreview ? Can any one tell me the procedure to configure ? Thanks&Regards Suresh

  • Cover Flow Won't Work!!

    After updating to the new version 7 iTunes, I am not able to use the cover flow function on one of my two computers. The Mesage "iTunes is unable to browse album covers on this computer" comes up. My computer meets all the requirements for processing

  • Reg table VBKD

    Hi, I want to know on what basis entries are made in the table VBKD. Even if a sales order has multiple line items, it is not having the data for those sale order and line items. This is not the case with all the sale orders, but only some sale order