/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Forced network boot attempt failed check cable and settings

04/03/2012 8260 views
I'm trying to remotely do an in-place rebuild using the K2000. I ran CCTK on the machine using the command "cctk --forcepxeonnextboot=enable" and then rebooted the machine. The machine reboots and displays 'Forced network boot attempt failed check cable and settings- strike f1 to retry boot, f2 for setup utility'. Obviously, the force PXE boot command worked, but it fails when trying to actually boot into PXE. any ideas?
If I manually boot into PXE from F12, it works just fine.
What method are you folks using to get the machines rebooted into PXE boot (from remotely)?
Thank you.
Answer Summary:
0 Comments   [ + ] Show comments

Comments


All Answers

0
Just curious all machines or just one or one model? Same part of the network, etc...?
Answered 04/03/2012 by: dchristian
Red Belt

  • so far just the one machine that we tested, optiplex 960. Same part of the network, if we manually hit F12 and select PXE / NIC, then it boots to Kace just fine. What method are you using in your environment to get the boxes rebooted and into Kace?
  • For the desktops, new machines are manually booted to PXE the first time. A CCTK script set the nic as the first boot device. Then the K2 has boot actions set for local hard drive. If we need to re-image we change the boot action, and send a reboot signal from the k1.
    • wow, that's a very interesting approach. So your desktops are "permanently" set to NIC boot and the K2000 directs it to HDD boot. Your list under the boot actions tab must be huge. This is a creative method, thank you for the suggestion!
      For the CCTK script, I imagine you are doing both cctk bootorder --enabledevice= and then cctk bootorder --sequence= ?
      Thank you
0

this is what I ended doing, created a network deployable package with CCTK files and these commands:

cd cctk
cctk --embnic1=on
cctk bootorder --disabledevice=0,1,2,3,4,5
cctk bootorder --enabledevice=embnic
shutdown /f /r

during the K2000 scripted install (rebuilding the box), I add a KBE task that does this:

cctk bootorder --enabledevice=0,1,2,3,4,5

Answered 04/13/2012 by: bthai
Yellow Belt

0

this is what I ended doing, created a network deployable package with CCTK files and these commands:

cd cctk
cctk --embnic1=on
cctk bootorder --disabledevice=0,1,2,3,4,5
cctk bootorder --enabledevice=embnic
shutdown /f /r

during the K2000 scripted install (rebuilding the box), I add a KBE task that does this:

cctk bootorder --enabledevice=0,1,2,3,4,5

 

Answered 04/13/2012 by: bthai
Yellow Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ