How to Use Windows PowerShell ‘Invoke-Command’ to Run Scripts on Remote Computers

The Death of RDP

If an IT administrator needs to install a software patch, restart a frozen service, or check the registry on a server across the country, the traditional workflow involves launching Remote Desktop Connection (RDP), logging in, waiting for the graphical desktop to load, and manually clicking around.

If they need to perform that exact same task on 50 different servers simultaneously, RDP is completely impossible.

The modern, enterprise standard for remote Windows administration is PowerShell Remoting, driven by the incredibly powerful Invoke-Command cmdlet. It allows you to beam blocks of PowerShell code across the network, execute them on a remote machine using its CPU, and instantly pull the results back to your local terminal.

1. Executing a Single Command Remotely

Assume you are sitting at your desk, and you want to know exactly what time a remote server (named FILE-SRV-01) last rebooted. You don’t need to log in graphically. You simply run:

Invoke-Command -ComputerName FILE-SRV-01 -ScriptBlock { Get-Uptime }

PowerShell securely connects to FILE-SRV-01, executes the Get-Uptime command locally on that server, and returns the resulting object directly to your terminal screen.

2. Executing Complex Scripts (The ScriptBlock)

The true power of Invoke-Command lies in the -ScriptBlock parameter. You are not limited to one command; you can send entire scripts inside the curly braces {}.

Suppose you want to check a remote server to see if a specific folder exists, and if it does, delete it:

Invoke-Command -ComputerName FILE-SRV-01 -ScriptBlock {
    $target = "C:\Temp\OldCache"
    if (Test-Path $target) {
        Remove-Item $target -Recurse -Force
        Write-Output "Cache deleted successfully."
    } else {
        Write-Output "Cache folder not found."
    }
}

3. Passing Local Variables to Remote Machines

This is a major stumbling block for beginners. If you define a variable on your local computer, the remote server cannot see it. They are operating in different memory spaces.

If you try to run this, it will fail:

$serviceToKill = "PrintSpooler"
# THIS WILL FAIL:
Invoke-Command -ComputerName SRV-01 -ScriptBlock { Stop-Service $serviceToKill } 

To inject a local variable into the remote ScriptBlock, you must prefix the variable with the special $using: scope modifier.

$serviceToKill = "PrintSpooler"
# THIS WORKS:
Invoke-Command -ComputerName SRV-01 -ScriptBlock { Stop-Service $using:serviceToKill } 

4. Executing at Scale (One-to-Many)

This is where Invoke-Command replaces hours of manual labor with seconds of automation. You can pass an array of computer names to the cmdlet, and PowerShell will execute the script on all of them simultaneously in parallel background threads.

$servers = @("WEB-01", "WEB-02", "WEB-03", "WEB-04")

Invoke-Command -ComputerName $servers -ScriptBlock { Restart-Service IISAdmin }

This single command instantly connects to all four web servers at exactly the same time and restarts the web service on all of them, completing the entire operation in a matter of seconds.

Conclusion

(Note: For Invoke-Command to work, the remote machines must have WinRM (Windows Remote Management) enabled. This is usually configured globally via Active Directory Group Policy in enterprise environments).

By treating remote servers as parallel processing nodes, Invoke-Command transforms Windows administration. It eliminates the need for graphical RDP sessions, allowing administrators to execute diagnostic checks, software deployments, and system repairs across hundreds of machines with a single keystroke.