This one stumps me, and it's only the second time I've used the Repackager, so maybe I'm missing something. I had an executable for a Microsoft Outlook plugin by a company called SugarCRM; the exe wouldn't install quietly, so I used the repackager to create an MSI.

Tested the MSI, it installed quietly, and the app appeared to be functioning the way it was intended.

We wanted to push this out via SMS and do some additional things--check for older versions, etc.--so I wrote a package in Wise, since that's the app I know how to create packages with.

At this point, all I'm doing with the Wise package is making an executable that installs the MSI. But when I install the executable on a test PC, the registry entries for the Sugar plugin are completely different than what they were when installing with just the MSI.

I've double- and triple-checked to make sure I'm not adding anything in the Wise package that would cause this, and I'm positive I'm not. But I have no explanation for why I'd see such dramatically different results in the registry based on whether I'm installing just the MSI, or the MSI wrapped in an exe made with Wise.

Just curious if anyone's seen this before or has any guesses as to how it's happening. Thanks.
0 Comments   [ + ] Show 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.


Could you give us an example of the before/after registry that changed?
Answered 02/03/2009 by: AngelD
Red Belt

Please log in to comment
Are you using a transform? Could be that it is applied sometimes but not others. I'd watch a verbose log on each to make sure the same actions are occurring when you run each way. Also it could be that launching the application can cause a lot of automated updates that make it appear different. As this is not an issue with the AppDeploy Repackager, I offer that you may get better attention for this particular problem in the Package Development forum.
Answered 02/03/2009 by: bkelly
Red Belt

Please log in to comment
Sorry it's taken me a few days to respond. Was working to get the package finished up for the production folk.

Bob, I'm not using a transform. Just a basic msiexec command to run the msi file. I'm going to do some more testing to see if I can isolate why the registry change is happening like it is.

AngelD, here are the correct registry entries if I install the app by running the MSI created with the repackager:
Windows Registry Editor Version 5.00
"DisplayName"="SugarCRM Outlook Plug-in"
"DisplayIcon"="C:\\Program Files\\SugarCRM\\SugarCRM Outlook Plug-In\\outlook_install.ico"
"UninstallString"="C:\\Program Files\\SugarCRM\\SugarCRM Outlook Plug-In\\Uninstall.exe"

And here are the entries if I install by making an exe with Wise, where all I'm doing is msiexec /i Sugar.msi:
Windows Registry Editor Version 5.00
Answered 02/06/2009 by: RonW
Third Degree Blue Belt

Please log in to comment
A bit confused.
This seems to have been added through an "EXE" installation.
And the below through an MSI.

So are you saying that "...\Uninstall\SugarOutlook" registry part is written by the MSI you've created with the appdeploy repackager?
Answered 02/06/2009 by: AngelD
Red Belt

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