From 1745de75336e0ecc27c59d86e1e56f2e5fc500a9 Mon Sep 17 00:00:00 2001 From: Kaushik Ainapure Date: Thu, 6 Jan 2022 20:14:46 +0530 Subject: [PATCH] Updates to include activation delay experience --- windows/deployment/deploy-enterprise-licenses.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/windows/deployment/deploy-enterprise-licenses.md b/windows/deployment/deploy-enterprise-licenses.md index 719e822d59..307d30d1f1 100644 --- a/windows/deployment/deploy-enterprise-licenses.md +++ b/windows/deployment/deploy-enterprise-licenses.md @@ -255,3 +255,10 @@ At a command prompt, type: **winver** A popup window will display the Windows 10 version number and detailed OS build information. If a device is running a version of Windows 10 Pro prior to version 1703 (for example, version 1511), it will not be upgraded to Windows 10 Enterprise when a user signs in, even if the user has been assigned a subscription in the CSP portal. + +### Delay in the activation of Enterprise License of Windows 10 + +This is by design. Windows 10 has a built-in cache to help with the volume of calls coming to determine the upgrades of Windows 10 devices. + +This cache stores three-day values, including responses that indicate that the device is not eligible for an upgrade. When a device makes the call to check for upgrade eligibility on behalf of the signed user with a qualifying license, it can take three days + the delay for the subscription purchase to go through OMS into the system that masters Windows10 licenses. +