156 votesncsutmf commented
I agree. Currently we have to use a script to determine which OS or architecture is on the client machine. Problem with that, the client machine has to download all versions of the installer and not just the one that is relevant to that machine, increasing load on the k1000 and/or replication share, increasing the traffic on your network, and increasing the time it takes to download and install on a given machine. It also increases that chance on larger software packages that the source file to be uploaded to the k1000 is too big to upload over http.
This is a great idea. We will need to first blend the software and managed install functions into the software catalog in order to do this. This is something that will take a while to implement, but certainly has our interest.ncsutmf commented
If this gets implemented, it should be an optional setting on the managed install. We had an issue with Office 2010 where SP1 was applied causing the version to change, and the Kace agent tried to install Office again w/o SP1. We had to change our smart label for Office to not apply if Office was already installed. If this was feature was not optional, we would have office installing and uninstalling itself, probably until it reached the max attempts for each.
Great idea. Can folks also provide links to other vendors’ tools?
This is part of a long-term vision in the roadmap towards restoring a machine’s identity on the K1000 when rebuilt from the K2000, with incremental progress being made in each release.