XistEnCe Posted January 20, 2011 Report post Posted January 20, 2011 Hi! I've just installed SCCM2007R3 with FEP2010. I'm trying to configure everything and get this show on the road - but..... When booting, the clients just wait for DHCP from the PXE server, and times out. Does the PXE boot, require the WDS service? Or is this optional? The server running SCCM is also a DHCP server, and I have defined a boundary which contains the net in the DHCP scope. Do I have to advertise anything for it to PXE boot? Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 20, 2011 Report post Posted January 20, 2011 A PXE Service Point indeed needs WDS, also when you are configuring PXE/ WDS on a DHCP server make sure they don't respond to the same port (http://www.petervanderwoude.nl/post/ConfigMgr-2007-PXE-Service-Point-and-DHCP-Options.aspx). Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 20, 2011 Report post Posted January 20, 2011 Thank you for the reply! I just installed the WDS service, and installed the PXE feature in SCCM afterwards. The I enabled it, and told it to reply. Clients still don't get any IP and times out to the PXE request. How do i define which dhcp server the clients should use for PXE booting? Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 Still having issues with no reply from the PXE servers.. If I check the WDS Role on the server, it's still listed as not configured for some reason. Is that correct? The server I'm running sccm on is also the DHCP - so I shouldn't have any problems there? Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 When using a media (CD/DVD/USB) to run the TS, I have no problem what so ever. But still no luck on getting the PXE to reply.. I imagine it could be the WDS Role reporting to be "not configured"? Is it safe to configure it normally? Or does the "hands off the WDS Role" rule still apply? Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 21, 2011 Report post Posted January 21, 2011 SCCM takes care of the PXE part. Did you already take a look at this post: http://www.petervanderwoude.nl/post/ConfigMgr-2007-PXE-Service-Point-and-DHCP-Options.aspx ? When running PXE/WDS on the same server as DHCP you need to do some additional settings. Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 SCCM takes care of the PXE part. Did you already take a look at this post: http://www.petervanderwoude.nl/post/ConfigMgr-2007-PXE-Service-Point-and-DHCP-Options.aspx ? When running PXE/WDS on the same server as DHCP you need to do some additional settings. But should it update the WDS settings or do I have to do that? It's listed under roles with a yellow "!" and it tells me it's not configured. I read the info on the link, and entered: 060 = client Identifier (PXEClient) Could not find this in the options at all 066 = boot server host name (Tried both FQDN and hostname of the computer with SCCM and PXE) 067 = boot file name (I have no idea what info to input here, and the REMINST\SMSBoot\x86\ and REMINST\SMSBoot\x64\ folders are both empty. The only file around is boot.sdi in the SMSBoot folder (Parent dir to x*\). Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 21, 2011 Report post Posted January 21, 2011 060 is the only one that is really needed in this case. Normally it should be added during the installation of the PXE Service Point. If not it needs to be created manually. Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 060 is the only one that is really needed in this case. Normally it should be added during the installation of the PXE Service Point. If not it needs to be created manually. Yeah, I find it wierd that it's not even in the list of options to add. It should be in the list with the rest, under the scope settings - right? Seems like it could be hard to get PXE working then.. What info should I input there, in case it magically appears? I've even tried reinstalling the PXE service point, with no luck.. Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 I ran through the configuration part of WDS Role, and it added the 060 value to the DHCP server. The value is set to: PXEClient and that's all good? Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 Now the client reports that No boot file name received and PXE-E53. This is probably linked with the file that's set in the DHCP settings? My folders are empty as stated earlier.. Why, I don't know - but it can't be a good thing? Is it possible to get a hold of those files from somewhere? Quote Share this post Link to post Share on other sites More sharing options...
Hi!
I've just installed SCCM2007R3 with FEP2010.
I'm trying to configure everything and get this show on the road - but.....
When booting, the clients just wait for DHCP from the PXE server, and times out.
Does the PXE boot, require the WDS service?
Or is this optional?
The server running SCCM is also a DHCP server, and I have defined a boundary which contains the net in the DHCP scope.
Do I have to advertise anything for it to PXE boot?
Share this post
Link to post
Share on other sites