KACE Product Support

If the software item that the MI is tied to is still being reported in inventory then you would have to find a way of removing that item from inventory first.

1) If you can pinpoint the condition that is causing it not to work AND you are able to capture that condition as a file or a registry entry then you could use a custom inventory rule to create a software item that represents this condition and then tie a near-duplicate MI to that software item. When this MI is installed the condition will be remedied.

2) If uninstall/reinstalling works to resolve it then you could disable the installation MI; deploy an MI that does a removal; disble the remove; re-enable the installation MI

3) If an over-install works then you could script the removal of the registry key used to detect software installations. [link]http://support.microsoft.com/kb/314481[/link]. When this is done the sofware will not appear in inventory and the MI will be redeployed.

A very simple Tweak that you can perform is to Create a New Software Item under Software Tab, supply the different software details, ie. Type the (Title or version) slightly different then the actual, upload the installation files again and create the MI using this Software Item, change deployment attempts to value 1 and deploy it to selected machines or label. You may use this item again and again by enabling or disabling it. [;)]

Afzal is assuming that an over-install works. I would say it is practical for one-offs, but not large re-deployments.

You are Right! I am assuming in practical scenario problem should occur on limited number of machines. I wonder why it is not practical if we select Max attempts value to one(1) for large deployments.