Multiple distribution packages assigned to one software
The problem is that there are a lot of software applications out there that don't differentiate themselves once installed between 32 bit, 64 bit, or any of the OSs (i.e. 2003 vs. 2008) but have different installation packages depending on these items.
Shawn Dutton
shared this idea
-
Chris Henning
commented
Some time I have different keys for the same software.
-
Anonymous
commented
You really need a way to merge multiple software items into a single Item. You have the option already for Versions Installed but you do not give us a way to manage it in the users Interface.
-
Chris
commented
I can't believe this has been missing for two years. It is unacceptable to not have this feature, given how IT organizations are more and more often going to mingle 32- and 64-bit operating systems in their environment..
-
ncsutmf
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.
-
Nathan Hill
commented
I agree. We have had a few software packages that I've edited the title property in the MSI just to allow the kbox to differenciate.
-
Mikko Kauttu commented
Definately a must have feature
-
Lee Frith
commented
This is definitely interesting. Thumbs up
-
Shawn Dutton
commented
This causes us to have to create a bunch of custom inventory items, one for each OS or bit version.