Run a Windows Server 2022 Standard KMS host—digital delivery from Lizensa with EU SME guidance, invoices, and order-linked activation help.
최근 30일 최저가: €49.90 (6/7/2026)
다시 시도하거나 표준 체크아웃을 이용해 주세요.
라이선스 키 + OS 언어에 맞춘 활성화 가이드. PDF VAT 인보이스 첨부.
모든 키는 발송 전 퍼블리셔의 활성화 서버에서 확인됩니다.
EU 업무 시간 내에 이메일 또는 채팅 지원을 통해 1시간 이내에 해당 언어로 답변을 드립니다. 과정을 안내해 드리거나 키를 교체해 드립니다.
A Key Management Service (KMS) host is not glamourous infrastructure, but for SMEs and structured IT teams it is often the quiet backbone of Windows volume activation: clients and servers that are licensed for KMS reach out to an internal host instead of retail activation lines or ad-hoc Multiple Activation Key (MAK) burn-down. This page describes Windows Server 2022 Standard in the KMS host role as reflected in our catalogue—digital delivery from Lizensa, straightforward naming on your invoice, and activation guidance you can follow with your order reference at hand.
If you expected a simple MAK for a handful of servers, pause. A KMS host is operational software asset management: DNS records, firewall paths, renewal intervals, patching the host, securing the KMS key material, and understanding which Microsoft products are allowed to activate against KMS in your licensing programme. This SKU is not “cheap Windows Server for a test VM”; it is activation services infrastructure sitting beside—but distinct from—CALs, RDS rights, Azure spend, and Microsoft 365.
To avoid shopping the wrong activation story, open these comparisons in another tab: our Windows Server hub; the companion 24 Core MAK – 500 users listing if you need MAK-style online activations instead of a KMS service; Windows Server 2022 Standard 16 Core for the general Standard framing; Windows Server 2022 Datacenter 16 Core when virtualization rights point at Datacenter; and Windows Server 2022 User CAL 50-pack so you do not mistake server OS purchase for access licensing.
This listing is digital fulfilment oriented to deploying or licensing a server to perform KMS activation services for qualifying Microsoft volume clients in your environment, where your entitlement and Microsoft’s volume activation guidance say KMS is valid. You receive Lizensa package documentation—delivery email, product identification aligned to the storefront name, and support contactability—not a substitute for your organisation’s Microsoft agreement context, site topology, or engineering runbook.
Edition — Standard: Many KMS hosts run on Standard when the workload is a dedicated, modestly resourced VM or physical box. If your design stacks numerous roles on the same machine, revisit resource sizing and separation of duties. Datacenter is a separate economics conversation; see Windows Server 2022 Datacenter 16 Core if your virtualisation plan suggests it.
Role — KMS host: Expect to install the Volume Activation Services role, configure your KMS host key according to official procedures, open required ports between clients and the host, and maintain DNS discovery records (typically _vlmcs._tcp SRV under the right zone) unless you intentionally deploy manual KMS target settings. Monitoring should include activation counts, event log health, patching, and certificate/time drift—activation failures often trace to basics.
Not bundled implicitly: CAL coverage for users or devices accessing general Windows Server services on other machines, RDS CALs for session scenarios, Azure usage, Microsoft 365 workloads on endpoints, backup licensing, or third-party tools. If the KMS host also serves file shares to staff, you still reason through CAL need—see again Windows Server 2022 User CAL 50-pack as a catalogue illustration.
Compared to MAK: The 24 Core MAK listing fits organisations that want counted online activations without maintaining KMS. KMS fits recurring activation renewal patterns common to volume Windows clients when infrastructure exists to host it responsibly.
Lizensa customer layer: We present the product name plainly, minimise jargon where possible, and keep your order trail usable for finance and IT alike—because the KMS story is half technology, half governance.
Before you build: sketch a one-page activation map: which VLANs reach the host, which service account installs the role, who rotates credentials, and how help desk staff will respond when a laptop shows “not genuine” after travel. That sheet saves more hours than tuning CPU counts in isolation.
Windows Server 2022 strengthens the platform used for infrastructure roles like this: kernel hardening paths, improved SMB stack defaults, TLS improvements, and an ecosystem of agents and backup tools that increasingly assume a modern baseline. For KMS specifically, “what’s new” is often whether your wider estate still coexists cleanly with Server 2022: management agents, antivirus, monitoring probes, and virtualisation hosts should all tolerate the new OS build.
Older environments sometimes keep KMS on a Windows Server 2019 host while clients move ahead; that can be valid if activation compatibility for your SKUs and Microsoft guidance still align. If you are refreshing everything to 2022 for consistency, migrate KMS deliberately—document the cut-over, time synchronisation source, DNS changes, and rollback.
If you only needed Server 2022 features for application workloads, not for KMS, do not conflate them. The newest server does not automatically equal the right activation design; sometimes MAK or agreement-based activation remains preferable for tiny estates.
| Item | Practical guidance | | --- | --- | | Base OS | Windows Server 2022 Standard installed and fully patched | | Compute | Right-size vCPU/RAM for low steady-state but spike-aware installs; avoid starving a domain-connected KMS VM | | Disk | Small OS footprint yet monitor logs; activation events can burst during mass client updates | | Network | Reliable LAN/WLAN paths from endpoints; fixed IP often used; firewall allowlists for RPC endpoints KMS requires | | Time | Accurate time and DNS—activation tooling faults when skew or broken SRV records appear | | Licensing fit | Confirm Standard edition and core licensing cover the physical host or virtual machine actually running the role |
When in doubt about edition versus older 2019 certification, review Windows Server 2019 Standard 16 Core alongside this page.
| Need | KMS host route | Alternatives | | --- | --- | --- | | Small static server count | Possibly unnecessary; MAK may be simpler operationally | 24 Core MAK listing | | Frequent workstation reprovisioning | KMS can reduce per-machine MAK accounting pain | Requires stable host operations | | No IT function to maintain DNS/firewall | High operational risk | Contracted MSP work or rethink activation model | | Dense virtualisation on host | Datacenter economics may dominate edition choice | Datacenter 16 Core | | Users accessing services | CAL planning still applies | User CAL example |
Price alone cannot pick between KMS and MAK. Pick based on who maintains the service, how Windows clients renew activation, and what your volume programme allows.
slmgr target settings through managed tooling.EU buyers receive GDPR-aligned processing of personal order data through Lizensa’s storefront practices; statutory digital content rights remain governed by applicable law and any consent to immediate performance—your checkout disclosures apply.
No. A KMS host must be properly installed and activated within a qualifying volume licensing context. Consumer retail keys and random marketplace offers are not interchangeable.
Yes. KMS solves activation mechanics. CALs address usage rights for accessing Windows Server services—different layer.
Smaller estates with rare builds often favour MAK simplicity—see the 24 Core MAK listing. Choose KMS when your renewal and scale justify running the infrastructure.
You can, but isolation reduces blast radius. Cost savings from consolidation must balance security and patching urgency for a activation choke-point server.
Many KMS hosts run on Standard if their virtualisation and density fit Standard rules. If you are on the fence about Datacenter economics, read Windows Server 2022 Datacenter 16 Core before deciding.
Check DNS SRV, firewall paths, KMS host events, system clock, edition of client, and SKU eligibility for KMS. Capture data before opening a support case.
No. Microsoft 365 is a separate subscription universe. This page is about on-premises Windows Server 2022 Standard in a KMS host scenario.
Lizensa sells the digital product bundle described in the catalogue; your reseller, enterprise agreement, or open-value programme terms remain your compliance checkpoint with Microsoft.
Why buy here. Lizensa is built for buyers who want software licensing explained in plain language, with a clean order path and documentation you can hand to finance or IT audit.
Privacy and paperwork. We process order and account data under applicable EU privacy rules, keep retention proportionate, and aim to minimise surprises in your inbox.
After purchase. Keep your order ID when you contact support; we tie activation and entitlement questions to that reference without asking you to share keys in public channels.
Stripe / SEPA / iDEAL / Bancontact — 모든 주요 EU 결제 수단을 지원합니다.
실시간으로 퍼블리셔의 활성화 서버에서 라이선스를 확인합니다.
라이선스 + 활성화 가이드가 60초 이내에 도착합니다. 평균 43초 소요.
원하는 언어의 가이드를 따라 2분 이내에 완료하세요.
이 제품의 첫 번째 리뷰를 작성해 주세요
후기를 작성하려면 로그인하세요Loyalty points are added to your account and can be redeemed for discounts.
추천마다 12% 수수료를 받으세요. 파트너 프로그램에 참여하세요.