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 · Maintained forks · Website and guides · Development setup · Contact
The tools are self-contained Windows PowerShell 5.1 scripts under the MIT license. Start with the deployment and compatibility guides, then validate the task-sequence step in your own environment.
Add computer accounts to Active Directory groups during a ConfigMgr task sequence. Uses Kerberos over LDAPS by default, verifies group membership, and logs the result in CMTrace format.
Code · Documentation · Releases · Gist · Deployment
Collect and archive OSD logs, then upload them to an SMB share. Includes upload retries and remote size checks, and keeps the local archive if the upload fails.
Code · Documentation · Releases · Gist · Deployment
Apply a disk layout in WinPE during a ConfigMgr task sequence. It irreversibly cleans and repartitions the target disk, so test it on disposable hardware first.
Code · Documentation · Releases
Part of the ConfigMgr-OSD hub, which links every OSD script project. Gists are standalone snapshots with MIT notices and checksums. The repositories and release packages remain the authoritative source for deployment guidance.
Note
Automated checks cover syntax, static analysis, and mocked scenarios. Live-environment testing has not been performed for this release. Use the AD group validation guide and OSD log validation guide, plus the disk-layout compatibility matrix, to plan your rollout.
More about security, logging, and compatibility
- AD group membership: bounded retries and domain controller failover.
- Log collection: WinPE support with explicit compatibility controls. Read the deployment guide before enabling an exception.
- Security: no credentials in command lines or source, no certificate-validation bypass, and no silent fallback to weaker authentication or transport.
- Troubleshooting: sanitized CMTrace-compatible logs, documented exit codes, and troubleshooting guides.
- Automated checks: PSScriptAnalyzer and mocked Pester tests, kept separate from live ConfigMgr, Active Directory, WinPE, and SMB testing.
I also maintain focused changes in these upstream-derived endpoint-management projects:
- Modern Driver Management — fork of MSEndpointMgr/ModernDriverManagement.
- Modern BIOS Management — fork of MSEndpointMgr/ModernBIOSManagement.
- Driver Automation Tool — fork of maurice-daly/DriverAutomationTool.
These remain forks rather than original projects. Review each fork's commit history, upstream documentation, and compatibility guidance before using it in production.
Set up a Windows workstation for Git, repository access, PowerShell editing, and the same validation tools used in CI.
vartaxe@outlook.com · Sponsor my work
These tools are free and open source. Sponsorship helps cover testing, documentation, and maintenance.
Please follow the affected repository's security policy when reporting a vulnerability. Use private vulnerability reporting when it is available; otherwise use the private contact method documented there. Do not report security issues in a public issue.