PXE-E21 remote boot cancelled for Latitude e5470

Article
2017-07-03

Question

_{Monday, July 3, 2017 10:15 AM}

We are getting PXE-E21 remote boot cancelled for Latitude E5470, its worked for other site & only for this specific site does not worked. We performed PXE OS deployment for other model E5430 & its worked.

This is for Windows 7 OS deployment

Need some assistance here.

All replies (8)

_{Monday, July 3, 2017 11:11 AM}

We are getting PXE-E21 remote boot cancelled for Latitude E5470, its worked for other site & only for this specific site does not worked. We performed PXE OS deployment for other model E5430 & its worked.

This is for Windows 7 OS deployment

Need some assistance here.

Show logs. And check ethernet drivers.

ну я такой прихожу и мур, мур, мур!

_{Monday, July 3, 2017 12:05 PM}

yea, look at smspxe.log on the site server and also verify you have an expected IP address.

Fred Bainbridge | Enterprise Mobility MVP | Systems Consultant, Now Micro | fredbainbridge.com

_{Tuesday, July 4, 2017 6:40 AM}

Hi,

Did you boot from UEFI or Legacy BIOS mode on this model of laptop?

Regards,

Jimmy

Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact <a href="mailto:[email protected]"> [email protected]</a>.

_{Tuesday, July 4, 2017 11:03 AM}

Boot from EUFI.

_{Tuesday, July 4, 2017 11:12 AM}

This is what we are seeing on E5470 side

Checking media presence.....

Media present ....

Start PXE over IPv4

Station IP Address is xx.xxx.xx.xx

PXE-E21 : Remote boot cancelled

_{Tuesday, July 4, 2017 11:16 AM}

xx:xx:xx:xx:xx:xx, 4C4C4544-0051-4410-804E-B1C04F5A4632: device is not in the database. SMSPXE 04.07.2017 09:18:48 2988 (0x0BAC)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 04.07.2017 09:18:48 2988 (0x0BAC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>566beeb0-c8ba-4c0d-9d51-783ea7bba88b</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="P012002D" OfferIDTime="22.05.2017 10:10:00" PkgID="P0100055" PackageVersion="" PackagePath="http://xxxx/SMS_DP_SMSPKG$/P0100005" BootImageID="P0100005" Mandatory="0"/></ClientIDReply>
 SMSPXE 04.07.2017 09:18:49 2988 (0x0BAC)
xx:xx:xx:xx:xx:xx, 4C4C4544-0051-4410-804E-B1C04F5A4632: found optional advertisement P012002D SMSPXE 04.07.2017 09:18:49 2988 (0x0BAC)
Begin validation of Certificate [Thumbprint 7DD30C139C4A3B74A9CD1DAF24FB4F7027ADF28F] issued to 'f98762f2-d3be-4768-a94e-174991788045' SMSPXE 04.07.2017 10:06:15 6588 (0x19BC)
Completed validation of Certificate [Thumbprint 7DD30C139C4A3B74A9CD1DAF24FB4F7027ADF28F] issued to 'f98762f2-d3be-4768-a94e-174991788045' SMSPXE 04.07.2017 10:06:15 6588 (0x19BC)

_{Tuesday, July 4, 2017 11:27 AM}

As far cm goes this looks like it worked.

Fred Bainbridge | Enterprise Mobility MVP | Systems Consultant, Now Micro | fredbainbridge.com

_{Wednesday, July 5, 2017 1:26 AM}

Hi,

So if you switch to boot from Legacy BIOS will this issue still exists?