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.
Are you imaging these? Why make a boot to set pxe boot??????????
If you spend enough $$$$ Dell will set the bios how you want it
All they need to do is set network first in the boot order while they are already in the bios to disable secure boot and do the other changes.
You can then create a task to switch it back to hdd first as one of your steps
We reimage and replace machines in the classrooms every year, this is what we do.
On new machines they have to disable secure boot and setup network booting, and bios password.... Reboot and hit f12 choose pxe boot.
On the boot menu have the default KBE to boot and other KBE's (one for each image) that are configured for an auto deployment.
We have a password for the PXE menu to prevent someone from f12ing and nuking a machine by reimaging.
You use the KBEM to create these custom KBEs to autoboot.
Our lazy monkeys can just press a couple of buttons put in a password and move on
They boot into the PXE menu, choose an auto-deploy boot that will image the machine and enter pxe password. They do not have to touch it again till complete.
We have them set the bios PW to start and then I call that password in the SDA tasks that reconfigure the bios. Keeps others out of the bios. We use a SMA script to change the password at least yearly
On existing machines we use the SMA and run WOL and then run a script that changes the bios boot order to pxe first and then reboots the machine.
On the SDA we create auto deployments for the machines and using the SMA labels to assign the correct image to the machines.
Any that fail to WOL we send tech to. They turn it on and manually f12 and those take off imaging.
You can push C|C with either SMA or SDA
You can create a portable version you zip and attach to tasks then it deletes when finished
You can compile the C|C commands into an EXE
They do not need to be techs to start images, we use student workers from media services to help in the summer they just need to be able to follow simple directions, so if your techs bitch about having to do menial work tell them you can replace them for less $$$
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: