A Journey Through Scripts and Automation

A Few Items Before We Start

I’ll be the first to admit—I’m not writing most of my scripts from scratch. Most of them start as something I’ve found online, tweaked, and transformed into something that works for my needs. And you know what? That’s okay. They call people like me “script kitties,” and I’m fine with that label. Why reinvent the wheel when you can upgrade it instead?

Consistency is Key: My Script Environment

One of the most important lessons I’ve learned over the years is the value of consistency when it comes to scripting environments. If you’re scratching your head wondering what an environment is, think of it as the workspace where your scripts run. A consistent environment saves you time and headaches, especially when troubleshooting or setting up something new.

Here’s how I organize mine:

1. Scripts Folder: All my scripts live in a folder named C:\scripts (yes, I’m a Windows user—more on that later). This ensures I always know where to find them.

2. Data Folder: If a script needs input files, those go into C:\scripts\Data. This keeps everything tidy and predictable.

3. Output Folder: Script-generated reports go into C:\CSVReports. I like to separate log files into a subfolder here called C:\CSVReports\Logs for easy reference.

By keeping these elements the same across all my projects, I can focus on the “meat and potatoes” of the script without worrying about where to find or store files.

A Windows Guy at Heart (But Not Exclusively)

I’ll admit it: I’m a Windows guy. Most businesses run on Windows, so naturally, that’s where my career started and where most of my expertise lies. That said, I’ve dabbled in (and sometimes fully supported) MacOS, OS/2, Linux, Unix, and a few other operating systems you’ve probably never heard of.

Because of this background, most of the scripts you’ll find here will be written in PowerShell or Batch. That doesn’t mean the functionality won’t work elsewhere, though. You might just need to adapt it to your platform. After all, when you boil it down, it’s all just 1’s and 0’s.

Anonymization for Security

Let’s talk security for a second. The scripts I share here are going to be anonymized. That means sensitive details like server names, IP addresses, or anything else that could compromise security will be replaced with placeholders. For instance, instead of showing my company’s Active Directory server name as ActiveDIR01 (which, spoiler alert, it’s not), you’ll see something like %DCHere%. This lets you easily substitute your own details without worrying about exposing mine.

What to Expect Moving Forward

I’ll keep this first post short and sweet (well, kind of). If there’s more to add, I’ll pin updates or create follow-up posts. For now, expect a steady stream of scripts that I’ve used throughout my career—each one designed to make life a little easier, and maybe even a little fun. Thanks for stopping by, and happy scripting!