Unfortunately, impersonation doesn't help when creating a new process.
A new process always inherits the security context of the parent process,
even if the thread starting the child process is impersonating. The only
way to create a child process under a different account (in 1.x) is to PInvoke
one of the CreateProcessWith* APIs.
In 2.0 you can add credentials to the Process class (but this assumes you'll
have the user's password - ugh).
--
Scott
http://www.OdeToCode.com/blogs/scott/ One option is to impersonate your application to run under that
windows account and then start the process. To know about
impersonation, check out this article.
http://support.microsoft.com/default...b;en-us;306158
"Christopher" <Ch*********@discussions.microsoft.com> wrote in message
news:A0**********************************@microsof t.com...
One of our ASP.NET Pages is starting a new Process using the Process
object.
When the process starts, it is started under the ASPNET User. We
tried editing the web.config file and the machine.config to operate
under other user accounts but our dynamically started process still
starts under
ASPNET.
How do you programatically start a process under a specific Windows
User Account? Thanks so much!
Christopher