Computer Lab Deployment - your thoughts/opinions/ideas.
Calling all Schools/Universities,
I'm fairly new to KACE and just spent the last week getting imaging with the K2000 to work (hooray!). We have spent the last several months getting all our applications on to the Software Portal on the K1000 (love that thing). My question is this;
With the K2000 pushing images and the K1000 pushing applications, how do you get them to working together QUICKLY to image computer labs with an OS and all the required applications?
I know you can label machines and apps and they will EVENTUALLY all install but we usually only have 24 hrs maximum to image a lab (usually less than 12 hrs). I have heard people say that software may not deploy for days or even weeks with agent check-ins. That won't work for us.
I know thick images have been discussed but we change apps all the time so we need thin images (OS with a little config) and then we push apps individually (using our current system which KACE has now replaced).
We also need to account for Deep Freeze. We can't throw a thaw and freeze task in every time we package an app. That won't work for us either.
I have heard that you can import apps from the K1000 to the K2000 but that would require us double-handling apps (as well as altering the scripts). That would work, but it's not great.
So, I guess my real question is - what do you guys do? If you do large scale lab deployments (we have 4 sites, each with multiple labs) can you please advise how you do things? What works, what doesn't? How do we get the best bang for our buck from the KACE systems?
Your help is greatly appreciated.
Community Chosen Answer
My last post install task is always an initial check in of the agent.
The K1000 has a label which holds new systems (less than 24hr in the inventory)
All Installs and also a fast patching job are linked to that label.
So all systems which have been installed and checked in getting all installs.
Answered 06/21/2014 by: Nico_K
Please log in to comment
log in to commentPlease