An Enterprise Journey in PowerShell Administration Link to heading

Starting at a large customer site led me deep into Windows PowerShell.
Batch files simply weren’t fun to work with — and certainly not helpful when it came to troubleshooting.

But how do you get started?

Although I tend to be the “solve the puzzle as you go” type, I highly recommend beginning with the essentials that every script will need: logging, auditing, and secure handling of secrets.

Let’s package these into a module so they’re ready whenever needed.

First Things First — The Common Module Link to heading

How to create a PoSh module:
👉 See PowerShell modules overview for more details.

Our goal is to build a reliable foundation module, which includes:

• Logging
• Audit logging
• Secure secrets management — encryption
• Secure secrets management — KeePass integration
• Error handling & structured exceptions
• Configuration management (e.g. JSON, XML, PowerShell data)
• Session and correlation ID support
• Input validation helpers
• Versioning and self-documentation
• (Optional additions: notifications, performance metrics, cross-platform support)

Building a Solid Basis Link to heading

Once the Common module is in place, we can extend our toolkit for enterprise administration:

• Lean device management
• Searching for devices
• Secret management
• Remote PowerShell execution
• Enhanced remote PowerShell execution
• Data collection and usage
• Reporting — email with Excel attachments
• Reporting — Grafana integration
• RDP tools — Rocket Remote Desktop (formerly ASG Remote Desktop)

Interesting Topics Link to heading

These areas cover specific challenges and tools that come up in enterprise operations:

• Working with certificates
• Local DNS caching
• Rocket Remote Desktop use cases
• Scheduled tasks and automation

👉 I’ll create individual blog entries for each of these topics — and dive deeper where needed.
Stay tuned as we explore these together!