Hi,

I am currently working with an application which is msi. The client has requested to add secedit command to configure an security settings. But when i try to run the script with admin account it works but when i try to run with standard users it si not working. Now my doubt is does secedit account requires admin rights for installation .If so what should i do to add to execute the same script in msi?

Kind Regards,
Yuvi
0 Comments   [ + ] Show Comments

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.

Answers

0
in application packaging terms hope you do understand what "locked - down environment" means

admin user - admin rights
standard users - restricted rights in a locked down environment

you just need to run your secedit script as a custom action in your msi

immediate execute
after install finalize
Not Installed as the condition
type 34 custom action
Answered 07/24/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment
0
A deferred Custom Action must execute between the InstallInitialize and the InstallFinalize action.
For Vista and above you must add the msidbCustomActionTypeNoImpersonate bit (In-Script Execution Options) to the CustomAction.Type column field due to UAC, this is of course recommended for all deferred custom actions for any operating systems.
Answered 07/24/2010 by: AngelD
Red Belt

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