Microsoft SharePoint Server 2019 — keep your intranet where you can prove it lives

If your organisation still says “our board wants the wiki in our rack,” you are not shopping for vibes—you are shopping for a documented server product with a reconciliation story for finance, an auditor, or a cautious insurer. Microsoft SharePoint Server 2019 is the on-premises edition that brings modern team and communication sites, sync-friendly libraries, and hybrid search patterns into infrastructure you operate—not a generic “cloud in a trench coat.” At Lizensa, we write retail software pages for people who read receipts: which server role you licence, what CAL mathematics remain your responsibility, and how this SKU differs from Microsoft 365 / SharePoint Online bundles that move menus every quarter.

This page is aimed at EU consumers, freelancers, and SMEs who need one honest product row for a project someone already named “Phase 2 intranet.” It is not a promise that a single purchase replaces email, real-time chat, Teams meeting capacity, or Entra ID governance you never budgeted. Where collaboration touches regulated data—health, finance, public sector—treat this text as orientation, then anchor decisions to your fulfilment email from Lizensa and the publisher documentation active on the day you deploy.

SharePoint succeeds when nobody improvises licensing at midnight. Pair the server with a supported Windows Server generation, a SQL Server tier that matches your growth model, and—almost always—CALs that map to humans or devices actually authenticating. If mail and calendars still live in Microsoft Exchange Server 2019 Standard on the same timeline, plan identity and TLS assumptions together; heavy topology frequently steps up to Microsoft Exchange Server 2019 Enterprise. Front-end presence and meetings that still lean on Skype-era estates may also involve Skype for Business 2019 beside SharePoint—not because nostalgia pays, but because migrations are staged, not wished away. For access maths to Windows itself, budget Windows Server CALs on the lanes your devices use, then keep the wider catalogue under /categories/microsoft so procurement does not fracture into orphan SKUs.

What you get

You receive entitlement to SharePoint Server 2019 as Lizensa describes after checkout: a perpetual server-side collaboration platform aimed at organisations operating SharePoint on servers they control. Typical outcomes buyers care about include:

• Modern site templates that do not look like 2007 intranet cosplay—responsive pages, web parts people can reuse, and communication sites leadership can actually read on a phone without squinting.
• Libraries tuned for real work—versioning, metadata discipline when you enforce it, sharing flows that behave predictably for staff who only visit the intranet twice a week.
• OneDrive sync scenarios anchored to your farm—not a consumer backup story, but a governed “files live in SharePoint, edits land where compliance expects them” narrative.
• Hybrid connectivity patterns where SharePoint Online already exists: unified search and selective routing can spare you dramatic big-bang moves if architecture (and policy) supports them.
• Integration hooks for Power Platform-style automation where your estate actually permits it—not every tenant enables the same endpoints; verify with the administrators who carry the pager.

You do not automatically receive SharePoint user or device CALs, Windows Server licences, SQL Server licences, SSL certificates, backup products, monitoring, third-party migration tooling, or a ready-made information architecture workshop. Lizensa delivers the software entitlement path your email specifies; infrastructure labour stays yours—or your partner’s—by design.

What’s new (and why 2019 still appears on sober roadmaps)

The 2019 wave matters because it sits in the modern UI era while respecting estates still standardised on Windows Server 2016/2019/2022 and SQL Server generations your DBAs already patch. Modern lists and libraries, team sites, and communication sites are the headline “feels current” improvements over legacy Team Sites that younger hires politely tolerate at best.

Hybrid is the quiet workhorse: organisations often keep authoritative records on-premises while selectively using cloud search or specific workloads online. That is a licence + network + identity conversation, not a checkbox Lizensa can abstract into poetry.

If you are net-new and cloud-first by policy, compare operational outcomes with a SharePoint Online roadmap before you comfort-buy a server SKU “just in case.” If you are cloud-averse by statute or WAN-flaky by geography, the on-premises edition can be rational even when marketing brochures prefer subscriptions.

System requirements

| Topic | Practical guidance | | --- | --- | | Windows Server host | Deploy on supported Windows Server generations per Microsoft’s matrix for your cumulative update level—commonly 2016, 2019, or 2022 in surviving projects. | | SQL Server | Plan SQL Server 2016 SP2+, 2017, or 2019 (confirm exact build compatibility with your patch posture). Size for search, usage, and content growth, not day-one empty libraries. | | RAM | 16 GB minimum for modest labs; 24 GB or more for production-adjacent farms with search and multiple roles—your architect’s spreadsheet beats our table. | | Storage | Allow generous system volume headroom plus content and search indexes; attachment-heavy teams swing budgets faster than CPUs. | | Architecture | 64-bit throughout; mixed legacy corners invite awkward support calls. | | Networking | Stable DNS, time sync, TLS endpoints someone maintains, and realistic hybrid paths if you use them. | | CALs | SharePoint CALs are required for users/devices accessing features—treat “we only have ten people” sceptically if contractors authenticate too. |

Comparison

| Route | What it is | Choose when | | --- | --- | --- | | SharePoint Server 2019 (this page) | On-premises perpetual farm you operate | Regulation, latency, or custody demands keep authoritative sites local | | SharePoint Online (Microsoft 365) | Hosted service with continuous feature change | You accept cloud identity, SLAs, and subscription economics | | Hybrid | Mix of on-prem + cloud | You can fund identity/security honestly and need staged migration | | File shares only | SMB paths and prayer | You truly need no metadata, search, or audit affordances—rare at enterprise scale |

Install and activation

1. Complete checkout; archive order ID, invoice, and Lizensa fulfilment together for VAT and depreciation trails.
2. Read the entire activation and download message before redeeming on “lab hardware you will wipe tomorrow.”
3. Freeze Topology choices: single-server nimbleness vs high availability that doubles patience requirements.
4. Install prerequisite roles/features exactly as Microsoft documents for your CU level—shortcutting this step creates ghost errors in search later.
5. Provision SQL with sane collation and growth settings; renaming later is a hobby nobody wants.
6. Run SharePoint products configuration and create/attach the farm; capture passphrase storage like an adult.
7. Patch to your nominated cumulative update plan; test search crawl and backup restore on copies, not on the day auditors arrive.
8. Apply CAL coverage and access policies before opening wide to the whole company chat.

EU digital content rules still matter: starting download or activation can affect withdrawal timing, while conformity rights remain when the product is not as described. Lizensa resolves issues faster when you send verbatim errors, build numbers, and the numbered step that failed.

Does this include SharePoint CALs?

No—assume CALs are separate unless Lizensa’s fulfilment text explicitly states a bundled pack. Budget user or device CAL math early.

Is this the same as Microsoft 365 SharePoint?

No. Microsoft 365 delivers SharePoint Online as part of a subscription identity world. This SKU is a server product for on-premises (and commonly hybrid) estates.

Which Windows Server should I install on?

Match Microsoft’s supported matrix for your patch level—see Windows Server 2019 Standard (16 core) or Windows Server 2022 Standard (16 core) lines in parallel procurement.

Do I need SQL Server licences too?

Yes, for supported configurations—plan Microsoft SQL Server licensing with whoever owns database spend; do not “borrow” dev editions for production comfort.

Can I run this without Exchange?

Many farms do, but email-enabled workflows and classic calendar glue may still point to Exchange—evaluate Exchange Server 2019 Standard if mail lives beside sites.

Is hybrid search automatic?

No. Hybrid requires identity, connectivity, and administrator time. Treat marketing diagrams as aspirations until your logs agree.

How many servers do I really need?

Labs cheat with one; production usually wants separation of roles as soon as “slow Monday” hurts revenue—your risk owner decides, not a footnote.

What if activation or setup fails?

Contact Lizensa with order ID, full error text, and screenshots (when safe). The 365-day activation guarantee applies when you avoid parallel experimental installs.

Related products

• Microsoft Exchange Server 2019 Standard
• Microsoft Exchange Server 2019 Enterprise
• Skype for Business 2019
• Windows Server 2019 Standard (16 core)
• Windows Server 2022 Standard (16 core)
• Windows Server CALs category
• Microsoft software hub