UAC Maintenace mode -ARP error
Hi
We have a app.msi file. There is no Setup.exe associated with msi.
The msi file is launched from custom executable with msiexec /i command.
The custom executable has manifest file embedded into it. When launched from vista machine which has the UAC enabled, our custom executable gets the consent from the user and launches the msi in elevated mode and this is working perfectly till now.
NOW WHEN THE USER TRIES TO LAUNCH MAINTENANCE MODE FROM ADD/REMOVE PROGRAMS, the first CA which is scheduled just after cost finalize in UI sequence is failing with error code 1721 with return value of 3.
This is pretty much straight forward as msi when launched from ARP will not run with elevated privileges and the CA is failing.
Is there a way when the installer is launched from Add/Remove programs, it should get the consent and launch the msi with elevated privileges ?
I know setup.exe will do this for us. (that it will get the consent and luanch)
Please provide me the possible solutions.
We have a app.msi file. There is no Setup.exe associated with msi.
The msi file is launched from custom executable with msiexec /i command.
The custom executable has manifest file embedded into it. When launched from vista machine which has the UAC enabled, our custom executable gets the consent from the user and launches the msi in elevated mode and this is working perfectly till now.
NOW WHEN THE USER TRIES TO LAUNCH MAINTENANCE MODE FROM ADD/REMOVE PROGRAMS, the first CA which is scheduled just after cost finalize in UI sequence is failing with error code 1721 with return value of 3.
This is pretty much straight forward as msi when launched from ARP will not run with elevated privileges and the CA is failing.
Is there a way when the installer is launched from Add/Remove programs, it should get the consent and launch the msi with elevated privileges ?
I know setup.exe will do this for us. (that it will get the consent and luanch)
Please provide me the possible solutions.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Firstly, the CA shouldn't be in the UI sequence in any event, since it would never run in a silent install.
Secondly, since it makes changes to the system, it should be in the deferred sequence. Once there, you can set it to run in the System context. If it requires property values, you'll need to pass them in the usual way, using the special CustomActionData property.
Secondly, since it makes changes to the system, it should be in the deferred sequence. Once there, you can set it to run in the System context. If it requires property values, you'll need to pass them in the usual way, using the special CustomActionData property.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
