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.

Answer Summary:
http://mystuff.clarke.co.nz/MyStuff/wsname.asp
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

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.

Answered 05/29/2012 by: djit
Yellow Belt

  • How are you machines currently named? Service tag?
    • We name them using a separate asset tag and a code for the site the device is at. Doesn't really lend itself to automatically pulling from a spreadsheet or something, as most of the time we have just one tech at a given site and they don't have the time to inventory and pull mac addresses into a spreadsheet while juggling all their other IT support duties, which is why I put together the GUI I'm using.
  • I know you are looking for something that will determine how it's booted, but as ckubaska mentioned http://mystuff.clarke.co.nz/MyStuff/wsname.asp will give you a ton of options.

    eg: wsname /N:WKS$MAC will give you a new name of WKS00508B052AE8

    wsname /N:WKS$ASSETTAG will give you a new name of WKS(ASSET TAG from BIOS)
Please log in to comment

Answers

1

We currently use this to name the machines. It will prompt at the beginning of an image for the name. 

http://www.kace.com/support/resources/kb/article/Get-Set-ComputerName

I have a powershell script (post install) created to join computers to a specific OU depending on the image. I use the "Add-Computer" command in powershell.

Answered 05/29/2012 by: dugullett
Red Belt

Please log in to comment
1

I use a bat file with wsname service tag = computer name to set the name of the systems, then join the domain and add the k1000 agent. works great.

Answered 05/29/2012 by: ckubaska
Fourth Degree Brown Belt

Please log in to comment
1

We use the get/set computer name scripts provided by Kace to autoname our machines.  I left the line <computername>xxx</computername> out of my sysprep answer file for the captured image.  When I deploy an image if I use the  get/set scripts windows 7 uses the old name.  If I do not use the get/set scripts the machine will ask for a name during the post sysprep phase.  We pre-stage our computer names in the correct ou's prior to joining the machines to the domain via an ldap import for groups or create manually for singles and do not delete them unless the name is no longer needed.

Answered 05/29/2012 by: SMal.tmcc
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity