SDA: KBEM CCTK / Reboot pre-install task
My techies complained that they need to manually configure BIOS settings before starting deployments. (lazy monkeys...)
Dell Laptops come in with factory BIOS settings e.g.:
- secure boot enabled
- UEFI network stack turned off.
--> this makes PXE booting out of the box impossible for us.
question 1: is there already a way to PXE boot into K2 with Secure boot enabled?
I see that there's still an open uservoice with the request:
--> guess it's planned for release 7?
So until then, to reduce user errors, I'm creating a multiplatform BIOS package with cctk and included it with KBEM.
Plan is that my techies only have to check UEFI network stack and Secure Boot in BIOS, then PXE boot into the manipulated KBE.
I've created a Custom Deployment that my techies can run. The Custom Deployment contains 2 pre-install tasks:
first task runs the cctk -i <config> command (--> the config file also sets a one-time pxe boot for the next reboot (so techies don't have to press f12 - pxe boot) like I said, they're really lazy)
second task runs: x:wpeutil reboot to reboot the machine.
While the tasks execute properly, the reboot task stays In Progress on K2:
Is there a way to make this task flag as completed?
Or any alternatives for the scenario above?
How do you guys handle this?
edit: I've thought about deploying command configure on all devices, being able to send updated configurations (like pwds) seem handy but I'm trying not to bloat my image. So I'm looking for a different approach.
Answer Chosen by the Author
You can try checking "Force continue on Errors" and the CCTK script should then complete. You just have to make sure the deployment really does what you want because now it will go thru even if it did not do the tasks correctly.
Have you tried to run the CCTK task as a midlevel in your scripted install? I use custom deployments images and configure the bios at mid level. I store my Wims on windows shares thru out the organizations sites.
As a Scripted you should be able to do this: