How To Run a Custom Action with Local System Permissions in an .msi Package (305574)


The information in this article applies to:

  • Microsoft Windows Installer 1.1
  • Microsoft Windows Installer 1.2
  • Microsoft Windows Installer 2.0
This article was previously published under Q305574

SUMMARY

This article describes how you can use the MsidbTypeNoImpersonate flag to run a custom action with the local system permissions context.

MORE INFORMATION

If it is necessary to run your custom action when using the local system security context, set the attributes of the custom action in the CustomAction table to either 3072 (msidbCustomAction TypeInScript + msidbCustomAction TypeNoImpersonate) or 3328 (msidbCustomAction TypeInScript + msidbCustomAction TypeNoImpersonate + msidbCustomAction TypeRollback).

The custom action will not run with elevated privileges if the user who is running the application is not an administrator on the local computer and the Windows Installer package (.msi) is not managed. The only way for a custom action to be run with elevated privileges for a nonadministrator is to set the AlwaysInstallElevated policy for both the user and the computer.

REFERENCES

For additional information on setting the AlwaysInstallElevated policies, click the article number below to view the article in the Microsoft Knowledge Base:

259459 How To Allow Users Who Are Not Administrators to Install MSI Packages

For additional information on how to edit Windows Installer tables, click the article number below to view the article in the Microsoft Knowledge Base:

255905 How To Use the Orca Database Editor to Edit Windows Installer Files

Modification Type:MinorLast Reviewed:7/13/2004
Keywords:kbhowto kbMSIFAQ KB305574
©2004 Microsoft Corporation. All rights reserved.