How can we improve the SDA (K2000)?

Link tasks to a deployment and not to an image

It would be more practical to link tasks (pre-install, mid-install, post-install) to a deployment rather than an image. We are several people to deploy the same image but we use different pre and post-install tasks... If each person changes the tasks for each deployment of the same image we risk to have conflicts...
Actually we duplicate the image to have different tasks but it's not a good solution because the same wim stored many times on the K2000 Appliance.
Another solution would be to just duplicate a link on the wim file and not the entire wim.

55 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Michaël shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • James Dolph commented  ·   ·  Flag as inappropriate

    Fully support this, MDT Uses this method. you create a deployment and then link the image to be installed and what applications. Really if you think about about, the "task groups" is almost what it needs to be. Just change it to where task groups is really deployments, and give the ability to link an image to it that it will use. Having to create multiple images and then link tasks to the image takes away from the entire idea of imaging and deploying with a single driver-less master image.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Tasks must be deployment-related and not image-related. The images should not be duplicated, but we must be able to do different deployment tasks with the same images.

Feedback and Knowledge Base