Bindview RMS Console 8.5
[font="courier new"] Hi ,
[font="courier new"]
[font="courier new"] Currently I am working on "Bindview RMS Console 8.5" application.
[font="courier new"]Setup.exe calls around 10 MSI's and none of these Vendor MSI's are installing alone...
[font="courier new"]Has any1 worked on this application n do someone know the silent switch for this application?
[font="courier new"]Kindly help me...
[font="courier new"]
[font="courier new"]Thanks in advance...
[font="courier new"]
[font="courier new"]
[font="courier new"]
[font="courier new"]
[font="courier new"]
[font="courier new"]
[font="courier new"]
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
India_Repackaging
15 years ago
Hello Gege,
I have not worked on `Bindview RMS Console 8.5' however check if there is a single MSI which calls the others sometimes called as a bootstrapper.msi. Also create a verbose log by enabling the windows logging by setting the follwoing key HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx
This should help you analyse things better.
I have not worked on `
Reg_SZ: Logging
Value: voicewarmupx
This should help you analyse things better.
Posted by:
anonymous_9363
15 years ago
Your post really ought to have been made to the 'package Devlopment' forum. A moderator may move it there at some point.
It's unlikely that there'll be a single MSI: nested MSIs are frowned upon these days. Well, there were until the advent of v4.5 of the WI egnine but that's a whole different can of worms.
Anyway, the advice of using a log file to determine what's going on is sound. Personally, I would just extract the MSIs and deploy them separately. If, as you say, they won't install alone, I'm guessing that you get a message to the effect that the MSI must be run by the setup program? If so, try setting a property called ISSETUPDRIVEN with a value of '1' on the command line, e.g.:
...........MSIExec /i [name_of_MSI] ISSETUPDRIVEN=1 [any other switches you might want to use]
It's unlikely that there'll be a single MSI: nested MSIs are frowned upon these days. Well, there were until the advent of v4.5 of the WI egnine but that's a whole different can of worms.
Anyway, the advice of using a log file to determine what's going on is sound. Personally, I would just extract the MSIs and deploy them separately. If, as you say, they won't install alone, I'm guessing that you get a message to the effect that the MSI must be run by the setup program? If so, try setting a property called ISSETUPDRIVEN with a value of '1' on the command line, e.g.:
...........MSIExec /i [name_of_MSI] ISSETUPDRIVEN=1 [any other switches you might want to use]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.