Sofware installs over and over and over
I've created many distributions including: Java, Flash, Reader etc. I push them to a single user or a group of users and it installs fine, but it will install the software over and over until I remove that user or group from the "deploy to listed machines/labels list." Is there any way to stop this, other than manually removing them, which defeats the purpose of pushing to a label? I'm sure it's something simple I'm missing.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
airwolf
13 years ago
If you tie the installers to Software Inventory items, then it will only attempt installing if the item is not already installed. If you created custom Software Inventory items, then you have to setup the custom rule to determine whether or not it is installed (i.e. a registry check in the Uninstall key).
Posted by:
hotta2000
13 years ago
Hi Jacksonc.
Do you have an earlier version of the software in your distribution ? Then you have to remove them from that distribution. You can also use custom inventory rules. Therefore you have to add a software item manually.
Do you have an earlier version of the software in your distribution ? Then you have to remove them from that distribution. You can also use custom inventory rules. Therefore you have to add a software item manually.
Posted by:
KevinG
13 years ago
The best practice is to manually install the software on a test machine that has the client installed. Let this machine check-in or do a force inventory update.
Now confirm that a Inventory Software Item has been automatically created by the check-in of the test machine. This assures that the Software Item is created correctly with the proper Vendor Name, Version...etc that can cause a MI to try install over an over again if not correct.
You attach your MI installer to this software item that was created for you. The common mistake is made by creating your own software item.
Now confirm that a Inventory Software Item has been automatically created by the check-in of the test machine. This assures that the Software Item is created correctly with the proper Vendor Name, Version...etc that can cause a MI to try install over an over again if not correct.
You attach your MI installer to this software item that was created for you. The common mistake is made by creating your own software item.
Posted by:
cmccracken
13 years ago
I use two labels with my distributions. My first label is a regular label that I apply to any PCs that need a software package (Ex. FinanceSoftware). I then create a smart label (NeedFinanceSoftware) that checks to see if the regular label is applied and if the software is installed. I then have my distribution install based on the smart label.
For some of my distributions, I know that all PCs will need the software (Ex. Antivirus) so I just have the smart label check to see if it is already installed.
What I like about it is that as soon as a PC checks in, it will automatically install its antivirus, then any additional software packages based on what labels I assigned. Once the software is installed, the "need" label is no longer valid, so it drops off on the next check-in.
Casey
For some of my distributions, I know that all PCs will need the software (Ex. Antivirus) so I just have the smart label check to see if it is already installed.
What I like about it is that as soon as a PC checks in, it will automatically install its antivirus, then any additional software packages based on what labels I assigned. Once the software is installed, the "need" label is no longer valid, so it drops off on the next check-in.
Casey
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.