How to run a script on many Windows PCs at once

In the RemoteAccessApp Console on Windows, select several PCs on the Devices page, right-click and choose Run a command. Type a PowerShell or Command Prompt command, run it, and you get each PC's output and exit code side by side, so you can see at a glance where it worked.

It follows the same consent as the mouse and keyboard: each PC asks the person there to allow it unless unattended access lets you in, and commands only run while Allow remote control is on at that PC. It needs Windows 10 version 1809 or later on the PCs. For one command right now, that's all you need.

To work on several screens at once rather than send a command, see how to control multiple computers at once with mirrored mouse and keyboard. There's a longer look at the free tools, with processes, services and logs side by side, in how to manage multiple Windows computers remotely.

ProManagement, on the website dashboard and in the Windows app, is for jobs you'll repeat or want done while you're away. A task is what to do (run a script, restart, Windows updates, or install and update apps with winget); running it on some PCs makes a job, where each PC reports its own result; a schedule runs a task by itself; and tags name groups of PCs, like "office" or "front desk". It's one part of how to manage multiple computers from one place.

A restart can even start from chat: with the Discord and Slack commands, /pc restart asks you to confirm, then runs as a normal Management restart with the same notice at the PC.

1. 1

   Step 1: Write the script, or pick one

   Open Management and the Scripts tab. Create a script, say whether it's PowerShell or Command Prompt, and file it in a group with tags if you like. It's the same library as the SSH terminal's scripts, in the app and on the website.

2. 2

   Step 2: Tag your PCs

   On the PCs tab, give PCs tags such as office or reception. PCs you tag later join any schedule that targets the tag.

3. 3

   Step 3: Choose Run a task

   Pick what to do (your script), on which PCs (tags, single PCs or both) and when: now, or on a schedule. Run on PCs… on the Scripts tab starts the same flow with the script filled in.

4. 4

   Step 4: Check the command and the PCs, then confirm

   The last step shows the exact command and every PC that will run it. Nothing starts, and nothing is saved, until you confirm. PCs that can't run it, such as one whose Agent needs an update, are left out and say why.

5. 5

   Step 5: Follow each PC on the Jobs tab

   Each PC moves from queued to running and then done, failed or skipped, with its output. A PC that's offline shows waiting for the PC and gets the job when it's back, for up to 24 hours.

6. 6

   Step 6: Save it as a quick task

   Choose Save as quick task to keep the script, its PCs and its timing as a one-click shortcut on the Overview. Tapping it fills in Run a task again, so you still see the command before anything runs. Scripts and quick tasks are in the roundup of what's new in RemoteAccessApp in October 2026.

A schedule runs a task once, daily, weekly, when the PC starts, when someone signs in, or on a cron expression. It can use your time zone, any other one, or each PC's own time zone, to run at 3:00 wherever each PC is.

Each PC keeps its schedules and runs them on time even when it can't reach our server. If a PC is off at that time, the run is skipped and shows as missed, or, if you choose, runs once when the PC is back within 24 hours. Change a script that a schedule uses and the editor warns you first; the schedule runs the new version from its next run. Maintenance windows keep updates, restarts and app changes to quiet hours you choose. For a real example, read a week of remote IT help for a five-person office, where one scheduled job checks for Windows updates and updates apps on all five PCs, kept to the evening by a maintenance window.

• You always see the exact command and the list of PCs before a job runs, and nothing runs until you confirm.
• The person at each PC is asked to allow a job and sees the command, unless unattended access lets your own account in (your PC, two-step verification on). No answer in 5 minutes counts as a no.
• Jobs that change a PC are skipped where remote control is turned off.
• Every job shows a notice at the PC and goes into that PC's activity log.
• A restart gives the person at the PC at least a minute's notice, which they can postpone.
• In a team, only people whose permissions on a PC include management jobs can run them there.

• Try it on one PC first, then the rest.
• Make it safe to run twice: check before you change something, so a second run does no harm.
• Exit with 0 on success and anything else on failure. The Jobs tab shows each PC's exit code, so failures stand out.
• Print a short line saying what it did. The end of each PC's output is kept with the job.
• Don't put passwords in scripts. Outputs are stored encrypted for 30 days, but a script is the wrong place for a secret.

For Linux servers, the same idea works over SSH: in the Windows app's Scripts & History panel (Ctrl+Shift+S), run one script on many saved hosts at once, free. See remote console access.