Creating custom K2000 boot actions
Is there a way to create a customized boot action in the K2 beyond what is already in the list? It populates by default the KBEs and starting scripted installs or system images automatically, but is there a way to duplicate one of those entries and have it pass command line arguments or maybe create a temp file for a preinstallation task to read? I currently have a GUI built for my techs to be able to manually enter the computer name and choose an OU to join the domain to, but I'd like to be able to use the same image (supposed to be a "golden image" used by everyone) and just have one of my existing scripts check those arguments from the boot action and skip the GUI, just grabbing the existing computer name and rejoining the domain.
Perhaps instead of a custom boot action, there's another way to achieve this? If not, it's not a huge deal to have to VNC into the device and enter the info manually, but it'd be nice to be able to schedule an unattended re-image with the same set of tasks.
Community Chosen Answer
My domain join tasks are solid and I'm satisfied with them. What I'm really interested in here is if there's a way for a preinstall task (in this case a vbscript) to recognize how the image it's in was launched (manually through the KBE or a boot action from the K2 console) and react accordingly.