Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Vendor MSI Custom Action

Created: 03 Apr 2009 | 1 comment
Deepanshu's picture
Deepanshu
+2 2 Votes
Login to vote

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.

blog entry Filed Under:
, ,

Comments

R-Vijay's picture
10
Jul
2010
2 Votes +2
Login to vote
R-Vijay

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 helpful.
 

Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
258,782