What SharePoint Server Subscription Edition (SE)
Here’s a structured, in‑depth guide to SharePoint Server Subscription Edition (on‑prem), tailored for an IT admin/architect view.
1. What SharePoint Server Subscription Edition (SE) Is
SharePoint Server Subscription Edition is Microsoft’s latest on‑premises SharePoint Server product, released initially in December 2021 as the successor to SharePoint Server 2019.alrafayglobal+1
Instead of major version jumps, it uses a continuous, evergreen update model with feature updates roughly twice per year (e.g., 22H2, 23H1).learn.microsoft+1
Key positioning:
- Designed for organizations that must keep data on‑prem or in regulated environments but still want more modern SharePoint capabilities.alrafayglobal
- Bridges legacy farms (2016/2019) and SharePoint Online, providing a smoother path for gradual or hybrid cloud adoption.learn.microsoft+1
2. Architecture and Supported Scenarios
Core architecture
- Runs on Windows Server 2019 / 2022, with SQL Server 2019+ for content and configuration databases.200oksolutions+1
- Supports traditional multi‑server farm topologies: web front‑ends, application servers, and dedicated search or distributed cache roles.200oksolutions+1
Typical farm examples:
- Single‑server farm (all roles + SQL for dev/PoC).learn.microsoft
- 3‑server farm: 2 front‑ends with Distributed Cache + 1 app/search server + external SQL cluster.200oksolutions
Common scenarios:
- Classic intranet, ECM, team collaboration, workflows, and departmental apps where data residency is critical.alrafayglobal+1
- Hybrid: search, BCS, user profiles, or OneDrive/Teams integration with Microsoft 365 while content remains on‑prem.learn.microsoft+1
3. Licensing and Subscription Model
“Subscription Edition” does not mean pure per‑user cloud subscription; it is still an on‑prem server product with license + CAL model, but updated continually.q-advise+1
High‑level licensing model:
- Server license for each SharePoint Server SE instance.q-advise
- Client Access Licenses (CALs) for users or devices that access the server, with Standard and Enterprise CAL layers similar to earlier versions.q-advise+1
Integration aspects:
- Project Server Subscription Edition is now a feature of SharePoint SE, enabled with a Project product key and Enable-ProjectServerLicense.microsoft
- Certain Microsoft 365 suites (E3/E5) provide equivalent on‑prem rights where Software Assurance/volume licensing applies; details differ by agreement and need licensing guide/LAR confirmation.reddit+1
4. New and Improved Features (vs 2019)
Microsoft positions SE as a security‑hardened, modernized, evergreen SharePoint Server with both platform and functional changes.learn.microsoft+1
Platform / security:
- Evergreen model: Two feature updates per year (H1, H2) plus regular security fixes.alrafayglobal+1
- Modern authentication: Support for OpenID Connect (OIDC), improved OAuth/OAuth2 scenarios, and better integration with identity providers.learn.microsoft+1
Security enhancements:
- Support for TLS 1.3 for improved encryption in transit.alrafayglobal+1
- Integration with Antimalware Scan Interface (AMSI) to detect malicious content before it’s processed.learn.microsoft+1
Functional / UX improvements:
- Continued improvements to “modern” UX parity relative to SharePoint Online (list/library experiences, site pages) though not full parity.alrafayglobal+1
- Simplified upgrade/patching model: you stay on SE and apply cumulative feature updates instead of doing in‑place version upgrades to 2022/2025 etc.learn.microsoft+1
Admin improvements:
- Support for newer Windows/SQL versions and modern TLS/protocol defaults to simplify compliance.learn.microsoft+1
- Updated Central Admin and PowerShell tooling, including new cmdlets for subscription‑style maintenance.learn.microsoft+1
5. Planning and Prerequisites
Infrastructure prerequisites
For a production multi‑server farm (typical pattern described in implementation guides):200oksolutions+1
- OS: Windows Server 2019 or 2022, fully patched.
- SQL: SQL Server 2019 or later on a separate server or cluster, with service account having dbcreator and securityadmin roles.200oksolutions
- Static IPs and hostname resolution for all farm servers.200oksolutions
Accounts to plan:
- SQL Server service account.200oksolutions
- Farm admin account (used to run setup and configuration wizard).200oksolutions
- Farm service account (used for timer, Central Admin, app pools, etc.).200oksolutions
All typically require local admin rights during installation and appropriate SQL roles.200oksolutions
Other considerations:
- Decide topology and server roles up front (e.g., stand‑alone, min‑role layout: Front‑end with Distributed Cache vs Application with Search).learn.microsoft+1
- Storage layout for content, logs, Search index, and Distributed Cache to meet performance and HA requirements.200oksolutions
6. Installation – High‑Level Steps
Microsoft provides an ISO image for SharePoint Server Subscription Edition; the installation flow is similar to 2016/2019 but with updated prerequisites.microsoft+2
- Prepare servers and SQL
- Install Windows Server, patch, join domain, set static IPs.200oksolutions
- Install and configure SQL Server instance, ensure connectivity from SharePoint servers.200oksolutions
- Run the SharePoint Products Preparation Tool
- Mount the SE ISO, run splash.hta, and choose “Install software prerequisites.”200oksolutions
- Tool installs required components (IIS, .NET, Windows features); restart if prompted.200oksolutions
- Run SharePoint Setup
- From the same splash screen, choose “Install SharePoint Server.”200oksolutions
- Enter your SharePoint Server Subscription Edition product key and accept license terms.microsoft+1
- Choose install path (often a non‑system drive is recommended for easier troubleshooting).200oksolutions
- Run SharePoint Products Configuration Wizard
- Launch the configuration wizard after setup (or from Start menu if closed).200oksolutions
- For the first server, choose “Create a new server farm.”200oksolutions
- Provide SQL Server name, configuration database name, and farm admin creds.200oksolutions
- Configure the passphrase (needed to join more servers), Central Admin port, and authentication method.200oksolutions
- Choose appropriate server role (e.g., “Application with Search” for the first app server).200oksolutions
- Join additional servers to farm
- On front‑end servers, run setup, then configuration wizard.200oksolutions
- Choose “Connect to an existing farm,” supply configuration DB server and passphrase.200oksolutions
- Select relevant min‑role (e.g., “Front‑end with Distributed Cache”).200oksolutions
- Post‑installation configuration
- Verify all servers appear correctly in Central Administration → “Servers in Farm.”200oksolutions
- Run the Farm Configuration Wizard or manually configure service applications: Search, Managed Metadata, User Profile, etc.learn.microsoft
- Apply latest cumulative update / feature update to ensure you are at the latest SE build.alrafayglobal+1
7. Upgrading from Older Versions
SE is designed as the forward path for SharePoint 2016/2019 farms.learn.microsoft+1
Upgrade approach:
- In‑place upgrade is not supported from 2016 to SE; you build a new SE farm and use database attach (similar to previous jumps).learn.microsoft
- The path 2016 → 2019 → SE or 2019 → SE via DB attach is supported and documented in Microsoft’s IT Pro guidance.learn.microsoft
Benefits vs staying on 2019:
- Longer support horizon with ongoing feature updates.alrafayglobal
- Access to new security and modern auth capabilities that will not be back‑ported to 2019.learn.microsoft+1
8. Development Model and SPFx
SharePoint Framework (SPFx) is supported on SE with a particular version band, allowing modern client‑side customizations similar to SharePoint Online (but usually one or more major versions behind the cloud).voitanos
Key points:
- You develop SPFx solutions targeting the version range supported by SE (documented by SPFx guidance for SE).voitanos
- On‑prem SE does not auto‑track the very latest SPFx versions released for SharePoint Online; you need to align with the specific version listed for SE.voitanos
Classic development:
- Farm solutions (full trust) and sandboxed solution patterns continue to function, consistent with 2016/2019.learn.microsoft
- CSOM and REST APIs remain primary integration interfaces for external systems.learn.microsoft
9. Operations, Patching, and Lifecycle
Because SE is “evergreen,” the operational model differs slightly from older versions.learn.microsoft+1
Updates:
- Microsoft issues Feature Updates (H1/H2) containing new functionality and changes, and cumulative updates/security fixes regularly.alrafayglobal+1
- You remain on SharePoint Server Subscription Edition but move through build numbers that correspond to these feature updates.alrafayglobal
Operational practices:
- Treat each feature update like a mini‑upgrade: test in staging, validate customizations and 3rd‑party solutions before production rollout.alrafayglobal
- Continue standard SharePoint ops practices: backups at SQL level, farm backup, search index protection, and config documentation.learn.microsoft
Lifecycle:
- SE effectively replaces future on‑prem “version names” (2022, 2025, etc.)—Microsoft has signaled that future innovation on‑prem will come via SE feature updates, not new separate major versions.q-advise+1
10. When to Choose SE vs SharePoint Online
Typical reasons to choose SE:nakivo+2
- Regulatory or contractual requirements for data to remain on‑prem.
- Tight integration with on‑prem line‑of‑business systems, low‑latency internal network dependencies.
- Customized solutions using full‑trust code that cannot move to SharePoint Online easily.
Reasons to prefer Online:
- Need for full modern experience parity, rapid innovation, and integrated services like Teams, OneDrive, Viva, etc.fiboo+1
- Desire to offload infrastructure, patching, and DR to Microsoft’s cloud platform.nakivo+1
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.