Detach the image media from the image deployment job
The idea is to have the same process for the Imaging that the scripted installation. Then the image captured will be stored in the media Library and not in the deployment image tab. To create an image deployment job, we will select the image in a dropdown list.
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 Mobile
This is silly.
Please refer to this improvement idea.
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.
Instead of picking an image file that has tasks assigned to it, give the ability to create Build Groups where you select the image and applications to be installed. Right now its static, if you want to use the same image but different programs you have to duplicate the image and assign a different set of applications tasks to it. This takes away from usable drive space. It would be easier to build the deployment groups that calls a certain image and application groups.
@Corey : Duplicate image takes twice as much space on the storage. If you can have just one image and duplicate only the tasks it should more efficient
ORLANDO Victor 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.
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.
AdminCorey (Admin, Quest KACE) commented
Seems like a decent idea, but you can just duplicate an image with similar results.
this would be great