SpnManager/install:0.4.0
Kerberos broken now? →
installation and system requirements

What it needs to run.

requirements
PowerShell
5.1, or 7.x
Operating system
Windows for the sense stages that read local services. Windows PowerShell 5.1 or PowerShell 7. Both are supported and the licence gate works on either — the module ships a build for each runtime and loads whichever one your shell can run
Active Directory
Read access for audits. Write rights on the target account for Execute. The RSAT ActiveDirectory module: required. It is declared in the module manifest, so importing SpnManager without RSAT installed fails outright rather than quietly skipping the directory work
Optional modules
ADFS, Exchange Management Shell, SharePoint: used when present; guided fallback when absent.
.NET
The C# engine: .NET 8 on PowerShell 7, or .NET Framework 4.7.2 and later on Windows PowerShell 5.1. The module ships both builds and loads whichever one your shell can run
Network
LDAP to a domain controller. WinRM to hosts you audit remotely; unreached hosts are reported, not skipped.
Every item marked as a placeholder must be confirmed against the release manifest before publication.

install
from {{DISTRIBUTION_CHANNEL}}
Install-Module SpnManager -Scope CurrentUserImport-Module SpnManagerGet-Module SpnManager | Select-Object Version   # 0.4.0

Marketplace purchases receive an entitlement, not a different binary. How the entitlement is presented to the module: a signed token you set as the SPNMANAGER_LICENSE_TOKEN environment variable on the machine that runs SpnManager. The module reads it from there. No separate installer, no different binary, and nothing is written to the module folder. See License →.


verify the download

Release artefacts are signed. Signing key, fingerprint, and verification steps live on the trust center →.