Scheduled Task - Copying files to remote computer

  • Thread starter Thread starter animedreamer
  • Start date Start date
A

animedreamer

I have a scheduled task in Windows XP that is calling a batch file to
copy files from one computer on my network to another. I wish to have
this task run under the system account, but I was having difficulty
doing this. The only way I could get it to work was if I first mapped
a drive to the remote computer and used this as the destination for the
files I am copying. Is there anyway I can have this task run without
first mapping a drive to the remote computer?
 
I have a scheduled task in Windows XP that is calling a batch file to
copy files from one computer on my network to another. I wish to have
this task run under the system account, but I was having difficulty
doing this. The only way I could get it to work was if I first mapped
a drive to the remote computer and used this as the destination for the
files I am copying. Is there anyway I can have this task run without
first mapping a drive to the remote computer?
Click to expand...

Run the task under an account that has appropriate access
right to the remote resource. The System account has no
such access (although your solution very neatly stepped
around this restriction, at the cost of embedding a password
in a batch file).
 
Well, I'm not mapping the drive from the batch file, so there is no
password in the batch file. What is confusing to me is that the task
WILL run using the system account after I mapped the drive (manually
from the console). So, if the system account has no such access, how
is it able to copy files via the mapped drive?
 
I was also wondering how come it worked with a mapped drive. You should get Error 5 on a mapped drive and "File not found" on a UNC path. I'd search the KB carefully on all NT products, there are articles explainng it and may be workarounds.
 
A theory on why without researching it. The service account logs on to the remote computer with null credentials. If mapped it may log on in a different way.

--
 
Well, I'm not mapping the drive from the batch file, so there is no
password in the batch file. What is confusing to me is that the task
WILL run using the system account after I mapped the drive (manually
from the console). So, if the system account has no such access, how
is it able to copy files via the mapped drive?
Click to expand...

I don't know, but why not doing it properly and running
the task under a suitable account?
 
Back
Top