Wow guys - there are a lot of different issues here. I strongly suggest different threads if you're not on the original question. Here's why:
1) Reboot to PE/Production "failures" can happen for a handful of reasons, including not sending the SBS files to the right PXE server, systems not getting the task, systems failing to run the task because they failed something else, systems not being recognized by the PXE server, SBS files ariving but not being handed off to the PXE Server Service from Interface. I've seen all of these at one time or another.
2) Using F8 to get into PE via PXE has little or nothing to do with a successful reboot to task. It just means the system was waiting to get somewhere, and did so. Consider it like this. Let's say you send a reboot task to a computer. You go to the computer 30 minutes later, and while sitting there, you shut down and restart it. When you return to the console, the task shows as successful. Did it succeed, or did you rmanual intervention make it look like it succeeded? When you use F8 to get into PE, you've learned nothing at all about any reboot-to task.
3) If a system "fails to reboot to production" we need to know EXACTLY what tha means. For instance, after imaging, maybe the next job never fires because the imaging task shows as failed? Maybe the system DID reboot but went back into automation? Maybe the system tried to reboot but hung? Maybe it went to production, but the image was damaged and it went back to automation and never reported up success?
Please, all of you, first, if your issue is not the same as the person who posted, start a new thread. Second, when you say something that is designed to happen in automation "fails" take note of exactly what you see happen and document that here. We can't help troubleshoot if we're just guessing, and I think we've done enough of that so far or we'd have more fixed issues. :D Even an "Well, I see ghost run, and then nothing happens - it just sits there" is a really good place to start.
Thanks!