Hi Rohan,
As I mentioned on the
Termintaing the process problem thread, the "Terminate process" custom action will stop the processes running under all the users if it is executed with administrator privileges or it will stop only the current user's process if it is executed without administrator rights.
A custom action inherits the administrator rights from the package that launches it. So, we can consider three cases about how admin rights are set for a package and inherited by a custom action:
1. If the
"Run as administrator" option is set for a package, the UAC will prompt at the beginning of the installation and all the custom action will inherit the admin rights.
2. If the the
"Run as administrator" option is not set for the package, but the package is installed
"per-machine", the UAC will prompt when the "Install Execution Sequence" starts (on the Progress dialog) and all the custom actions added on the "Install Execution Stage" will inherit admin rights.
3. If the the
"Run as administrator" option is not set for the package and the package is installed
"per-user", the UAC will not prompt for that package and no custom action will inherit admin rights.
Best regards,
Eusebiu
FOLLOW US
Get the latest news in Application Packaging