SCCM 2012 SP1-SQL 2012-Server 2012

[boyjaew2]

I just set up a new standalone primary site in our environment and I am playing hell getting PXE going. Through the various steps I have taken to validate everything is working I noticed that if I look at the WDS configuration VIA server manager they do no match up with the [proper] settings that I have set on the DP role. For example, I have obviously enabled PXE on the role, but in the WDS console under PXE response tab it is clearly checked "Do not respond to any client computers".

 

I find this a bit odd. I do not run sccm and dhcp on the same server. So, I expected all this to be "set up for me" when I enabled PXE on the DP role. Is this usual behaviour or should I back track on WDS and try again?

 

Thanks.

[Rocket Man]

I know SCCM is supposed to install WDS and configure when you specify a PXE DP....

 

BUT

 

I always....always install the WDS role first via server manager and restart the host......then I enable PXE on the DP(having configured the boot.wims first, deploy from server etc etc..)

 

This will then configure the WDS and add the extra PXE files to the SMSboot directory..... and considering your DHCP server is isolated from your PXE server there is no need to add DHCP options etc to DHCP scope..

I have always do it this way now and have never had any problems with PXE

 

I have however initially let SCCM do all the work for me when first tricking about with it.... but on occassions it did not work especially across slow links on remote PXE DPs

 

Rocket

[boyjaew2]

Thanks for the feedback. I'll give it a try.