No worries, unfortunately package management in Windows is in a pretty poor state as there is no first class manager like yum or apt. Chocolatey is pretty good and I would recommend using it if possible as it abstracts a lot of the information away to the point where you can just mention the package name and what state you want it to be but unfortunately some companies policies are not to trust external repositories.
Every msi installer and most installers (if they are designed properly) will create a key in *HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall* or *HKLM\:Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall* when on a 64-bit OS and the software is 32-bit. The value of this key is either a guid that is unique to the software and version or in the case of an executable is a string that is unique per software. These paths can be queries for the information you are looking for and the benefit of win_package is that you only need to supply the unique key of the package and in the case of an exe installed package the arguments to run the UninstallString silently. Unfortunately there are vendors out there who have packaged their software incorrectly and don't follow this standard and there is not much you can do but to put in some manual workarounds for these. Thanks Jordan -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/da219720-4e73-44ca-943d-337e2332b367%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
