Do I need set boot file name in DHCP?
Hi, I am not sure if this has been asked before. I have install the SCCM, and do the necessary steps. and installed WDS on the server. but I am recieving no boot file name error on the client. I checked the DHCP and found the boot file name was not set in the scope options. My question is : will SCCM set this option? or I need to set this option myself?
November 23rd, 2007 3:37pm

Did you get anywhere with this? I've got the same issue... I'm not having any luck.
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2007 10:00pm

Just to be clear, you have the WDS server installed (not configured). Have you also: (1) Installed the PXE Service Site role? (2) Distributed the x86 and x64 boot images to the PXE DP? Thanks,
November 29th, 2007 12:20am

Yes... I installed WDS then did nothing to it... Installed the PXE service role and then distributed the x86 image to the DP... did I need to do both? I'm just not sure about my DHCP settings... my DHCP server is on a seperate server, do I need to manually setup the scope options? Otherwise, how are my clients going to know to go to the SCCM server?
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2007 12:55am

Kevin Wehnau wrote: Yes... I installed WDS then did nothing to it... Installed the PXE service role and then distributed the x86 image to the DP... did I need to do both? I'm just not sure about my DHCP settings... my DHCP server is on a seperate server, do I need to manually setup the scope options? Otherwise, how are my clients going to know to go to the SCCM server? You will need to distribute both the x86 and x64 boot images to the DP. You will need to talk to your network folks to ask them to configure the UDP helpers on the appropriate subnets/vlans to point to the IP address of your PXE service point. Otherwise, it's possilbe that the DHCP requests will not make it from the clients to the PSP. You should be able to verify PSP functionality using a machine on the same IP subnet as the PXE service point, unless there are network configuraitons that are explicity blocking the traffic. Hope this helps!
November 29th, 2007 1:22am

I actually have got my network guy to setup a helper for the IP of my SCCM/WDS server and my DHCP server... But I still feel like I am missing something... Do I need to add a 066 or 067 option on my DHCP scopes to get the DHCP client to actually try to connect to the SCCM/WDS server? This is what I had going on with my SMS2003 OSD setup with PXE, but I cannot find any documentation anywhere explaining what I need...
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2007 6:44am

With appropriate UDP helpers in place, I have not had to add 066 or 067 to the DHCP scopes. Here's what WDS has to say: " If a DHCP server is running on the Windows Deployment Services server, Windows Deployment Services must be configured to not listen on port 67 and DHCP Option Tag 60 must be added to all DHCP scopes on your DHCP server. Non-Microsoft DHCP servers require manual configuration of DHCP optioin tag 60. If Microsoft DHCP is running on this server click the check boxes to set the following options, if non-Microsoft DHCP is running on this server check the first box and manually configure DHCP option 60. _ Do not listen on port 67 _Configure DHCP option 60 to PXE Client" Also, please ensure that the required UDP ports are open on the firewall on the WDS server. If you are still having issues, you may want to fire up NetMon on the WDS server to see if it is recieving the duplicate DHCP requests. That will surely tell you if your IP helpers are working.
December 1st, 2007 3:41am

I swear I must be an idiot.... I am still having no luck at all... I am getting a tftp file not found error... I checked with netmon, and the DHCP request is coming though, as well as the request to the tftp server. Did I miss something in SCCM? Do I need to do anything else to enable it? Is there a good how-to or step-by-step out there? I see plenty about click this if your DHCP server is on the same box, but nothing about it being seperate, should it just work? I defintely don't need to set anything in DHCP? no 066,067,060, or 150? I have firewalls off on both servers, and it's wide open in between. And I have an IP helper for my DHCP server as well as one for the address of the SCCM server with the PXE service role installed. I'm sorry to beat a dead horse here, but I'm feeling pretty lost, and none of the docs I find seem to do anything to enlighten me. kevin
Free Windows Admin Tool Kit Click here and download it now
December 3rd, 2007 10:35pm

What are the contents of the RemoteInstall directory on your PXE Service Point?
December 4th, 2007 2:34am

3 folders... SMSBoot SMSIMAGES - Shared to SMSPXEIMAGES$ SMStemp and both the x86 and x64 boot images have been distributed there to SMSPXEIMAGES$
Free Windows Admin Tool Kit Click here and download it now
December 4th, 2007 2:39am

I just noticed today that I get the "no boot file name recieved" when the computer does not exist in the sms database. Have you imported the computer's mac address? check the smspxe.log on the wds server.
December 4th, 2007 7:34am

Here is what my smspxe.log has when it tries to boot... [010.010.014.029:67] Recv From:[010.010.024.001:67] Len:548 79571c smspxe 12/4/2007 3:12:42 PM 1864 (0x0748) Executing LookupDevice(013A9E88-8C45-CB11-9B1D-AEFE281DF6F9, 00:0D:60:2C:2F:7B) smspxe 12/4/2007 3:12:42 PM 2424 (0x0978) CDatabaseProxy :: LookupDevice succeeded: 0 0 38 1 smspxe 12/4/2007 3:12:42 PM 2424 (0x0978) MAC=00:0D:60:2C:2F:7B SMBIOS GUID=013A9E88-8C45-CB11-9B1D-AEFE281DF6F9 > Device found in the database. MacCount=1 GuidCount=0 smspxe 12/4/2007 3:12:42 PM 2424 (0x0978) [010.010.014.029:67] Recv From:[010.010.024.001:67] Len:548 79676c smspxe 12/4/2007 3:12:44 PM 1864 (0x0748) Ignoring req from [010.010.024.001:67] Dest Server:[010.010.014.008] smspxe 12/4/2007 3:12:44 PM 1864 (0x0748) [010.010.014.029:4011] Recv From:[010.010.028.005:68] Len:54823fc2c4 smspxe 12
Free Windows Admin Tool Kit Click here and download it now
December 4th, 2007 11:24pm

Ok, next obvious question. Is that computer in a collection with a TS advertised to it Comparing that log to my own smspxe.log, the very next line should be "Excuting GetBootAction" and the a list of Advertisements for the device is displayed.
December 5th, 2007 4:01am

Yep, it's got a Vista installation TS advertised to it... I guess my next test is going to be putting up a DHCP server on the same subnet as my WDS server and boot a client there... maybe it's something not being passed back to the clients subnet? Are the IP helpers for the WDS and DHCP all I really need?
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2007 4:26am

Ahh, yeah, if it's on a different subnet then you need to setup the iphelper on your switch.
December 5th, 2007 4:41am

I have IP helper setup for both the DHCP server and the WDS servers IP address... and I imagine since it's showing up that much in the log, that is working, wouldn't you think?
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2007 4:43am

When I boot a machine on the same subnet after putting up a scope on that subnet, this is what my smspxe log shows... [010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7a8d0csmspxe12/4/2007 9:12:57 PM1864 (0x0748)Executing LookupDevice(84724231-D221-4EF8-A6CD-9678C625C627, 00:03:FF:88:6E:93)smspxe12/4/2007 9:12:57 PM2424 (0x0978)CDatabaseProxy :: LookupDevice succeeded: 33 1 33 1smspxe12/4/2007 9:12:57 PM2424 (0x0978)MAC=00:03:FF:88:6E:93 SMBIOS GUID=84724231-D221-4EF8-A6CD-9678C625C627 > Device found in the database. MacCount=1 GuidCount=1smspxe12/4/2007 9:12:57 PM2424 (0x0978)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7a9d5csmspxe12/4/2007 9:13:01 PM1876 (0x0754)Ignoring req from [000.000.000.000:68] Dest Server:[010.010.014.008]smspxe12/4/2007 9:13:01 PM1876 (0x0754)[010.010.014.029:4011] Recv From:[010.010.014.011:68] Len:548 23fd37csmspxe12/4/2007 9:13:01 PM1876 (0x0754)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7aadacsmspxe12/4/2007 9:13:43 PM1876 (0x0754)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7abdfcsmspxe12/4/2007 9:14:06 PM1876 (0x0754)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7ace4csmspxe12/4/2007 9:14:10 PM1876 (0x0754)Ignoring req from [000.000.000.000:68] Dest Server:[010.010.014.008]smspxe12/4/2007 9:14:10 PM1876 (0x0754)[010.010.014.029:4011] Recv From:[010.010.014.011:68] Len:548 23fe434smspxe12/4/2007 9:14:10 PM1876 (0x0754)[127.000.000.001:4011] Recv From:[127.000.000.001:9000] Len:274 257cfecsmspxe12/4/2007 9:16:09 PM1864 (0x0748) But then it does the same thing, but doesn't seem to even look up the device. [010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7aff3csmspxe12/4/2007 9:33:28 PM1864 (0x0748)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7b0f8csmspxe12/4/2007 9:33:32 PM1876 (0x0754)Ignoring req from [000.000.000.000:68] Dest Server:[010.010.014.008]smspxe12/4/2007 9:33:32 PM1876 (0x0754)[010.010.014.029:4011] Recv From:[010.010.014.011:68] Len:548 24005a4smspxe12/4/2007 9:33:33 PM1876 (0x0754)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7b1fdcsmspxe12/4/2007 9:33:52 PM1876 (0x0754)[010.010.014.029:67] Recv From:[000.000.000.000:68] Len:548 7b302csmspxe12/4/2007 9:33:56 PM1876 (0x0754)Ignoring req from [000.000.000.000:68] Dest Server:[010.010.014.008]smspxe12/4/2007 9:33:56 PM1876 (0x0754)[010.010.014.029:4011] Recv From:[010.010.014.011:68] Len:548 240165csmspxe12/4/2007 9:33:56 PM1876 (0x0754)
December 5th, 2007 5:40am

I get that sometimes after I've done a few different PXE builds on a particular machine, I've found the only way around it is to delete the computer from the SMS database and re-import it, or use a different computer.
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2007 8:07am

· If the machine already has the SCCM client it doesn’t need to PXE boot. · If you are PXE booting to an SCCM PXE Service Point you need to set option 66 to tell unknown computers where your PXE Service Point is. o DHCP helpers (relay agents) would pass along DHCP traffic but wouldn’t apply to the options DHCP sends. · You do not need to specify a file name (Option 67) · When troubleshooting: o Make sure your task sequence has “use boot image” on the Advanced properties page. o Make sure your advertisement says “make this task sequence available to boot media”. o Make sure your workstation is set to boot to the network. o Make sure you remember to press f12 on the workstation when it asks. o If you are testing with Hyper-V, make sure the guest vm has a legacy NIC and that is the MAC you’ve specified for any SCCM configuration. o Make sure your boot images have PXE and regular distribution points. o Make sure you’ve setup both x86 and x64 boot images, even if you’re not installing both versions of Windows. o Make sure your operating system images are not given PXE distribution points. They should have regular DPs only. Mike Crowley Check out My Blog!
February 16th, 2011 5:40pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics