Hi - I am trying to install multiple instances with chained msi's with IS Basic MSI. Everything works on the first instance install, but the 2nd installation's msi's don't appear to be working (because they think they are already installed). Wha...
Alright - I have no idea why this would make a difference....In the Install Condition, I put back in "Not Installed" and all of a sudden it lays down the chained msi. What is going on here?OK - Apparently that was a fluke. Can't get it to work agai...
Thanks EJ. It helps a lot to understand what is going on behind the scenes.As far as multiple instances with chained msi's - I've been changing the product codes for the chained msi's with MsiViewModify scripts, but they never get installed on multi...
EJSchuiteman wrote:Hi,an easier way to change the name in Add/Remove Programs is to set property ProductName with the values you want. Make sure it executes in the Execute Sequence.In Custom Actions choose "New Set Property".Property Name: ProductNam...
Thanks Michael - I'm already ahead of you. I tried the overwriting the ProductCode in the ISChainPackage table.... but I couldn't get it working so I gave up on it since I didn't even know if it would do what I was trying to make it do :confused: ...
Another update:So I was able to get multiple instances with chained MSIs to install as I mentioned in my last post. Here is the basics.First, create as many transforms for each chained MSI as you have instances available of your installation. Here ...
