kms.viktorbarzin.me

Quick start — fully automatic on a new machine

On the home / lab network, a freshly-installed Volume License edition will activate itself once Windows can find the SRV record. The bootstrap script below sets the Primary DNS Suffix, optionally installs Office + Project (LTSC 2024 VL), triggers slmgr /ato + ospp.vbs /act, and prompts for a single reboot.

powershell -ExecutionPolicy Bypass -File "\\nas.viktorbarzin.lan\Emo shared\kms-bootstrap.ps1"

Off-LAN? Skip auto-discovery and pin the host explicitly:

slmgr /skms kms.viktorbarzin.me
slmgr /ato

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /sethst:kms.viktorbarzin.me
cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /act

Windows desktop

Per-edition GVLKs. Volume License only — Home and retail SKUs cannot KMS-activate. Click any key to copy.

Windows 11 / 10

Windows LTSC

Legacy desktop

:: open cmd.exe as Administrator
slmgr /upk                            :: remove existing key
slmgr /ipk <PASTE-GVLK-HERE>          :: install GVLK
slmgr /skms kms.viktorbarzin.me       :: optional: skip auto-discovery
slmgr /ato                            :: activate
slmgr /dlv                            :: verify (look for "LICENSED")

Windows Server

Server SKUs need only 5 unique clients to satisfy the KMS activation count threshold (vs. 25 for desktop).

Windows Server 2025

Windows Server 2022

Windows Server 2019

Windows Server 2016

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2

Windows Server 2008

Office · Project · Visio

All listed editions are Volume License. Install via the Office Deployment Tool with the matching Configuration.xml below (use Channel shown in each row), or manually swap a retail key with ospp.vbs /unpkey:<LAST5> + /inpkey:<GVLK> and /act.

Office LTSC 2024

Office LTSC 2021

Office 2019

Office 2016

<Configuration>
  <Add OfficeClientEdition="64" Channel="PerpetualVL2024">
    <Product ID="ProPlus2024Volume"   PIDKEY="XJ2XN-FW8RK-P4HMP-DKDBV-GCVGB">
      <Language ID="en-us"/>
    </Product>
    <Product ID="ProjectPro2024Volume" PIDKEY="FQQ23-N4YCY-73HQ3-FM9WC-76HF4">
      <Language ID="en-us"/>
    </Product>
  </Add>
  <Updates Enabled="TRUE" Channel="PerpetualVL2024"/>
  <Display Level="None" AcceptEULA="TRUE"/>
  <Property Name="AUTOACTIVATE" Value="1"/>
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
</Configuration>

cd "C:\Program Files\Microsoft Office\Office16"
cscript ospp.vbs /sethst:kms.viktorbarzin.me
cscript ospp.vbs /inpkey:<PASTE-GVLK>
cscript ospp.vbs /act
cscript ospp.vbs /dstatus               :: verify --LICENSED--

Downloads

Office Deployment Tool

Single binary that installs every Office VL edition listed above, driven by a Configuration.xml.

Single setup.exe covers Office 2016, 2019, LTSC 2021, LTSC 2024. Configuration.xml controls product + channel.

Windows ISOs

• Windows 11 (consumer media tool) ↗
• Windows 11 Enterprise (eval ISO) ↗
• Windows 11 IoT Enterprise LTSC 2024 (eval) ↗
• Windows 10 (consumer media tool) ↗
• Windows 10 Enterprise (eval) ↗
• Windows 10 Enterprise LTSC 2021 (eval) ↗
• Windows Server 2025 (eval ISO) ↗
• Windows Server 2022 (eval ISO) ↗
• Windows Server 2019 (eval ISO) ↗
• Windows Server 2016 (eval ISO) ↗
• Volume Licensing Service Center (VLSC) ↗ — Source for VL media not on the Eval Center (e.g. legacy LTSB, retail-channel signed VL builds).

Bootstrap script

One-shot PowerShell that wires DNS suffix, Office install, and activation:

FAQ & gotchas