Skip to content

SchunkOps 1.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Sep 04:22
v1.2.0
d3d8e82

SchunkOps 1.2.0

SchunkOps 1.2 expands the Windows IT Toolkit from day-to-day endpoint and server diagnostics into senior infrastructure investigations while keeping the same read-only-first operating model.

Collect first. Change second. Document always.

New in 1.2

Account lockout tracing

Get-SchunkAccountLockoutTrace correlates account lockout events across domain controllers and surfaces caller-computer evidence so engineers can investigate recurring lockouts without manually opening Security logs on every DC.

Kerberos / SPN auditing

Get-SchunkKerberosSpnAudit reviews service principal name ownership and duplicate registrations to help isolate Kerberos authentication failures and identity collisions.

Group Policy change review

Get-SchunkGpoChangeAudit inventories recently modified Group Policy Objects and can generate SHA-256 report fingerprints for baseline and change-review workflows.

DHCP / DNS consistency

Get-SchunkDhcpDnsConsistency compares active DHCP lease information with forward and reverse DNS state to surface stale, mismatched, or missing name-resolution records.

Certificate chain validation

Test-SchunkCertificateChain validates local X.509 trust chains and returns structured chain-status evidence instead of a browser-specific certificate warning.

Failover Cluster health

Get-SchunkClusterHealth summarizes nodes, clustered roles, resources, networks, Cluster Shared Volumes, and quorum state for Windows Failover Clustering investigations.

Fleet health

Get-SchunkFleetHealth collects normalized health from multiple Windows systems over CIM without requiring SchunkOps to be installed on the remote machines.

VMware vSphere inventory

Get-SchunkVSphereInventory uses an existing VMware PowerCLI connection to return read-only host, datastore, VM, and optional snapshot health context.

Module size

SchunkOps 1.2 exports 28 public commands spanning:

  • help desk / endpoint triage
  • Windows Server operations
  • Active Directory and domain trust
  • DNS and network diagnostics
  • account lockout and Kerberos investigations
  • Group Policy change review
  • local privilege inventory
  • certificate validation
  • failover clustering
  • multi-server fleet health
  • VMware vSphere inventory
  • incident evidence and before/after comparison

Install

The GitHub release contains the versioned module ZIP and SHA-256 checksum. Once the PowerShell Gallery publisher credential is configured, the same version can be installed directly from the Gallery:

Install-Module SchunkOps -Scope CurrentUser
Import-Module SchunkOps
Get-Command -Module SchunkOps

Start with:

Get-SchunkEndpointTriage

Senior engineers can continue with:

Get-SchunkFleetHealth -ComputerName server01,server02,server03
Get-SchunkAccountLockoutTrace -Identity jsmith -LookbackHours 24
Get-SchunkKerberosSpnAudit -Identity svc_web
Get-SchunkGpoChangeAudit -SinceDays 14 -IncludeFingerprint
Get-SchunkClusterHealth -Cluster sqlcluster01
Get-SchunkVSphereInventory -IncludeSnapshots

Documentation

  • Five-minute quick start: docs/QUICKSTART.md
  • Help Desk Field Guide: docs/HELPDESK.md
  • Senior Engineer Field Guide: docs/SENIOR-ENGINEER.md
  • Incident-response workflow: docs/INCIDENT-RESPONSE.md
  • Privilege / dependency guide: docs/PRIVILEGES.md

Safety and quality

The 1.2 release is guarded by PowerShell parsing, PSScriptAnalyzer error rules, Pester module tests, export validation, discoverable command-help checks, and a static safety contract for the senior diagnostic set.

The release pipeline requires the release version to match the module manifest, creates a versioned ZIP artifact and SHA-256 checksum, and publishes the GitHub Release only after its quality gates pass. PowerShell Gallery publication is a separate protected job that requires the maintainer's Gallery API key. Authenticode signing is supported when code-signing secrets are configured; otherwise the CI-validated module can be published unsigned.

SchunkOps does not contain environment-specific credentials or phone-home telemetry. Operators remain responsible for reviewing commands, permissions, exported evidence, and organizational policy before production use.

Assets 4
Loading