Why PowerShell?

What is all of the hype around PowerShell? As a junior systems administrator years ago, it was easy to just see PowerShell as a blue and white command shell capable of doing the same things as a command prompt. Why would I use Test-Connection when I already have ping in good ol’ CMD? Despite this confusion, I would eventually see its potential in a variety of settings. First, when using a Windows Forms GUI script to manage Exchange users when working at a managed service provider. The simplicity and the precision the tool commanded in routine tasks not only reduced time, but spurred accuracy.

I saw this more when I started working in an education environment where PowerShell scripts were the backbone of identity management in syncing accounts across Google, Azure, and Active Directory. Then, when working at a credit union, I had the privilege of automating hundreds of hours of work over about thirty PowerShell (and some Python) scripts. I’m talking about making processes better for tens of employees, people not having to get up early for work because PowerShell scripts are doing the work for them. In both settings, the customers our systems are taking care of (students and credit union members) got better, unified, and more standard service. Not only all of that, but the organizations I’ve had the privilege to work for have also saved time and money by not implementing expensive proprietary software.

PowerShell has amazing potential not only for your organization but for your resume. I hope you will gain some awesome skills from this newsletter to help both!