Release notes

v1.0.1

Version 1.0.1 contains focused reliability fixes and clearer deployment guidance. The new version identifies its own source and download assets; previous releases are not replaced.

The workflow publishes this version first as a prerelease candidate. The maintainer verifies the downloaded ZIP, sidecar, and extracted source, then explicitly approves promotion of the same release to regular/latest. Promotion does not change the tag or verified assets; the GitHub release status records whether that approval stage is complete.

Changes

• Archive creation fails safely on an existing filename instead of deleting the previous ZIP.
• Credential-bearing mapping arguments are cleared on early SMB inspection and TCP preflight failures as well as normal completion.
• Sanitized errors identify SMB inspection failures without copying raw exception messages into logs.
• Regression tests cover these cases, preservation of earlier retained runs, and staging retention after ZIP creation failure.
• Deployment and troubleshooting guides now describe the full parameter, output, exit-code, and retention contract.

Requirements

Use Windows PowerShell 5.1 in an active ConfigMgr Task Sequence running as Local System. WinPE needs the corresponding PowerShell/.NET components. Configure an existing UNC destination, a least-privilege account, hidden password variables, an external timeout, and native credential cleanup on success and failure.

SMB3, integrity, encryption, and per-connection NTLM blocking remain the defaults. Older clients and some WinPE images may require explicitly approved compatibility settings; the script never changes Windows authentication policy.

Validation status

Validation covers Windows PowerShell 5.1 parsing, PSScriptAnalyzer, Pester, matching version/tag metadata, and exact-byte SHA-256 coverage. Local filesystem and ZIP operations are tested with real files; ConfigMgr and SMB behavior is mocked.

Live ConfigMgr, WinPE, and SMB validation remains pending. A regular release does not certify production compatibility. Check CI for the exact revision and complete the environment rollout checklist before broad deployment.

Documentation

See deployment for setup, security for requirements and reporting, and validation for automated checks and the pilot checklist.