Service executable on a network path running as LocalSystem?
From: Edward Forgacs (edward.forgacs_at_optusnet.com.au)
Date: 12/01/04
- Previous message: William Stacey [MVP]: "Re: Is Strong Naming is Tamper-Proof?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 1 Dec 2004 13:02:59 +1100
While this sounds quite absurd, I know it is possible to get this to work.
Let me explain.
My "My Documents" folder is located at a network path because I use offline
files on my laptop. This means that all of my visual studio projects are in
a network location (this is how I want things to stay). Because it is a
"special" folder, however, this means that the SYSTEM account has full
control permissions to the network folder containing my documents..
For some time I have been debugging a service in which the executable was in
this network folder. The service started and worked perfectly.
Today I created a new a account on the domain. Since then nothing I have
tried will make the service start as long as the executable is in a network
folder and the startup type is set to LocalSystem.
If I move the execuable to a local drive, it works. If I change the security
permissions to make it use a domain acount, it works.
My question is, how the heck do I get it working again from a network path
with the startup type set to local system?
I need it this way because it *has* to be debugged from this network
location and it *has* to be deployed as LocalSystem. I don't want to switch
the logon type when it is deployed.
- Previous message: William Stacey [MVP]: "Re: Is Strong Naming is Tamper-Proof?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|