"The Bootmenu" in all its glory is always resident on your Core - DOSMENU.CFG in (default path) - "C:\Program Files\LANDesk\ManagementSuite\landesk\files\"
Now, in order to display this, the client has to be able to download this. We do this via HTGET - which is essentially a HTTP-based copy. Since we use HTTP, you can check your Core's IIS log (in "C:\Windows\System32\LogFiles\W3SVC1\") for errors in this regard when trying to get the file.
Check whether that file gets copied down OK / see what IIS has to say - it's possible you're being blocked by NTFS permissions or something else that IIS doesn't like for starters :).
LANDesk EMEA Technical Lead.
Do you have any options configured in your DHCP where the clients may be being re-directed to an alternative TFTP server (For example a tftp address for VoIP phones)?
I ran into this off and on before and it always turned out to be that tftp was being blocked on our switches. Contacting the rogue switch guy and having him change it back worked everytime.
Go to here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
Search for MTU.
If you see any MTU settings that are not 1500, change them to 1500.
Also, make sure that you don't have PEBoot.img open with Winimage and locked.
I have attached the txt file you asked for me to check on the coreserver. From what i see i dont think there are any errors. Can you tell me if there are? It seems to log a file in this folder every day.
ex080205.log 44.6 K
I have attached a print screen on an area within DHCP that i may have to enable? Pls confirm this is right? I ticked the box for this option and entered in a string value? is this required? please check print screen of the "configure options" of scope options area in DHCP.
DHCP.doc 31.5 K
You do not need to enable Option 66 unless you want to have your PXE Representative on your DHCP server.
Is that what you are doing?
no i only enabled that option as im still stuck on this annoying issue and trying anything possible. i will untick this because its not required.
It all sounds so easy setting this PXE boot up within LD but we are still seeing issues.
i will run down exactly what im doing. First of all i have two PCs (coreserver, and a managed device pc) that are PXE representitives.
We are on SP5, i have once after this update re-pushed the pxe representive scripts to these two devices.
I have a OSD depolyment script which has been dragged across to PXE BOOT MENU option in LDMS window. (Screenshot is shown in attachment)
Update button is pushed
I then go to the new device which i want to PXE boot from i start it up and push F12 which then takes me to a screen where i can see-
The client network card is picking up client id, mask, dhcp, proxy, gateway addresses
Then i see the following menu-
LANDesk DOS Menu
Linux PE Menu
Linux PE Provisioning
Which option would i push next- either WinPE Menu or Managed WinPE option? i have chosen both at different times but im still seeing the following messages when i do-
Boot server IP- 10.blah.blah.blah (it picks up the PXE rep PC Device)
PXE-T01: File not found
PXE-E3B: TFTP Error - File Not found
PXE-M0F: exiting Intel boot agent
This is as far as i can get... is something i missing in the steps to deploying a script via PXE option?
PXE BOOT MENU.doc 38.0 K
1 of 1 people found this helpful
You won't see the Menu created in the poorly-named PXE Boot Menu in the F8 menu. The F8 menu is really the only PXE boot menu and what we call the "PXE Boot Menu would really be better named as "OS Deployment Script Menu". You can get to it by choosing and of the F8 options that say "menu".
So basically it won't show up until you are in WinPE.
So if the PEBoot.img files is really on the PXE rep, then I can only think of a few things causing this:
1. You are PXE booting from a different PXE Rep you didn't know existed (Check during the F8 menu for the Proxy IP). If it is the right PXE rep then this is not the issue.
2. You already have a TFTP server running on the workstation so the LANDesk tftp server was unable to load. Stop both PXE rep services and then from a command prompt run this command:
Netstat -an |Findstr 69
- or -
Neststa -a |Findstr tftp
3. Something on the network is blocking the TFTP traffic to the PXE rep. Either the firewall on the PXE Rep or something in between.
Again another strange resolution here, i remembering months and months ago i was able to see the boot menu screen. I have two machines as mentioned before- a PXE rep on the coreserver and one on the a pc device on the network.
You mentioned to check the files- PEBoot.img files - c:\Program Files\LANDesk\PXE.
Everytime PXE booting it would always pick up the PC device as the PXE rep. So what did was cross referenced that folder PXE with the one that was on the core server (it was also a rep) the coresever had more files in it. ?!?!?!!?
All i did was copy over the missing files from that PXE folder on the coreserver to the PC device that PXe booting always picked up. And this time it worked.
How very strange and im still scratching my head why i would have need to do this when i have pushed the pxe representive a few times to these machines!! the job saying successful when it in fact didnt copy over all the files!!
Why would one pxe rep machine differ to the other?? when they both had PXE rep scheduled jobs being pushed to them!?!?!?
well i know we are up and working...
I am having this same issue on different subnets. Tried all the things mentioned above but no luck.
I am having the same issue. But when i search for a MTU value there is none found in the entire registry. Could you possibly give me a screenshot of what the registrys meant to look like?