Managing a Windows server means dealing with tasks that need to run consistently, including disk cleanups, health checks, log rotations, and backups. PowerShell automation on Windows VPS makes this reliable by letting you run those jobs on a schedule, without manual steps, and with clear logs for every run.

PowerShell includes built-in commands for scheduling tasks, saving logs, and handling errors. You can set it up once, and then your server runs the job automatically.

In this guide, you will learn to set up a real automation workflow on a Windows VPS, from writing the PowerShell script and enabling clean logging, to creating a scheduled task that can run even when no one is signed in.

Prerequisites for PowerShell Automation on Windows VPS

You will need a Windows VPS running Windows Server 2019, 2022, or newer to follow this guide. If you want to purchase a reliable Windows VPS, you can check PerLod Hosting to check the plans and offers.

Once you accessed your Windows VPS, open PowerShell as Administrator and confirm the execution policy allows your scripts to run:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine

RemoteSigned allows locally created scripts to run without signing. If the script is downloaded from the internet, it must be signed. You only need to do this once per server.

Create the PowerShell Automation Script

You must create the folder that will hold your scripts. To do this, you can use the commands below:

New-Item -ItemType Directory -Path "C:\Scripts" -Force
New-Item -ItemType Directory -Path "C:\Logs\Maintenance" -Force

Then, create the script file at C:\Scripts\Maintenance.ps1. This example will check disk usage and clean up temp files, which are two universal tasks on any Windows VPS:

# C:\Scripts\Maintenance.ps1

#region --- Logging Setup ---
$LogDir  = "C:\Logs\Maintenance"
$LogDate = Get-Date -Format "yyyy-MM-dd"
$LogFile = "$LogDir\maintenance_$LogDate.log"

if (-not (Test-Path $LogDir)) {
    New-Item -ItemType Directory -Path $LogDir -Force | Out-Null
}

Start-Transcript -Path $LogFile -Append
#endregion

#region --- Log Helper Function ---
function Write-Log {
    param (
        [string]$Message,
        [ValidateSet("INFO", "WARN", "ERROR")]
        [string]$Level = "INFO"
    )
    $timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
    Write-Output "[$timestamp] [$Level] $Message"
}
#endregion

#region --- Main Logic ---
Write-Log "Maintenance script started."

# --- Disk Usage Report ---
$drives = Get-PSDrive -PSProvider FileSystem
foreach ($drive in $drives) {
    $usedGB = [math]::Round($drive.Used / 1GB, 2)
    $freeGB = [math]::Round($drive.Free / 1GB, 2)
    Write-Log "Drive $($drive.Name): Used=${usedGB}GB  Free=${freeGB}GB"
}

# --- Temp File Cleanup (files older than 7 days) ---
$tempPaths = @("C:\Windows\Temp", $env:TEMP)
foreach ($path in $tempPaths) {
    if (Test-Path $path) {
        Get-ChildItem -Path $path -Recurse -Force -ErrorAction SilentlyContinue |
            Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-7) } |
            Remove-Item -Recurse -Force -ErrorAction SilentlyContinue
        Write-Log "Cleaned temp files older than 7 days in: $path"
    }
}

# --- Log Rotation (delete logs older than 30 days) ---
Get-ChildItem -Path $LogDir -Filter "*.log" |
    Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-30) } |
    Remove-Item -Force -ErrorAction SilentlyContinue
Write-Log "Log rotation complete. Removed logs older than 30 days."

Write-Log "Maintenance script completed."
#endregion

Stop-Transcript

Two things handle logging in this script:

• Start-Transcript: Saves everything the script prints, including errors and warnings, into a log file. With -Append, new runs add to the same log instead of replacing it.
• Write-Log: Prints your own messages with a timestamp and level (INFO/WARN/ERROR). Because it uses Write-Output, those messages also get saved by Start-Transcript.
• Stop-Transcript: Stops logging and closes the log file. Put it at the end of the script.

The log file for a run on a specific date would be saved as:

C:\Logs\Maintenance\maintenance_2026-02-24.log

Create the PowerShell Scheduled Task

At this point, you can run the script automatically on a schedule. You can create a Windows scheduled task with PowerShell, so your script runs at the exact time you want and keeps working even when no one is logged in.

Scheduled tasks in PowerShell are built from four components, including Action, Trigger, Principal, and Settings, then registered as a single task.

You must define the components and register the task.

Define the Action

The action tells Task Scheduler what to execute. You can use:

$action = New-ScheduledTaskAction `
    -Execute "powershell.exe" `
    -Argument "-NonInteractive -NoProfile -ExecutionPolicy Bypass -File `"C:\Scripts\Maintenance.ps1`""

Option explanation:

• -Noninteractive: Prevents the script from hanging on prompts.
• -NoProfile: Skips loading the user profile and speeds up startup.
• -ExecutionPolicy Bypass: Overrides execution policy just for this run.
• -File: Specifies the script path to execute.

Define the Trigger

In this step, you must set when the task runs. Common examples include:

# Daily at 2:00 AM
$trigger = New-ScheduledTaskTrigger -Daily -At "02:00"

# Every Sunday at 3:00 AM
# $trigger = New-ScheduledTaskTrigger -Weekly -DaysOfWeek Sunday -At "03:00"

# Once at a specific datetime
# $trigger = New-ScheduledTaskTrigger -Once -At "2026-02-25 06:00"

Define the Principal

The principal controls which account runs the task and at what privilege level. To do this, you can run:

$principal = New-ScheduledTaskPrincipal `
    -UserId "SYSTEM" `
    -LogonType ServiceAccount `
    -RunLevel Highest

• -UserId “SYSTEM”: Runs as the built-in SYSTEM account and no password needed.
• -LogonType ServiceAccount: Runs whether or not a user is logged in.
• -RunLevel Highest: Grants full administrator privileges to the task.

Configure Task Settings

At this point, you must set task settings like time limits, retries, and what happens if the server is offline when a run is scheduled. To do this, you can use:

$settings = New-ScheduledTaskSettingsSet `
    -ExecutionTimeLimit (New-TimeSpan -Hours 1) `
    -RestartCount 3 `
    -RestartInterval (New-TimeSpan -Minutes 5) `
    -StartWhenAvailable

• -ExecutionTimeLimit: Kills the task if it runs longer than 1 hour.
• -RestartCount 3: Retries up to 3 times on failure.
• -RestartInterval: Waits 5 minutes between retries.
• -StartWhenAvailable: Runs the task immediately if a scheduled start was missed.

Register the Task

In this step, you can create the actual PowerShell automation on Windows VPS. You need to register everything as a named task so the system can run your PowerShell script automatically.

Register-ScheduledTask `
    -TaskName "NightlyMaintenance" `
    -Action $action `
    -Trigger $trigger `
    -Principal $principal `
    -Settings $settings `
    -Description "Nightly disk check and temp file cleanup" `
    -Force

The -Force flag replaces the task if it already exists with the same name, so you can run the command again to update the task without getting errors.

Manage Scheduled PowerShell Tasks

Once the task is created, you can check its status, run it on demand, or disable it temporarily. In this step, you can use these commands to view, run, disable, enable, and remove your scheduled tasks.

List all scheduled tasks:

Get-ScheduledTask

Check a specific task’s status and last run info:

Get-ScheduledTask -TaskName "NightlyMaintenance" | Get-ScheduledTaskInfo

Run the task immediately without waiting for the trigger:

Start-ScheduledTask -TaskName "NightlyMaintenance"

Disable a task temporarily:

Disable-ScheduledTask -TaskName "NightlyMaintenance"

Re-enable it:

Enable-ScheduledTask -TaskName "NightlyMaintenance"

Remove the task permanently:

Unregister-ScheduledTask -TaskName "NightlyMaintenance" -Confirm:$false

Get-ScheduledTaskInfo shows LastRunTime, LastTaskResult, and NextRunTime; these are the first things you should check when a task isn’t working as expected.

Troubleshooting PowerShell Scheduled Tasks with Event Logs

When a scheduled task fails, the Task Scheduler event logs usually explain why. In this step, you can query those logs with PowerShell so you can quickly identify errors and understand what went wrong. To do this, you can run:

Get-WinEvent -LogName "Microsoft-Windows-TaskScheduler/Operational" |
    Where-Object { $_.Message -like "*NightlyMaintenance*" } |
    Select-Object TimeCreated, Id, Message -First 10

Common event IDs to watch for include:

• 100: Task started
• 102: Task completed successfully
• 103: Task failed to start
• 201: Task action completed
• 203: Task action failed

Also, you can check the ask’s last result code directly. A result of 0 means success; 0x41301 means the task is still running; anything else displays a failure:

(Get-ScheduledTaskInfo -TaskName "NightlyMaintenance").LastTaskResult

Full PowerShell Registration Script

Here is a complete registration script you can copy, adjust, and run on your server:

$action = New-ScheduledTaskAction `
    -Execute "powershell.exe" `
    -Argument "-NonInteractive -NoProfile -ExecutionPolicy Bypass -File `"C:\Scripts\Maintenance.ps1`""

$trigger = New-ScheduledTaskTrigger -Daily -At "02:00"

$principal = New-ScheduledTaskPrincipal `
    -UserId "SYSTEM" `
    -LogonType ServiceAccount `
    -RunLevel Highest

$settings = New-ScheduledTaskSettingsSet `
    -ExecutionTimeLimit (New-TimeSpan -Hours 1) `
    -RestartCount 3 `
    -RestartInterval (New-TimeSpan -Minutes 5) `
    -StartWhenAvailable

Register-ScheduledTask `
    -TaskName "NightlyMaintenance" `
    -Action $action `
    -Trigger $trigger `
    -Principal $principal `
    -Settings $settings `
    -Description "Nightly disk check and temp file cleanup" `
    -Force

Write-Host "Task registered successfully."
Get-ScheduledTask -TaskName "NightlyMaintenance" | Get-ScheduledTaskInfo

FAQs

Conclusion

With a good script, a schedule, and logging in place, your maintenance runs the same way every time and on time. With PowerShell automation on Windows VPS, you can set it up once, then just check the logs and last run result when you need to.

We hope you enjoy this guide. Subscribe to our X and Facebook channels to get the latest updates and articles.