Video Screencast Help

Client Build Wizard Workflow

Created: 21 Sep 2011 • Updated: 06 Oct 2011 | 3 comments
noodleNT's picture
+7 7 Votes
Login to vote

This was a proof of concept I did to see if I could use Workflow as the front end to the new Deployment Solution in 7.1. The idea is to create a wizard our Help Desk could use to build and deploy client computers. It works fairly well but I am stuck on creating a "Pre-Defined" computer through the ASDK. You can create a computer resource in Altiris and assign a user to it just fine. Unfortunately it can't be used as a "Pre-Defined" computer. However, it this is still a great example on how Workflow and Altiris can work together and would like to share it with you all. Perhaps one of you could even figure out how to get around this "Pre-Defined" computer mess.

The Workflow does the following:

  1. Pulls a list of users in AD
  2. Pulls a list of imaging jobs from a folder in Jobs & Tasks (You must define this list folder and have your jobs ready)
  3. Dynamically creates a computer name based on the user and computer model selected
  4. Creates the user or computer resource if it doesn't exist
  5. Queries SMP for all assigned computers to a selected user
  6. Schedules the build job

Comments 3 CommentsJump to latest comment

noodleNT's picture

There is no ASDK for pre-defined computers in workflow still. So I am thinking of a way to do this without the need.... will post an update later if it works.

0
Login to vote
b3tts32's picture

Did you ever find a way to create a pre defined computer?

0
Login to vote
noodleNT's picture

Symantec did add a pre-defined computer API function but we have found it is incomplete. It doesn't update the SBSStore (and other background voodoo) to be able to get tasks to run on pre-defined computers created by the API.

What I ended up doing is ask our Help Desk to enter the MAC address of the computer they are going to build in a form. It then checks for the computer in the NS and deletes it from AD and the NS if a match is found. The HD person then boots the machine into PXE and clicks next on the wizard\form. I then have a list box that will populate with any new machine with the name "minint" in it. Since Altiris no longer knows about this computer, once the PECT agent registers with the NS it automatically creates a new computer with the name "minint-random". The HD user then selects this computer and we use that guid to assign any jobs we want to it. Not every ideal but it does work.

 

0
Login to vote