Hi all, Running SCCM SP2R2 on Parent SErver. I have installed PXE Role to a Windows 2008 Server which is running WDS/DHCP at Satelite office. I have configred the following options: DHCP 60 'PXEClient' (WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes) DHCP 66 : *IP of DHCP/WDS/PXE Server* - THis is all the same server. DHCP 67: pxeboot.com Clients are now getting straight away "PXE-E55 Proxy DHCP Service did not reply to request on port 4011" - when trying to pxeboot and install image. There is no firewall, client and DHCP/WDS/PXE server are all same subnet. Thre are quite a few blogs abgout this but I am yet to find why this is happeneing to me. Some people say to configure 66/67, others say not. - tried both, still doesn't work. - What else should I look for? Does anyone have this successfully work with PXE/WDS/DHCP on same server and can deploy images. My x32/x64 Boot images are successfully deployed to the said DHCP/WDS/DHCP server as are the win7 images. MAny THanks

Actually - could it be that the boot images aren't in the D:\RemoteInstall\SMSImages\SMSPKG\foldername of boot image and are only in D:\SMSPKGD$ ?

Option 67 should be set to: "SMSboot\x86\wdsnbp.com" plus you have to distribute both (x86 and x64) WinPEs to the PXE service point.Torsten Meringer | http://www.mssccmfaq.de

I see, thanks Torsten, let me change Option 67. and re-distribute the 2 boot images again to both location on the PXE/DHCP server.

What is the difference between pxeboot and wdsnbp? (in the smsboot\x86 and x64 folder) What process creates the files within those folders?? - is ti when you deploy boot images to the smspxeimages$ folder ?

OK - All updated - now getting error: pxe-e32 tftp open timeout http://adventuresinosd.blogspot.com/2011/03/troubleshooting-pxe-in-sccm-osd-part-2.html http://blogs.technet.com/b/mcs-ireland-infrastructure/archive/2008/06/18/pxe-boot-problems-with-configuration-manager-2007.aspx don't help.

Do you see that the client is trying to reach the PXE service point in the "BIOS boot screen"? Are there any hints in smspxe.log on the PXE service point (IOW do you see the MAC address listed)?Torsten Meringer | http://www.mssccmfaq.de

The PXE Server sees it (in smspxe.log) <![LOG[[192.168.051.012:4011] Recv From:[192.168.051.078:68] Len:548 19e9d30]LOG]!><time="14:24:54.089+-60" date="05-16-2011" component="smspxe" context="" type="0" thread="2572" file="smspxe.cpp:663"> <![LOG[Executing LookupDevice(009AE0FD-2741-E011-8010-B05922125302, E8:9D:87:B1:7A:1E)]LOG]!><time="14:24:54.136+-60" date="05-16-2011" component="smspxe" context="" type="0" thread="2192" file="database.cpp:394"> <![LOG[CDatabaseProxy :: LookupDevice succeeded: 0 0 8730 1]LOG]!><time="14:24:54.136+-60" date="05-16-2011" component="smspxe" context="" type="0" thread="2192" file="database.cpp:444"> <![LOG[MAC=E8:9D:87:B1:7A:1E SMBIOS GUID=009AE0FD-2741-E011-8010-B05922125302 > Device found in the database. MacCount=1 GuidCount=0]LOG]!><time="14:24:54.136+-60" date="05-16-2011" component="smspxe" context="" type="0" thread="2192" file="pxehandler.cpp:341"> <![LOG[[192.168.051.012:4011] Recv From:[192.168.051.012:9000] Len:274 15b0530]LOG]!><time="14:25:39.477+-60" date="05-16-2011" component="smspxe" context="" type="0" thread="2572" file="smspxe.cpp:663">

I had enabled Multicast - I have now unticked the tab for enabling multicasting in the Distribution point Site Role

I have tried setting the 067 Bootfile name : wdsnbp.com only (taken out the smsboot\x86 bit) The timeout error tells me it can see the bootfile but is not able to downhload it, does this seem logical?

Well, I figured my setup was corrupted somewhere so spent the time re-installing and now works a treat. HEre are the exact stepps I took Pre-install work on Satelite Server: removed all boot images (carried out from Parent Site Server) removed pxe site role (carried out from PArent Site Server) removed wds on Satelite Server (reboot) renamed remoteinstall to remoteinstall_old removed DHCP 60: PXEClient from Server Options on Satelite Server (reboot) Install Work (on DHCP/DC/DNS Server in Satelite Office) Configured Site server IIS / Webdav / BITS (http://technet.microsoft.com/en-us/library/cc431377.aspx) - Optional - This is for multicasting using HTTP and BITS (reboot) Install WDS (reboot) Ran wdsutil /initialize-server /REMINST:"D:\remoteinstall" (or whatever drive has remoteinstall folder) Install PXE Site Role from PArent Server (reboot) Deploy boot image to server (this confirms D:\smspkgd$ is working and smspxeimages$ in remoteinstall is working) - Wait for Status message on PArent server to show successfull delivery Ran WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes DHCP Options set: 066 Boot Server Host Name: *IP of DHCP/WDS/PXE Server* 067 Bootfile Name: SMSboot\x86\wdsnbp.com Reboot Properties of WDS Server - Change PXE Response Tab to 'respond to all requests' At this point I noticed my Parent Server was still showing the PXE_CONTROL_POINT "Control Manager detected PXE service point is not responding to PXE requests. The error is 16389" - So I deleted files in Windows\Temp\Pxeboot directory on the Satelite Server. Restart WDS - Waited 30 mins and got the green light in Site Status Copied my packages and images to the satelite server, left it over night and this morning pressed F12 on a laptop and the image is being deployed! Thanks Torsten for your help