Differences
This shows you the differences between the selected revisions of the page.
| guide_schedule 2022-05-24 | guide_schedule 2024-05-31 (current) | ||
| Line 11: | Line 11: | ||
| * [[guide_automation|Automate your operations using WinSCP scripting functionality]]. | * [[guide_automation|Automate your operations using WinSCP scripting functionality]]. | ||
| - | ===== [[win10]] Scheduling on Windows 10, Windows 8 and Windows 7 ===== | + | ===== [[win10]] Scheduling on Windows 11, Windows 10, Windows 8 and Windows 7 ===== |
| To add new scheduled task: | To add new scheduled task: | ||
| * Open //Task Scheduler//: | * Open //Task Scheduler//: | ||
| - | * Windows 10: Go to //Windows Start Menu > Settings//. In //Find a setting// box type "Task Scheduler". &win10 | + | * Windows 11: Go to //Windows Start Menu > All apps > Windows Tools > Task Scheduler//. Or just type //"Task Scheduler"// into the search box. &win11 |
| + | * Windows 10: Go to //Windows Start Menu > Windows Administrative Tools > Task Scheduler//. Or just type //"Task Scheduler"// into the search box. &win10 | ||
| * Windows 8.1: Right click Windows //Start// button and select //Control Panel//. In //Control Panel//, go to //System and Security > Administrative Tools > Schedule Tasks//. &win8 &wincp | * Windows 8.1: Right click Windows //Start// button and select //Control Panel//. In //Control Panel//, go to //System and Security > Administrative Tools > Schedule Tasks//. &win8 &wincp | ||
| * Windows 7: Go to //Windows Start Menu > Control Panel//. In //Control Panel//, go to //System and Security > Administrative Tools > Schedule Tasks//. &win7 &wincp | * Windows 7: Go to //Windows Start Menu > Control Panel//. In //Control Panel//, go to //System and Security > Administrative Tools > Schedule Tasks//. &win7 &wincp | ||
| Line 24: | Line 25: | ||
| * In //Add arguments// add appropriate WinSCP [[commandline#scripting|command-line]] parameters to execute the [[scripting#commands|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters). | * In //Add arguments// add appropriate WinSCP [[commandline#scripting|command-line]] parameters to execute the [[scripting#commands|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters). | ||
| * You should also add ''[[commandline#logging|/log]]'' parameter to turn on [[logging|session logging to file]]. | * You should also add ''[[commandline#logging|/log]]'' parameter to turn on [[logging|session logging to file]]. | ||
| - | * The resulting arguments may look like: \\ ''%%/log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"%%'' \\ Note that the command-line parameter ''[[commandline#scripting|/console]]'' was not specified, which makes ''WinSCP.exe'' not show the console window, so as not to disturb you while you are using your workstation. \\ You can have WinSCP [[ui_generateurl|generate the command-line template]] for you. | + | * The resulting arguments may look like (as a single line): <code batch,wrap>/log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"</code> Note that the command-line parameter ''[[commandline#scripting|/console]]'' was not specified, which makes ''WinSCP.exe'' not show the console window, so as not to disturb you while you are using your workstation. \\ You can have WinSCP [[guide_automation#generating|generate the command-line template]] for you. |
| * If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field. | * If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field. | ||
| * When done, click //Next//, review your options and confirm with //Finish//. | * When done, click //Next//, review your options and confirm with //Finish//. | ||
| Line 34: | Line 35: | ||
| * In advanced properties add appropriate WinSCP [[commandline#scripting|command-line]] parameters to execute the [[scripting#commands|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters). | * In advanced properties add appropriate WinSCP [[commandline#scripting|command-line]] parameters to execute the [[scripting#commands|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters). | ||
| * You should also add ''[[commandline#logging|/log]]'' parameter to turn on [[logging|session logging to file]]. | * You should also add ''[[commandline#logging|/log]]'' parameter to turn on [[logging|session logging to file]]. | ||
| - | * The resulting command may look like: \\ ''%%"C:\Program Files (x86)\WinSCP\WinSCP.exe" /log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"%%'' &winpath &win64 \\ Note that the command-line parameter ''[[commandline#scripting|/console]]'' was not specified, what makes ''WinSCP.exe'' not show the console window, not to disturb you while you are using your workstation. \\ You can have WinSCP [[ui_generateurl|generate the command-line template]] for you. | + | * The resulting command may look like (as a single line): <code batch,wrap>"C:\Program Files (x86)\WinSCP\WinSCP.exe" /log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"</code> &winpath &win64 Note that the command-line parameter ''[[commandline#scripting|/console]]'' was not specified, what makes ''WinSCP.exe'' not show the console window, not to disturb you while you are using your workstation. \\ You can have WinSCP [[guide_automation#generating|generate the command-line template]] for you. |
| * If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field. | * If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field. | ||