HOMELAB / DOCUMENTATION

PowerShell Notes and Automation

The PowerShell tasks I have used in IT support and the scripting habits I am developing.

Why I use PowerShell

PowerShell is useful to me because it turns a repetitive task into a script that I can run easily and consistently. I use it for troubleshooting, administration, and small automations.

How I approach a script

  1. Work out what I want the command to change.
  2. Test the command on a limited scope first.
  3. Add basic error handling or checks where needed.
  4. For scripts that alter multiple systems, I prefer a preview or validation step when possible.
  5. Make the output understandable enough to troubleshoot later.
  6. Document required dependencies, required permissions, and changes made by the script.

What I’ve been learning

I’m working on improving how I structure scripts rather than keeping everything as one-off terminal commands. That includes reusable functions, parameter handling, clearer output, and better documentation.

Real-world example

As part of my duties as a technician for Contra Costa Health, I developed a PowerShell deployment to install Webex silently and machine-wide across a fleet of healthcare translator workstations to support the department’s transition to VoIP. I had to get familiar with installer switches like ALLUSERS and SILENT and integrate them into a script that remotely connects to each machine. The script can digest a .CSV list of computer names or IP addresses and loop through it, remotely installing Webex on each device without interrupting the users.