Practices for managing automatic deployment of software package (groups) to new systems?
I work for an EDU that has the K1000 and K2000 appliance. We currently have a very diverse software stack that varies depending upon department, geographical location and a few other variables.
Historically, we have built monolithic, hardware dependent images that we captured and deployed via the ghost platform.
We are in the process of moving over to hardware agnostic processes using the K2000 and K1000 which has worked very well for our smaller and baseline images.
We currently have a baseline image for Employee, Instructional and special use systems. After deploying one of these baseline images via the K2000 appliance a tech then installs the additional software needed for that area via the K1000.
It is on the road map to eliminate the process of having to manually add software after deployment but A lot of these areas have significant overlap and duplicates in between packages. The main thing I'm trying to avoid is numerous hard references to the same software inventory package as that creates issues where things will fall out of parity.
My current thought process is that we may need to break things down granularity by labels.
Let's say that a lab needs the following packages.
- Autodesk Suite
- Solidworks Suite.
- Misc apps that belong exclusively to the architecture department.
7-zip and Notepad++ are on all systems whereas Autodesk are only on some areas. I'm thinking I would want to create Labels bound to MI's that are structured similar to this.
- Software Bundle: Instructional - All
- Software Bundle: Autodesk Suite
- Software Bundle: Solidworks Suite
- Software Bundle: Architecture Department