sca-local-system-admin

Use Get-Service to list and inspect services, then Stop-Service, Start-Service, or Restart-Service to change their state. Always run with -WhatIf first to preview destructive actions, and check -DependentServices before stopping anything.

Run Get-Process piped to Sort-Object CPU -Descending to find the top consumers, then use Stop-Process with the specific -Id to terminate one instance. Killing by ID is safer than by name, which terminates every matching process.

Build the task from four pieces: New-ScheduledTaskAction, New-ScheduledTaskTrigger -Daily, New-ScheduledTaskSettingsSet, and New-ScheduledTaskPrincipal, then register it with Register-ScheduledTask. Use Start-ScheduledTask to test it immediately instead of waiting for the trigger.

Yes, most tasks require an elevated PowerShell session. Service control, local user management, and reading the Security event log all fail without admin rights, so the PowerShell window title must show Administrator.

The Security log requires elevation, and Get-EventLog is the older slower API that misses modern event channels. Use Get-WinEvent with -FilterHashtable so filtering happens at the source, and remember StartTime is inclusive of the given timestamp.

This project covers only the local machine: no domain joins, Active Directory cmdlets, Azure connections, or remote PowerShell sessions. Those scenarios are handled in later projects using a Windows Server VM.