Hi,
I have a scenario where we need deploy an installer with one set of properties stamped in the MSI (via writing directly into the MSI in an Orca-type approach) and then if the admin finds the settings they applied in the properties were wrong they re-edit the same MSI and install that.

This of course casues the old 1316 error as we cannot guarantee the admin saves the MSI under the same name and the original MSI file has long gone.

The question is, how do i reinstall/repair the msi with the same productcode/packagecode/upgradecode and apply different properties?

Regards

Paul
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
Presumably this then is a tidy-up exercise being run from an admin workstation? In that case, it strikes me that a scripted approach would be best: just uninstall what's there via scripted calls to the Installer engine and re-install by running MSIExec against the new MSI. Some judicious use of MSIZap from the SDK would probably help.

Unless I've completely misunderstood, of course...
Answered 10/14/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi,

Thanks for the reply, the whole process needs to be seamless, scripting it would be great but to give you a little more background our product basically generates "Agent" installers from a central console, this happens every time an update to the Agent product is available.

What we have found is that some admins do not test their agent installers prior to deployment to ensure the settings are correct, so sometimes the agent never reports back to the console, the settings for the agent are stamped in the MSI as part of the generation and the admin has the option to restamp the very same agent installer if they got the settings wrong (same binaries and codes, just different properties).

All they have is one msi, we have to make this as easy to use as possible therefore no external scripts, so they should hopefully be able to repair/reinstall with new MSI and inherit properties.

I think this may go against the whole "make a change - update the version" concept, but I am in the business of breaking the rules :)

Regards

Paul
Answered 10/14/2008 by: HotSpot
Orange Senior Belt

Please log in to comment
0
ORIGINAL: HotSpot
What we have found is that some admins do not test their agent installers prior to deployment
Forgive me, but to my mind, the simpler route is to 'educate' your admins. You're going to be jumping through all these hoops, simply because they're too bone idle to check their work?!?
Answered 10/14/2008 by: VBScab
Red Belt

Please log in to comment
0
We have learnt the hard way that not all Admin pay attention to big red letters, but it may be the best way to do this as I don't fancy doing something that is against the norm of an fragile technology.

Cheers!

Paul
Answered 10/14/2008 by: HotSpot
Orange Senior Belt

Please log in to comment
0
you may want to search out John's approach of using an XML/WIX approach

i think he's @ http://johnmcfadyen.spaces.live.com/
Answered 10/14/2008 by: kiptek
Second Degree Green Belt

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