L8. Remoting, Jobs, and Scheduled Automation

Remoting Concepts

PowerShell remoting lets you run commands on other machines. On Windows, WinRM is common. PowerShell 7 also supports SSH-based remoting, which is useful across platforms.

Enter-PSSession -ComputerName server01
Invoke-Command -ComputerName server01 -ScriptBlock { Get-Service }

In real environments, remoting depends on network reachability, authentication, authorization, host configuration, and logging. Do not treat it as just a command syntax problem.

Jobs

Jobs let work continue in the background:

$job = Start-Job -ScriptBlock { Get-Process | Sort-Object CPU -Descending | Select-Object -First 5 }
Receive-Job $job -Wait -AutoRemoveJob

PowerShell 7 also supports parallel processing:

1..5 | ForEach-Object -Parallel {
  "Worker $_ on $([Environment]::MachineName)"
} -ThrottleLimit 3

Use throttling. Unlimited parallelism can overwhelm endpoints, APIs, or your own machine.

Scheduled Automation

For local Windows automation, scheduled tasks are still practical:

$action = New-ScheduledTaskAction -Execute 'pwsh.exe' -Argument '-File C:\Scripts\Inventory.ps1'
$trigger = New-ScheduledTaskTrigger -Daily -At 3am
Register-ScheduledTask -TaskName 'DailyInventory' -Action $action -Trigger $trigger

In cloud and DevOps environments, the same script may run under GitHub Actions, Azure Automation, or another runner. Keep scripts non-interactive, parameterized, logged, and idempotent.

Lab

1. Start a local job that gathers process data.
2. Receive the result and remove the job.
3. Use ForEach-Object -Parallel with a throttle limit.
4. Draft a scheduled-task command for a daily inventory script.