Pre-reqs only decide if the package can be installed or not. Since your desired state is that under a certain circumstance it is OK not to install the package then a pre-req is not sufficient.
One way instead is to look at the package in question being wrapped in a script so that the script decides the install or not for a version that is newer than the one in the package.Either case (install or not) would end in a success and allow things to continue.
I suppose you could avoid including the particular package in the bundle and instead set it as a dependency within one of the other package bundle entries. With a dependency you can be more specific about whether something should be installed or not, and if it isn't needed it does not cause a failure. The difficulty is that you cannot set dependencies on a package bundle, only on packages within the bundle hence the reason for not including it in the bundle.
Hope one of these helps.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality
I solved it this way. I created a simple batch file, which call the msiexec with the command I want. Then I made a distribution package and set a detection rule, so it won't install, if the package is already installed.
It is a pity that you can't add a detection rule for MSI Packages. I can understand MSI don't need a detection logic, but if i want to define somthing special.