Software Deployment

Back when I was a customer, I had all of my tasks setup on the K2 as postinstall tasks.  When the deployment was done, I wanted it to be finished and not have to hand off to the K1 to finish.  For me the K1 was for keeping that software up to date or deploying new software not available at time of deployment.  Having both products does make the decision harder, but it is nice to have the flexibility to choose the option that works best for your organization and situation.

depends on the size of the installs.  I use images so most of our software is prestaged in the images, confgured the way we want it to be.  Other software is pushed via the k1000 MI's, it has better tracking, repair and uninstall of packages.  The only software I install via the k2000 is the k1000 client and drivers.

I've tried both. I've found that if the K1 is trying to push out multiple tasks not all tasks get installed. You usually have to wait on the next check in, and it will finish up. I've worked around this by creating a label for new imaged machines, and then having them check in more frequently.

My personal opinion would be to create post install tasks on the K2 especially for software that does not change often. This guarantees all the software needed is installed.

Our baseline image as the major stuff on there, AV, Office, Reader...and the rest is pushed from the k1. we give our new machines a Base Install label and the K1 installs everything else that we need beyond what we have defined as basic image software.