Re: Starting a process "cmd.exe" from within a service...
- From: mabra <mabra@home>
- Date: Thu, 06 Jul 2006 14:51:54 +0200
Hi !
Just a thought. I am not familar with the process properties in .Net 2.0 [what looks you are using].
Each started process needs some desktop and you are possibly on the way to start the new process in the same desktop, as the starter has. In case of the started process users identity do has less rights than the starter, it cannot access the startes desktop/winstation.
I found this starting processes with WMI, while I was logged on onto the console as an admin, I tried to start a visible process with less rights, which always fails for the mentioned reason. I used sysinternals winobj then to modify the security attributes on the consiole users dektop and this helped.
For process in .Net 2.0, I don't know.
As I said, just a thought.
Best regards,
Manfred
Marius wrote:
I'm running a serice under a local admin account. The service runs specific DOS commands (eg. "dir c:\") upon request using "cmd.exe". I create a ProcessStartInfo and enter the user credentials in the UserName, Password and Domain fields. The start the process using the ProcessStartInfo. However, running the process just hangs. I can see the "cmd.exe" process that has started (task manager) using the specific user credentials, but it just hangs..
If I do not impersonate the user in the service, all runs fine.
When I run the exact same service code as a console under the same credentials as the service, then the process runs and returns results. Any reason why the process would hang when running the service vs console?
- Prev by Date: Re: Bug in HttpWebRequest/Response Dispose() implementation?
- Next by Date: C++, unmanaged code
- Previous by thread: Re: Starting a process "cmd.exe" from within a service...
- Next by thread: RE: Password prompts when signing with smartcard
- Index(es):
Relevant Pages
|
