Services with desktop interaction and access to remote shares issue

[Joseph Whalen]

I have a bit of an issue I'm trying to resolve. I have two systems one
running windows server 2003 the other running windows 2000 server. I
have a service that runs on the windows server 2003 that requires
interaction with the desktop. As a result, it must be run as a local
system account. However, the service relies on a shared drive on the
windows 2000 server in order to function correctly. The problem I'm
encountering is that I can not connect to the remote share without
authentication because the account I'm running the service as is a local
account. So I either have to sacrifice the desktop interaction or the
remote share.

Previously on a Windows2000 only environment there was a registry
setting you could enable that would allow no session connections to the
remote share. While there are obvious security concerns with
non-authenticated shares, this solved this issue brilliantly. In the
environment I'm working in, the security issues are less of a concern
then are is the functionality of having the GUI and the remote share.
With the introduction of Windows server 2003 this registry hack no
longer works.

Does anyone have any ideas out there that would help me to accomplish my
goal of having a service with desktop interaction and access to a remote
share on a domain?

 

[Dave Patrick]

This may help.

http://www.microsoft.com/resources/...dowsServ/2003/all/deployguide/en-us/58643.asp

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I have a bit of an issue I'm trying to resolve. I have two systems one
| running windows server 2003 the other running windows 2000 server. I
| have a service that runs on the windows server 2003 that requires
| interaction with the desktop. As a result, it must be run as a local
| system account. However, the service relies on a shared drive on the
| windows 2000 server in order to function correctly. The problem I'm
| encountering is that I can not connect to the remote share without
| authentication because the account I'm running the service as is a local
| account. So I either have to sacrifice the desktop interaction or the
| remote share.
|
| Previously on a Windows2000 only environment there was a registry
| setting you could enable that would allow no session connections to the
| remote share. While there are obvious security concerns with
| non-authenticated shares, this solved this issue brilliantly. In the
| environment I'm working in, the security issues are less of a concern
| then are is the functionality of having the GUI and the remote share.
| With the introduction of Windows server 2003 this registry hack no
| longer works.
|
| Does anyone have any ideas out there that would help me to accomplish my
| goal of having a service with desktop interaction and access to a remote
| share on a domain?