PXE Booting pc for Image deployment

Hi Folks,
our sccm 2012 system was working fine then all of a sudden has stopped working, when we try to image a pc using F12 we get this error message, can anyone help me out resolving this issue.
I've already uninstalled/installed pxe/wds but still getting this error, I've also create our boot images fresh but still the same.

Is this reproducible? Or is it only happening to a single machine or multiple different machines? If it is on only this machine, do what Paul states. The disk on the workstation is the issue.
-Tony

Similar Messages

PXE boot issues with Windows Deployment Services

I am trying to move from FOG to WDS after running in to serious UEFI issues with FOG.Right now I'm stuck with machines PXE booting to WDS server.I keep getting the message ProxyDHCP service didn't reply to request on port 4011.WDS and DHCP are on different servers. There are plenty of IP addresses available, and they are on the same subnet. I did originally configure DHCP option 60, but deleted that option after troubleshooting. I have configured Windows Firewall to allow inbound and outbound connections on UDP ports 67-69 and 4011 on both DHCP server and WDS server. I have also tried just using IP address in DHCP option 66. As for option 67, I don't even know the right bootfile name to use at this point, figured I'd tackle that if I ever get past this error message.I have tried restarting the WDS service several times, as well as the...
This topic first appeared in the Spiceworks Community

After working with many companies in their Office 365 Change Management and End User Adoption strategies, we’ve found that companies who make it fun have very high success rates. So what can you to make it fun?Host an Office 365 Showcase.We’ve helped companies produceOffice 365 Showcases, which have a lively, trade show flair. Kiosks are set up in a cafeteria, meeting room or other convenient location. Hosting each kiosk is a departmental Office 365 Power User who demonstrates a unique aspect of the software to everyone who stops by.Read more about how to make Office 365 Change Management and End User Adoption Fun

PXE boot support for Xen PV -- OVM 3.1.1

I thought with 3.1.1 PXE boot support would be included for full PV vm install. Has someone achieved this?

No problem ... found my answer here : Is it possible to install PVM without DHCP in local network?

PXE Boot Solution for VDI

How to PXE boot the Zero Client in Horizon View to access the linked clones using TFTP server.
We are planning to use the old desktops as the Zero Clients. We want to boot from the PXE boot to access the non persistence linked clones or persistence disks . Is that possible to access by PXE boot.
Used Product. Horizon View 6.

No problem ... found my answer here : Is it possible to install PVM without DHCP in local network?

PXE boot different from imaging server

I am having problems with my PXE pre-boot imaging. we have 2 servers, 1
runs dhcp, and 1 runs imaging. when I boot a workstation for re-imaging,
the PXE loops continuously stating that the proxy server is 192.168.1.6 when
it is actually 192.168.1.7 (the imaging server.) how to do I get the pxe
workstation to recognize that the proxy server is 192.168.1.7 instead of the
dhcp server.

T wrote:
> I am having problems with my PXE pre-boot imaging. we have 2 servers, 1
> runs dhcp, and 1 runs imaging. when I boot a workstation for re-imaging,
> the PXE loops continuously stating that the proxy server is 192.168.1.6 when
> it is actually 192.168.1.7 (the imaging server.) how to do I get the pxe
> workstation to recognize that the proxy server is 192.168.1.7 instead of the
> dhcp server.
>
>
>
Turn off PXE that is running on the IMaging server.

Apple Training for Image Deployment

Has anyone here attended one of the Apple Training seminars on Mac OS X Deployment v10.4 (listed as MacOS 310 on the training units site)? I'm trying to find out if the training covers multicast ASR.

Thanks. You were right, and it was a great class.

Capturing an image to use for PXE boot

I'm using Windows Deployment Services in conjunction with Windows Deployment Terminal (Windows Server 2008) to capture an image from one of our workstations to use as a PXE boot image for future computers. I've created the capture image and PXE booted
to that image, which brings up the "Image Capture" wizard. After capturing the image, I created an install image in WDS using the same .wim file. After trying to PXE boot, the workstation yet again brings up the "Image Capture" wizard.
I then right clicked the image under Boot Images (in WDS) and selected "Create Discover Boot Image." A loading window pops up, but always ends with an error saying something to the extent of the image doesn't have WDSClient Binaries. Does anyone
know what this is or how to fix this? Or even if I'm going about it the right way? If anyone has any advice, I'd appreciate it.

Hi,
Yes, you can.
Here are the rough steps:
1.
Install and configure the WDS Server.
2.
Add the Windows 7 boot image to WDS.
3.
Create a Capture Boot Image and add it to Boot Image.
4.
Create a reference Windows 7 computer (install Windows 7, Office and other applications as you like)
5.
Sysprep the Windows 7 computer.
6.
PXE boot the reference Windows 7 computer into capture image on the boot screen and then capture the image.
7.
Upload the captured image to WDS server.
8.
PXE boot clients, choose the captured image to install the system.
Please refer to this link
http://social.technet.microsoft.com/Forums/windowsserver/en-US/be3af7db-b71b-4b14-b166-fef83cde0ac6/deploy-windows-7-from-waik-with-some-application-added?forum=winserversetup
I had the similar problem couple of years back
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Policy retreiving for client that is pxe booting

Wanna ask, to which management point server does a client will retrieve its policy prior to executing the TS? Does it based on the ip address boundary range?
Which logfile I can see to reoubleshoot client pxe issue? is it smspxe.log?

Short answer is: it doesn't. But we have to break down what's happening.
Remember when you PXE boot you are actually operating at Layer 2 still, and the WDS services are answering a broadcast. So no MP enters the picture before a TS runs _at_all_, instead it's the Distribution Point (which controls the WDS/PXE services
in 2012) that is connecting to the client and providing the TS.
You can actually see this happening on the SMSPXE.log (I'm going from memory on the log name, sorry if i got it wrong) in the SMS_DP$\sms\logs when the PXE servive gets the mac, matches it against the DB then provides the TS available.
Again we are basically doing this at layer 2, even though the client will eventually get an IP and use said IP to TFTP download said image...
More depth here:
http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx
EDIT: to speculate on your question a bit: so if there are multiple DPs in the same subnet, or there is possibly IPHelper in the picture in some way ... the DP that answers is basically random unless a response delay is set (can be done on the DP in
in the MMC).

Machines cannot PXE boot using SCCM 2012 DP

There are a lot of posts about PXE boot, but I can't find the common thread to tie them all together. My test machines cannot PXE boot.
My lab environment is very simple:
10.10.0.0/24 subnet
10.10.0.10 = W2k8 R2 DC, DHCP, DNS
10.10.0.11 = SCCM2012 (on W2k8R2 with SQL Server 2008 SP3 and CU4)
All machines are Hyper-V virtual machines connecting through the same virtual network.
Setup the PXE service from DP properties. I let SCCM install WDS. WDS in Server Manager does not have a server node, but the WDS service is running. DP PXE tab is configured as follows:
"Enable PXE support for clients" is checked
"Allow this distribution point to resond to incoming PXE requests" is checked
"Enable unknown computer support" is checked
"Require a password when computers use PXE" is not checked
"User device affinity" is set to "Allow user device affinity with automatic approval"
PXE is configured to respond on all network interfaces
The PXE server response delay is 0 seconds
The DHCP server has options configured as follows:
Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Both DP and MP on SCCM server are configured for HTTP.
Both x86 and x64 boot images have been distributed to DP. The media was updated after PXE was enabled on the DP.
Both x86 and x64 boot images have "Deploy this image from the PXE service point" enabled on the Data Source tab of their properties.
I have tried both unknown computer task sequence and a computer import task sequence (old computer association). They all end in abortpxe.com
Complete PXE response is as follows:
=================================================================
PXE Network Boot 03.23.2009
(C) Copyright 2009 Microsoft Corporation, All Rights Reserved
CLIENT MAC ADDR: 00 DD CC BB AA 00 GUID: 532D27E3-A184-4D27-A822-30A8B6F4A39D
CLIENT IP: 10.10.0.106 MASK: 255.255.255.0 DHCP IP: 10.10.0.10
GATEWAY IP: 10.10.0.5
Download WDSNBP...
Architecture: x64
WDSNBP started using DHCP Referral.
Contacting Server: 10.10.0.11 (Gateway: 0.0.0.0)
The detalis below show the information relating to the PXE boot request for
this computer. Please provide these details to your Windows Deployment Services
Administrator so that this request can be approved.
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
===========================================================
From the smspxe.log:
]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:31:39.445+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:31:39.480+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.505+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:31:39.533+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:31:39.553+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:00.963+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.008+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.027+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.084+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: {C9929C4D-735A-4973-8659-4D3D5D5E4F92}]LOG]!><time="16:32:01.108+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:6428">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:01.151+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.174+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:01.209+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="16:32:05.230+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="bootimagemgr.cpp:1736">
<![LOG[Set enterpirse certificate in transport]LOG]!><time="16:32:05.290+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9207">
<![LOG[Set media certificate in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.325+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="16:32:05.366+240" date="05-06-2012" component="SMSPXE" context="" type="1" thread="3600" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
=============================================================================================
I've been hammering this for about 10 hours now (or to be honest, it's been hammering me) and it must be something very simple I'm missing. I have a feeling that I'm doing something I used to do in 2007 and whatever that is, it does not work in
2012.
If I connect using boot media, Task Sequences execute perfectly.
TIA,
Tom

Option 66: 10.10.0.11
Option 67: smsboot\x86\wdsnbp.com
Pending Request ID: 6
Contacting Server: 10.10.0.11
TFTP Download: smsboot\x64\abortpxe.com
PXE Boot aborted. Booting to next device
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777218" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
Those options are fine when using DHCP options. They must be configured right because ConfigMgr does send a reply to the client ("abortpxe"). It basically tells you that ConfigMgr knows the MAC address and/or SMBIOSGUID of the client, but cannot find
a deployment for it.
Just find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there's an deployment available (properties of the client with resourceID 16777218).
Torsten Meringer | http://www.mssccmfaq.de
Your answer really helped me. I was searching for 2 days trying to find a computer in Config Manager. Your suggestion to "Just
find ResourceID 16777218 in the console (you might have to add the ResourceID column) and double check if there" was the trick to finding the computer in Config Manager. Thanks for all of your help
Gregory Campbell System Administrator

Creating new OSD task sequence causes PXE boot to fail

I'm running SCCM 2012 on Server 2008 R2. Currently we have a standard task sequence we use for all of our Windows 7 deployments that is working fine. We use PXE boot to load up WinPE to select the task sequence to load and all is good.
I've made a new task sequence to deploy custom configuration settings to a group of computers. I've duplicated much of the original task sequence, using the same boot media. After i deploy the new TS to the All Unknown Computers collection, PXE boot does
not work anymore.
It downloads WDSNBP, starts by DHCP referral, contacts the server. After that I just get a Pending Request ID: number says contacting server then fails. If i go back to my new TS and delete the deployment, all is good again.
Can i create a new task sequence using an existing reference image? Has anyone seen this type of issue before? I see similar issues online, but it seems to be for people that cannot PXE boot at all. My problem is just that the new task sequence seems to
kill PXE boot when it's deployed.

This is from the log file, looks like it can't find the boot image. I'm using the same boot image for both of the task sequences though.
<![LOG[Set media certificate in transport]LOG]!><time="11:35:45.257+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="11:35:45.257+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="11:35:45.301+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="11:35:45.359+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6204">
<![LOG[Set media certificate in transport]LOG]!><time="11:35:45.419+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="11:35:45.420+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="11:35:45.455+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="11:35:45.508+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1736">
<![LOG[Getting boot action for unknown machine: item key: 2046820353]LOG]!><time="11:35:45.572+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="pxehandler.cpp:226">
<![LOG[Set media certificate in transport]LOG]!><time="11:35:45.637+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:9220">
<![LOG[Set authenticator in transport]LOG]!><time="11:35:45.637+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
<![LOG[Set authenticator in transport]LOG]!><time="11:35:45.678+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:7592">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID>44f40eda-b0b0-44ae-87e1-9b9464046c39</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="COL20062" OfferIDTime="20/02/2014 11:22:00 AM" PkgID="COL00086" PackageVersion="" PackagePath="http://TECH-SVR2.county-lambton.on.ca/SMS_DP_SMSPKG$/COL00045" BootImageID="COL00045" Mandatory="0"/></ClientIDReply>
]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6402">
<![LOG[Client Identity: 9ca0acb3-06b1-4737-9db0-1e4b75336ec9]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="libsmsmessaging.cpp:6428">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindBootImage: COL00045]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1652">
<![LOG[Looking for bootImage COL00045]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1686">
<![LOG[PXE::CBootImageCache::FindImage]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagecache.cpp:657">
<![LOG[MAC=9C:B6:54:A3:53:19 SMBIOS GUID=70DCD781-5008-11E4-8264-8BD5B90C0061 > Could not find an available image BootImageID=COL00045]LOG]!><time="11:35:45.743+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="pxehandler.cpp:2095">
<![LOG[PXE::CBootImageManager::FindMatchingArchitectureBootImage]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1736">
<![LOG[PXE::CBootImageManager::FindBootImage: COL00045]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1652">
<![LOG[Looking for bootImage COL00045]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagemgr.cpp:1686">
<![LOG[PXE::CBootImageCache::FindImage]LOG]!><time="11:36:05.335+300" date="02-20-2014" component="SMSPXE" context="" type="1" thread="4532" file="bootimagecache.cpp:657">

MDT Image Deployment Using Flash Drive

Hi,
In my environment i am using MDT 2010 image deployment process to deploy Windows XP and Windows 7 OS images,
As image deployment is foccussed on multiple remote locations we have planned to move with USB Flash drive (Pen Drive) for image deployment,
The problem occurs here in normal system through diskpart utility i can able to get all the disks including my flash drive but in win pe mode i am unable to get my flash drive listed in diskpart utility.
so the image deployment process hangs on to the microsoft solution accelerator screen i am unable to predict the actual reason but i can predict this can happen because of mass storage driver problems.
I tried the same using USB Hard Disk and succeded with the deployment and i am unable to guess what makes difference between USB Hard disk and USB Flash Drive.
Can you just help me out on this to close the problem ASAP..
So that i can proceed with my roll out activities.
Thanks in advance,
Siva

Hi,
At last the image deployment using flash drive works for me.
I attempted the following steps,
First i converted the flsh drive to bootable flash drive using diskpart utility,This can be done in Windows 7 Operating system only.
navigate to cmd and type Diskpart,and enter the below commands,
List disk
Select Disk no
create partition primary
select partition no
active
format fs=ntfs
Assign
Exit
Upon completition,Insert windows 7 DVD to the system and do the following
Navigate to DVD Drive in my case it is G: and change directory to boot
G:cd boot
G:\Boot>Bootsect.exe /nt60 I: where I: is my flash drive
Then copy the contents to the Usb flash drive and change the first boot device of the target system to local hard disk and deploy the image
while in Win pe mode use disk part utility to check whether your disk got detected.
If everything is ok then it will work.
Thanks for your valuable time.
Thanks and Regards,
Siva
Thanks Siva Aadhi-CIT. MCITP

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

PXE boot fails

All
I have an issue with PXE booting into zenwork imaging. Using zenworks
V4.0.1 when you boot the pc into zenworks maintence mode, the pc downloads
from the server until it get to "Uncompressing and laoding zenworks
imaging, please wait" and then errors with the message "Invalid
compression format (err2) -System halted.
I have tried replacing the z:publiczenworksimaging and the pxe folders
with copies from another server, however I still get the same issue.
Does anyone know which file is uncompressed or needs replacing/restoring?
Thanks
David

On Mon, 13 Aug 2007 08:22:28 GMT, David wrote:
> Yes
> It fails on all pcs - however if you use a boot cd it works ok. It must be
> what the server is sending down as part of the pxe boot process that is
> the issue.
> Thanks
> David
hmm I would check sys:\tftp and try the ir7 update
If you have already compiled drivers or have linux.2 please put them on
http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
Live BootCd and USB Disk from Mike Charles
http://forge.novell.com/modules/xfmod/project/?imagingx
eZie http://forge.novell.com/modules/xfmod/project/?ezie
Marcus Breiden
If you are asked to email me information please remove the - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.didas.de

WDS for custom image deployment via PXE

I've recently spun up a 2012R2 server and I'd like to use it so I can netboot clients to it and install a custom image on the machine, no hassle. I have figured out how to take an image from a Windows 7 install disk and add drivers to it.
However, I'm wondering the best way that I could configure an image to use that has all programs, profiles, updates, and drivers on it for a 'universal' install. Is this possible?
For example, can I have a 32-bit image that has Chrome, FireFox, and some other programs on it, complete with any drivers that might be needed for NIC and WLAN cards, graphics adapters, etc? And then a 64-bit image for the same thing. Ideally, these
would house drivers for any of our machines, so I could PXE boot a 64- or 32-bit desktop or laptop, regardless of the model (They're all one manufacturer) and have them install the image and be configured, ready to go?
I would also like to know how I could create a custom image/ISO from a machine that is already ready-to-go as a template.
Thank you for answers in advance.
If it helps, i'm on a Windows 8.1 x64 machine myself, but the machines I'd like to image are Windows 7 (both x86 and x64).

Yea. In a nut shell:
1. Do the install and create the needless account the setup process forces you to create.
2. On first log in enable the original default Administrator account and give it a password
3. Log in with the default Administrator account.
4. Delete the local account that setup forced you to create
5. Go to Advanced system Settings --> User Profiles, and remove the profile for that account. This is important,...this removes the registry entries for the Profile as well (just deleting the folder structure under "C:\Users" does not,
and problems can result).
6. Build your image model from this point using the original default local Administrator account. This is the only account that Sysprep will leave on the machine when it is run. Note the machine is not a Domain Member when I am at this point.
I only join the machine that I apply the image to when I finally deploy the machine to be used .
7. Run Sysprep on the machine to prepare it for duplication, then shutdown or reboot. When starting up you do not want to allow it to boot into the OS or you will have to rerun Sysprep again. You can use WDS to "capture" an image
after doing a network boot from the Nic. You can also boot the machine using a Windows PE bootdisk and manually capture an image with ImageX (comes with WAIK for Win7). But ImageX is commandline only and annoying,...there is a GUI alternative called
GImageX (google it). Then manually copy the captured image to the WDS Server. Note when you capture an image,..you are only capturing the Boot Partition,...not the entire drive.
The details of all this you can sort out by studying "how to use" WDS and WAIK (Win7). That should put you on the right track.
A source for creating a bootable Windows PE disk is here.
http://winbuilder.net/

Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

Hi
I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
Cheers

Hi Joel,
This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
The related KB:
PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
http://support.microsoft.com/kb/259670
The similar thread:
PXE-E53: No boot filename received
http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
WDSServer (Windows Deployment Server) Fails to Start
http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

PXE Booting pc for Image deployment

Similar Messages

Maybe you are looking for