Running SFTP from script but Task Scheduler does not like part of it.

Question

Hello,
I am trying to do some (not so) simple file copying using SFTP in this manner:
 1) Map a drive to the destination, the SFTP program will not accept UNC paths
 2) Use SFTP to copy the files to the target Server
 3) Write a Timestamped entry to a log file
 4) Remove the source files after copy
 5) Remove the drive mapping
Everything works but Step two and that only fails running from the Task Scheduler (W2K8 R2).  Running from the command line directly in PowerShell or using the Run box works fine all the way.
The sftp program is BitVise SSH Client using their log utility.  The makes the command line very complicated.
The line I use in the Scheduler is powershell "D:\Scripts\SFTP_TPCCommission.ps1" Dev  I have also tried using the -command parameter.  Again, it only does not work in the scheduler.
Here is how I invoke it:
$CmdLine = "`"D:\\Program Files (x86)\\Bitvise SSH Client\\logs\\`" sftpc " + $Server + " -pk=1 -cmd=`"put -o -lf Z:\" + $File + " /TPCCommissions`""
& log ($CmdLine)
I have also tried a Here String to do the same thing.  It works the same way.
$ArgText = @"
"D:\\Program Files (x86)\\Bitvise SSH Client\\logs\\" sftpc $Server -pk=1 -cmd="put -o -lf Z:\$File /TPCCommissions"
Any ideas?

Answer 1

In a batch file or at the command (not PS) line the command structure looks like this:
log "D:\\Program Files (x86)\\Bitvise SSH Client\\logs\\" sftpc <user@server> -pk=1 -cmd="put -o -lf Z:\<Source> /<Destination>"
The double slashes are requirement of the log program which calls the sftpc program with its command structure.
The double-quoted section after "-cmd=" is required.  The Z: drive is mapped because the SFTP program does not support UNC paths. (Stupid, but that is all I have to work with.
What you see in my post is just the part giving me trouble.  I am using PS to keep track of what I am copying to the destination and removing from the source and creating a timestamped log of that activity.
As to the comment about Task Scheduler, I am using it.  Like I said, it all works fine from anywhere but the Task Scheduler.