I’m Claudio Mendes (@vartaxe). I write PowerShell tools for the repeatable jobs around Windows deployment, with clear inputs, useful logs, and explicit outcomes. Most of the work here brings together Microsoft Configuration Manager and Active Directory.

Projects

Both projects are MIT licensed, target Windows PowerShell 5.1, and have no third-party runtime module dependencies. Pick the task you need to automate:

Add computers to AD groups

Add a domain-joined computer to Active Directory groups during a ConfigMgr task sequence, with Kerberos over LDAPS by default, direct membership verification, bounded retries, and CMTrace logging.

Runtime: full Windows, after domain join and restart.

Read the AD group guide · Browse source

Copy OSD logs to a file share

Collect OSD logs, create a local ZIP and manifest, and upload to an SMB share with retries and remote size checks. Keep the local archive if the upload fails.

Runtime: a ConfigMgr task sequence; WinPE needs the documented prerequisites.

Read the OSD log guide · Browse source

A consistent approach

• Self-contained tools. No large framework to import into a task sequence.
• Explicit security choices. No credentials in command lines or source, no certificate-validation bypass, and no silent fallback to weaker transport.
• Troubleshooting first. Sanitized CMTrace-compatible logs, documented exit codes, and deployment examples.
• Honest status. CI results and live-environment validation are different things.

Community

I learn a lot from people who share their deployment notes and scripts. Maurice Daly’s Driver Automation Tool is a useful example of making the setup, logs, and troubleshooting as helpful as the code.

Further reading: MSEndpointMgr, Deployment Research, CCMExec, System Center Dudes, and GaryTown.

Places to keep learning: Midwest Management Summit, Workplace Ninja Community, and Workplace Ninja Summit.

These are independent projects. Links recognize sources of inspiration, not affiliations or endorsements; each resource keeps its own license.

Contact and support

For general contact, email vartaxe@outlook.com. For bugs or usage questions, use the affected repository’s issue templates and support guide. Report vulnerabilities through its private vulnerability reporting page, not a public issue.

GitHub Sponsors helps cover testing, documentation, and maintenance. Both tools remain free and open source.