Network folder path issue

[VirginiaJenkins (imported)]

Hello,

I am having issues when using a task that executes a .cmd file on a network share. For whatever reason, and it could be something with corporate policy, I am only able to use the UNC path sporadically when pointing to the share. If I browse to the folder using my map drive, it works correctly. The problem is that anytime my computer is rebooted, robotask doesn't recognized that the drives have been mapped again on startup. Because of this, all jobs that I have created that point to a folder on a network share fail. I have to go in and browse out to each folder again to get the task to recognize it again. This is becoming a huge problem because I have so many jobs now. It isn't feasible to go in and remap each job every time my computer reboots. Is there a way to correct this?

Please help.

I didn't find the right solution from the Internet.

Thanks

[TopManFL (imported)]

I had no idea why this was here until I saw Paolo's edit. It's a cute way to spam a group with an embedded link. Looks real enough to leave and dangerous enough to remove the link.

[Paolo]

​Exactly. And it was a first post.