Windows 10 IoT Enterprise LTSC 2021 requires a valid product key from the appropriate licensing channel; it cannot be activated using numbers printed on a generic hardware tag or device label that is not explicitly a Windows product key.
For Windows IoT Enterprise LTSC, activation is done using one of these models:
- Volume Licensing (Enterprise/IT scenarios)
- Requires either a Multiple Activation Key (MAK) or activation via Key Management Service (KMS).
- The KMS client setup key for Windows IoT Enterprise LTSC 2021 is:
KBN8V-HFGQ4-MGXVD-347P6-PDQGT This is a generic KMS client key only; it does not itself grant a license. It is used when activating against an existing KMS host in the organization.
- Licensing assets (media and MAK/KMS keys) must be obtained from the organization’s Volume License Administrator via programs such as MPSA, MCA, or Select Plus. If the supplier did not provide a key, the Volume License Administrator or Microsoft Account Manager must be contacted to obtain the correct key.
- OEM / Device-maker scenarios (PKEA, ePKEA, OA 3.0)
- OEMs building specialized devices must enable activation before the device leaves the factory using one of:
- PKEA (unique 5×5 key per device),
- ePKEA (embedded key with a fixed activation count), or
- OA 3.0 (key stored in firmware, discovered automatically by Windows).
- If the device was originally shipped by an OEM with Windows IoT Enterprise preinstalled, the OEM is responsible for providing or embedding the activation key. If the reloaded image no longer activates automatically, the OEM or Windows IoT Distributor must be contacted to obtain the correct key or recovery media.
If no product key was provided and there is no access to a Volume License key, KMS infrastructure, or OEM activation key, activation cannot be completed. In that case, the next step is to contact:
- The Volume License Administrator or Microsoft Account Manager if the device is licensed via Volume Licensing, or
- The Windows IoT Distributor/OEM that supplied the device if it is an OEM IoT device.
The numbers on the server tag alone are not sufficient unless they are explicitly documented as a Windows product key or are tied to an OEM activation mechanism (such as OA 3.0) that the reinstalled image is configured to use.
References: