I am trying to update a package done by someone else and while I have done a transform for the vendor msi and installed all prereqs seperatly the previuos packager has done a capture of the vendor msi and nested the 2 prereqs.
The first one works fine as it was installed from relative path but the other one Crystal 11 was nested in installation and now won't allow an uninstall or reinstall and if left the new install reads it as not being installed and trying to uninstall before dploying the update produces the "the system administrator has set policies to prevent this installation" even when uninstalling from ADD/Remove.
I have tried MSIZap and still no result. Tried all the other suggestions on google i.e. settings in group policy.
Any suggestion would be greatly appreciated.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I wouldn't waste my time trying to work round this mess but would build a separate MSI to remove everything, including the old installation data in the registry, then start again, doing it properly.
Answered 04/13/2010 by: VBScab
Red Belt

Please log in to comment
0
I thought that msizap removed all the installation registry keys, but that didn't resolve it either.
Answered 04/13/2010 by: SuccessSystems
Senior Yellow Belt

Please log in to comment
0
First things first. What I would do is completely redesign the package and do it right this time round (not gonna make any remarks about your predecessor, but have a guess what I think [;)])

As far as the prereq. Is it a nested MSI in the existing package? If so,if you can somehow make/get your hands on a package that can do a silent uninstall, you could change the uninstallstring (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) and the LastUsedSource (HKCR\Installer\Products\) for this package in the registry. This way the next uninstall will use your package and not whatever the old installer put in place. It's abit of a hack but it works....

Hope this helps

PJ
Answered 04/13/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
I tried the uninstall string but not the last used source. I also found that there were a lot of installer keys missing and no cached msi in C:\WIndows\installer. I will try your suggestion and let you know.
Thanks for all the input.
Answered 04/13/2010 by: SuccessSystems
Senior Yellow Belt

Please log in to comment
0
I thought that msizap removed all the installation registry keysIt doesn't get all of them, particularly those involved with Group Policy-pushed deployments.
Answered 04/13/2010 by: VBScab
Red Belt

Please log in to comment
0
Ok so installed the old package and the issue is that there is no entry in HKCR\Installer\Products for this package. there is an entry in the add remove. Any other suggestions?
Answered 04/14/2010 by: SuccessSystems
Senior Yellow Belt

Please log in to comment
0
My suggestion is still the same - start again.
Answered 04/14/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity