5 replies to this topic

[JWPP]

Guys

I'm trying to install an MSI on a PC which has locked down privileges. However, the MSI won't install because it says it needs "Administrator Rights". But I thought that MSIEXEC automaticaly gave the user admin rights......

Anyway, I'm needing to Nest an MSI within another MSI but I can't do it because of this error. Is there a way round, can I set the admin rights within the Parent MSI or change the user using the su.exe command.

Also, can I run two MSI's from the same MSI at the same time by usign a VB Script in CA....


Thanks in anticipation

John.

[pnunes]

Your problem may be dure to the "AlwaysInstallElevated" registry key which needs to be set. The workstations in question do not have this policy set to allow installers to have admin privileges.

Alternatively, I suppose you can use a vbscript outside of the MSI and use su.exe to gain the access you need. I have never tried this but I see no issues. Keep in mind that I believe this approach would not work if the VBScript is within another MSI. When MSI calls another MSI, it uses a different mechanism than if MSI calls VBScript which then calls another MSI. I believe msiexec.exe can only load one database at a time and the VBScript would try to load another DB. The CA which calls another MSI simply runs the "Execute" sequence and NOT the user interface (Client side) as a VBSCript would attemp.

I would structure the project as a VBScript which calls the first MSI with su.exe, does some error control, then calls the second. If you need the user interface of the first to "wrap" the second, then try having a VBScript invoke SU.exe for the first MSI, then this MSI would call the second using the MSI CA.

Here are some MSFT articles on the subject.

http://www.microsoft...dows....830.htm

http://www.microsoft...dows....553.htm

http://msdn.microsof...rary....wpw.asp

[JWPP]

Thanks for the indepth response.

The AlwaysInstallElevated unfortunatley was already set up so the solution you suggested there didn't work. Thanks anyway though.

I did have a fiddle with calling another MSI from within the first MSI by the method of SU.EXE but this fails as you said, but the way we're deploying apps is via 1 MSI therefore it's going to be hard to get this problem resolved.

If you could shed anyother light on the matter It'd be much appreciated.

Regards.

[Shridar]

I believe the info' provided in the article given below might lead you to find a solution!

http://www.wise.com/...?articleno=1278

[pnunes]

Did you try having a batch file or vbscript run su.exe which then runs your MSI which then runs the other MSI using the "Launch another .msi package" custom action (type 7, 23, or 39). Calling an MSI from another MSI is possible as long as you use this special Custom Action. Also, when using this action, the user interface sequence is not run in the second MSI, so you must either set defaults or pass in piblic properties.

[Shridar]

I have never tried invoking a second MSI from a main MSI. Sorry, I couldn't be of help. If i come across a solution, will get back.