4 results found
4 votesJames Dolph shared this idea ·
58 votesunder review · Ken Galvin responded
Thank you for your suggestion. I have put this in our product feature backlog. Please vote for this feature if you are interested so we can move it up the priority list. If a workaround is discovered, it will be posted here.
161 votesunder review · 10 comments · KACE Systems Deployment Appliance (SDA) » Feature Enhancements · Admin →
An error occurred while saving the comment An error occurred while saving the commentJames 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.
An error occurred while saving the commentJames Dolph commented
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.
Please refer to this improvement idea.