Vendor MSI Custom Action
Deepanshu
April 3rd, 2009
How do we cope with vendor-MSIs that contain CustomActions needing LocalAdmin-rights?
By default most CustomActions run in User-context. Installer should have elevated privileges to install the application. If a custom action needs admin rights and it's in user context we can change it to system context the only point we should remember is that our MSI installation should be in user context so this custom will get executed properly without any issue.
Custom Actions
Custom actions are intended to run in both system and local user account. It's the scenario which takes the best call, to choose between them. For eg. creating a folder in C:\ will need system admin privilatges.., whereas creating a folder in a network share will need user privilages..bcos, the user will be having permissions to work with a network share and a system admin may not have the access.. Only a network admin would !!!
Check this link below, which explains on various Custom actions best practives.. Hope it proves helpfulk.
http://www.msigeek.com/2008/04/few-guidelines-and-best-practices-for.html
Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com
Would you like to reply?
Login or Register to post your comment.