How can I manage Managed Installation with Patching task ?
I used to deploy a specific version of a software through a Software managed installation. This method was a bit heavy to support because I had to follow softwares updates and updates them through a new package at each release.
Recently, I've discovered the Patch module which contains most of the software I currently follow.
Because I want to automate softwares updates, Patch is a good solution but seems to be always overwritten by the Software Managed Installation version, which create an infinite cycle between installing update and reinstalling with the targetted version from the MI. I understand that there are two choices to avoid this situation :
- Create a custom inventory based on something else than the version of the software
- Use Catalog Managed Installation, which allow to install a software with no regard to the version because it's based on installed executables
I choosed to use the 2., but it seems that some of my computers act like if it was a Software MI (with a specific version) while others works as expected. Softwares are being overwrite despite of the fact that it's a catalog installation.
Do I miss something ?
I am not sure if you are missing something, but you seem to say that you can deploy the upgrade as a patch or as a MI, but if you deploy it as a patch the update gets overwritten or replaced by the MI? That would suggest that they are in fact different versions of the software, as the MI will run and expect to see the version of software to which it is attached appear.
I think you need to apply an element of control to your updates using labels, as an example....
You want to update software x from v3 to v4
You have a patch that appears to do that
You also have a managed installation that will install v4
You need to run the patch on a machine and note the version of the software app that then appears in inventory
It is also worth running the managed install on a different device and do the same, you may find they then display different versions.....
You will also need to note the behaviour of the MI, does it install v4 alongside v3 or does it remove all traces of v3?
Only then can you decide what path to take. Once you have that, create a smart label with criteria into which your target machines will fall and update.
N.B. The only time that patches and MI's will compete and create a cycle is if the application version they are both expecting is different!
Here is the KACE® Systems Management Appliance 11.1
Patching Catalog: Supported Operating Systems and Applications.
If may have to use a MI or scripting to deploy SW not supported by patching.