gt; From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
> Sent: Wednesday, July 14, 2010 5:25 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Using Integrated security for connectionstring in
> CustomAction
>
> That would not hel
yprou [mailto:stelios.kyp...@formicary.net]
Sent: Wednesday, July 14, 2010 5:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Using Integrated security for connectionstring in
CustomAction
That would not help in my case though, since i am aiming to validat
Yes i eventually realised that in order to do this kind of action, you
must impersonate LocalSystem in you c# custom action.
But in order to do that, you must have a priviledge called:
"Act as part of the operating system" OR "SE_TCB_NAME".
LocalSystem has this priviledge, but no users, and it's a
Forget installation for a moment. How would you do this in any program?
On Wed, Jul 14, 2010 at 2:24 PM, Stelios Kyprou <
stelios.kyp...@formicary.net> wrote:
> That would not help in my case though, since i am aiming to validate any
> user defined values entered in the UI sequence.
> So in the c
That would not help in my case though, since i am aiming to validate any
user defined values entered in the UI sequence.
So in the case where the user chooses to run the "service to be
installed" as LocalSystem, and the connectionstring uses integrated
security, i want to make sure that the conn
The custom actions used in the WixSQLExtension do not have the
"no-impersonate" bit set, so they never run as LocalSystem (except in the
rare instance that the installation were being performed by a service
running as LocalSystem). Thus, if you are using the WiX-supplied SQL support
you must launch
6 matches
Mail list logo
