Joh. Berenberg Gossler · November 2012 — December 2012
Scripting Consultant
I migrated an existing batch script to PowerShell and enabled the internal team to automate server provisioning.
Automation · Freelance Senior System Engineer
PowerShell automation for infrastructure and operations
A script that only its author understands is an operational risk. I build automation that checks states, reports errors cleanly and can be handed over.
For IT leaders, recruiters and project agencies · Germany and DACH
By Rizwan KhanTechnically reviewed: 1 Aug 2026
What it means in practice.
I automate recurring administrative tasks and technical checks where manual variations lead to errors, lost time or inconsistent results. The focus is on maintainable scripts with clear inputs and outputs, logging and a documented handover.
PowerShell is not used for its own sake. The automation grows out of the actual operating process and supports provisioning, diagnosis, data preparation or access control with reproducible steps.
- Automated administration and technical checks
- Server and client provisioning
- Logging, error handling and reproducible diagnosis
- Data and attribute processing
- Documentation and knowledge transfer
When support makes sense.
- Manual operating workflows produce inconsistent results
- Technical checks or provisioning should become reproducible
- Existing scripts need logging, error handling and the ability to be handed over
Concrete deliverables.
- Scoping of the real operating process and the automation goals
- Maintainable PowerShell workflows with clear inputs and outputs
- Logging, error handling, documentation and knowledge transfer
Matching project evidence
Siemens AG · August 2011 — September 2011
System Administrator
I automated Windows 7 administration with PowerShell and handed over the knowledge in practical support workshops.
Dataport AöR · June 2015 — December 2025
Senior System Engineer
I supported business-critical specialist applications and took migrations through test, change and go-live into data-centre operations.
UKE Hamburg · January 2010 — March 2010
System Administrator
I analysed complex ACL, GPO and folder redirection issues and automated access control via user attributes.
BGW · January 2025 — present
MECM/SCCM Expert
I support Windows 11 deployment, software distribution, patch management and troubleshooting within the MECM processes.
Frequently asked questions from projects.
What makes PowerShell automation fit for operations?
Clear inputs, verifiable states, controlled error paths, meaningful logging and documentation that does not depend on the original author.
Is automation treated as an isolated script?
No. The starting point is the complete operating process, including approvals, responsibilities and handover.
Confidentiality boundary: only confirmed areas of responsibility and abstracted approaches appear publicly. Client-specific architecture details remain unpublished.
Further reading
Insight · reviewed 2026-08-01
Designing PowerShell automation that is fit for operations
Requirements for maintainable PowerShell automation: clear states, safe inputs, logging, error handling, tests, documentation and handover.
Discuss your project context in confidence.
A short description of the starting point, goal and timeframe is enough for a first technical conversation.