Rocket Man Posted June 23, 2012 Report post Posted June 23, 2012 SCCM 2012........need help.... Does anyone have any information on setting up pxe properly. My DHCP server is on a different machine. I enabled pxe service point on the distribution point and WDS was installed and started its service. The boot images have populated the SMSBoot directory within the RemoteInstall folder, both x86 and x64 with all files pxeboot.com etc.... I have tried every configuration possible that I know off but still no luck. The best progress I made was getting it to boot once. This was achieved by having the DHCP server co-inhabitant with the DP and option 60, 66, & 67 specified in DHCP which Microsoft do not recommend applying. But as I said this worked for "1" pxe deployment and then all of a sudden stopped working. I have setup SCCM on a stand alone site with all services on the same server as the primary server and it works fine. What is so different than this PXE setup via SCCM than setting up WDS and configuring it from the server roles, after all it is only a damn PXE server. Is this a bug within SCCM2012 does anyone know. I am getting access violation errors and all sorts from trying different configurations, but still no pxe boot. The WDS works fine stand alone and clients get pxe responses with no hassel, but when the pxe role is enabled via SCCM and WDS gets installed all go's wrong. Is there permission settings on the new directories it creates, SMSBoot etc??? Any advice is appreciated. Thanks. Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted June 23, 2012 Report post Posted June 23, 2012 Have this one sorted now.......Hope this helps others with remote DPs acting as PXE service points also. Do not let SCCM create the WDS services for you by enabling PXE on the DP. Do a standard install from the server roles. Restart the server. DO configure the WDS and do not let SCCM configure it for you. Get the WDS up and running and check that clients on the LAN can recieve a PXE boot from the WDS. Once happy that the machines are recieveing a pxe boot THEN add the PXE role to the DP from the SCCM server. This will then populate the already created RemoteInstall folder with the new directories. Make sure to tick the boot images options ( Deploy this boot image from the PXE service point) before distributing them to the remote DP. i have tried endlessly following Microsoft tech docs on configuring this with no progress, as it is documented to allow SCCM to configure everthing for you.....from my testing I believe this to be untrue. If you already have WDS running on your network then leave it as it is and add the pxe service point. I have now got 15 remote DPs acting as PXE service points by configuring WDS fully before ativating the PXE from SCCM server. Hope this helps others. Quote Share this post Link to post Share on other sites More sharing options...
tmiller_hockey Posted June 25, 2012 Report post Posted June 25, 2012 Our problem was solved using the iphelper in our switches. Quote Share this post Link to post Share on other sites More sharing options...
