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.
Michaël
shared this idea
-
Anonymous
commented
Really disappointed that this suggestion is nearing 4 years of age without even being Under Review or Planned. This is by far my biggest pet peeve of image maintenance in the K2000. Instead of 1 thick client image and 1 thin client image and being able to use tasks for the rest, I have to have a total of 12:
Site 1 ThickClient Org A
Site 1 ThickClient Org B
Site 1 ThinClient
Site 1 ThinClient Mobile
Site 2 ThickClient Org A
Site 2 ThickClient Org B
Site 2 ThinClient
Site 2 ThinClient Mobile
Site 3 ThickClient Org A
Site 3 ThickClient Org B
Site 3 ThinClient
Site 3 ThinClient MobileThis is silly.
-
James Dolph
commented
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.
-
ORLANDO Victor
commented
that's wonderful
-
Anonymous
commented
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.