I had the same problem, but ended up ignoring it because manually PXE booting made more sense for my team. Afterwards, it was suggested to me that I make sure that there are no other tasks existing tasks for the machine I was trying to get to autoboot. Perhaps check this?
Thanks for the reply. Unfortunately ignoring is not an option for us as we image so many devices, it will take forever to get through them one by one. There are no other tasks in there as these are brand new machines. They are out of the box and we need to put an image on them before we package them back up and ship them out.
Someone must have come across this before?
We have techs that start the PXE/USB/CD boot from the physical machine, OR some of them log into the console and start the job.
I have tried this before...putting a reboot as the only action in the "System Migration" and then scheduling the task, are rebooting the machines, then it picks up the template automatically.
Thanks for the reply. I don't think people are understanding the problem though. I don't expect the machines to reboot, or someone to reboot it to pick up the template.
- From console
- Enter Bare Metal Server item
- Schedule Template...
- Add the Bare Metal item to the Scheduled Task
- Start the Scheduled Task
- Item goes to Pending in the status
- On the physical machine, power it on...
- It defaults to NIC boot
- Gets a DHCP lease
- Recognizes that there is a Scheduled imaging task already to go and auto-boots into WinPE
- Starts the task automatically
Where ours goes wrong is the bold section above. This never happens. Even with the task already started, the machine boots, gets a DHCP lease, and then offers the PXE Menu and says Press F8 for menu....
If we press F8 at this time, AND manually choose WinPE provisioning, then it will load to WinPE and start the task by itself. If we DO NOT press F8 and manually choose WinPE provisioning, then it will timeout the F8 option in 10 seconds, and move to boot frokm HDD.
Therefore the scheduled task never gets done as it never gets to WinPE to do it.
Any ideas here? I tried confirming and using different delivery methods on the task but nothing seems to kick it to auto-load past the F8 menu and into WinPE.
- From console
I totally believe you FYidoctors. We have the exact same issue at our place and it drives me insane!
Found that sometimes removing and redeploying the PXE Rep fixes it. Other times, i have restarted the scheduler service on the core server. It still happens now and I havent been able to pin it to anything yet. We're running 9.5 Sp1.
Have you managed to resolve your issue yet?
What are you using as the identifier in your bare metal import? I've always had best success with MAC address. However, are you certain nothing is getting in between with a different MAC address (such as a docking station)?
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality