Can the import agent monitor a shared folder or mapped drive that resides on another location other than where the import agent is installed?
Question
Question
Answer
Yes. For the monitored folder you can use \\ syntax if it is not a mapped drive or local drive.
For example: \\servername\sharedfolder. Where servername is the name of the server or that houses the shared folder you are looking at.
Note that you will have to start the Import Agent service with an appropriate Windows account. This account will need to have Windows access/rights to the folder you are trying to monitor. If Import Agent is starting with Local System then it will more than likely not have access to the shared folders or folders located on another server.
Hello, is this method still supported in Import Agent 12? When setting up a monitored folder starting with \\Server it says the path is invalid and won't allow the profile to be saved. Changing it to a local disk (e.g. C:\Temp) works fine.
Yes, it is. However, when using UNC paths, they have to be available to the user specified in the Import Agent service login. By default, the service uses Local System which cannot access other machines. You'll need to change it to a domain user with access to the specified path.
Hi Miruna,
Thank you for this, however the service is running as a service account which has access to the path in question - I've confirmed by logging on to the Import Agent server as the service account and accessing the path.
I raised case #26894 for the issue, and the issue is actually with the IA Config utility - it doesn't validated UNC paths that contain spaces as a valid path. Alex Huang has kindly raised bug #630247 for the issue, which will be addressed in the next release.
Cheers!
Dan