---
type: entity
title: KMS (Key Management Server)
created: 2026-07-01
updated: 2026-07-01
tags: [licensing, infrastructure, microsoft, activation]
related: [kms-activation, microsoft-windows-10-11, intranet-connectivity]
sources: ["output/rz_uni_greifswald_de_support_faq_software.md", "output/rz_uni_greifswald_de_support_faq_software_betriebssystem_windows_10_aktivierung.md"]
---
# Key Management Server (KMS)

The **Key Management Server (KMS)** is a Microsoft volume activation service hosted by the Universitätsrechenzentrum (URZ). It is the internal university system used for the automatic activation of volume-licensed software, specifically Microsoft Windows and Microsoft Office. It allows devices with university-procured licenses to activate automatically without requiring individual product keys for every installation.

## Functionality and Connectivity
The KMS allows devices to activate their licenses provided the device can communicate with the server `kms.uni-greifswald.de`.

### Connectivity Requirements
To reach the KMS, a device must have [[intranet-connectivity]] via one of the following:
1. A wired network connection (with [[device-registration]]).
2. [[eduroam]] WLAN.
3. [[openvpn]] (for off-campus access).

## Activation Processes

### Microsoft Office
Office activations must be renewed at least every 180 days. This renewal occurs automatically when an Office application is started while connected to the intranet.

### Microsoft Windows 10/11
For Windows 10 and 11, activation is performed manually via the Windows Software Licensing Management Tool (`slmgr.vbs`).

**Prerequisites:**
- The device must have [[intranet-connectivity]].
- The command prompt must be run with **Administrator privileges**.

**Commands:**
To point the operating system to the university's activation server and trigger the process, use the following commands:
1. **Configure KMS Host:**
   `cscript "C:\Windows\system32\slmgr.vbs" -skms kms.uni-greifswald.de`
2. **Activate:**
   `cscript "C:\Windows\system32\slmgr.vbs" -ato`

## Troubleshooting
If the `-ato` command fails, the URZ requires the following information submitted via the [[groupware]] ticket system for diagnosis:
- Connection method (Wired, eduroam, or VPN).
- IP address or MAC address.
- Computer name.
- Exact error code from the command prompt.