From 016d6f1370e8e41310637e5bd0250805a67972c5 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Tue, 2 Apr 2019 21:10:59 +0500 Subject: [PATCH 1/3] Updated the doc Under requirements, Windows 10 pro or enterprise version 1703 doesn't need to be activated before applying Win10E3 license. --- .../deployment/windows-10-enterprise-subscription-activation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-10-enterprise-subscription-activation.md b/windows/deployment/windows-10-enterprise-subscription-activation.md index 767a8c0724..a8baa55101 100644 --- a/windows/deployment/windows-10-enterprise-subscription-activation.md +++ b/windows/deployment/windows-10-enterprise-subscription-activation.md @@ -63,7 +63,7 @@ The following figure illustrates how deploying Windows 10 has evolved with each For Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA), you must have the following: -- Windows 10 (Pro or Enterprise) version 1703 or later installed and **activated** on the devices to be upgraded. +- Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded. - Azure Active Directory (Azure AD) available for identity management. - Devices must be Azure AD-joined or Active Directory joined with Azure AD Connect. Workgroup-joined devices are not supported. From f8092de5dde1cc3a26ce09262c9c75a1f81b8d2e Mon Sep 17 00:00:00 2001 From: Ken Withee Date: Tue, 2 Apr 2019 22:25:16 +0500 Subject: [PATCH 2/3] Update windows/deployment/windows-10-enterprise-subscription-activation.md Co-Authored-By: joinimran <47118050+joinimran@users.noreply.github.com> --- .../deployment/windows-10-enterprise-subscription-activation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-10-enterprise-subscription-activation.md b/windows/deployment/windows-10-enterprise-subscription-activation.md index a8baa55101..e0170f19f7 100644 --- a/windows/deployment/windows-10-enterprise-subscription-activation.md +++ b/windows/deployment/windows-10-enterprise-subscription-activation.md @@ -63,7 +63,7 @@ The following figure illustrates how deploying Windows 10 has evolved with each For Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA), you must have the following: -- Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded. +- Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded. - Azure Active Directory (Azure AD) available for identity management. - Devices must be Azure AD-joined or Active Directory joined with Azure AD Connect. Workgroup-joined devices are not supported. From e695aa27cc873e95147daa0312133543ed5a0c3c Mon Sep 17 00:00:00 2001 From: Ken Withee Date: Tue, 2 Apr 2019 22:27:34 +0500 Subject: [PATCH 3/3] Update windows/deployment/windows-10-enterprise-subscription-activation.md Co-Authored-By: joinimran <47118050+joinimran@users.noreply.github.com> --- .../deployment/windows-10-enterprise-subscription-activation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-10-enterprise-subscription-activation.md b/windows/deployment/windows-10-enterprise-subscription-activation.md index e0170f19f7..a8baa55101 100644 --- a/windows/deployment/windows-10-enterprise-subscription-activation.md +++ b/windows/deployment/windows-10-enterprise-subscription-activation.md @@ -63,7 +63,7 @@ The following figure illustrates how deploying Windows 10 has evolved with each For Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA), you must have the following: -- Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded. +- Windows 10 (Pro or Enterprise) version 1703 or later installed on the devices to be upgraded. - Azure Active Directory (Azure AD) available for identity management. - Devices must be Azure AD-joined or Active Directory joined with Azure AD Connect. Workgroup-joined devices are not supported.