Task Schduler can't reference network drive
I have an issue with task scheduler and networked drives. I have a task that runs a perl script. This script references config files that are on a shared network drive. When I run the script manually or scheduled through TM, the config files are not utilized. If I move the config files to a local folder and reference them there, everything works fine. I've tried using different user accounts, including admin. I've made sure all permissions are set to full. The log files show completed tasks and in fact it does complete but because of the missing config files, the output formatting is incorrect. Appreciate any ideas or thoughts about what I'm missing.
February 13th, 2012 4:22pm

Instead of using a network drive, use the UNC path instead. With Windows 7, mapped drives are user based and are only active during an interactive session. UNC paths are always available--providing the servers are up and running. Don't use: z:\share\app.exe. Instead, use: \\server\share\app.exe.
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2012 4:25pm

Instead of using a network drive, use the UNC path instead. With Windows 7, mapped drives are user based and are only active during an interactive session. UNC paths are always available--providing the servers are up and running. Don't use: z:\share\app.exe. Instead, use: \\server\share\app.exe.
February 14th, 2012 12:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics