SCCM 2007 PXE boot problems

[nevermind86]

hi all

 

have recently setup my site server all is working well, have updated to sp2 to deploy windows 7 via PXE/OSD, having followed the guide here to accomplish this (which is great by the way) I have run into a problem that i have googled the crap out of and cannot resolve, have gone through my OS capture process with the boot image and task sequence and have gotten my .wim image fine, now I have pushed both boot images out to both DP's. I have tried configing WDS and not configuring it as there are mixed reviews on this. my ccm pxe role is installed succesfully confirmed with the logs. my operating system image is distrubted to the main sms dp not the pxe one. my task sequence is set to run as a boot image. it all appears correct. however when booting a client either virtual or physical the damn thing just stops on the below error, some people have suggested maybe enabling port 19/20 on my dhcp but im not convinced. please can anyone point me in the rite f***** direction, thanks.

 

boot images

 

 

 

dhcp scope
os install

the
pxe boot

 

sms[xe log file




and finally task sequence



sorry for the spam wasnt sure how best to present it, any help would be mucho appreciated !!

[nevermind86]

an update, changed the DHCP options from the FQDN of the server to its ip address, it now starts to PXE however the i get the error code "a recent software or hardware change has occured which is preventing the OS from startup up" \boot\bcd 0xc00000f !!

[Balthier]

I'm having PXE problems myself. Sometimes it works, sometimes it doesn't. You could try this and see if it helps

http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

 

You can also have a look here http://netsaber.wordpress.com/2008/07/15/configmgr-os-deployment-wds-and-dhcp-on-same-server-issueresolution/

 

Btw, when you have installed WDS, DHCP and PXE on the same server, what configuration changes do you make?

Why have you set the two DHCP server options 66 and 67 manually?

[nevermind86]

hi,

 

ill check them out now, i installed wds only and did not set it up, i let sccm do that, i have set 66 to point to the sms ip and 67 to point to the boot image (unc path) of the OS, another update:after unininstalling all pxe point and wds and resintalling step by step from a guide after the pxe has started it almost looks like the sequence is about to begin, hang for a few seconds like its trying to process something and i get lots of these "GetUnknownMachineResource (001,x86):" in my smspxe log.... anyone?

 

[nevermind86]

im just wondering, do you need R3 to have the ability to advertise to unknown machines?

[nevermind86]

i think ive become a little confused, do i need to advertise my windows image to a bare metal system or should it just pick it up, do i need to target unknown collection?

[nevermind86]

update: it works !! im a massive tool, i had missed the part where you deploy the wim image in its deploy task sequence (had missed the small URL at the bottom of the previouos document) sorry for wasting anyones time, also I would like to know hoever, is there a way to deploy this to any new mac address or soemthing similar as i dont particularly want to add a new mac each time i want to image a machine?

[nevermind86]

anybody know if its possible to allow unknown mac address to pickup the pxe boot?

[Rocket Man]

 

anybody know if its possible to allow unknown mac address to pickup the pxe boot?

 

If you have unknown computer support enabled then yes.

If you dont then you have to import the systems info(MAC and NetBIOS Name) into SCCM to allow it to PXE boot which the means your MAC address is no longer unknown.

 

The first option is the easiest and most efficient way......with a DP password and a TS password it is almost as secure as a DP that does not allow unknown computer support!