I am not sure what the precise permission set it. That it runs on XP and not
on Win2003 could certainly be a permissionset issue, but if you (an
authenticated domain user?) have a different permission set on an XP
domain-joined machine vs a Win2003 domain-joined machine within the same
domain - and are therefore seeing this stuff while developing your app -
that's just hokey and your domain admin should fix that.
If you are planning on running your app as an NT Service, you should not be
running in a Local Admin context anyway. You want to run in LOCAL SERVICE or
NETWORK SERVICE, depending on what the service does. Don't elevate your
process's priv's to admin just to make it work.
"Daniel" <so*******************@yahoo.com> wrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
what permissions does a windows service need to execute another process?
System.Diagnostics.Process process =
System.Diagnostics.Process.Start(info);
just local administrator? any specific permitions?