✅ 1. System Requirements
- A Windows Server (2012 R2 or newer recommended)
- Administrator access
- A KMS Host Key (GVLK) from Microsoft (usually part of a Volume Licensing agreement)
🛠️ 2. Install the KMS Host Key
a) Install Volume Activation Tools (if not already installed)
- Open Server Manager
- Go to Manage → Add Roles and Features
- Click Next through to Features
- Check Volume Activation Services
- Complete the wizard and install
b) Run Volume Activation Tools
- After installation, go to Server Manager → Tools → Volume Activation Tools
- Choose:
- Key Management Service (KMS)
- The local computer
- Enter your KMS Host Key (from VLSC)
- Activate it online (or by phone if needed)
🔧 3. Configure the KMS Host
Once the key is validated:
- The server will create a SRV DNS record (
_vlmcs._tcp
) automatically (if DNS is configured correctly) - KMS clients will find it via DNS
To verify:
powersnslookup -type=SRV _vlmcs._tcp
You should see your KMS server listed.
🔥 4. Allow KMS Port Through Firewall
KMS uses TCP port 1688. Run:
powershellnetsh advfirewall firewall add rule name="KMS TCP 1688" protocol=TCP dir=in localport=1688 action=allow
💻 5. Activate Clients Using KMS
On client machines:
- Use a GVLK (Generic Volume License Key) from Microsoft
- Set KMS server and activate:
cmdslmgr /ipk <GVLK>
slmgr /skms <KMS_server_name_or_IP>
slmgr /ato
🔄 6. Verify KMS Server Status
On the KMS host:
cmdlmgr /dlv
You’ll see:
- KMS version
- Activation count
- Threshold (25 for clients, 5 for servers)
- Whether clients are connecting
📈 7. KMS Activation Thresholds
- Windows Clients need a minimum of 25 activations
- Windows Servers need 5
Until the threshold is reached, clients will not activate.