Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

clients don't boot to automation

Updated: 21 May 2010 | 5 comments
tamahome's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I schedule a job that requires linux or dos like deploying an image, but when the client pxe's, it shows the pxe boot menu, but then blithely local boots to Windows.  It seems pxe doesn't know that an automation job is scheduled for it.  How to fix?

Comments

bhawver's picture
28
Jul
2009
0 Votes 0
Login to vote

Couple of items to check

Ensure that the PXE server is the same version as DS.  Also ensure that the PXE Manager on the DS can see the other PXE servers.  Also make sure that the task/job is set to use the correct automation client.  If it is set to Auto, it may have a problem finding Linux, try changing it to Auto (Linux).

Also, you might try restarting the PXE/TFTP and PXE Manager services on both the PXE server and the DS Server.

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.

RFredette's picture
28
Jul
2009
0 Votes 0
Login to vote

Another couple to check

To add to the previous post, you can also check:

1) Make sure there are no other jobs in line for the machine.  Agent update jobs or old "widespread" install jobs that require a windows OS will make the PXE boot fall through.

2) I have run across a scenario where my 6.9 server has many (50+) jobs waiting for machines to connect so it can run them.  I have then noticed that what used to be an instant "drag the job and it runs" is now delayed by about a minute.  No big deal normally, but if you rush to PXE boot, the deployment job is not yet "ready" so the PXE falls through.

tamahome's picture
29
Jul
2009
0 Votes 0
Login to vote

#2 did it

RFredett's #2 did it.  My jobs were also executing slowly; I cleaned up some jobs that were pending for off or undeployed computers and linux pxe jobs starting working again.  Hmm, I didn't get any email notifications of replies.

Carl_G_Taylor's picture
29
Jul
2009
0 Votes 0
Login to vote

BIOS/Memory

Another thing that can cause this I've found is old BIOS versions and in some cases with HP desktops <512MB 

mabdelnabi's picture
30
Jul
2009
0 Votes 0
Login to vote

Host Entry

I also had to make an entry in the Automation host file. That helped with issues like that I was having in couple of my PXEs.