CScript requires that any arguments being passed to a script be preceded by a slash. So I wouldn't expect any of the arguments you specified outside the script name and /nologo
to be forwarded to the script. So in general you would do something like this: cscript myscript.vbs //nologo /source:value /target:value
. These are named arguments. You can use positional arguments but these tend to not work as well when called outside the command line.
Another thing to consider is that if you're using Task Scheduler then there are 2 fields to be entered. The first field is the program name and that would be cscript
. The second field is the arguments where you specify all the arguments to the script host. This is where your stuff needs to go. But having mentioned that then be aware that MS doesn't recommend that you try to run these scripts directly. There are problems. The recommended approach, as discussed in this old blog post is to create a command file that calls the script host instead. This would also resolve your argument issue I believe.