Skip to main content

How to Schedule a Task on a Remote Computer in Batch Script

Automating routine maintenance, such as system reboots, script execution, or log clearing, often requires scheduling tasks on servers. Instead of connecting to each server individually and using the graphical Task Scheduler, you can use Batch scripts to rapidly deploy scheduled tasks across your network.

In this guide, we will learn how to use the built-in schtasks command to create, run, and delete scheduled tasks on remote Windows computers.

The schtasks Command​

schtasks.exe is the powerful command-line equivalent to the Windows Task Scheduler UI. It allows an administrator to create, delete, query, change, run, and end scheduled tasks on a local or remote computer.

To interact with a remote computer, we use the /S switch followed by the computer name or IP address.

Basic Syntax for Remote Creation​

schtasks /Create /S RemoteComputerName /TN "TaskName" /TR "CommandToRun" /SC ScheduleType [Options]
  • /S system: Specifies the remote system to connect to.
  • /TN taskname: The name of the task.
  • /TR taskrun: Specifies the program or command that the task runs.
  • /SC schedule: Specifies the schedule type (e.g., MINUTE, HOURLY, DAILY, WEEKLY, ONCE, ONSTART, ONIDLE).

Creating a Scheduled Task Remotely​

Let's assume we want to schedule a script (C:\Scripts\UpdateInventory.bat) to run on a remote server (Server01) every day at 2:00 AM.

Example 1: Basic Daily Task​

@echo off
setlocal

set "TARGET_PC=Server01"
set "TASK_NAME=DailyInventory"
set "SCRIPT_PATH=C:\Scripts\UpdateInventory.bat"

echo Creating scheduled task on %TARGET_PC%...

schtasks /Create /S "%TARGET_PC%" /TN "%TASK_NAME%" /TR "%SCRIPT_PATH%" /SC DAILY /ST 02:00 /F

if %ERRORLEVEL% equ 0 (
    echo Task '%TASK_NAME%' successfully created on %TARGET_PC%.
) else (
    echo Failed to create task. Check network and permissions.
)

endlocal
pause

Specifying Credentials (Crucial Step)​

By default, schtasks assumes the task will run under the context of the user currently logged into the remote machine. For automated server tasks, you generally want them to run regardless of who is logged in, and under a specific service account (or the SYSTEM account).

To do this, use the /RU (Run As User) and /RP (Password) switches.

Example 2: Running as the SYSTEM Account

Running as SYSTEM is highly common for administrative scripts because it doesn't require a password (meaning you don't have to embed plain text passwords in your batch file), and it runs whether anyone is logged in or not.

@echo off
setlocal

set "TARGET_PC=FileServer02"
set "TASK_NAME=WeeklyBackup"
set "SCRIPT_PATH=C:\BackupScripts\RunBackup.exe"

schtasks /Create /S "%TARGET_PC%" /TN "%TASK_NAME%" /TR "%SCRIPT_PATH%" /SC WEEKLY /D SUN /ST 23:00 /RU "SYSTEM" /F

if %ERRORLEVEL% equ 0 (
    echo Task '%TASK_NAME%' successfully created on %TARGET_PC%.
) else (
    echo Failed to create task. Check network and permissions.
)

endlocal
pause

Running, Querying, and Deleting Tasks Remotely​

Once a task is created, you may need to manage it.

1. Running a Task Immediately​

Sometimes you can't wait for the schedule and need to trigger the task now.

schtasks /Run /S "Server01" /TN "WeeklyBackup"

2. Querying a Task​

To check if a task exists or see its state (Ready, Running, Disabled).

schtasks /Query /S "Server01" /TN "WeeklyBackup"

3. Deleting a Task​

To remove a task you no longer need. The /F flag forces deletion without prompting for confirmation.

schtasks /Delete /S "Server01" /TN "WeeklyBackup" /F

Handling Permissions​

Executing schtasks /S against a remote computer requires the script to be run by an account with Administrative privileges on that target computer.

If you are running the script as a standard user but need to authenticate to the remote machine as an Admin, you can use the /U and /P flags for the schtasks command itself (this authenticates the connection, not the user the task runs as).

Wrong: Embedding passwords in clear text for the connection is incredibly insecure.

schtasks /Create /S Server01 /U Domain\Admin /P P@ssword123 ...

Correct Approach: Let the script prompt for credentials if necessary, or rely on scheduled tasks running under secure service accounts to deploy other scheduled tasks.

Troubleshooting Common Errors​

Error: Access Denied​

You do not have administrative rights on the remote machine. Verify you launched your command prompt "As Administrator" with an appropriate account.

Error: The Network Path was not found​

The Remote RPC service is disabled on the target, the firewall is blocking file/print sharing (TCP 445), or the machine is simply offline.

Note on Mapped Drives​

When scheduling a task, remember that it runs in its own context on the remote machine. If the task runs as SYSTEM, it does not have access to mapped network drives created by the user. If your scheduled script needs to access network locations, it must use UNC paths (\\server\share) and the computer account (e.g., DOMAIN\Server01$) must have permissions on that share.

Conclusion​

The schtasks command is an indispensable tool for network administrators. By combining it with Batch scripting variables and loops, you can rapidly configure uniform scheduled tasks (like log rotations or standardized maintenance scripts) across dozens or hundreds of remote computers from a single central console. Always remember to use the /RU SYSTEM switch for non-interactive administrative tasks to avoid password management headaches.

Table of Contents