Collect deployment logs

Copy OSD Logs to File Share collects a focused set of deployment logs, writes a manifest, creates a local ZIP, and uploads it to an authenticated SMB destination. Failed uploads retain the local archive; successful uploads verify remote byte size, not a content hash.

v1.0.1 includes targeted reliability fixes and operator-focused documentation. Automated checks cover local behavior; live ConfigMgr, WinPE, and SMB validation remains pending.

Start with the deployment contract

  1. Read the deployment guide for package setup, variables, retry limits, and an external Task Sequence timeout.
  2. Check compatibility before approving exceptions. The secure default requires SMB3, integrity, and encryption, and refuses unverifiable connections.
  3. Follow the security requirements: hide passwords, disable parameter logging, and use native cleanup steps on success and failure while preserving the script result.

Run only in an active ConfigMgr Task Sequence as Local System with Windows PowerShell 5.1. PowerShell 7 is not a supported Task Sequence runtime. WinPE requires the appropriate PowerShell/.NET components and may need explicitly approved SMB compatibility settings.

Documentation

Guide Use it for
Deployment Task Sequence layout, variables, parameters, and credential lifecycle
Compatibility Supported runtime targets and opt-in SMB exceptions
Architecture Collection, manifest, ZIP, upload, and cleanup sequence
Logging CMTrace diagnostics, retained archives, and sensitive source logs
Troubleshooting Upload failures, timeouts, WinPE storage, and checksums
Validation Reproducible static/mocked checks and pending live scenarios
Examples Placeholder Task Sequence configuration
Release process Source-byte checksums and publication safeguards

Source and release

Use the source repository for the maintained script, tests, and contribution guidance. The PowerShell source is also available directly; download the complete package when following the deployment guide.

Use the v1.0.1 release for the versioned ZIP and SHA-256 sidecar, and read the release notes for its changes. Each release keeps its own identity; later changes do not replace earlier downloads. This site follows main, so its documentation can be newer than a downloaded package.

A regular GitHub release distributes a reviewed version; it does not establish live platform compatibility. Check the validation scope and exit-code contract before rollout.

The workflow initially publishes a prerelease candidate. Regular/latest status follows only after downloaded-asset verification and explicit maintainer approval to promote the same release; see the two-stage release process.

MIT licensed by Claudio Mendes. See the license and security reporting guidance.