-
Notifications
You must be signed in to change notification settings - Fork 0
Home
SPSUpdate is a PowerShell tool that installs SharePoint Server cumulative updates and runs the post-setup Configuration Wizard (PSConfig) across a farm. It targets SharePoint Server Subscription Edition and requires only PowerShell 5.1 or later — there is no DSC dependency.
SharePoint Server 2016 and 2019 reached end of support on 14 July 2026. For those versions, use the previous major release v4.2.0.
SPSUpdate installs the update binaries, mounts and/or upgrades content databases in parallel via scheduled tasks, runs PSConfig on the local and remote servers over CredSSP remoting, and configures the side-by-side patching token for zero-downtime upgrades.
- Install cumulative update binaries locally (
ProductUpdate) - Parallel content-database mount/upgrade across 4 sequences (LPT-balanced by size)
- Post-setup Configuration Wizard (PSConfig) on local and remote servers via CredSSP
- Side-by-side token configuration for zero-downtime patching
- Near real-time HTML patching dashboard (live progress across servers, sequences and PSConfig)
- Configuration as a PowerShell data file (
*.psd1) - Service credential stored as a DPAPI-encrypted
secrets.psd1— no third-party module - Windows Event Log instrumentation (dedicated
SPSUpdatelog) - Self-contained
SPSUpdate.CommonPowerShell module (manifest-driven version)
SPSUpdate.ps1 (entry point, scheduled tasks)
| imports
v
SPSUpdate.Common (PowerShell module: Public/ + Private/)
| CredSSP remoting (Invoke-Command / New-PSSession)
v
Each SharePoint farm server --> binaries install / PSConfig / DB upgrade
The credential used for remoting and scheduled tasks is read from Config\secrets.psd1 (DPAPI), and every run writes lifecycle entries to the SPSUpdate Windows Event Log.
- Getting Started — prerequisites, CredSSP, installation, first run
-
Configuration —
*.psd1environment config andsecrets.psd1explained - Usage — actions, sequences, scheduling, output, the live dashboard and the event log
- Release Process — for maintainers: how to ship a new version
Navigation
Project