Windows 10: Can I access a mapped network drive in task scheduler when user is logged off?

I have a python script that needs to grab files from a mapped network drive. The script works fine if I run it with the option "Run only when user is logged in", but will not run if the "Run whether user is logged in or not". It won't even work if I try to run it with the highest privileges and select to run only when the user is logged on. I get an error that says the network drive cannot be found. I am getting this error from python, but since it works fine with the other option checked I believe it has something to do with how Windows is running it.Is it impossible to access a network drive

:)

 

Task Scheduler Tasks copy file to mapped network drive fails

JR, the only other thing that springs to mind is to make sure that the scheduled task is being run as the user that is currently logged on. You note that you are doing this, but make sure that the user name is in the form of machine_name\user_name (assuming that you are in a workgroup and not a domain).

For confirmation, open a command prompt and run the command "whoami". The user name that you specify should look exactly like the output of that command.

If that user is not logged on when the scheduled task is run, then you may need to add the "net use" command as you noted earlier to establish the connection and map the P: drive.

- - - Updated - - -

Here is a sample of what my working task looks like (tested while I am logged on as PYROMANIA\hanness):









Here are the contents of the actual batch file:

Code:

 

Task Scheduler Tasks copy file to mapped network drive fails

JR, is it possible that when run via task scheduler you don't have task scheduler set to run the task as the currently signed in user? If the task is run under another account, then P: will not be already mapped for that account.

Sample:

 

Task Scheduler Tasks copy file to mapped network drive fails

I've read a dozen or so of the posts regarding Task Scheduler issues - so far haven't seen my issue solved.
Tasks which functioned more-or-less in W7 were saved, then imported to a new PC with a fresh install of W10. They seem to have imported intact. They all call batch files.
One of the commands in a batch file is to copy a file from the local C: drive to a shared network drive. The drive is already mapped for the logged-on user as "P:".
If exists c:\userdir\example.dat copy c:\userdir\example.dat p:\example.dat
I made a new BAT file that only has this command. When I run the bat file manually (double-click) it functions, but if I run the task which calls it, the action fails.
The Windows account has full privileges on the share (mapped network) drive and admin rights on the PC. What could be stopping the Task Scheduler-invoked bat file command from copying the file?
Thanks,
JR
Windows Version 10.0.17763