1 of 1 people found this helpful
normally you've these menu entries after F8:
LANDesk DOS Menu
Linux PE Menu
Linux PE Provisioning
- Most important for you is the entry "WinPE Menu".
- If you choose it, WinPE will be started from your PXE.
- After the WinPE is started the LANDesk boot menu is started (dosmenu.cfg...)
- You must register WinPE on your core, before using and install (copy) it to your PXE. (\\core\ldmain\landesk\vboot\ldvpe1.img).
- During "PXE Representative Deployment" the ldvpe1.img will be copied to the PXE server and renamed to peboot.img in "%programfiles%\landesk\pxe\system\images\"
It is not possible to start with DOS WinPE, but you can use DOS commands in WinPE (32bit commands only, so not all 'old' tools are working!).
Some other hints:
our WinPE client machines are not sending or the coreserver is not receiving the SOAP requests
It's not clear what that means. What have you tried and where / how did it fail?
I really don't want to get into trying to resolve my issue with using WinPE on the core server - as I posted that discussion at: http://community.landesk.com/support/thread/5008 and haven't had any luck resolving it yet.
Basically I can get to the F8 menu - select the WinPE - the RAMDISK loads fine - the PXE Menu Scripts are listed. I select the script - the menu disappears and that's it. Nothing happens. An OSD log file is not generated on the core server. Not initiating CustJob to launch OSD script. Inventory Server and Management Agent services are running - IIS has been reset. Verified PXE.asmx - using mac address can initiate GetObjIDFromMacAddress starting CustJob. I'm working with Chuck Putnam on this and we worked right through:http://community.landesk.com/support/docs/DOC-3473 to no avail.
Last thing we tried - was to try and sniff for packets on the coreservers subnet and the client subnet.
The way our network is set up - we didn't see anything worth while.
I really don't want to have to get the mac address for each machine I have to core-load. Worst case - I will I guess.
I've got to figure out a way to use WinPE with using the coreserver and use the PXE rep instead.
Thanks for the interest though.
After the menu disappeared, is it possible to map a drive?
- Open a command shell (press the GO-button) and check for a mapped drive (net use).
- If nothing is mapped, check if you've network (ping).
- If you've network try to map a drive with net use or drvmap.
- If you're mapping is successful, check the timeout settings in your OSD script
- if you have no network, add the network driver for your hardware in the PE image and try again.