The ability to add labels to software could be invaluable. As someone working at a school the process could look something like this.

Basic Software (Lable)
• 7-Zip
• Office
• Java
• Adobe Reader
• Chrome

Class1 Software (Label)
• Class Specific software 1
• Class Specific software 2

Instructor Software (Label)
• Smartboard Tools
• Finance Software
• Class Monitoring Software

Department 1 Software (Label)
• Special software that they just HAVE to have /s

From this point I can now add labels to images that dynamically update.

If I later decide to add Firefox to my basic software label I won’t have to update ALL of my images. Class images can be more easily managed. A student’s image could include the basic and class labels. Then duplicate that image and add the instructor label.

The ability to group post installation tasks would be a great addition to Kace.

Like this idea a LOT- creating template images (image + reused post-install tasks). We have computer lab images in which the only differences are a few post-installation tasks, like which printer gets installed, who the local admin is, and the Computer Description field. Because we use a hybrid image/scripted install process, every summer when we update Windows Updates on the lab image, we have to rebuild the image for each lab (drag and drop all our post install tasks, or duplicate and change, duplicate and change, duplicate and change, etc)... it'd be a huge time saver if we could chose an image template (core image + standard batch of post-installation tasks) then add the few lab-specific post install tasks. That way, once we update the Lab image template (or master), all our lab images are updated.

This template idea is a great suggestion. I don't like having to remake all my scripted installs just because I have changed the operating system.

This should really be extended to grouping other tasks as well. This would simply the management of multiple SOE's. For example, you could create a 'notebook group' of tasks, which would include all of the post installation tasks relevant to a notebook (VPN software, power management etc). Likewise you could group applications based on user positions - you could have a "sales user profile" which would be a group of applications used by the sales team.

Even better would be the ability to nest groups.

A similar functionality used to exist in IBM/Lenovo's imaging solution (Image Ultra Builder).

Labels in the K2000 are somewhat flat: I find I have to create a giant list of 20 items when I'm creating a scripted install.... for each image.... even if there's only 1 thing added. No fun :-(

Would it be possible to assign post install tasks a label, and then apply that label to an image? Instead of each individual post install task.

So here's the scenario:

We install a certain set of software for ALL machines, and then we have some tasks we run only on laptops or only on desktops (or only on lab computers)

I'd like to be able to create something like a scripted install that can then be reused in another scripted install. So, my "master" SI would be "install windows, set computer name, install flash, java, etc". Then, I create a "Deploy laptop" SI that first calls the master SI and then adds additional tasks such as install encryption software. And then I could create a "Deploy english lab" that called the master SI and then added an additional job such as "install software X"

The "master" batch of SI tasks should automatically update any SIs that use it if I make changes to the master SI. As it stands now, if we decide to add software to our entire fleet of SIs, we have to update each and every one of them.

I would think Kace could easily support this, similar to the regular \\k2000\drivers_postinstall\manufacturer\os\model function.
You could use something like 'Get_Manufacturer_Model_OS.vbs' to poll the hardware type and run model-specific installs. Like from \\k2000\software_postinstall\manufacturer\os\model. You already have the logic; just add the ability to do installs for software dependent hardware (as I have seen recommended by Kace support).

It woiuld be good to be able to create driver groups for those drivers that need to be installed as post install tasks due to conflicts in the driver feed. ie All Lenovo L420 drivers in one group that is then applied as a single post install task that runs all child tasks.