2

I have a Windows service that monitors remote shares for job control and job output files and processes and moves files to archive folders.

My best solution so far is using methods available in the System.IO namespace (like Directory.Exists(), File.Move(), etc) to access and move these files.

The issue with this approach is that if the remote computer is not in a domain (which it is not), my service that performs these operations must run under a user account that also exists on the remote (Windows) computer, and the permissions must be set accordingly for the share and the file system objects on both the remote and the local computers.

I am concerned about issues that might arise down the road if the environment changes because people are not aware of these dependencies. I'd much rather build a more robust solution. Do you have suggestions?

cdonner
  • 37,019
  • 22
  • 105
  • 153

1 Answers1

1

You would map the network path by using NetUseAdd, WNetAddConnection2 one of the variants.

http://pinvoke.net/default.aspx/netapi32.NetUseAdd

Nate Bachmeier
  • 26
  • 2
  • Interesting. I still have this account around somewhere and I am using an impersonation approach, so it works. It seems that NetUseAdd along with a drive mapping might not require this. – cdonner Mar 05 '13 at 16:41