1 of 1 people found this helpful
Ok. This looks like a change introduced in BMC Installer v10.7.00. In order to install a package, we need to uninstall the previous installation of the same version of the package. If not, the package will be skipped. This wasn't the case with BMC Installer v9.6.00, where it installed over the top of any previous installation every time the setup.exe is run.
Also v10.7.00 doesn't allow installation under different folders (like C:\BMC Software), where v9.6.00 continued the installation after a warning message.
This was observed on Windows node with above BMC Installer versions also through deployable TSOM silent installer package.
Ugh... I can't say I "like" this post! ;-)
Could anyone from BMC comment on this? This will have deep consequences on deployments!
Me too! I've always appreciated the fact that you could go on installing new km versions on top of previous ones without uninstalling them.
Maybe its the only good thing of the Patrol installers and uninstall is a pain !
I'll stick with 9.6 installer forever if the new ones are really supposed to work that way !
Actually, from what I understood, it's the installation of the same version of the same KM on top of itself that is prevented by the installer. Normally, an upgrade should work, and that's good! ;-)
Correct Bertrand Martin. The issue is only when we install the same version over the top. If we remove/modify a KM file and want to reinstall the original back, we have to uninstall and install again when installing with Common Installer v10.7, unlike previous versions.