Hi,If SCM 2007 + WDS are on one server, and DHCP is on a different server, both are win2008 btw,are there any special DHCP options that need to be configured on the remote DHCP server?e.g. Does option 60 need to be the name of the SCCM / WDS server?Thanks,Ward

Yes you need to configure 1. #60 2. #67 -- \boot\x86\pxeboot.com 3. #66 -- FQDN for SCCM server. Also you need to enable the IP helper on your switch so that there can be a direct routing between the DHCP and the SCCM server.

In that scenario all you have to do is authorize the SCCM/WDS server in DHCP is my experience Michael

Hi,Thanks for your answer. Ok based on what you said, for option #67 what will happen if it is a 64 bit boot images?Thanks,Ward

Michael,Are you say you don't need to configure anything extra just do the authorization? So no extra DHCP options are required?Thanks,Ward

I'm running that same configuration and we didn't need to do anything special at all.

p.MsoNormal, li.MsoNormal, div.MsoNormal {margin-top:0cm;margin-right:0cm;margin-bottom:10.0pt;margin-left:0cm;line-height:115%;font-size:11.0pt;font-family:'Calibri','sans-serif';} .MsoChpDefault {;} .MsoPapDefault {margin-bottom:10.0pt;line-height:115%;} @page Section1 {size:595.3pt 841.9pt;margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.Section1 {page:Section1;} Like CD Shriver said.. No customization is needed, and regarding X64, PSP will take care of this for you as long as you have distributed both x86 and x64 boot images p.MsoNormal, li.MsoNormal, div.MsoNormal {margin-top:0cm;margin-right:0cm;margin-bottom:10.0pt;margin-left:0cm;line-height:115%;font-size:11.0pt;font-family:'Calibri','sans-serif';} .MsoChpDefault {;} .MsoPapDefault {margin-bottom:10.0pt;line-height:115%;} @page Section1 {size:612.0pt 792.0pt;margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.Section1 {page:Section1;} If you want to play around with WDS you might get some pointers her http://kongkuba1.spaces.live.com/blog/cns!EEFF1607E296E5AB!311.entry Michael

Hi People,I am new to the IT world..... i am trying to set up sccm2007.... this is my setup:2 physical box's 1 running server 2003 sp2 my dc ad,dhcp,dns etc1 running server 2003 sp2 my sccm 2007 sp1, sql 2005 sp2, wds , mdt 2008.i have followed a video by Richard smith...problem is when i pxe boot client it just sits running thishcp..../ my question is do I need to authorize wds sccm in dhcp???cause i get no response when trying to pxe boot...... i have gone through all setup in sccm 2007 to deploy os....i think its either wds? sccm? pxe filter whats wrong but need some advice cause it just dosent get an IP from dhcp on pxe.Please please helpMr MThanks

Ward, Like both kungkuba1 and cd shriver have already stated no customization is needed in this config, assuming the clients are in the same subnet as the dhcp server.

all clients are on the same subnet as DHCP...... which things should I check to make sure PXE is setup correctly (sccm side) could it be the pxe filter (the vbs file which you need to modify with your site code etc) im just not geeting any ip from dhcp.... but when i boot machine into windows i get an ip and have network access remote desktop etc.....thanks for helping

What error/ response do you get when the pxe process launches at the client. Just look at the screen until it times out, it'll flash a message by before it boots into the live os.

i am getting this :when pxe booting....after dhcp...../ PXE E53: no boot file p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;font-family:'Calibri','sans-serif';} span.EmailStyle15 {font-family:'Calibri','sans-serif';color:windowtext;} .MsoChpDefault {;} @page Section1 {size:612.0pt 792.0pt;margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.Section1 {page:Section1;} receivedi can confirm i have created boot image from osd dir in sccm....and new/updated the dp point im sure i have missed something to do with the pxe setup some where or could it be something on dhcp or ad that sccm needs to authorised...... Thanks

It's probably looking for the initial PXE load files from the RemoteInstall folder. Tell me, did you configure WDS when you first installed it?

Nope, no WDS configuration is needed. Have you created a pxe service point in sccm? Have you distributed your boot images to the pxe service point?

tried with wds configured did not work (re installed wds)does mdt 2008 need to be installed for sccm to work? does this pxe filter need to be setupif sccm/wds needs to be authorised in dhcp where/how can i do this?Thanks

Hi,MDT is not required, it only extends the option available in the task sequence. Did you configure the DHCP options 67to your bootimage \SMSBoot\x86\wdsnbp.com and 66 to your sccm server?Regards, Jannes Alink

It might be a good idead to just reinstall the whole thing. In my experience that usually fixes most of my PXE problems. Follow these steps:1)deinstall the PXE role (check the .log files to determine success)2)uninstall the WDS role3)reboot server4)check and make sure the shares are gone (SMSPXE$, and RemoteInstall)5)Install WDS (Note: do NOTHING to the WDS other than install it)6)Install the PXE Role (check .log files to determine success)7)push boot images to the PXE service point.See if that helps. It's a fairly quick process.

could you verify the content of the smsboot folder in the remoteinstall folder on the wds server?"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

my problem was the pxepoint was showing a critical error was WDS service not starting.... so i decided to reinstall from scratch, server 2003 sp2 reinstalll sccm2007. problem im facing now is, but this maybe a coincidence but wds seemed fine until I installed MDT 2008 then once rebooted wds service fails to start each time it just under services.msc "starting" ??? any ideas guys?? tried changing the service to start with domain admin credentials but think that made things worse.... Thanks

Did you ever get this figured out, Frank?

well, after a complete re-setup I found it to be the mini-switch we were using was playing up... which was brand new which was even more surprising. Physical layer I know... but we live and we learn... i have got sccm set up now, still in testing but we are deploying software and so far so good but still working out how it all ties together.Thanks for all the help.Frank

I have WDS and DHCP on the same server, and SCCM on different servers. However, the DHCP/WDS server is on a different subnet then all my clients. We have about 48 different subnets ranging about 15k computers. So do I need to have WDS running on each of my subnets?Also would I need to run MDT on my WDS server to be able to configure the filter? Were running into a lot of problems settings this thing up. It's becoming a big PNA.Thanks for your help.

My guess is, Scott, that you'd have to have at least an IP forwarded located in each subnet pointing to an existing PXE server. I guess the question of how many WDS servers you deploy would come down to bandwidth limitations. In other words, is each subnet a different physical location or is it just different logical groupings in the same building? I prefer a seperate SCCM/WDS server for each physical location, but you could get by with one to handle multiple subnets if those subnets were all connected with a robust network connection.

hi when clients boot with pxe they failed with this error file:\file\bcd

See smspxe.log on the PXE service point and also make sure that both (the x86 and x64) boot images are distributed to the PXE SP.

Correction: 66: SCCMPSPHOSTNAME.DOMAINNAME.COM 67: \boot\x86\wdsnbp.com Using pxeboot.com will fail...