Release 5.0.0 - drop SharePoint 2016/2019 support (SE-only) - #27
Merged
Conversation
…r module only SharePoint Server 2016 and 2019 reached end of support on 14 July 2026; SPSUpdate now targets Subscription Edition only. - SPSUpdate.ps1 and Invoke-SPSCommand load the SharePointServer module idempotently instead of adding the Microsoft.SharePoint.PowerShell PSSnapin (including inside the remoting HERE-STRING sent to each server). - Start-SPSConfigExe / Start-SPSConfigExeRemote drop the SharePoint 2013 (FileMajorPart 15, 15\BIN, 15.0 hive) branch and the version guard around Upgrade-SPFarm; they target the 16.0 hive and 16\BIN unconditionally. - Start-SPSProductUpdate drops the OSearch15 branch (keeps OSearch16) and the 2016/2019/SE cumulative-update detection; the CU is always Subscription Edition. - Get-SPSLocalVersionInfo no longer takes a ProductVersion parameter and resolves the Subscription Edition product name only. PSScriptAnalyzer clean; 164 Pester tests passing. Refs #26
- README, wiki Home and the offline install guide now state SharePoint Server Subscription Edition as the only supported product, with a note that 2016/2019 reached end of support on 14 July 2026 and users on those versions must use the previous major release (v4.2.0). - Usage wiki: keep the 2019 -> Subscription Edition migration context and add a note that running InitContentDB on a 2019 source farm requires v4.2.0. - Remove the '2016/2019 snap-in vs SE module' wording from the offline guide. Refs #26
- SPSUpdate.Common manifest ModuleVersion -> 5.0.0. - CHANGELOG: prepend the [5.0.0] section (Removed / Changed / Migration). - RELEASE-NOTES: replace with the 5.0.0 notes only (GitHub Release body). - Tests: bump the module version guard to 5.0.0. Refs #26
Pester Test Results 1 files 19 suites 2s ⏱️ Results for commit 9f0f3a4. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SPSUpdate 5.0.0 is a breaking change that drops support for SharePoint Server 2016 and 2019. The tool now targets SharePoint Server Subscription Edition (SE) only.
The deprecated
Add-PSSnapin Microsoft.SharePoint.PowerShellpath has been removed in favour of an idempotentImport-Module SharePointServer, and every version-detection branch (2013/2016/2019) has been removed from the config-wizard, product-update and helper functions.Fixes #26
Changes
Refactor (SE-only)
src/SPSUpdate.ps1: load SharePoint viaImport-Module SharePointServer(was Snapin/version detection).Invoke-SPSCommand.ps1: remoting bootstrap now imports theSharePointServermodule idempotently; removed the 2016/2019-vs-SE version branch.Start-SPSConfigExe.ps1/Start-SPSConfigExeRemote.ps1: removed the SP2013 (15) branch, hardcoded the16.0hive +16\BIN,Upgrade-SPFarmis now unconditional.Start-SPSProductUpdate.ps1: removed theOSearch15branch (keepsOSearch16), simplified CU detection to SE.Get-SPSLocalVersionInfo.ps1: removed theProductVersionparameter; resolves "Subscription Edition" unconditionally.Docs
README.md,wiki/Home.md,src/SPSUpdate_README.md: Subscription Edition only, with a note pointing 2016/2019 users (including migration scenarios) to the 4.2.0 release.wiki/Usage.md: kept the 2019 -> SE migration context and the note thatInitContentDBagainst a 2019 source farm needs 4.2.0.Chore
SPSUpdate.Common.psd1: ModuleVersion ->5.0.0.CHANGELOG.md: new[5.0.0]section (Removed / Changed / Migration).RELEASE-NOTES.md: 5.0.0 release body.tests/SPSUpdate.Common.Tests.ps1: version guard bumped to 5.0.0.Migration
Farms still on SharePoint 2016/2019 (including 2019 -> SE migration scenarios where
InitContentDBruns against the 2019 source) must stay on SPSUpdate 4.2.0. Upgrade to 5.0.0 only once the farm is Subscription Edition.Validation
InitContentDB(read-only): SharePointServer module loads, inventory + HTML report generated.ProductUpdate(KB5002893): full campaign completed - 10 Done / 0 Failed (3x ProductUpdate + 4 content-db upgrade sequences + 3x Configuration Wizard), live dashboard stamped 5.0.0.