How to Restart a Remote Computer using PowerShell

Remote Management in Enterprise Environments

When you are managing a cluster of Windows Servers or hundreds of employee workstations in an Active Directory environment, walking over to a physical machine to press the power button is not an option. If a server requires an emergency reboot after installing a critical security patch, or if a user’s workstation has completely frozen, you need a way to force a restart over the network.

PowerShell provides a native, highly efficient cmdlet designed specifically for this purpose: Restart-Computer.

The Basic Remote Restart

To restart a remote machine, your IT workstation must have network connectivity to the target, and you must be logged into PowerShell with Domain Administrator credentials (or an account that is a member of the target machine’s Local Administrators group).

Open an elevated PowerShell prompt and execute the following command, specifying the hostname or IP address of the target machine:

Restart-Computer -ComputerName "FILE-SRV-01"

The command will reach out via Windows Management Instrumentation (WMI) or Windows Remote Management (WinRM) and instruct the server to begin a graceful shutdown process. Running applications will be given a chance to close, and users will be warned.

Forcing the Restart

If the remote server has completely hung, or if a user left a massive unsaved Excel document open on the screen, the graceful shutdown will halt, and the server will sit waiting indefinitely at a “Programs need to close” screen.

To prevent this and guarantee that the server reboots immediately, you must append the -Force parameter.

Restart-Computer -ComputerName "FILE-SRV-01" -Force

This acts like pulling the power cord. It instantly kills all running applications without saving data and forces the kernel to reboot.

Restarting Multiple Computers Simultaneously

If you have just pushed out a mandatory software update to an entire department and need to reboot 10 computers at once, you do not need to run the command 10 separate times. The -ComputerName parameter accepts arrays.

You can provide a comma-separated list of hostnames:

Restart-Computer -ComputerName "PC-01", "PC-02", "PC-03", "PC-04" -Force

PowerShell will establish simultaneous remote connections to all four machines and trigger the reboot sequence in parallel.

Monitoring the Reboot Process

If you are restarting a critical database server, you likely want to know the exact moment it comes back online so you can verify the services are running.

You can tell PowerShell to pause your script and wait for the remote machine to successfully boot back into Windows by using the -Wait parameter.

Restart-Computer -ComputerName "FILE-SRV-01" -Wait -For Wmi -Timeout 300

In this example, PowerShell triggers the reboot, and then sits quietly, continuously pinging the WMI service on FILE-SRV-01. The moment the server is fully booted and responding to WMI queries, PowerShell releases the lock, allowing your script to continue to the next step. If the server fails to boot within 300 seconds (5 minutes), the command will time out and throw an error.