Windows installer security/credential question -


folks,

i've got strange issue @ moment visual studio 2010 built msi...

when run msi, performs few tasks, executes tool built - tool carries out more advanced work couldn't within custom task.

the issue here, when msi starts custom built tool, doesn't execute same credentials start msi (i.e. administrative login).

is there parameter can pass msi enforece this? or perhaps can pass credentials process when start it?

my process started using process process = process.start(procinfo) nothing fancy. i've noted ability pass in parameterised username/password/domain, vary depending on user installing - can extracted installer somehow?

any (or questions) welcomed.

dave

edit: clarity... i'm running msi under domain account, , want custom process run under 'context'. @ present, starts (regardless of whether start administrator or not) under system account (rather mydomain\me). i'm using windows server datacenter edition if helps...

i should add, think policy issue, i've no idea check/where check...

by default windows installer runs custom actions current user. if msi elevated, custom actions run elevated user.

please note if running msi administrator, doesn't mean custom actions have full administrator privileges. on vista or higher user can gain administrator privileges through elevation.

so if custom actions need administrator privileges, make sure use msidbcustomactiontypenoimpersonate flag run under local system account.

if not problem , need access current user data, can please give me more details?


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -