Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

managed PC not booting to PXE

Created: 19 Apr 2011 | 7 comments

I'm testing rebuilding an existing managed PC. I have the management agent on it and its showing up in the NS console. when I do a reboot to PXE, it reboots but skips the PXE. I have a reboot job setup pointing to a Preboot configuration. I have the NIC as the first boot option in the bios. It does get an IP address but then displys a list of data thats too quick too read before it goes off screen (Lenovo desktop)

Name  OS      Arch  OEM extension automation type Used in taks

winXP winPE  x86    DS Agent          PXE                  Yes

I cant figure out why this is not working.

Booting 'new' machines goes into PXE and starts the build fine.

Appreciate any pointers.

Joe.

Comments 7 CommentsJump to latest comment

bhawver's picture

You might check to see if there is an updated BIOS for the effected machine.  I've seen posts on here that can sometimes cause problems with PXE booting.  If there isn't a newer BIOS available, you might see about downgrading the BIOS.  If that fixes the problem, you may want to contact the manufacturer with the problem so that they can be made aware and possibly release a new BIOS to fix the issue.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

BugTastic's picture

I'm pretty confident the bios on these machines are fine. I just tried another lenovo model. did a fresh install - it booted to PXE (didn't bring up the intial deployment menu) i dropped the deploy job onto it and it was successful. Now if I run the following job while winodws is up and running it skips PXE

Reboot to PXE - reboots here but doesn't go into PXE!
deploy image
reboot to production

 edit: I just created a USB automation boot disk and it loads up WinPE and kicks off the job no problems. Odd!

bhawver's picture

Is it only affecting that particular model?  If so, then I'm not sure how you could be confident the BIOS is fine.  If you were saying that it worked on some of the same model and not others, then I would probably agree, however, if you are saying that it works on other (different) models, but not this one, it strengthens my argument that the BIOS might be the culprit.  Adding that it works on USB automation and not PXE is also another argument that the BIOS may be the problem.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

BugTastic's picture

But the PXE does work when I deploy an initail image. It boots into it OK.

bhawver's picture

Now that is interesting.  I guess I didn't see that it was working fine for one job and not the other.  Sorry for the confusion.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Saeed's picture

I guess you should try by creating a a new job and then assigning to the same machine.

If a forum post solves your problem, please flag it as a solution. If you like an article, blog post or download vote it up.
 

BugTastic's picture

See my post from above :

Reboot to PXE - reboots here but doesn't go into PXE!
deploy image
reboot to production

 

I do create a job and assign it to machine.